Peripherals Won't Work

Discussion in 'Installation and Configuration of Parallels Desktop' started by ebriggs2, Feb 19, 2009.

  1. ebriggs2

    ebriggs2 Bit poster

    Messages:
    8
    I recently upgraded to version 4.0. Now my peripherals will no longer work with my virtual machine running windows XP. If I plug in my printer or my GPS, I get the dialogue box, do you wish to connect this device to your mac or to your virtual machine. If I choose mac, everything works with my mac. But if I choose the virtual machine,m the dialogue box goes away as if it has gotten my message. But my virtual machine insists that the printer is off-line, and can't find my GPS. What's up? And how do I fix it?
     
  2. Srinivasulu.V

    Srinivasulu.V Hunter

    Messages:
    118
    Hello,
    Just have a check whether parallels tools are Installed or not?
     
  3. ebriggs2

    ebriggs2 Bit poster

    Messages:
    8
    Thanks problem solved

    I put in my installation CD and clicked reinstall parallels tools, now it's working. At least the printer, will try the GPS later after work.
    Thanks
     
  4. ebriggs2

    ebriggs2 Bit poster

    Messages:
    8
    GPS won't work with Parallels (still)

    GPS still won't work. It all gets curiouser and curiouser. Yesterday, after about the 50th attempt, my computer running Windows XP in the virtual machine would interface with my GPS. Then I reinstalled the Parallels Toolbox as instructed and am back to ground zero. I reinstalled the Garmin plug in and the USB driver for my Garmin device, and all is still a no go.
    But since it worked briefly yesterday, I just do not get it.
     
  5. ebriggs2

    ebriggs2 Bit poster

    Messages:
    8
    Software Bug

    After spending a lot of time trying to fix this problem, it turns out that there is known bug that the Parallels supports staff did not tell me about right away. http://kb.parallels.com/en/5998
    To me this a major hassle, and I am disappointed that the Parallels support staff (via email and this forum) did not come out right away and tell me about this bug. So I wasted hours when they could have directed me immediately to the correct support document. Not to mention, not even an apology for having known about this bug since at least January and not having fixed it.
     

Share This Page