Error 1722 when using Receptor remote on Windows 7

[kashmir95]

Hey all,

Just got a new lappy. Its running Windows 7 and i am having trouble installing and using Receptor remote.

At the completion of the install the following msg comes up :

'Error 1722. There is a problem with this Windows Installer Package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.'

The remote app icons are on the desktop and all seems to be installed. When i run the remote software it detects the receptor, but when i hit connect i get the following :

Receptor remote control is not properly installed and cannot be found.

Then it wants to be pointed to the vncveiwer app, which i do - and it opens the receptor remote and i can mess with my receptor.

Why is it so?

[Kevin@MuseResearch]

Kashmir,

NOt 100% sure about the error that comes up when installing, but the "not installe properly" error is a known issue when running receptor remote on any 64 bit windows platform. To summarize, it basically gets confused about the existence of 'program files' and 'program files x86' on the windows 64 bit systems. The only work around right now is to do what you describe above: browse to tight vnc and click to open it.

[keykent]

Kashmir,

NOt 100% sure about the error that comes up when installing, but the "not installe properly" error is a known issue when running receptor remote on any 64 bit windows platform. To summarize, it basically gets confused about the existence of 'program files' and 'program files x86' on the windows 64 bit systems. The only work around right now is to do what you describe above: browse to tight vnc and click to open it.

I just ran into the same problem. This is very annoying. Do you have a fix on the way?

[wheresgrant]

Ditto... I'm experiencing the same thing except when it directs me to the vncveiwer app it cannot be found. I've uninstalled and reinstalled Muse Remote Control four seperate times. I've had this unit close to one month and still have not successfully connected with a PC yet.

[BlueKachina]

Is there an official fix for this yet?
Just got a Receptor 2, and am also running into this problem.

Please advise.

[Kevin@MuseResearch]

Hey all. Glad to say I have been testing a few proposed fixes for this issue. Look for them to accompany the next Receptor OS update thats released.

- Kevin

[BlueKachina]

Excellent News!
For the time being, I've saved session data from the VNC session to a file. I've also pinned the VNCViewer to my taskbar. That means that when I right-click on it, the session shows up as an option within the jumplist (Win 7). Makes for a good simple way to view your Receptor remotely.

[Jace-BeOS]

Hey all. Glad to say I have been testing a few proposed fixes for this issue. Look for them to accompany the next Receptor OS update thats released.

- Kevin

So owners of the first generation Receptor won't get this fix, since we won't get an OS update?

[Jace-BeOS]

Actually, we do get the Receptor Remote update, and what a fine update it is indeed. It still only ever shows "Scanning for Devices..." and then when i clicked on the drop-down box to see if maybe it was in the list anyway, i got a crash. Funny enough (not funny at all, in fact), the "Scanning for Devices..." drop-down box is currently superimposed at the top of my window z-order (because i left the crash box open to screen capture it).



Win Vista SP2. Receptor is on its own dedicated crossover cable directly to my machine. What gives, guys?

[Kevin@MuseResearch]

Win Vista SP2. Receptor is on its own dedicated crossover cable directly to my machine. What gives, guys?

I'd have to agree! What gives?!. In our test this remote passed fine when communicating with Rev C units. Theres a few possiblilities here.

1) Muse Remote is a new application, you may have to revisit the permissions for the firewall and other anti-virus applications before it can properly find Receptor.

2) You may also try going to preferences for the application. Go to compatibility and try running it in windows XP mode (I know a lot of the Receptor remotes in the past needed this treatment on windows systems).

3) check the version number of the software installed, and make sure it's the one most up to date. You may want to run the uninstall utility and make sure both the old and newer Receptor remotes are cleared out of there. Then run the new installer again to make sure its a clean install.

Hope that all helps! if not give us a shout again.

- Kevin