Edit. tried sony oemslp from same project by searchengine. Once again the OEM logo is installed but nothing else.
Here you can download crypto's archive in one go. Please note it hasn't been updated since 2nd January 2011, so doesn't include the latest additions. The Windows XP OEMBIOS Archive.part1.rar mediafire.com/?3r159kpyjo2ilrb The Windows XP OEMBIOS Archive.part2.rar mediafire.com/?1rp85nlc4bsdd5i The Windows XP OEMBIOS Archive.part3.rar mediafire.com/?f198fb66ytuyo9f The Windows XP OEMBIOS Archive.part4.rar mediafire.com/?n8s6jl1ftgyu1f5 The Windows XP OEMBIOS Archive.part5.rar mediafire.com/?d3cl4454mnxt1f0 The Windows XP OEMBIOS Archive.part6.rar mediafire.com/?7fd1aw78hxzh23k Sorry for the links being not clickable, since I'm not supposed to post links till I have made 20 posts.
I am now in the middle of making my own XP Pro SP3 multi-OEM I am getting stuck on the driver packs installing. Snip from page 1... 4. Now you can integrate the drivers from driverpacks dot net.One advantage of integrating the driverpacks is that you won't face the SATA problems that normally most people do face while installing XP on newer Sata hard drives..And moreover your MultiOEM Windows XP Dvd will become universal as it will have drivers for almost all types of hardwares... So the steps for integrating this method is as follows..... XP Source ---> Updatepacks+Addons --->MultiOEM Addon ---> Driverpacks I get all the way to driverpacks then it goes wrong, I fed RyanVM tool the driverpacks and things go wrong. If needed I can show the logs for this stage.
Cheers for that, I finally worked this out for myself. The guide was correct on Page 1, but not fleshed out a lot for newbies.
FYI: Used Method 2 from 1st post. Just tried this disk I made and it did not work right. XP loads onto my test Acer machine and then asks me to activate. I verified the Acer 8920G has the XP Bios string needed to activate and the tool said was good (the freedos ISO tool option 1) During the XP install the script from Mr Smartypants loads and copies the logos for the Acer system. Then halfway through it asks you for the license key... odd I thought as the script should have loaded this? Carried on regardless and got a working Windows Desktop. Within another minute, Windows demands to be activated... so I check in C:\ and read the oemscan log and last few lines read: Code: Reading BIOS Memory Matched AcerSystem Checking Authenticity of OEMBIOS files CAT file missing D:\OEM\FILESETS\XP\717B6EF3\OEMBIOS.CAT Attempting to move OEM logo files from "D:\OEM\Logos\AcerSystem" I thought to make an OEM SLP DVD you needed the compressed files, so can I just ignore this CAT file missing as it is there as OEMBIOS.CA_ I have kept all the logs from making the DVD so can insert here if needed. Would appreciate any help that can be given to me.
Ah glad it is not just me then. Seems we are in same boat I will have to drill into the code/scripts and see what is wrong. If you need to bounce ideas off me, or use me for testing then let me know. Have been doing IT for 16+ years, so I am happy to run tests on what you need. EDIT: Seen some things I missed, and know I made wrong for sure. So now I am testing in VM to see how it goes, then if it loads I will test in real machine tomorrow. Watch this space and sorry if we have gone OT but this Multi-OEM in one disk is proving to be little more complicated than the steps in post #01.
Will do.. I have a XP OEM ISO on my computer from march 2010 i think. I used step method #2 and it worked fine after some trouble. What happened now and why i get these problems I dont know..
Mad question for you... On this forum in post #1 it says to use COMPRESSED BIOS files to make SLP CD On siginetsoftware it says to use UNCOMPRESSED BIOS files Quote: 5. Add the four decompressed OEMBIOS.* (bin, sig, dat, cat) files you downloaded to the Sony folder you just made (XP filesets go in FILESETS\XP\*, 2003 filesets go in FILESETS\2003\*.) So who is right on this one... anyhow I have burned 3 coasters so now going to make a 4th one and see how this works.
Why not test in the VM...You burn no coasters that way.. To make an OEM disc, you add compressed files to the i386 folder. For the multioem, you add UNcompressed files to the manufacturer folder in the multi pack (Filesets).. VMWare has a bios you can add all oem strings to and test your discs..You can easily add oem string to vbox as well, it is free (Officially). (EDIT): All bullets on the first post of this thread state uncompressed files to be used. Do not confuse the multi oem file folder with simply making an OEM SLP disc (Single OEM such as Dell, HP, Sony, etc.)
I did try a few times to add OEM strings to vbox, but each time it failed to activate. I do use the latest and tried one of the automatic patch tools to add the string needed, but failed saying it could not find it. So I gave up and burned them instead. I can now have a few cups of coffee at same time Thanks for your time. Still wondering which is right though in regard to compressed/uncompressed BIOS files I am not one to give up so will get there soon. Edit: sorry was in middle of XP install, seems you are saying compressed are correct. I am making a multi-OEM disk so the guides say keys go in the OEM folder not the i386.
I am saying that if you are using the multioem package and the oem folder, then you use the uncompressed files. You need to adjust the winnt.sif file to allow the install to use the contents of the OEM folder at the root of the cd. To make a single oem disc, say an HP disc, you would only use one set of compressed files.. Seems you are confused about more than the difference between the single OEM:SLP activation and the multioem package in the OEM folder..no offense intended.. If you are using the multioem package by _smartypants than you would not need any compressed files at all, just the uncompressed files in the appropriate folder tree placed in the OEM folder
Many thanks for the time to reply. Yes I have read a few guides and there was a contradiction about compressed or uncompressed BIOS files simply. I have had another go at finding the string in the vBox DLL and found it has a different value which is why search and replace could not find the string. Not to worry would take a lot to offend me I done a load of reading and have baked my own thing now, just to test it now in the vBox and see how it goes.
The files I had might've been compressed ones, you need uncompressed for Multi OEM's.. I will upload a mirror of both compressed and uncompressed files to the same folder and delete the "autokit.rar"
Where did you find the instructions to use COMPRESSED BIOS files in the first post of this thread... As Far as i can see it reads as following... Anyways I am glad that you sorted it out..