JP1 Remotes

Posted: **Tue Sep 07, 2010 9:56 pm**

Capn Trips wrote:I know this is not a RM problem, but a Win 7 issue, but can anybody help me solve it? I cannot find a way to simply "delete" a file association. I can only CHANGE it to a different executable program, and the RM and RMIR shortcuts are not available options!

OKay, if you want to manually delete them, then go into "regedit" and delete the following keys.

HKEY_CLASSES_ROOT\.rmdu
HKEY_CLASSES_ROOT\.rmir
HKEY_CLASSES_ROOT\RemoteMaster 1.98.rmdu
HKEY_CLASSES_ROOT\RemoteMaster 1.98.rmir

EDIT: I just realized that you'll probably have the following instead:

HKEY_CLASSES_ROOT\RMDeviceUpgrade
HKEY_CLASSES_ROOT\RMRemoteConfig

I created the following registry file that you can merge with your registry to recreate the associations. It is also uploaded here (http://www.hifi-remote.com/forums/dload ... le_id=8920).

Code: Select all

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\RMDeviceUpgrade\Shell\Open\Command]
@=""C:\\Program Files (x86)\\Java\\jre6\\bin\\javaw.exe" -jar "C:\\Program Files (x86)\\RM\\RemoteMaster.jar" -h "C:\\Program Files (x86)\\RM" -rm "%1""

[HKEY_CLASSES_ROOT\RMDeviceConfig\Shell\Open\Command]
@=""C:\\Program Files (x86)\\Java\\jre6\\bin\\javaw.exe" -jar "C:\\Program Files (x86)\\RM\\RemoteMaster.jar" -h "C:\\Program Files (x86)\\RM" "%1""

[HKEY_CLASSES_ROOT\.rmir]
@="RMDeviceConfig"

[HKEY_CLASSES_ROOT\.rmdu]
@="RMDeviceUpgrade"

It assumes that following exists:

"C:\Program Files (x86)\Java\jre6\bin\javaw.exe"
"C:\Program Files (x86)\RM\RemoteMaster.jar"
"C:\Program Files (x86)\RM"

If you want to edit to your paths, then make sure the double and single slashes exists appropriately.

The results:

Uploaded with ImageShack.us

BTW, Greg, when I deleted the associations and reran the newest setup.vbs the file associations were not created.

Posted: **Wed Sep 08, 2010 6:28 am**

Thanks eferz for pointing me in the right direction. I have always been terrified of messing with regedit, but finally did so. After doing what you suggested, I still had the same problem, so I went back into regedit and did an edit>find for rmdu (and subsequently rmir) and found the same keys in multiple areas, including HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE, etc.

I deleted them all (unless it happened to match the desired values from this thread) and now it works.

I have NOT run setup.vbs again, because I'm happy that I finally got the associations working correctly, but it obviously failed to correctly add/modify the necessary Registry Keys to get it done.

Posted: **Wed Sep 08, 2010 9:13 am**

eferz wrote:BTW, Greg, when I deleted the associations and reran the newest setup.vbs the file associations were not created.

That's what I'd expect based on what Capn has reported. Unfortunately I haven't a clue what's going wrong or how to fix it.

It looks to me like the code in Setup.vbs for creating the file associations does the same things you did in that registry file.

Posted: **Wed Sep 08, 2010 10:13 am**

gfb107 wrote:
eferz wrote:BTW, Greg, when I deleted the associations and reran the newest setup.vbs the file associations were not created.
That's what I'd expect based on what Capn has reported. Unfortunately I haven't a clue what's going wrong or how to fix it.

It looks to me like the code in Setup.vbs for creating the file associations does the same things you did in that registry file.

I hate Windows from Vista on. That's the reason I gave up programming. Are you aware that there are two versions of the registry? Microsoft in their infinite wisdom has decided to hide stuff from the user. (ahem). There is an Adminstator level that is used during installation, and then a hidden data store registry that happens when an application modifies the registry. My guess is that somehow you are being bitten by that feature.

Posted: **Wed Sep 08, 2010 1:41 pm**

I think it may be something unique to Win7 64. I used the same vbs script on Win7 32 and had zero problems. I also made sure I ran it as admin. It may also be possible some third party program (anti-virus, etc.) is blocking writes to the registry from vb scripts.

Posted: **Wed Sep 08, 2010 8:10 pm**

I don't know if this will make a difference, but here's a version of Setup.vbs that creates the file associations only for the current user (in HKEY_CURRENT_USER\Software\Classes) instead of all users (in HKEY_CLASSES_ROOT)

The created associations work in XP (but then again so did the old ones), but they aren't visible using the "assoc" and "ftype" commands.

You probably have to go through and clean out the existing registries in order to know whether the change helps.

If that doesn't work, I guess I'll change my script to generate a .reg file with the correct path information, which can then be merged into the registry.

Posted: **Mon Sep 13, 2010 11:37 am**

Has anybody tried out the updated Setup.vbs? I'd really love to put this issue to bed.

Posted: **Mon Sep 13, 2010 2:41 pm**

I'm not sure that I'm inclined to do so. We have demonstrated that vbs scripts (on Win 7 64) apparently don't overwrite existing entries, so for me to just run the script will demonstrate nothing, since I currently have the file associations working correctly, so i will not know whether the script overwrote them correctly, or just left them as is.

And it may be selfish, but I'm not particularly enthused to go into my registry and delete every rmdu and rmir association entry in order to test the script and then have to go back and re-create them if the script doesn't work.

Posted: **Mon Sep 13, 2010 2:54 pm**

The new script puts the entries in a different place, so although you won't know for sure that the new entries work without deleting the current ones, you will be able to tell if the new entries were created.

I assume you also have the .reg file that created your currently working associations, so that makes putting them back a little easier.

Of course I understand not wanting to break a working system. It is entirely up to you.

Posted: **Mon Sep 13, 2010 9:23 pm**

Going forward, you should probably include an uninstall script, that way these registry entries aren't lurking behind between versions. It doesn't help much for people who had installed prior, but it could prevent future issues. Especially for those who decide to move the folder locations.

Posted: **Tue Sep 14, 2010 8:08 am**

Well I ran the script and after checking the registry, the correct entries appear in several additional locations beyond where I had them, and the associations still work correctly, so I have to assume that the script is good. Note that I did NOT delete the extant entries, but it's clear that the script added some that I had not, and IF it overwrote mine, it did so correctly.

Posted: **Tue Sep 14, 2010 8:44 am**

Thanks for testing. It is helpful to know that new entries were actually created.

Maybe that is enough to give someone else the courage to try wiping out working associations first, to determine whether the new entries actually produce working associations.

Posted: **Tue Sep 14, 2010 9:58 am**

OK, I searched the registry for rmir, rmdu, remotemaster and rmd and deleted all entries then reboot. I ran setupvbs in preview 6. when I double click a .ir file I'm asked what to open with, double clicking a .rmir file RMIR flashes on the screen and closes. The error file is here http://www.hifi-remote.com/forums/dload ... le_id=8944

I don't know if it matters but the error file says I'm using Win7 x86, I'm actually using x64.

Mike

Edit: here are the entries created by setup.vbs http://www.hifi-remote.com/forums/dload ... le_id=8945.
rmir3.reg and rmir6.reg didn't have corresponding rmdu entries
Double click on rmdu file works.

Edit2: On further examination the rmir file I was opening is corrupt. Double clicking on a different rmir file works as expected so I guess everything is good.

Edit 3: THANKS FOR ALL YOU DO I don't know if I could keep going with all the criticism, your hard work IS appreciated.

JP1 Remotes

RemoteMaster/RMIR v2.00-preview4 - setup.vbs