Worked for me a few days ago on a hand-me-down eMachine model C6415 (no "system recovery" partition; CD/DVD lacks drivers; remaster/update 'not supported', ...) OEMBIOS scan claimed no match to any of 106 strings script did produce fileset w/CRC32=C86378C7 (RWeverything found Gateway in BIOS) I added noted cab compression parameters to cmd/batch script, ran same to obtain OEMBIOS files ... edited setupp.ini to OEM channel Tested (on separate partitions - kudos to Partition Magic and PenDriveLinux!) ... on XPsp2 VRMHOEM_EN(+GRTMUPD_EN) & MSDN's XPsp3 and "genuine" per MGA diagnostic So far, so good - there's hope for viable backup/update/remaster yet ... in spite of a clear lack of 'support' from hardware and software OEM's (legal intentional sabotage?) I hope to eventually get this suitably configured At least there's GNU/Linux (& BSD?) support for 'remaster'
Can someone explain more what to do after running OEMBIOS backup. It creates files then what do you do with it? hxxp://forums.mydigitallife.net/threads/9795-The-Windows-XP-OEMBIOS-Archive Do I download the dataset for my manufacturer (HP in my case) and then burn it to DVD? If XP is installed, is there a way to make it OEM pre-activated still?
Updated oembios-winntsif script v1.01.14Beta : 21120508.2 Script now uses Subroutines Activation status check Has optional command line switches (see oembios-winntsif.vbs /cmd:switches) Adds comments to windows answer file creation Remote window answer file creation on LAN via switches