Custom Query (16363 matches)
Results (229 - 231 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #18993 | duplicate | MACOS CATALINA | ||
| Description |
Bonjour Depuis la maj de l'O.S MAC, ma partition windows 10 se plante Cordialement |
|||
| #897 | worksforme | converted VMWare 6 vmdk with MS Win XP guest to a vmdk for VirtualBox pro current; failed | ||
| Description |
and have done 1. enable IO APIC support in VirtualBox
and 4. removed VMWare tool from MS Win XP. Additional details: latest stable VMWare 6.x, using a 10 GB extensible vmdk Windows XP Professional-s001.vmdk Windows XP Professional-s002.vmdk Windows XP Professional-s003.vmdk Windows XP Professional-s004.vmdk Windows XP Professional-s005.vmdk Windows XP Professional-s006.vmdk Windows XP Professional-s007.vmdk Windows XP Professional.vmdk I am using the latest stable VirtualBox pro (with USB support) RHEL5 rpm. These files and additional ones are in a directory. I made a cp -pr of this directory into another with a different directory name. I used VMWare on the new directory to perform steps 2, 3, and 4 above on a running MS Win XP. I then shutdown MS Win XP, exited VMWare, and started VirtualBox using the same new directory with the modified WinXP image as the file to start -- using only the Windows XP Professional.vmdk file -- not the sub (-s00x) files. As MS Win XP boots, VirtualBox suffers a fatal error; I have the logs VirtualBox automatically generates. What have I done wrong? I do not want to reinstall all my MS Win XP applications from CD-ROM; ghost would not solve this problem because it would make an image of MS Win XP with devices/drivers that VirtualBox cannot use. Once I get the modified MS Win XP running under VirtualBox, I will install the VirtualBox equivalent of VMWare tools into the running MS Win XP so that the screen will resize, etc. |
|||
| #2262 | fixed | USB still no go from non-root account | ||
| Description |
Your latest 2.0.2 on a RHEL 5 current (17 Sept 2008) host with a MS Win XP Pro guest is a big improvement, but USB still does not work properly from a non-root account. USB devices are shown as these are inserted into the hardware and recognised by Linux, but are grey and cannot be attached to the MS Win guest from a non-root account. This feature does work as root. Moreover, you have one dangerous provision: you allow the Linux USB pointing device (e.g., a Logitech track ball) to be disconnected from Linux and thus never reconnected without a lot of editing of configuration files as root from a scrolling screen on a plain terminal (e.g., ctrl-alt-F1). The greyed out check box widget is a permission issue, but you should automatically correct this; the pointing device should not be offered if possible or given either protection or a GUI recovery. Without easy access to USB, I will continue to use VMWare in which all of these work as they should. |
|||

