开云体育

Bob, I'm launching ok, but opening an entry in the roster takes a very long time or never happens for some entries (>5 minutes). I don't have a decoderindex.xml file. -Ken Cameron, Member JMRI Dev

Bob, I will try what you requested when I get home this evening. Thanks, Tom Wilson

Could one or two people who are seeing this problem try something for me, please? *) Go to your profile directory *) Check whether there’s a “decoderIndex.xml” file there. I’d like to know

I think we’ve tracked this down. A workaround might be possible. More to follow. Bob -- Bob Jacobsen jacobsen@... +1-510-708-5988 AIM, Skype JacobsenRG

Just updated on my test system to the latest 4.9.2 and the issues with the 3 way points in the control panel appears to have been sorted. I removed the turn off validation script from the startup and

Bob, Cliff and Dave ... Thank you for the solution. I was able to make the change successfully.

I'm seeing similar from HEAD about trying to open roster entries. I've not tried with an install version of 4.8.2 yet. At least this happening on Win10. -Ken Cameron, Member JMRI Dev Team www.jmri.org

Given my problems with 4.8 I'm going back to 4.6 It may work for him but not for me [Non-text portions of this message have been removed]

Hi Bob I have the same error upgrading from 4.9.1 to 4.9.2 (running under Windows10 pro): JMRI lauches OK but very slowly, then when trying to add a new lok or trying to open an existing roster entry,

Terry, The factory reset works in 4.8. This was confirmed for me by Gerry Hopkins. You will need to fix your system if it does not work for you. Peter

Sorry for the trouble. I’d be very interested in seeing those log files. Bob -- Bob Jacobsen jacobsen@... +1-510-708-5988 AIM, Skype JacobsenRG

Does that carry over into Engine Driver? The club has a PC with the sole purpose of providing Wi-throttle service. We almost exclusively now run using smart phone throttles. Thomas DeSoto, TX

Since the Factory Reset issue for wow decoders was not fixed in 4.8 maybe i should go back to an earlier version Usually if i wait for a production version i don't have these type problems Also in the

Terry, On some systems when upgrading past 4.7.* (so that means 4.8) it is found better to run the uninstall and insure the \Program Files (x86)\JMRI folder is gone. That insures none of the

It was always set on com 1 and still is

OK, then it looks like my supposition was correct. I'll have to leave it to someone with more intimate knowledge of converting between the two interface methods to advise you, but before they do, it

Dave I absolutely accept your comments. As many accessory decoders do not require any JMRI programming, what I was after was a "dumping ground" for Accessory Decoders generally, in order to populate

4.6 Terry Visit My Web site@ http://conewriversubdivision.yolasite.com/

You haven't answered my question. You have already been told you are wasting peoples time by not answering a direct question. So just what was the previous version? A direct answer would be real

My earlier versions go all the way back to 2.6 years ago I've used the same preferences the whole time because the hardware has remained the same I mostly use production releases to avoid bugs