Custom Query (16363 matches)
Results (934 - 936 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #957 | fixed | IRQL_NOT_LESS_OR_EQUAL | ||
| Description |
Host: Windows XP Professional SP2 Guest: Mandriva Linux 2008.0, DreamLinux 2.2 VBox 1.5.2 When I try to install one of the two linux distro's mentioned above, I get a BSOD containing "IRQL_NOT_LESS_OR_EQUAL". I haven't tried other distro's yet, but the fact that I get the same error while one distro is debian-based and the other is redhat-based gives me the impression there's either something wrong with VBox, or with my computer.. I was unable to find 'VBoxSVC.log' so I couldn't attach it. My hardware consists of:
Kind regards, Stijn |
|||
| #958 | fixed | VirtualBox 1.5.2 with webservices (soap) | ||
| Description |
Hello! I will use VirtualBox 1.5.2 with webservices. This is not an Vbox defect! To this day, i doesn't found some docs/howtos to setup this. I have written a soap client in PHP to get the vbox version number. My sample: /* CLIENT: show VBox version */ <?php $client = new SOAPClient('http://192.168.1.150/webserv/vboxwebService.wsdl'); try {
} catch (SOAPFault $f) {
} ?> The file vboxwebService.wsdl point to soap address localhost on port 18083. This is the address to the soap server? My sample return as output "Can't connect to host". How looks the connection between soap server to VirtualBox? Can you put some simple soap samples to VirtualBox website please? Many thanks Michael |
|||
| #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. |
|||

