Custom Query (16363 matches)
Results (1669 - 1671 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9048 | obsolete | DMG can't be dragged into Virtual Media Manager | ||
| Description |
In the Virtual Media Manager, in the CD/DVD Images section, I can drag an ISO into the list and it is made available to my virtual machines. I can't drag a DMG image in. Adding the same DMG image when prompted for install media or choosing a file from the VM work fine. I'm using VirtualBox 4.0.8 on Mac OS X 10.6.7. |
|||
| #9053 | obsolete | FSTENV assembler instruction - wrong implementation | ||
| Description |
Hi, I believe VirtualBox has wrong implementation of FSTENV assembler instruction. It is not dumping last float-pointing instruction address correctly. I've created a simple application in assembler which can be used as proof. Try and debug this application with debugger (OllyDbg for example) and take a look at buffer after the FSTENV instruction. It should contain address of FNOP assembler instruction. format PE GUI entry main include 'win32a.inc' section '.data' data readable writeable buffer db " ", 0 section '.text' code readable executable main: nop mov eax, buffer fnop fstenv [eax] invoke ExitProcess, 0 section '.idata' import data readable library kernel32, 'KERNEL32.DLL' import kernel32, ExitProcess, 'ExitProcess' You can compile the example code with FASM. |
|||
| #9056 | obsolete | Blue screen on Windows 7 64 bit with seamless mode and CentOs 5.6 | ||
| Description |
I experienced a lot of BSOD on Windows 7 64 bit but they happened ONLY when using seamless mode (which is very cool IMHO!). I used to use cygwin but now I am using VBOX and CentOS (for developing puposes) almost all the time. No problems at all if I run VBOX (4.0.8 r7178) in normal mode. If I enable the seamless mode, everything seems to work but I get random BSODs. They're always different from each other.. sometimes it's the tcp stack sometime it's memory or irq corruption, etc etc Disabling seamless mode and enabling the normal windowed mode never caused a BSOD. |
|||

