USB Devices in Windows

Discussion in 'Parallels Desktop for Mac' started by irieblue, May 25, 2006.

  1. irieblue

    irieblue Bit poster

    Messages:
    2
    I am trying to use a USB device (which does not have a MacOS X driver), for which I have installed the Driver in a windoxs XP VM. The issue I am running into is that Parallels desktop always claims that another Application is using the hardware and to wait a few minutes.

    Does anyone know of a workaround? In my particular situation, inside MacOS X, the Apple USB Composite driver is loading against the device (because no other driver loaded), however my understanding is that the composite driver will bow out if another driver attempts to open the usb hardware.

    Can someone from parallels clarify why Parallels desktop thinks the USB hardware is in use by another Application? Is this on the Mac Side? On the windows side there is definitely not another driver that can drive this particular piece of USB hardware.

    Thanks...

    irieblue
     
  2. irieblue

    irieblue Bit poster

    Messages:
    2
    Anyone from Parallels care to comment on why Parallels thinks another Application is using the hardware? Is it because the composite driver is loaded in MacOS X?
     
  3. Jmdor

    Jmdor Member

    Messages:
    26
    I know that my Hasp does the same thing, and parallels has fixed it for the next release. Maybe you're in the same boat.
     
  4. ajay

    ajay Hunter

    Messages:
    153
    USB keychain memory backup

    While I haven't tried it yet, I backup my Quicken data on a USB memory stick on my Windows machine. Will this work with XP vm under a Mac?

    Update: Answered my own question by trying it. I backed up my Quicken (Windows version) data files on a USB memory stick and plugged it into my Mac running WinXP vm. It recognized the memory device and I was able to dump the data easily and without problem.

    Thanks Parallels Team.:)
     
    Last edited: May 28, 2006
  5. netdog

    netdog Hunter

    Messages:
    117
    This will be fixed in RC2. If your device worked with B6, it should work with RC2.
     

Share This Page