FreeStyler

@ZaForD you might find FUJITSU SIEMENS oembios files @ my RapidShare folder Acer Asus BenQ Compaq Dell eMachines Founder Fujitsu Fujitsu-Siemens Gateway Hedy Hewlett-Packard IBM Legend Lenovo Medion Packard-Bell Samsung Sony Targa TCL Tsinghua Tongfang Computer Toshiba Wishlist NEC LG

Official DELL OEM Media, no other modifications besides "our" vender specific oembios files in \$OEM$ folder I'm going to have to try this out. Which files are in your dllcache? if you delete the files in the system32 folder will it replace them with the files in the dllcache or does it ask for the CD? dllcache, only the *.cat file....others are missing there.....what the hell is going on here? It looks like you're not using my current scripts from post 43. http://www.msfn.org/board/index.php?s=&sho...ndpost&p=512579 Which version of my script are you using, or did you modify one of my scripts? No, i'am using current scripts posted in post #43 - No Modifications...i am using "Dutch" Windows XP OEM Media though,so maybe...?

Official DELL OEM Media, no other modifications besides "our" vender specific oembios files in \$OEM$ folder I'm going to have to try this out. Which files are in your dllcache? if you delete the files in the system32 folder will it replace them with the files in the dllcache or does it ask for the CD? dllcache, only the *.cat file....others are missing there.....what the hell is going on here?

Official DELL OEM Media, no other modifications besides "our" vender specific oembios files in \$OEM$ folder

SFC runs a full scan at T-9. If you leave the origionals where SFC can find then they will be restored. Are you sure about that? I just finished a install on HP system with modified Dell Oem CD Media, right files are still in place...thus not being replaced by DELL original oembios.* files SFC at T-9 I md5 compared installed files, it are guaranteed the HP ones and not the original DELL

SFC runs a full scan at T-9. If you leave the origionals where SFC can find then they will be restored. Ah, ok...we do not want that

Can't i just leave to original "dell" set left in place (both in /i386 dir as in dosnet, txtsetup, doesn't it get overwritten by smbios2 command at t9 of the installation process?

Bezalel, above is another example of one which ads multiple spaces after the innitial string, as Acer = 41636572 all 2020202020 20202020 20202020 are useless MfgHex=Left(MfgHex,8) Where could this be added in your script? So adding this, it will check for strings like: Acer, Hewl , Dell , Comp , Tosh, Leno etc etc ? BTW, you told you removed all references of oembios.* files from dosnet.inf en txtsetup.sif and removed all oembios files except oembios.ca_ from /I386 folder What happens if smbios2 can not find matching "oembios" for current install? shouldn't we insert a default set for whenever smbios2 can not find any oembios files matching the System Manufacturer hex-string

This probably means they have "locked" that BIOS string, had this same issue with a INTEL board the other day

Manufacturer: BENQ Model: JoyBook 2100E 42454E51 Manufacturer: Gateway Model: 3250SB CTO PC 4761746 5776179 Manufacturer: Founder Model: Founder PC 466F756E 646572 OEMBIOS files that are still on my "wanted" list: Gateway Packard-Bell NEC LG

Did these 2 come with Windows Xp Preinstalled? i don't know these brands, oembios files? PS, Thx for the LENOVO files

I'm not concerned with disk space since identical files are only written once to the CD. Implementing this would require hardcoding the manufacturer names in the script (I don't want to do this) or maintaining a database (too much work for too little benefit). no, i believe the opposite is true and the benefit of such method will be greater then its limitations... I'll try to explain...if you search manufacturer strings for example "Dell" or as hex "44656C6C" you would have a more variable system that should work on various types of Dell Systems. Dell PC's come with a randomly named '"System Manufacturer" string, one advantage it always starts with "Dell" eg; Dell Computer Corp. Dell Computer Corporation Dell Computer Corporation. Dell Inc. And maybe a whole lot more variations... who knows! Using a technique like this you have a more "reliable" versatile fail safe method that should work on every dell pc Same counts for Acer, eg: Acer Acer, Inc. AcerSystem

I will trim the string to remove leading and trailing spaces in a future version. Partial matches are hard to code and if I ever implement CRC32 it will be impossable to implement partial matches. That would be cool, hey maybe eventually you can make a check that searches for Strings like: IBM, ACER, DELL....this way you would save quite some diskspace as you do not need files for every other variation in "System Manufacturer" names.

Yes, 4C454E4F564F.* files are being used for all pc's where Manufacturer is set to: LENOVO Modelname and type as of yet is not being used in this whole story (might be later)

@Bezalel What if a developer string has additional spaces behind the actual manufacturer string? Lets say I i have a HP box, which is being reported as: Can your script filter out the additional spaces or can you make/modify your script so it checks if, when no exact match is being found files with a partially the same pattern (4865776C6574742D5061636B617264) are being used? FreeStyler

jrf2027, sure i would love to get the "gold" ones BTW, HOME and PRO oembios.* are suposed to be the same (to be sure, can you do a md5 compare on them?) If you have access to the computers the XP runs on, can you dump their BIOS/DMI info for me and send me those text files? Download this tool http://crystalmark.info/download/download....=CrystalDMI.zip Unzip & Run it -> Select “All Information” from the dropdown box -> CTRL + C Then preferably paste (CTRL + P) the copied info into separate txt files. I am currently working with "BIOS" patched Microsoft Virtual PC's to test as many oembios files as i can, for some strange reason up to now DELL, SONY, SAMSUNG oembios files always fail the SLP

Ah, think i have proper files for those, actually i meant older DELL oembios files only.... it doesn't succesfully activate with newer OEMBIOS files from DELL XP Professional SP2 Media

Think this could work if older "sp0 & sp1" OEMBIOS files are being used, newer big vendor machines like newer DELL's are being shipped with SP2 and contain OEMBIOS that use a more "strict" system... I noticed Bezalel files are sp2 files (at least by looking at the date eg; 2004) to test this statement I would like to have some DELL OEMBIOS files that are dated 2001 or something smiliar...anyone can help me with that?

Manufacturer: MEDIONPC Model: MS-7012 4D454449 4F4E5043 Manufacturer: Dell Computer Corporation Model: Dimension 8300 44656C6C 20436F6D 70757465 7220436F 72706F72 6174696F 6E btw, there is a other, easier way to install Windows XP OEM SLP media, on different brands of oem, just pick one brand of which you have valid OEM media and run a batch command / boot floppy and change the DMI BIOS "System Manufacturer" string into (for example: MEDIONPC) the one you have and it will install without problems, no serial, activation or validation required This all can be done with use of a DOS DMI-Editor program that needs to be run from pure DOS, it can run under XP Command_prompt allthough you cannot change anything! Run it using command: dmi /p Press "Page Down" once and edit the "System Information" Manufacturer string, press "Enter" info is being saved to BIOS DMI table, Tested & working on both AMI & AWARD bioses HP pc need two lines edited, eg: "System information" Manufacturer and Base Board information" Manufacturer both with "Hewlett-Packard" there are command-line commands you could run without it showing the gui, eg: dmi /sm "Hewlett-Packard" dmi /bm "Hewlett-Packard" dmi /sm "IBM Corporation" dmi /sm "MEDIONPC" this method is tested with HP ("Hewlett-Packard"), IBM ("IBM Corporation") and MEDION ("MEDIONPC") brand pc's