Page 1 of 1
RM 1.64 gives error w/ older .rmdu file - fixed in RM 1.65
Posted: Sun Aug 20, 2006 3:35 pm
by clemon79
I was using an older version of RM (something in the 1.5's), and it was working fine. I upgraded to the new version, and if I run it standalone, it seems to be fine, but if I run it by opening a preexisting .rmdu file (specifically, the one I'm trying to use is
Philips_17PF8946-37_LCD.rmdu, then I get errors (in a window titled "Remote Load Error") as follows:
Code: Select all
java.io.FileNotFoundException: Images\URC-9910New.map (The system cannot find the path specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(Unknown Source)
at java.io.FileReader.<init>(Unknown Source)
at com.hifiremote.jp1.ImageMap.parse(ImageMap.java:19)
at com.hifiremote.jp1.Remote.load(Remote.java:223)
at com.hifiremote.jp1.RemoteManager.findRemoteByName(RemoteManager.java:162)
at com.hifiremote.jp1.DeviceUpgrade.load(DeviceUpgrade.java:1021)
at com.hifiremote.jp1.DeviceUpgrade.load(DeviceUpgrade.java:998)
at com.hifiremote.jp1.DeviceUpgrade.load(DeviceUpgrade.java:965)
at com.hifiremote.jp1.DeviceUpgrade.load(DeviceUpgrade.java:958)
at com.hifiremote.jp1.KeyMapMaster.loadUpgrade(KeyMapMaster.java:805)
at com.hifiremote.jp1.RemoteMaster.createAndShowGUI(RemoteMaster.java:721)
at com.hifiremote.jp1.RemoteMaster.access$300(RemoteMaster.java:12)
at com.hifiremote.jp1.RemoteMaster$2.run(RemoteMaster.java:746)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
I see that twice, then the upgrade DOES open, but I can't see the image of the remote in the Layout tab. (I DO have the newest Images set unzipped and in an Images subdirectory below my RM directory. And in fact that file mentioned in the first line is right there.)
Again, if I just run RM alone, this all works. If I run RM alone and then do a File > Open of the upgrade, it works. If I try to double-click the upgrade directly, it pukes as above. If I make changes to the upgrade, resave it, and then double-click it, it still pukes.
Any ideas?
Posted: Sun Aug 20, 2006 7:29 pm
by gfb107
DId you rerun setup.bat after installing the new RM?
Posted: Sun Aug 20, 2006 7:36 pm
by clemon79
gfb107 wrote:DId you rerun setup.bat after installing the new RM?
I did, yeah. And I looked at the setup.reg it produced, and near as I can tell it all looks good.
Again, if I open RM by itself, and then open the .rmdu file, it's fine. It's only if I double-click the .rmdu file itself to have it launch and open within RM.
Can you provide a list of the registry changes it makes, maybe? (Or is that that .reg file?) If I felt comfortable doing it (meaning, if I had positive confirmation that those were indeed the changes you make) I'd chop those out of the Registry and try it again. Was there a change in what you do to the Registry between versions 1.5whatever and this one? I'm wondering if the inability to uninstall those changes between versions might be part of the issue.
The thing that is kicking at me is the first line of that error. It's saying that file can't be found, and it is indeed there. When I open it manually there is no problem and RM finds the file just fine.
AHA! Okay, dig this:
If I try to open the .rmdu file via double-click, and it's in the SAME FOLDER AS THE RM INSTALL (and therefore the remotemaster.jar executable), no problem. It's happening when I try to open the file from a DIFFERENT folder. (In this case, My Documents\My Received Files)
Posted: Sun Aug 20, 2006 8:08 pm
by ElizabethD
I have \Images in the same folder with .jar and the whole 1.64 setup.
I did run setup and it was all working fine once I moved the Images to the RM directory.
When I double click any .rmdu file I also do NOT get the image and the same exception.
But when .rmdu file is opened using Open, all is well.
WindowsXP home.
Edited: My .rmdu and KM files also are NOT in the RM164 directory, i.e. I don't use the RM's default location. So that's it, eh?
Posted: Sun Aug 20, 2006 8:15 pm
by clemon79
ElizabethD wrote:
When I double click any .rmdu file I also do NOT get the image and the same exception.
But when .rmdu file is opened using Open, all is well.
WindowsXP home.
Edited: My .rmdu and KM files also are NOT in the RM164 directory, i.e. I don't use the RM's default location. So that's it, eh?
Yeah, you're having the exact same problem I am. The thing is, in 1.5whatever, this was fine.
So Greg, knowing this, are you able to repro the issue?
Posted: Sun Aug 20, 2006 8:57 pm
by ElizabethD
Yesterday I set me few favorite remotes in RM164. Today, when I double clicked the .rmdu file, the exception is there for every one of those remotes, plus the first one that always comes up, Anthem.
Log:
https://www.hifi-remote.com/forums/dload ... le_id=3505
clemon79 - Just a suggestion - if you can, I'd change the title, since RM isn't crashing. It's just the images problem.
Posted: Mon Aug 21, 2006 9:18 am
by gfb107
There is a bug, but the thread title is indeed misleading. Look for a fix today or tomorrow.
Posted: Mon Aug 21, 2006 9:34 am
by clemon79
gfb107 wrote:There is a bug, but the thread title is indeed misleading.
Agreed. Sorry about that. I should have just said "throws error" instead of "crashes".
Look for a fix today or tomorrow.
Excellent, I'll be keeping an eye out. As of all things of this sort, I just wanted to be sure it wasn't a problem on my end. Thanks very much!
Posted: Thu Aug 24, 2006 8:38 pm
by gfb107
Posted: Thu Aug 24, 2006 8:43 pm
by clemon79
Seems to work like a champ, Greg. Thank you very very much!