@Freestyler i never played with XPmode, i'll have a look. is oembios.exe capable of listing XPmode when it scans?
Should be Anyway, I think i managed to patch it without causing boot issues --------------------------------------------------------------- VirtualBox 4.1.x x64 patch for the OEM pre-activation technique used in Windows XP Mode VHD.
with the latest patcher on 32bit = Nothing patched! what is the bios range for the "Windows_Virtual_XP_F9161D8E7FCC11DDBFAA369856D8959 3" ? and is there a space between the 9 and 3 last digits or does it end 93
000F908A, the spaces exist due to vBulletin text formatting Code: F000,908A,,Windows_Virtual_XP_F9161D8E7FCC11DDBFAA369856D89593 excerpt of the OA 1.0 whitepaper
@amiga Does patched x32 version boot, when you install for example Windows Loader on the VM? When i get home i will lookup the differences in x32 and x64 and try to make a patch that fits both (if possible) I usualy use RW-Everything, but HWDirect works exactly the same
@FreeStyler created new win7 vm installed windows loader used it to activate and then tested rebooting several times everything fine. also used xpmode vhd and booted and all activated with patched vboxdd2.dll corrected post above in summing up i put old pattern by mistake Oops.. cut and paste and not enough sleep lol
hi atreyu, i'm asking if it would not be better to add and extra information as extension pack to vm configuration that let the user to choose the bios he need. then modify devacpi and recompile the to refer to the vm configuration. i'm working on the extension.
Hi, About a month ago, I posted a feature request for an SLIC passthrough to the VirtualBox bug tracker. I went with the legitimate angle of a "passthrough", because the Windows 7 license allows one to run Windows on a machine either virtually or on bare metal. If I missed something important, please add your thoughts! virtualbox.org/ticket/9231
Installed the latest v4.1.2 to w7 x64 and open VBoxDD.dll v4.1.2(x64) in Winhex but cannot find C4CEB8.... Am I missing something?
just replace in VboxDD2.dll Code: C4CEB8450250FF76FEE82B7483C40430E4D1E08846FDB8460250FF76FEE8177483C40430E40246FD80D4008846FD31C050B874 with Code: 57696E646F77735F5669727475616C5F58505F4639313631443845374643433131444442464141333639383536443839353933 and it will work
To anyone reading this thread on how to patch vboxdd2.dll please note that the 64 and 32bit versions have different strings that need replacing to achieve ms xpmode activation this has been so since version 4.1.0 of vbox
I'm trying to get vbslic.exe to work with VBoxDD.ddl from this release (x64) and getting told the version is not supported. What is xls patch?