virtualbox.org

I have the same problem syncing my Palm T|E in an XP guest that others have had:

• - the Palm is enabled in the VB USB filter list
  - HotSync 4.1 is running and configured properly for USB sync in my XP guest (my guest is an image of standalone system, where HotSync works fine, so there should be no config problem)
  - when I start a HotSync from the T|E, the XP guest sees the Palm as a USB device but HotSync doesn't sync, and doesn't respond when you right-click on the system tray icon
  - when the T|E eventually gives up, HotSync on the XP guest responds normally again

The other posts have had Linux hosts, and the fix has apparently been to disable visor.ko. What would be equivalent on a Vista host?

I tried disabling the Palm device in Vista's DevMgr, but that didn't help (no surprise, maybe, since VB seems to trap USB device detection so that the Palm doesn't appear in the Vista DevMgr when VB is running...)

Any other ideas?

Thanks.

Basically the same setup here:

• Vista (SP1) host
• XP (Pro, SP2) guest
• palm T|X
• palm device enabled in the VirtualBox USB filter list
• HotSync running and configured for USB sync in XP guest
• on starting the HotSync from the palm device, the XP guest sees the Palm as a USB device but HotSync does not sync; but it reacts in some way as it does not respond to right clicks on the system tray icon
• when the palm device eventually gives up, the HotSync application on the XP guest responds normally again

Sorry, I do not have any new ideas, but maybe pushing this topic up again will help a little...

Any help appreciated!

Hi Sun/Virtualbox support people.... would like to add a follow-up reminder to this topic as there definitely are developers like me that rely heavily on VB for odd jobs like these (Vista host, XP guest, Hotsync for Palm in guest) and would love to see a resolution to this tiny concern.

I tried VB out once or twice and made the full switch on all my development boxes from VirtualPC to VB within the week... great product! I'm sure the concern above has a workaround though. Looking forward to your help on that.