Closed baldrick1 closed 3 years ago
Is there any particular reason why you're using the older version 2.0.3 and not the latest 2.1.0?
Inertia, mostly. This has worked properly in the past. I'm suspicious of Microsoft's guerrilla updates, personally, but hoping you might have any ideas in the interim. I' will install v 2.1.0 and report back today.
The guerrilla update that got you was Oracle's, not Microsoft's. If you look through the closed issues, there are several having to do with the level of Java that broke the JNI layer to rxtx, which is the reason for the v2.1.0 release.
Thanks for the tip. I bow to you and your patience. Of course running the new version works perfectly on Win-10 now.
Sounds like things are back to normal now - closing.
I've gone though several issues that are now closed but none have had advice that worked. I am using an FTDI USB-Serial adapter Running Win-10 64 bit. ADTPro sees the com port (3 in this case) but also sees whatever I set the com port to in the properties manager.
Same issue in v2.0.1 and 2.0.3 Error log is attached.
Thanks in advance for your help. hs_err_pid10984.log