Custom Query (16363 matches)
Results (1048 - 1050 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1073 | fixed | Crashes when i merge .reg file. | ||
| Description |
Crashes when i merge .reg file. When i double clicked a .reg file, then pressed OK button, I got a Blue Screen. then both guest Windows System and VirtrualBox crashed. btw. My guest system with McAfee AntiVirus Enterprice 8.1 patch 15 installed. |
|||
| #1074 | obsolete | Full screen mode does not use maximum resolution (with workaround) | ||
| Description |
We are using VBox on a Linux Fedora 7 host with Windows XP as guest. We are using displays with a resolution of 1600x1200. The following problem with Full screen mode occurs: When using full screen mode after installation, the guest only uses a resolution of 1400x1050, the rest of the display remains black. The first attached log file shows this (wrong mode in vmmdevRequestDisplayChange). This also happens after several toggles of Full-screen and back. The following workaround works: When setting the maximum resolution in the XP guest (Display -> Settings) one time to 1600x1200, then after this the full screen switching always works - also after a restart of the VM (see second attached log file). Nothing changed on the hosts screen resolution between these two log files We are using xrandr 1.2 enabled video drivers but I have no idea whether this has some effect on these problems. |
|||
| #1075 | wontfix | Invalid snapshot because of parent modification not detected | ||
| Description |
We are using a configuration, which is not really "standard" on Linux host with Windows XP guest: We are using a shared VDI which is used readonly used by several client, which create their own snapshot derived from this VDI, so each user has his own "virtual installation" based on this common base vdi. When modifying this common vdi (installation of a changed base install), VBox does not detect that the snapshots derived from the old install are invalid. The could be prevented by a simple timestamp in the vdi and its snapshots. I know, this problem will not occur when using VBox "as designed" so please close this ticket when appropiate |
|||

