Custom Query (16363 matches)
Results (1558 - 1560 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5419 | obsolete | Windows 7 Guest haengs after Kapersky AV 2010 installation | ||
| Description |
The Windows 7 Guest hangs at boot time after the installation of Kaspersky AntiVirus 2010. There is no problem with the installation untill you reboot the system. |
|||
| #15823 | obsolete | openSUSE packages have bad libvpx dependency | ||
| Description |
I am on openSUSE Tumbleweed and installed the repository from http://download.virtualbox.org/virtualbox/rpm/opensuse/13.2/virtualbox.repo as described on the website. However, trying to install any one of VirtualBox-4.3, 5.0 or 5.1 fails with: Problem: nothing provides libvpx.so.1()(64bit) needed by VirtualBox-<version> Note that I have libvpx3 and libvpx4 installed, but it looks like those only provide libvpx.so.3 and libvpx.so.4, respectively. An older libvpx package is not available in the openSUSE repositories. |
|||
| #10623 | obsolete | OS/2 Warp 4 reports SYS0318 error on install, then "failed to return the target drive" | ||
| Description |
As per https://forums.virtualbox.org/viewtopic.php?f=4&t=49723, I am experiencing several errors (all relating to the same issue, I hope) while installing OS/2 WARP 4 in Virtualbox. I am able to reach the third (second installation) diskette, at which point the the setup begins to refer to the CD. I am shown the copyright and OS information, and I am prompted to press enter. After pressing enter, I am presented with this screen (see the Error1 image), directly followed by this screen when I press enter (see the Error2 image). I am then left with no choice but to press F3 and return to the prompt, where I am able to access and write to the hard drive if I have it partitioned already. Some system information: I am running Windows Vista 64bit SP2, apparently (according to vbox) with VT-x/AMD-V enabled. Nested paging appears to be unavailable. The VM has 64MB of ram allocated to it, and a 512MB hard disk image. As I said, I am able to access and write to the hard disk, so I don't really know what the issue is. |
|||

