[DISCUSSION] VirtualBox - Update, SLP & SLIC

Same HP oembios files fails to activate using Hewlett-Packard string. Using SLIC 3.0 toolkit noticed that memory location reported for HP SLP starts with E000 whereas HP String has F000 for oembios files.

F000,FFEA,6,COMPAQ
F000,0000,FFFF,Hewlett-Packard

Replaced it with 'IBM CORPORATION' and used IBM 2003 CRC-36E95D7A oembios files which looks for string in E000 location and it worked perfectly.
e000,0000,ffff,IBM CORPORATION
f000,0000,ffff,IBM CORPORATION

Seems HP SLP will work for Windows XP but for 2003R2 it works perfectly well with IBM string.

 

You need to login to view this posts content.

 

Who do not have this set, do we?

LEGEND Dragon / LENOVO (OEMBIOS CRC=8AD619BD)
'f000','e000','1fff','LEGEND Dragon'
'f000','f000','0fff','LENOVO SureNAS'

 

Sorry, you are right, and looking at it, it would not activate anyway...

sebus

 

You need to login to view this posts content.

 

If you search and replace the following hex values in VBoxDD2.dll (taken from VirtualBox v3.1.4 x64) you are able to use the XP Mode Mode vhd in VirtualBox without having to swap oembios files

orginal

Code:

C40683C400E9D801E9D501B81300508B460A50FF7604E8FF7483C406B83F0250FF76FEE8CC7483C40430E4508B460A4050FF76

replacement (ASCII = Windows_Virtual_XP_F9161D8E7FCC11DDBFAA369856D89593)

Code:

57696E646F77735F5669727475616C5F58505F4639313631443845374643433131444442464141333639383536443839353933

 

Nice one! Thanks

So VBoxDD2.dll has the SLP info & it seems that VBoxDD.dll can have the SLIC 2.1 info

sebus

 

Yes, vBoxDD2.dll seems to hold the VBOX default DMI information and functions to display custom DMI properties defined in the Virtual machine XML file
I am going to try to patch VBoxDD.dll so it can contain SLIC data, I have some ideas on how to accomplish... now just hope it will work

I am not sure the HEX values above are the same when using x32 version of VirtualBox... however these values should be the same or similar on older X64 VirtualBox releases (eg: 3.1.2 and/or 3.1.0)

 

How do I edit vboxdd.dll in VirtualBox running in Ubuntu?

 

You do NOT, because Linux does not USE .dll

sebus

 

You need to login to view this posts content.

 

Have been trying to patch SLIC into the vboxDD.dll... till now without luck, darn i can't stand the fact i can not figure out whatever atreyu did

 

I expect he might have re-built the dll from the source code...

sebus

 

He said he patched it... at least that is what i make of above remarks

 

Would WindSLIC injection work like it does for vnware?

 

ummm maybe a typo above but,

vboxDD.dll = slic data (vista/7)

vboxDD2.dll = slp data (xp)

 

yep typo...corrected

 

I tried a few days to compile the windows executeables and dll's, but VirtualBox 3.1.4 PUEL refuses to accept the new compiled VboxDD.dll from the OSE Version. I thinks this is because the new compiled dll is not signed.

I think also, that it is very strange, that there is a patched and signed dll from atreyu. Maybe he has access to the development equipment from sun/innotek. If anyone has onother explanation, i would like to hear it.

Greets Obelix

 

The digital signature is invalid, so the dll was cracked!

sebus