VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1591 - 1593 of 16363)

Ticket Resolution Summary Owner Reporter
#1920 obsolete Windows Mobile (RNDIS) USB device NOT WORKING BY DEFAULT Eric Mangold
Description

I have an issue with connecting my Windows Mobile device to the Guest OS (Windows XP SP2). Host is Ubuntu Linux 8.04. The device is an HTC Mogul (PPC-6800). The device appears as "HTC Generic RNDIS".

The actual "symptoms" inside the Guest vary... sometimes the device shows up in Hardware Manager (as "Windows-mobile network adapter"). Other times it doesn't show up at all, and other times it shows up with a red icon next to it indicating a problem status.

In no cases will ActiveSync ever recognize that you have a mobile device plugged in.

All other USB devices that I've tried work fine inside the Guest.

MY WORKAROUND:

To make it work I have to make one setting change on the PDA itself. Go to Settings -> Connections -> USB to PC. UNCHECK the box that says "Enable advanced network functionality". My device sometimes hangs trying to apply this setting.. if so use the soft reset hardware button, then try again.

This setting totally changes how the device behaves on the USB bus.. it now appears as "HTC Generic Serial" and with different USB IDs, etc, and it uses different protocols to communicate with the Host Adapter (it's a lot of black magic I don't know too much about).

This issues really does need to be resolved somehow, as I actually want to be able to use the "advanced network functionality" that my PDA has to offer.

I'm happy to assist in debugging and development, including remote access to systems where you can access my device if that would be of any assistance.

I've attached the output of two commands to this ticket. "VBoxManage list usbhost" and "lsusb".

#2150 fixed Installation error 2803 when installing vbox on win XP x86 Eric Mangold
Description

Already have vbox 1.6.4 installed (using all defaults during installation).

Vbox (1.6.4) was currently running when attemping this install of 2.0.0 (no msg box about closing running vbox was given).

Installer reported error "2803" and I had to close it.

Closed running vbox, and re-ran setup. Installed OK.

Probably you guys should use a mutex to detect if the app is running, see e.g. for Inno Setup http://www.innosetup.com/iskb.php?mutexsessions

Cheers

#4000 fixed Abort VBox upgrade if at least one VM is running or paused Eric Mangold
Description

I often used Ctrl-P to toggled the "paused" state of a Windows XP VM (Linux host).

This has always worked great, however today I upgraded to 2.2.2 (r46594).

The next time I tried to unpause the VM (it had been paused for many hours) an error dialog came up "Unable to resume execution..." with the error Callee RC: NS_ERROR_ABORT (0x80004004)

This results in an aborted VM and loss of execution state... not fun :(

OS: Ubuntu 8.10 $ apt-cache policy virtualbox-2.2 virtualbox-2.2:

Installed: 2.2.2-46594_Ubuntu_intrepid

...

I've attached the log for this

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy