Announcement

Collapse
No announcement yet.

Precise and VirtualBox

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Precise and VirtualBox

    I installed the BINARY version of VB from the repository (not the OSE version in the repository), along with the extension, and kernel drivers and modules.

    I turned on my old Sony VAIO for the first time since Jan 3rd and fired up VB on it. I exported the WinXP guest OS as an *.ora file, leaving all settings unchanged. Using a USB stick I moved the 9.7GB ora file to this laptop and ran the import program, checking the box which forced a resetting of the network drivers.

    The guest WinXP came up nicely, but I got a message that USB 2.0 hci was being disabled because the guest addtions extensions were not installed, so I couldn't get it to recognize USB sticks when the WinXP desktop appeared. That was strange because the the WinXP display took 3/4ths of my 17" screen, at a 1024X780 setting, up from 640X480, something it couldn't do without the guest addtions. And the guest additions icon was setting in the WinXP tray!

    I decided to get the guest addtions from Oracle's website. Firing up WinXP I tried to install the new additions file, but I couldn't find it from the WinXP guest. It saw only the additions from the repository. Playing around with the VB settings for the WinXP guest OS I saw an option under "Preferences" to install the guest additions in VB itself, not specifically in the guest OS. It saw the newly downloaded additions file immediately and I installed it in VB. When I fired up WiinXP the old additions was still setting in the system tray. I ran the "Install Guest Additions" from the VB menu dialog and chose as the destination directory the directory that the old additions was in, and rebooted the WinXP. The WinXP settings panel did not disable the USB check box when I checked it, but found no joy. Even though I plugged several USB sticks into this laptop, and they were recognized by Precise, WinXP could see them.

    I checked the USB settings dialog again for WinXP. There were three devices listed that I had plugged into the Sony and which WinXP had recognized on that box. I deleted them and created a new one. It was given the name "New Filter 1". That didn't help, WinXP still couldn't see by Toshiba 16GB USB stick. I googled a bit and found that one had to set the device parameters in a "new filter 1". I opened KInfo and displayed the device details for that USB stick, and entered them into the device settings tab on the WinXP USB dialog panel and changed "New Filter 1" to BACKUP16G, the device's label. When I fired up the WinXP guest OS and clicked on the "Devices" menu option in the VB frame surrounding the WinXP display, my Toshiba USB stick was listed. I clicked on it and it immediately mounted. I browsed around a bit, and then unchecked the device in that menu. It immediately dismounted. I tried several other sticks and they were identified immediately and I was able to mount and umount them, even though I had not entered them in the WinXP USB settings dialog. I shut down WinXP and checked the VB USB dialog. The only device listed was my BACKUP16G stick. Apparently, identifying just one USB stick primed VB to recognize them all. Strange.

    But, the import of my WinXP guest OS concluded perfectly, with all functionality and applications working as they should. Of course, since I hadn't run it for over a month, there were updates to install before it would shut down, so the auto update feature was working nicely as well. I am a happy camper! 8)
    Last edited by GreyGeek; Jan 28, 2012, 10:08 AM.
    "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
    – John F. Kennedy, February 26, 1962.

    #2
    Originally posted by GreyGeek View Post
    Apparently, identifying just one USB stick primed VB to recognize them all. Strange.
    Strange indeed. I've used only unspecified filters and haven't (so far) encountered any problems. But then again, my VM is Windows 7, not XP; I wonder whether that matters here, though?

    Comment

    Working...
    X