[Released] OEMScan Addons v1.7 Beta2

[Siginet]

I am in the final testing stages of my latest OEMScan addons. I have added a new executable that I created called "OSTYPE.EXE".

OEMSCAN.EXE is run at SVCPACK Stage (T13). Then OSTYPE.EXE is run next in the SVCPACK Stage (T13). OSTYPE.EXE verifies that a successful OEMSCAN.EXE was run... then it places itself in the RunOnce portion of the registry. When the computer boots into windows for the first time... OSTYPE.EXE is run in the background to change the product key you specify in OSTYPE.ini (Which resides in the folder holding the OEMBIOS.* files that were used. OSTYPE.ini will hold the slp keys for each OS you wish to pre-activate. It also looks for a directory called "OEMLogos" to copy logo files to the system as well.

So there is no need for a winnt.sif file. But at least one slpkey will be needed to pre-activate windows.

Here is a barebones version for you guys to test. It has the HP/Compaq logos in it allready.

http://integrator.siginetsoftware.co...?addons&id=166

you just need to add the oembios.* files into the svcpack\HPQ and svcpack\pavilion directories.

CD4E1902 FileSet goes in HPQ
06D652A4 FileSet goes in Pavilion

Inside the SVCPACK\HPQ\OSType.ini and SVCPACK\Pavilion\OSType.ini file you will need to edit:

[XP Professional]
SLPKey = 11111-22222-33333-44444-55555

[XP Home]
SLPKey = 11111-22222-33333-44444-55555

With valid SLP Manufacture Keys for each specific OS.

[mr_smartepants]

Sweet! I look forward to testing this.

So there is no need for a winnt.sif file. But at least one slpkey will be needed to pre-activate windows.

OK, I'm confused. If there's no need for the winnt.sif file, then where does the key go? Does the key HAVE to be slp or can any key be used to satisfy OOBE.
Questions I'm sure will be answered once I get my hands on this.
Thanks Siginet

[Siginet]

It is based on my 1.4.1 addons. which do not require winnt.sif either. You can install and when asked for a key you can put in any slp key for it to pre activate. Then at first boot it will change the key to the key you have listed in your ostype.ini file for the specified os type. You have to use an slp key to activate.. but you don't need detachedprogram or winnt.sif to do it.

[dolivas27]

Oh I can't wait to test this one out excellent work Siginet you are really on a roll .....:-D

[TwoJ]

Thats great Siginet

I'm actually a bit preferential to setting the key at t39, but if everything works at t13 then that works for me!

could you also include the Cicero bios files that FreeStyler got (thanks again for that).

will the ostype.ini file reside in the $oem$ folder of each OS?

[Siginet]

No the files will remain in the OEM folder at the root of the disk. So that this method is compatable with one OS or Multiple OSes as well.

So far my tests are working perfectly. I think I'll upload a beta OEMSCAN ADDON today. What manufacture do you all feel would be the best one to test with. One that we all have. I have been doing my tests with HP/Compaq.

Actually I'll upload a barebones version and you guys can add the oembios files and logos to it yourselves.

[Siginet]

I added a link to a BareBones OEMScan Addon v1.7 to the top post.

[mr_smartepants]

Oooooohh Yeah!
I'm all over it!

Oh, Siginet, you might want to remove those keys from the OSType.ini files.
It's OK, I won't tell.

[Siginet]

Oh No! I could have swore I removed the keys.

I'll remove the link now then.

Untill I can get home and fix it.

[FreeStyler]

@Sigi

How did you manage to get the different OS types using AutoIT, WMI?
Any chance i can get the Source code for that procedure?