Custom Query (16363 matches)
Results (1084 - 1086 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8046 | duplicate | VirtualBox 4.0.0 breaks OpenStep 4.2 | ||
| Description |
VirtualBox 4.0.0 appears to break compatibility with an OpenStep 4.2 guest. All versions of VirtualBox from 1.6.0 to 3.2.12 successfully ran OpenStep 4.2. VirtualBox 4.0.0 does not. It is not clear what causes the problem. It might be related to display. OpenStep boot proceeds normally until such point as it switches from text (verbose) boot to graphics mode, at which point it simply goes to a black screen with a frozen mouse pointer drawn on it and does not move from there. |
|||
| #12024 | fixed | This kernel requires the following features not present on the cpu : pae ...... Unable to boot - please use a kernel appropriate for your CPU. | ||
| Description |
I am trying to set up Hadoop on my Windows XP "Hp Pavalion zt3000" that has pae. 1) I installed the most recent version of VirtualBox.
2) The machine came up with no problem and I started it.
3) Then I downloaded Ubunto 13.04 32 bit for desktop.
4) This is the error message that I received :
5) I then powered down the VirtualBox and went to "Settings" -> "System" -> "Processor". And the Extended features _ Enable PAE/NX was geyed out by default. This means that it was turned "off" and I could not turn it on. 6) I then figured out how to turn on PAE via the API
7) I then went back to the UI in Vertual Manage and PAE was checked as "on". However there appers to be a minor problem - it was also greyed out. 8) When I rebooted my system and restarted VirtualBox, when it tried to install Ubunto I still received the same message. Even though it showed PAE as checked as "on" it was actually not turned on. I believe that this a bug in your software. Sincerely Yours, Jomo Willacy |
|||
| #16204 | fixed | Virtualbox Driver doesn't have WHQL Certificate | ||
| Description |
Driver signing changed in Windows 10 1607 Version: Microsoft said: Starting with new installations of Windows 10, version 1607, the previously defined driver signing rules will be enforced by the Operating System, and Windows 10, version 1607 will not load any new kernel mode drivers which are not signed by the Dev Portal. OS signing enforcement is only for new OS installations; systems upgraded from an earlier OS to Windows 10, version 1607 will not be affected by this change. If your driver doesn't have Microsoft Windows Hardware Publisher Certificate (For Example:IDM Browser WFP Driver), Windows will block the installation of this driver. So Does Virtualbox should get a Microsoft Certificate? |
|||


