** Reply to message from vbox-users <[email protected]> on Sun, 13
Jan 2013 14:50:35 +0000

> > From: Cliff Scott [mailto:[email protected]]
> > 
> > Maybe I'm missing something, but with a Mac host at least, using more than
> > 1
> > cpu for Win XP or OS/2 clients results in the USB access not working. I 
> > would
> > love to use both CPUs that I have, but need the USB access or can use only 
> > 1.
> 
> I never heard of that before.  Why would that be?
> 
> Can you confirm if it's still true?
> 
> Are you running a current version of VirtualBox and Guest Additions?

I'm running 4.2.6 with the 4.2.6 Guest Additions and Extension pack. I only
figured it out by accident. First on OS/2 I had USB working and then enabled
the 2nd cpu and the USB access died. Turned off the 2nd cpu and it came back.
A while later I loaded WinXP and couldn't get the USB to work. Tried all the
usual things that work in a stand alone system to no avail. Finally I looked
on the VBox forum for messages relating to that and found one that mentioned
that the multiple CPU usage was a common problem. Turned off the 2nd cpu and
the USB worked. I think that was on version 4.2.4. Just tried it on 4.2.6 and
it still has the same problem. WinXP comes up with a message that the USB
device is "not recognized". I had the same issue with trying to attach a USB
printer to WinXP. What ever is the issue it is still there.

Cliff

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
Unsubscribe:  
mailto:[email protected]?subject=unsubscribe

Reply via email to