Ok, who's using my 'USB device' already?

[iCF-74 ToughMac]

Hi,

 

I'm having a problem with my USB Pharos 500 GPS being unusable because of the problem below:

 

 

Parallels Desktop has detected the new USB device USB-Serial Controller D.

Do you want this device to be automatically connected to the virtual machine VM XP Pro Corporate?

 

USB device you are trying to connect to the virtual machine is being used by another application. Close that application or unplug the device and plug it again. Then try to connect the device again.

 

 

I plug it in and I get the above messages. Something is already trying t read the USB? or that com port? and will not allow me access to it. ONCE and only once while I had JUST installed MS Streets and Trips did I reboot to have XP detect the GPS and it worked fine until I rebooted, and then I was continually plagued with the errors above. Before I rebooted though I was in GPS heaven .. running Mapsource, Streets and Trips AND Google Earth all on the same GPS via GPSGate, and all thru Parallels (build 5624)[XP Pro]

 

 

****Is there a simple way to detect WHAT is already using my GPS? IF I can determine what app is interfering I can shut it down and prevent the problem, no?

 

 

Thanks,

 

Joe.

[iCF-74 ToughMac]

I upgraded to Parallels 4.0.3522 (Nov. 8, 2008), and have a slightly different problem now -

 

I plug in the GPS and when asked who to hand the GPS over to I choose virtual system (XP Pro). Perfect .. almost. The problem now is that the GPS shows up as an 'unknown device'. I have the updated Pharos 500 GPS drivers downloaded, but I cannot use them when I try and install them for the device.

 

I get the error :

 

'The wizard could not find a better match than the software you already have installed'

 

But when I look at the 'driver details', I get this message:

 

'No driver files are required or have been loaded for this device'

 

 

I'm still researching this problem .. seems a number of people have experienced this same thing. Obviously pointing the unknown device towards the correct drivers should fix the problem but in some cases such as this it doesn't.

 

Any ideas?

 

 

Thanks,

 

 

Joe