Chris,

?

With the idea of a big jump between versions, the main caveat is that you have to deal with any interesting errors that come up. They likely will be simple but solving some might take a fair amount of work. Watching the system console is critical to this to know what’s happening. Also the ability to manually edit the panel xml file to make some of the corrections might be needed. Or use it as a base and rebuild.

?

How easy will depend on lots of things. Which command station? Which types of signals? Did it use how many of the different things? Are there things you would like to add?

?

-Ken Cameron, Member JMRI Dev Team

?

?

Chris,

?

The DCS200 is fine, lots are still in use. Just change the battery backup every year or three. As to what to keep or dump, make an inventory of everything, that will help. Depending on how much of what, the direction to go may change.

?

I designed a JMRI system for a user with a bunch of Team Digital boards. They work ok for their time. But if thinking of replacing, LCC has some interesting options.

?

What you need off that old computer is really one directory if everything was done normal back then. That’s the JMRI directory under the username home directory. I think XP used C:\Documens and Settings\loginid, so JMRI directory under that would be something you really want a copy of.

?

But if somethings were done a little differently, you would want the whole JMRI directory from the C:\Program Files\JMRI, that’s the whole install of the program. If they customized some icons etc.. they might be in that directory tree instead of the one in the home directory space.

?

With either of those directories, capturing the ‘session.log’ file from the last run will show all the paths used for different things.

?

-Ken Cameron, Member JMRI Dev Team

?

?