Custom Query (16363 matches)
Results (1513 - 1515 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #14963 | obsolete | Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) on 5.0.12 Mac | ||
| Description |
I raised this on the forum initially and was referred here as somebody else reproduced it. This is a newly installed VirtualBox 5.0.12 on a nearly new Macbook Pro (8GB RAM running 10.11.2. I created a Solaris 64 VM to install SmartOS and attached the SmartOS USB VMDK and a new VMDK for the Zpool. On poweron, SmartOS went through configuration OK, but when it rebooted (as per usual) I got a Critical error. The log is attached. |
|||
| #11845 | obsolete | Grey overlay from session restore remains if user switches to other virtual desktop | ||
| Description |
When you restore a saved session (Currently using VirtualBox 4.2.12 on OpenSuSE 12.3 with Gnome 3.6 Desktop - but problem was also present on earlier versions of those) and switch to another virtual desktop while the session is loaded, a grey transparent overlay will remain over the guest OS. I feels like looking at your desktop through a very dirty monitor. The overlay can be removed by saving and restoring the VM session while staying on the same desktop. The behavior is slightly annoying since I have to wait for the VM to restore and cannot use the time for other tasks. |
|||
| #12892 | obsolete | Wrong target path in start menu entries on Windows 7 64-bit | ||
| Description |
On Windows 7 64-bit virtualbox is installed to "c:\Program Files\Oracle\VirtualBox" Start menu entries are generated in "c:\ProgramData\Microsoft\Windows\Start Menu\Programs\Oracle VM VirtualBox" If I check the properties of the LNK file in the start menu folder the target of the start menu entry points to "c:\Program Files (x86)\Oracle\VirtualBox" This occurs if I use a 32 bit application to show the LNK properties, e.g. total commander. This application opens the common file properties dialog, but it seems that the contents depends on the calling application. Example: Show properties of file "c:\ProgramData\Microsoft\Windows\Start Menu\Programs\Oracle VM VirtualBox\Oracle VM VirtualBox.lnk" The target points to "c:\Program Files (x86)\Oracle\VirtualBox\VirtualBox.exe" The working directory points to "C:\Program Files\Oracle\VirtualBox\" This is quite strange, because I didn't see any "(x86)" in the lnk file when I check it with an editor. Furthermore if I show the properties of the start menu entry using the start menu > All programs > Oracle VM Virtual Box > Oracle VM VirtualBox, right-click > properties I see the correct entries, thus no (x86). The different targets result a problem if I use a tool that reads the properties of the lnk file, e.g. an application launcher. I tested the behaviour on Windows 7 Professional, last updates installed, german localization. No changes regarding UAC since installation of Windows 7. It seems that is caused by the different handling of the targets depending of the environment (32 vs. 64 bit). Is it possible to set fixed paths during installation and generation of the LNK files? |
|||

