Yes it is a bit more involved, I sucessfully made a multi xp pro by converting a XP corp disk to oem and updating the oemscan.ini I tested on an HP and IBM sucessfully. To make sure that oemscan.exe was working properly, I dropped dell bios files into the i386 so that if oemscanexe didn't work it would prompt me for activation since it would have dell files on an HP computer. As further proof, it successfully activated on an IBM laptop I ran it on as well. I installed from the disk I made and it sucessfully ran the oemscan.exe (you can see it run at T-13) and it activated properly. I checked activation after running all updates including sp3 and wga by using the following command: %systemroot%\system32\oobe\msoobe.exe /a If everything worked properly then you get a box pop up saying that windows has already been activated. I can write up a step by step tut for this but it will be a couple of days before I have the time. Also, the XP Pro OEMscan.ini needs to be updated and edited slightly because some of the bioses it references are out of date (specifically the Asus one) Since you need to supply the bios files yourself, the main thing you need to do is update the key. I also expanded the list for all major manufacturers, and will be adding in the rest later on this week (I got lazy after I covered the major ones as it was late and I wanted a working copy to bring to work with me the next day lol) I'll probably upload the neccessary files after I finish adding everything in and checking that it works. I'm also still working on properly intergrating the txtmode Satadrivers and need to mess with a script I'm writing in the meantime to have the oemscan run with "OEMPreInstall=No" so that f6 functionality is preserved until I can intergrated the Sata drivers properly. Easiest way to get started with XP Pro is to follow Suicides post on page 2 That will convert the Corp disk to OEM and then you test that by dropping 1 manufacturers bios files into the i386 and put the key into WINT.sif, if that activates sucessfully, then you start working on the $OEM$/oemscan.exe to make it multi.
Ignore my question about the oemcopy.cmd not copying the oembios.bin, oembios.sig, and oembios.dat files. As we mentioned, OEMscan.exe properly copies those files and oemcopy.cmd is really only need to copy the oobeinfo,ini, oeminfo,ini, and oemlogo.bmp It seems having the oemcopy.cmd copy those files over again is kind of redundant. It will sucessfully replace the dllcache files if run post install, it seems like somekind of wpf or sfc issue that prevents them from overwriting during T-13. I don't know if it would cause any issues in the long run if those dllcache versions are left unreplaced, but so far I haven't noticed any problems from it. You could always run sfc.exe /Purgecache and just forget about the dllcache in general. That would however make windows unable to automatically restore corrupted systemfiles as it would have no backup of them and Windows would end up prompting you to insert your install disk to replace messed up files. EDIT: Actually I just ran sfc.exe on a fresh install of windows to see if it would break activation and it doesn't. So I think it'd be best to just remove the lines in oemcopy.cmd for oembios.bin, oembios.sig, and oembios.dat as they don't work anyway. Truthfully it doesn't matter one way or the other, but for script cleanliness I am gonna remove those lines. Just Successfully integrated sata drivers to it.... bye bye f6 and floppy.... next up is autoinstalling all drivers by hwid.....
Hi Just came across this post,just to let you all know that after a lot of work & trial & error,I've had my multi oem working quite successfully for the last 9 mths Here are a few screen shots to share.
Nice GUI. I have a question, I see you're using OEMAUTO. How does that differ from OEMSCAN and SETKEY. I've seen some releases using it, but I've never seen references to it in threads like these. Thanks in advance.
Urie, I did not know that OEMAuto was considered "warez" as it is only an autoit script to invoke OEMScan - OEM bios Filesets -Royalty keys - Logos - Wallpapers etc. Sources came from another forum dealing with Multi Oem projects. See pics.
Are you it is not called OEMSCAN_ADDON_MULTIOEM v1.8 ? iv'e never heard of oemauto. when i was talking warez i was going by the images you poster of the cd the stuff that was on it i,e acronis e.c.t.
Yes the later version 1.8.1.2 OEMAuto.exe replaces OEMScan.cmd (check SVCPACK folder if U use addon).The "Other Stuff" on my Dvd are legit programmes that I use in servicing. The graphics layout i did myself and U can see my company logo at the top.This Dvd is strictly for inhouse technicians reinstalling windows when repairing machines. I think you might have jumped to the wrong conclusion that this was dloaded from the net whereas as I stated - I created this after a lot of reading articles in forums etc.
yes sorry i did jump to wrong conclusion anyway i do have OEMAUTO in OEMSCAN_1.4.1_MR_SMARTEPANTS_ADDON_MULTIOEM_1.8.1.2
X2 thanks , i too have succesfully made the disc . i have only tried it on one pc tho and it activated. i was also concerned about the errors showing at t-13. after reading more i am happy again . i did have no success activating when i built the iso starting with VL media .no win.sif. .i built the ISO starting with a gateway oem disc and all was succesful . activated oem slp HP on my HP machine cheers
You still need to add product key to winnt.sif file that key will get changed later on in install by setkey program.
How To Add a Vendor My universal OEM discs are working well, but I recently encountered something new that requires some assistance. I tried to use/update the disc for a MSI-based system. D/l'd the corresponding file from the OEMBIOS archive here at MDL, but I couldn't figure out whether to use [MSI], [MSI-2831-MS], [MSI-PC], [MSI-PenNote] or whatever to match the BIOS string for the vendor in OEMSCAN.INI. This is the section I added to OEMSCAN.INI: Code: [MSI] PATH=".\MSI\" RANGE="" MATCHARG="" CMD="" CMD="SetKey *****-R83RH-KTC88-H6Y62-XQJBT" [MSI-2831-MS] PATH=".\MSI\" RANGE="" MATCHARG="" CMD="" CMD="SetKey *****-R83RH-KTC88-H6Y62-XQJBT" [MSI-PC] PATH=".\MSI\" RANGE="" MATCHARG="" CMD="" CMD="SetKey *****-R83RH-KTC88-H6Y62-XQJBT" [MSI-PenNote] PATH=".\MSI\" RANGE="" MATCHARG="" CMD="" CMD="SetKey *****-R83RH-KTC88-H6Y62-XQJBT" Is there a util which will reveal the vendor string or maybe there's a procedure one can use in conjunction w/ good ol' DEBUG for this ? I've already read quite a bit of the related threads, but didn't see (not that isn't there) any info on this subj. TIA.... :-- MR --:
What was the output from the oembios.exe. I can give you the strings if you can give me the oembios.exe output. MSI will only work if the bios was an original MSI OEM XP machine, or a VERY manually modded retail bios. MSI SLP 1.0 strings have a very narrow address offset. using any one of the bios slp mod tools will not get it done.. Could you elaborate on the problem you have and what you have tried, in case I have missed some of your posts..