Well, I was wrong Current version does not implement the custom ACPI table, it's still in development. It's still true that excel patcher is not working, some work to do...
atreyu, Do you have a patch for v4.1.10.76836 Windows? By the way, the extension pack is still build 76795.
atreyu, Sorry for asking such a noob question, but what exactly am I supposed to download (for the Windows version of VirtualBox)? If I'm not mistaken: - The VBoxDD_4110_oneiric_amd64.tar.bz2 contains a VBoxDD.so file - which is for the linux version. - The Windows kit is a bunch of source files - The vbslic_4110_windows.7z contains a vbslic.exe So I guess I should be doing something with the vbslic.exe file. Am I just supposed to run it? I thought you just patched the VBoxDD2.dll, and I just need to replace the regular DLL with your patched file. But I don't see any DLL in any of the above files.
It says the usage is: vbslic VBoxDD.dll So I did just that. Will be testing it soon. What about the VBoxDD2.dll? I've seen some posts regarding this file...is it supposed to stay untouched?
Yah & no... only for NT 6.0 and 6.1. 6.2 is 8, which may use MSDM table with SLIC for oem:slp (or oemm) activation.
Thanks user hidden for this version but an another newest is out today 4.1.12.77245 h**p://download.virtualbox.org/virtualbox/4.1.12/VirtualBox-4.1.12-77245-Win.exe (replace h**t to http)
@Tito: My processor does not support Intel VT-x. But I could easily install Windows Vista/7 using VirtualBox. But with Windows 8, VirtualBox has this hardware assisted virtualization requirement. What could be the reason for it? When Windows 8 RTMs, will VirtualBox still require VT-x for Windows 8? Windows 8 on VMware Workstation, VWware Player works absolutely fine. But still I wish I could somehow install it in VirtualBox because its way too smooth and faster to work on. I tried everything from exporting disks to exporting VMware machine as OVF, nothing seems to work!