xehqter

OEMSCAN isn’t compatible w/ Windows 2003 server yet for a few reasons. Time is the big one; I have no time to code on the weekends. Secondly I rarely need to install W2K3 server since it’s pre-installed on the boxes we order. OEMSCAN won’t work with vista so I’m forced to update it but things need to slow down @ work first.

Post #1 oemscan_v1.3.1.rar ( 20.22k ) Number of downloads: 342

I use the same SLP key for each manufacture so I’m not verse with the ChangeKey scripts. What happens if you run 'cscript changekey.vbs .\HPQ\serial.txt' from the command prompt?

Don’t know what to tell you, during what part of setup are you running oemscan.exe and secondly does it also fail if you run oemscan after the install is finished?

@Floppy OEMSCAN uses the CreateProcess API to execute whatever is in the string. PromptKey.vbs isn't an executable file, it’s a script. You need to run the interpreter wscript which will parse/run the script. [SM] CMD="wscript PromptKey.vbs"

Sorry, I thought you were asking for a XP Home SLP key. Windows XP will install with SLP CD Keys but won’t activate a non Royalty (Motherboard & Oembios) system, I can see why the admin’s don’t want us to publish the keys, but it makes it allot easier to say, Just use this key for home, and this key for pro. To correct Bezalel’s typo, you need to use the setupp.ini from an OEM CD.

SLP Keys are special CD Keys which are issued to Royalty OEM Manufactures. These CD Keys are REQUIRED for activation using the OEMBIOS Method. SLP CD Key’s ARE NOT COA Sticker keys on the side of the computer. SLP CD Keys won’t activate unless you have a Royalty OEM Motherboard & OEMBIOS file set that match the motherboard. SLP keys aren’t locked to the oembios files. You can use a dell slp key on a gateway system. You MUST use a Pro SLP key with a XP Pro installation and a Home SLP key with a XP Home installation. Some discussion was raised that Microsoft in the future could match the manufactures issued slp keys to the system however some manufactures use other manufactures keys so I think its unlikely. Some people have written scripts to go along with OEMSCAN which change the cd key for each oembios set. I don’t know anything about them, so don’t ask. Giving out SLP CD Keys appears to be against forum rules so don’t ask. Oembios file sets aren’t dependent on the version of XP your installing. The same file set will work on Pro or Home. Royalty OEM’s inject a string into the bios, the OEMBIOS.DAT file tells Windows the string and string location in the bios. No you can’t mix and match different OEMBIOS parts, all four files must be from the same set. The OEMBIOS.DAT file is encrypted, “some” people have tools which can decrypt the file this is how they know the SLP strings. Don’t ask for the tools you won’t get them. OEMBIOS File sets are identified by the CRC32 hash of the oembios.cat file. Rapid share is deleting unpopular files from Bazalel’s repository. You can copy the 4 oembios files (oembios.bin, .cat, .sig, .dat) from a factory installed copy of XP to get that OEM's FileSet if you can't find it. To add a set to oemscan, acer for example. Create a directory in the same directory oemscan.exe resides and name it Acer. Download 717B6EF3.RAR from Bazalel’s repository and extract its contents to the Acer directory. Open oemscan.ini in notepad and add the following. [AcerSystem] PATH=".\Acer" That’s it. 'AcerSystem ,AcerSystem ' is a comma separated list of SLP Strings that Windows activation checks. Two instances of AcerSystem means there are two memory addresses that Windows XP Checks. Refer to http://www.msfn.org/board/index.php?showto...mp;#entry534097 for a list of SLP strings and CRC’s. No you don't have to create Multiple entries for AcerSystem, just one for each unique name. You can run OEMSCAN.EXE any time during setup, be it from cmdlines.txt, svcpack.inf, or RunOnceEx. You can even run it after XP has installed. Auto Accept Royalty Keys? I use winnt.sif and have one static SLP key for Pro & Home.

I see 06D652A4 on allot of 2004/2005 Compaq laptops that won't activate with CD4E1902

Like I said above if it matches Hewlett or Compaq use CD4E1902. Some HP systems embed the word Compaq in their BIOS, its normal. If that isn’t confusing some Compaq’s use “HP Pavilion”

oembios.cat is used to identify the set NOT oembios.bin. Choose the file set that corresponds to the manufacture of your computer. HP is tricky, it could be either 06D652A4 or CD4E1902. If you want to know for sure download oemscan and run it in a command prompt. If it says that it matched “HP PAVILION” get 06D652A4 and if it says it matched Compaq or Hewlett get CD4E1902.

Use this entry in the oemscan.ini file for the ASUS_FLASH (B20C65BF) OEMBIOS file set to avoid false positives. In your oemscan.ini file did you search for asus or asus_flash? [ASUS_FLASH] PATH=".\Asus" RANGE="0xFC000:3FFF"

And the SLP String is MEI_CF not confusing at all

Are you using version 1.3? There was a bug in 1.2.1 which reported false corruption. I checked ASUS FLASH with 1.3 and they passed validation. If you used a CD maybe they were burned incorrectly, check the checksum’s on the CD. OEMBIOS.CAT B20C65BF OEMBIOS.DAT 8C3FD204 OEMBIOS.SIG 05858B8E OEMBIOS.BIN C904A0D0

@sn3ak While debugging v1.3 I commented a line of code that caused OEMSCAN to fail if it couldn't disable Windows File Protection that was present in v1.2.1. I uncommented the line and released v1.3.1, lets see if that fixes the issue you were having. Other then that there is nothing special in this release.

I am using your oemscan.ini with no modifications. no I am not using any modifications to the system. how would I figure out the crash address? the only thing special over a standard OEM install, is call a batch file to install windows updates. but I have tried with those disabled as well, and I think I stated before that it's been working perfectly, other then these few machines. When the crash dialog appears you have two options. You can send a crash report or see what’s in the crash report. Click on see what’s in the crash report you should get a box with a bunch of memory addresses/dumps and dll files.. That’s the data I need.

Well, let's start simple; attach your oemscan.ini file. Are you using a modified sfc_os.dll file? Try installing using an unmodified XP cd and then running oemscan.exe. If it crashes again post the crash address. See if oemscan.exe crashes in dry run mode "oemscan.exe /d"

If you run Magical Jelly Bean's Key Finder after the unattended install does it have a different CDKey?

@WordUp48 I have no idea, that’s out of the scope of this topic @Floppy please read this the first paragraph of System Locked Preinstallation (The second paragraph is incorrect) and Multi Manufacturer Pre-Activation I’ll repeat myself again, YOU CAN’T USE THE COA STICKER KEY, YOU MUST USE A SLP CD KEY!!! You can find an SLP key on the internet, in the winnt.sif file of a recovery cd, or by using a key retrieval tool on a factory installed copy of XP. OEMScan contains a sample oemscan.ini file which supports those Royalty OEM’s, you can modify to file to your liking, adding or removing vendors. I don’t distribute the OEMBIOS file sets, you have to download them. Goto Bezalel’s repository, the filename is the CRC32 hash of the OEMBIOS.CAT file, the text below it is the SLP String that the OEMBIOS file set contains. Extract the files to their respective directories. If you’re using it on an HP you should get 06D652A4 which goes in the Pavilion directory and CD4E1902 which goes in the HPQ directory. Secondly you must change the key to an SLP Key. Then run oemscan.exe, assuming it finds a match, reboot and you shouldn’t see any more prompts for activation. With an unattended OEMSCAN cd it goes like this. 1. The SLP cd key goes in the winnt.sif file. (unless you manually want to enter the same key each time) 2. Somewhere in your unattended scripts you run oemscan.exe which uses the list of SLP strings in the oemscan.ini file to match to your bios. If it finds a match it copies the corresponding oembios file set over. 3. You boot into windows with no activation prompts If you still don’t understand and want a simple solution use Siginet’s OEMScan RVM Integrator Addon

@Floppy Just copy the royalty oembios files to the corresponding manufacture directory and run oemscan.exe that’s it. However you must be using a SLP (Royalty OEM) CD Key, NOT the cd key on the sticker attached to the case. It can be run during setup, after setup, whenever you choose.

@DiscountPC CMDOW /RUN /HID OEMSCAN.EXE @WordUp48 OEMSCAN is for techs that use the OEMBIOS activation method on different Royalty (ie: Dell, Gateway, Compaq, etc) systems. Before techs had to create a separate install for each manufacture, now they have one install and OEMSCAN copies over the correct files for each OEM. If you’re not installing XP daily, you might consider the Backup Activation Method described here http://unattended.msfn.org/unattended.xp/view/web/29/ @Floppy I don’t know what UnWinXpCd is; there are different ways to run applications in Unattended Windows. With OEMSCAN you don’t need to create multiple CD’s.

@discountpc If you want to hide the window that runs oemscan why not use cmdow or something similar. @merline01 oemscan is run during or after the windows xp setup to copy over the royalty OEMBIOS files. First Windows XP must be using a SLP (Royalty OEM) CD Key, this is NOT the key located on the side of the computer. Second you need the Royalty OEMBIOS file set for dell which can be obtained from Bazalel’s repository, simply extract the files into the dell directory and run oemscan.exe If you want to integrate OEMSCAN into an XP CD Siginet has a fantastic add-on for the RyanVM Integrator called OEMScan v1.21 RVM Integrator Addons which will save you the trouble of writing a script to run OEMSCAN during setup.

1.3 fixes that bug. The cat file is a backup copy of the systems original oembios.cat file which is used to restore incase validation fails on the Royalty OEMBIOS file set. Version 1.3 deletes the file if validation passes.

There are utilities that read the OEMBIOS.DAT file and output the unencrypted data, knowing the addresses contained within isn’t essential for a few reasons. If a bios contains “Dell Inc” chances are very good it’s a dell. With the exception of gateway all the current oembios file sets I’ve seen contain the obsolete filesets addresses and SLP strings. Collecting memory addresses and bios information isn’t vital to the project anymore. Collecting new OEMBIOS file sets is however. A distinction needs to be made between specific ranges and broad ranges. For example HP Pavilion uses 0xF0000-0xFFFFF, that range encompasses most of the bios which includes among other things the DMI Tables. Dell uses 0xFE838-0xFE850 which is a very specific range inside the BIOS not the DMI tables. I’m reluctant to give a detailed answer to your problem because the solution could very easily aid piracy and it isn’t necessary anymore Like Siginet said, the project is slowing down. The next milestones are Windows 2003 & Vista support.

@Siginet & FreeStyler I didn’t even think of that, rofl.. good catch.. Siginet is correct in both instances (Win32API & Gateway). So we don’t confuse the masses here is the correct memory range for A04597C6. Technically it could be RANGE="0xF32F0:40" but in the unlikely event the word gateway is overlapped in both ranges Windows won't activate. The top instance specifically addresses A04597C6. C86378C7 is used for any instance of gateway in the BIOS. Today I came across a gateway 450MHZ P3 with the latest bios (March 2000) that didn’t have the word gateway in the bios. #Specific memory ranges that are present in A04597C6 but not in C86378C7 [Gatewa] PATH=".\oemfiles\GATEWAY\A04597C6\" RANGE="0xF32F0:20, 0xF3310:20" [Gateway] PATH=".\oemfiles\GATEWAY\C86378C7\"

New version of my OEMScan util http://www.msfn.org/board/index.php?showtopic=82638 New Features in V1.3 Fixed bug in BIN/SIG/DAT hash check Removes unused dllcache\oembios.cat file Allows you to pass a custom argument to your script Allows you to specify an exact range to search Changed scan range from 0xF0000-0xFFFFF to 0xE0000-0xFFFFF Dry Run parameter to validate OEMBIOS set. run oemscan.exe /d