RMIR remote not found - EEPROM adapter works on term program
Moderator: Moderators
-
The Robman
- Site Owner
- Posts: 21923
- Joined: Fri Aug 01, 2003 9:37 am
- Location: Chicago, IL
- Contact:
Congrats on getting it sorted, if your customized code works with your partially working adapter, it sounds like you're all set.
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
I've always blamed Java for the crash. I don't think there's anything you can do about it. That's why I've never reported it.mathdon wrote:I have never heard of that happening before, and certainly AutoDetect always works for me. The rmaster.err file from a crash might be interesting, if you can post one. Apart from that, I'm afraid I have no suggestions to contribute to this thread.mdavej wrote:FWIW, auto detect hasn't worked for me for many years and often crashes RMIR immediately. I always have to pick the comm port manually.
What Java build do you use? There are some issues with jre1.8.0 builds later than 202, though an immediate crash is not one I have come across. Builds later than 202 used with the default RMIR Windows look-and-feel can cause a problem that Rob described to me as "double vision". Shortly after "double vision" appears, RMIR does crash. The solution is to change the look-and-feel to something else - even Windows Classic is OK - or upgrade Java to Windows 11 or later. The current version is Java 15.mdavej wrote:I've always blamed Java for the crash. I don't think there's anything you can do about it. That's why I've never reported it.
Graham