Thx for the patched file atreyu. These fixes work on Gentoo Linux under app-emulation/virtualbox-bin-4.0.X with just a small modification. The files you have were created for running under Ubuntu where I guess they install some of the VirtualBox files to /usr/lib/virtualbox. In my case since it's a binary build instead of from source it gets installed into /opt/VirtualBox. It appears that the VBoxDD.so file has to reference VBoxDD2.so and it is hardcoded to reference /usr/lib/virtualbox/VBoxDD2.so?? Anyways I just made the folder and copied over the VBoxDD2.so file and it worked. I couldn't use symlinks because VirtualBox errors out if you use symlinks and I couldn't try a hard link since it crosses filesystem boundaries. Anyways if anyone out there is using Gentoo this fix is easy. Create Directory: mkdir /usr/lib/virtualbox Chmod it for good measure (Should need this in theory unless your umask isn't 022): chmod 644 /usr/lib/virtualbox Copy File: cp -p /opt/VirtualBox/VBoxDD2.so /usr/lib/virtualbox 4.0.6 hasn't hit portage on Gentoo yet, but 4.0.4 is working great. SLIC Dump Toolkit confirms HPQOEMSLIC table on Windows 7 x64 guest VM. Edit: Seems 4.0.6 hit portage just this morning. Updated to 4.0.6 and working like a champ
Thank you for your feedback, crash_maxed, this may be useful to others VBoxDD.so is built as "for distrib", that happens to be a "hardened mode" - I think this means with hardcoded paths You can find the /usr/lib/virtualbox string near the top of the file, maybe it can be superposed with other path, eg /opt/VirtualBox can be found in the linux-all installation files
so does this turn the system to slic 2.1 once the VBoxDD.so file is installed on the linux host or is there more work needed?
atreyu thanx a lot 4 ur job. I have a questions one for SLIC and another for WinXP DMI or SLP: - How can i change SLIC from HP to another one? - I have insert DMI info from my real motherboard into VirtualBox WinXP and when i boot into virtual WinXP i see changed values of DMI info but my OEM WinXP i still unactivated. Where am i wrong?
vbslic vBoxDD.dll "ACRSYS[ACRPRDCT_MSFT]2.1-8F845FB1.BIN" (example) DMI info that is entered through the xml config file sometimes is not placed in the correct BIOS SLP range to be succesfully activated (for example DELL and ASUS require a specific range not covered by DMI entries) What brand OEM XP set are you trying to have pre-activated?
1. Thanx for explain! 2. I try to work with my office OEM Dist WinXP Pro from Russian OEM manufacturer KRAFTWAY.
Code: KRAFTWAY (OEMBIOS.CAT CRC32=2CD5F907) F000,0000,0140,KRAFTWAY F000,0600,0200,KRAFTWAY F000,0FD0,0200,KRAFTWAY F000,0000,FFF0,KRAFTWAY The entries in red require a specific memory range the SLP string needs to be listed in. The entry in green covers a much wider memory range, but it still can be possible this is listed outside the Vbox DMI area i can't test this right now, but if you like i can look into it further, else maybe patching vBoxDD2.dll may be the only solution
Hi Hood, FreeStyler is saying that he doesn't think editing the VM's .xml file will work. Due to the address range KRAFTWAY uses. But you should try it out anyway. It will only take a couple of minutes. If it doesn't work then edit vBoxDD2.dll with a Hex Editor, following his instructions. Good luck.
I have verified, the KRAFTWAY oembios set doesn't activate when using VM's .xml entries, so you need to patch vBoxDD2.dll
FreeStyler maybe i do something wrong but string "06/23/99" is started from hex offset 1733D so i insert KRAFTWAY from offset 17330. Seems that it's activated!) Thanx a lot bro!
What vBox version are you using? What processor architecture? Anyway like you already discovered the difference in offset shouldn't matter to much
Probably it's caused by a little difference between 64-bit and 32-bit versions of VirtualBox vBoxDD.dll file, as i am using the 64-bit version of VirtualBox