So my father in law had a crash and i had to replace his motherboard. Now slp string is missing and xp says i have to reactivate. My thought on this is to run decryptoembios.exe and see what string is expected and then inject this in right place with amitool. all to keep him close to original as possible. Decrypting gives me something like Code: [OEMBIOS] BIOS=f000,0000,ffff, FUJITSU BIOS=f000,0000,ffff, SIEMENS BIOS=f000,0000,ffff, PRIMERGY BIOS=e000,0000,ffff, FUJITSU BIOS=e000,0000,ffff, SIEMENS BIOS=e000,0000,ffff, PRIMERGY Makes me think there can be more than one string present. Is this string later related to his product key so i have to match it? or it doesn't mater as long as xp finds one of this strings? Is there more i have to watch out for? or maybe a better way to go?
The tool you need to run is oembios.exe to see if SLP1.0 string is in dmi area motherboard may already have one.
ok, but if there is a string, then i have to replace the oembios files + SLP Product Key to match that string?
So you are confirming what i suspected, if i only put in ex. SIEMENS at area f000,0000,ffff his xp will be up and running again?
Normally, it would I do believe this specific set might be a bit tricky to work with (notice the white space before the SLP string?) According to the SLP 1.0 Whitepaper using such white space isn't allowed, eg:
ok cool. Thanks for your collaboration! Fortunately it's not his oembios.dat file, i just used it as an example cus im at work Will investigate as soon as i come home, hopefully his is without "white spaces"