开云体育

In one of those recurring moments of optimism, I've uploaded a new Windows installer. I hope that this one works well enough that I can spend some time updating the documentation, creating the

There is. The decoders and programming screens are defined by text files. The beginnings of some documentation are at: http://jmri.sourceforge.net/PaneProg/ConfigFile.html The documentation

Dave, If you wouldn't mind sending me the 32x32 and 48x48 images, I'll see if I can add them to the Windows icon file. Robin

128x128,48x48, and 32x32. -Dave

Dave, Great. What size are the Mac icons? I started with that artwork but needed to massage it alot to fit the Windows icon sizes. As noted in my previous post, Windows primarily uses 16x16 and

Robin, I've taken Jim Well's "logo.gif" artwork and created a set of Mac OS X icons. I'm sending those off to Bob later today (they were on the "wrong" computer). Maybe these will also be usable

PC Magazine has a nice, free, icon editor: IconEdit32. I used it to add a 48x48, 16 color icon to go with the existing 16x16 and 32x32 icons if anybody cares to have it. (48x48 icons are used for the

I have not yet been able to fix the LocoBuffer communications in the 0.9.3.5 test installer. The problem appears to be that the "RTS" lead, pin 4 in the 25 pin connector, is not being driven active.

can that the I think what the installer is trying to do is split out the shared executable and data components from the user preferences/settings so that multiple users on the same PC can have their

Bob, Interesting. In many years of using Windows this is the first program I can recall that ever created user folders in the Windows folder! Based on that perhaps something is amiss in the

I forgot; YES! Jon Miller AT&SF For me time has stopped in 1941 Digitrax DCC owner, Chief system NMRA Life member #2623 Member SFRH&MS

OK I removed the two files that the install should have removed, javax.comm.properties and win32com.dll. Nothing different is happening! Jon Miller AT&SF For me time has stopped in

OK, I figured out my roster problem. I have to import each engine, one by one, from the old files. That works ok, reloaded them all. Now back to the LocoBuffer. I loaded the old program

That's what I thought too, which is why the program originally kept them together. But when I went to a "real" installer, I discovered that there are Windows "recommendations" that it enforces, and

Oops - hadn't thought people would want to do that. In addition to copying the .xml file for the individual loco, there's an index that needs to be copied in the "roster.xml" file itself. Could you

Bob, It looks like the installer put JMRI/programmers and JMRI/roster folders in the Windows folder on my machine. This seems unusual to me. I checked and the roster info is being stored there. I

OK, started checking things out and this is what I found. As I said before I had a successful install. Today I turned the railroad on and found out the LocoBuffer can't talk to the DCS100

Bob: I've been quietly following your group as well as downloading and testing the software. I currently have the following: Computer: Dell Latitude C800 laptop, Win XP Pro, 256 RAM. DCC: Digitrax

Bob, I have some good news. After a lot of investigation, it appears that the original download actaully appeared to W2K as a MS-DOS program and I guess that was the cause of the problem. Whe I

Oops forgot to mention one clue: I think the packaets are being transmitted ok as I can see them with my AVR dev kit so I suspect there is a problem with receive. Is it possible that I am seeing