Custom Query (16363 matches)
Results (937 - 939 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #959 | fixed | problems with BIOS reals beyond LBA boundary? | ||
| Description |
I observe the following problems with VirtualBox. An explanation that fits this problem patterns is that there is a problem with BIOS initiated reads beyond the LBA boundary of a disk.
Here is an explanation that fits the above problem pattern: in real mode, reads from disks that are beyond the LBA boundary (separate interface INT 0x10,AH=0x42 IIRC) is broken. FAT/NTFS MBR uses the AH=0x02 interface for everything beyond sector 1024*255*63. This fits all problem/no problems:
Side notes: Vmware is able to boot into ALL of the 3 cases were virtual box isn't able. For problem 4, I made sure to add the necessary drivers into the criticaldevice section of the windows registry. I'm not sure if I did that correctly, but what really indicates that there is a problem at a much lower level (bios level) is that, in problem 3 I'm not only unable to boot into windows, but also unable to boot into the recovery console. the recovery console refuses to load because HAL.dll is not found (as I said HAL.dll is likely to reside after the LBA boundary). My next test case is: format a plain NTFS disk, fill it up with to 8GB, and do a fresh win xp install. The result (if my thesis is correct) should be that NTLDR is not found, and booting dies. (will do that in about a week, I just filed this bug now so that this issues is known, and this knowledge isn't lost if for some reason I forget to do this) Of course, if you have further insight you are free to provide it. |
|||
| #960 | invalid | VirtualBox segfaults on Arch - 2.6.23.9 kernel with vboxdrv loaded | ||
| Description |
VirtualBox GUI works without vboxdrv module loaded.
Original reports: #8851 and #8879. |
|||
| #961 | invalid | Vrdp disabled, but vboxvrdp.exe tries to reserve the port | ||
| Description |
I have virtual machine where "enable vrdp server" is unchecked, but disabled server port field has 3389. When I start this v.m. from gui, it works; but if I start it vis commandline by vboxvrdp.exe, it fails with message "vrdp server port 3389 is already in use" |
|||

