Billybob,
There are two more potential causes for the "JAVA Platform binary has stopped working" message when using a PR3:
One is that if you plug it into a different USB port, Windows may think it's a different device and assign a different Com port number. The other is if your USB port goes into a low-power "sleep" state.
Java handles the lack of communication with the PR3 poorly in either of those cases, and the result is that not-very-helpful "Stopped Working" message..
As for Windows 10 and the PR3, they work just fine together. And depending on how current you are with your Windows updates, you may not even need to install the Digitrax "drivers". More into on that here: <>
HTH,
Steve
"Breezlys"
---In jmriusers@..., <jawhugrps@...> wrote :
Jack,
That's a frustrating experience!
Historically, the "JAVA Platform binary has quit working" message, when using a Digitrax PR3, is one of two things: PR3 firmware version or Windows PR3 drivers. Both are available from the Digitrax web site, in the "Downloads" section. For me, the PR3 firmware update solved my "binary stopped working" problems on a 64-bit Win7 computer.
You will want to use the "PR3 WIndows XP, Vista, 7, 8, and 10 Drivers". You can use DigiIPLII (available in the "SoundLoader2" package on the Digitrax web site "Downloads" page) to find out which version of firmware you have in your PR3. Use the DigiIPLII tool's "Find Devices" button to get the firmware version information. I think it is in the "S/W" column in the "Find Devices" table. Current PR3 firmware, as available on the Digitrax web site "downloads" page is "1.0".
An additional problem sometimes crops up - some USB cables shipped with the PR3 have been known to cause USB difficulties with some computers, and replacing them often solves USB problems.
I'll leave the Windows 10-specific investigations to those who have experience with it; I have thus far been able to not even touch a Win10 machine, so don't have any experience.
Depending on what JMRI version you are using, there may be a relationship to some new interface software that has been in very recent JMRI versions - ones where the so-called "PureJavaCommunications" library is used instead of the older "RXTX" library. What JMRI version are you using? Numbers are important here, as JMRI 4.6 can be significantly different from JMRI 4.7.6!
There are other possible causes, including "corrupted" JAVA installs, "corrupted" windows installs, etc. These are less-likely causes, and should be left for later investigations if problems persist after investigating the items above.
My bet would be PR3 firmware revision, but I could be wrong...
Regards,
Billybob
[Non-text portions of this message have been removed]