Custom Query (16363 matches)
Results (307 - 309 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3358 | obsolete | Low perfomance on shared folders | ||
| Description |
In the new VirtualBox version (2.1.4) with Guest Additions 2.1.4 under a Windows XP SP 3 guest OS and a Windows XP SP 2 host OS, continues happening the issue of share folders performance, the performance of these is very slow. It's supposed that shared folders should have a similar performance as local folders in the guest. However there is a huge performance difference between them, local folders are fast as they are supposed, but shared folders are very slow compared with them. |
|||
| #3365 | obsolete | DOS6.22 + EMM386.EXE crashing Vbox | ||
| Description |
Im created VM with params 512Mb HDD, 32 RAM, 7 Video Ram, CDROM, SB16 emulation. Installed DOS 6.22. Added EMM386.exe in config.sys (device=emm386.exe auto) started test DOS application (alone in the dark 3) now VBox crashed with message in its log: fatal error in recompiler cpu: triple fault. |
|||
| #3367 | obsolete | Fun and games with whacked out video modes in XP guest / Linux host | ||
| Description |
This was mentioned in the comments of the (now closed) 3096 ticket. http://www.virtualbox.org/ticket/3096 This is not fixed in 2.1.4 as the 3096 problem was, so this is a new ticket, and I have more information and some potential workarounds. This was my comment from there:
Now, I've gone back and created a new XP SP2 machine and applied no updates (just to make sure none of the MS updates since SP2 have any impact and I can eliminate that as a source of the problem) and just installed the VirtualBox guest addons. After rebooting, I found I had 32 bit color but still only 640x480 resolution available from the desktop settings. Under advanced -> show all modes for the adapter, it showed 6 possible modes, 5 in 640 x 480 and only one in 800 x 600 (4 bit). I thought, maybe the graphics memory. It was set to 12 Meg. So I shut down the vm and upped the video memory to 64 Meg and rebooted. Now I've only got 640 x 480 with 4 bit color and "all modes" only shows 4 modes, 640 x 480 and 800 x 600. Changing back to 12 Meg had no effect. On a silly lark, I hit "full screen" (host window manager decoration maximize) and was surprised by the answer. It had full 32 bit color (but still only 640 x 480). But when I went back to the desktop properties, I found I could now select all the other higher resolutions. If I drop out of maximize, I've still got 32 bit color but stuck back on 640x480 and I'm back with "All modes" showing only 5 modes available. If I manually resize the window from the host window decoration handles, I can resize it up to a bit but it doesn't change what the guest thinks (properties still says 640x480 32bit). After a certain point, it won't let me enlarge it any larger and it snaps back like a rubber band Using the machine mode "full screen" (Host-F) give me a 1280x1024 in the VM and all modes appear properly. If I hit Host-F again, it drops back to the manually sized window with the custom resolution. From there, I can set the resolution from within Windows to any resolution smaller than the custom resolution I had it at and the host window now resizes! Yeah! I believe we have a workaround... Maybe... Workaround that appears to work for me. After installing the guest addins...
Unfortunately, this workaround doesn't appear to be sticky. If I shut the VM down and restart it, I'm back at 640x480 with 4 bit color. If I immediately do a Host-F, I'm at full screen with 1280x1024 w/ 32 bit color and another Host-F takes me back to 800x600 w/ 32 bit color, which I can not immediately increase from within Windows. If I use the host window manager handles to expand the window, I find it does now expand and I find more and more modes present in the "All Modes" list box in the guest, up to a certain limit (1232 x 919 for some weird reason). At this point, I can make it work, at least for the SP2 VM. Less than elegant is the understatement of the year. It was slightly more complicated on my fully patched fully loaded production XP SP3 system but, after increasing the video memory from 8M to 128Meg and then playing with the bit plane depth within Windows and then doing the Host-F trick, that one worked as well. Seems like it remembers some settings from one to the other. This seems to be a real complicated interaction between video memory and window resolution from the host to within the XP guest. The log files are from the XP-SP2 guest system and not the SP3 system. |
|||

