[Bezalel]

vpn-user, on Jun 5 2006, 04:15 PM, said:

I replace the 4 files after install during the sysprep process using wfpreplace.exe to get around windows file protection. That way Windows is preactivated before Windows Welcome page appears.

This method wouldn't work for me bacause at T-9 setup starts a full scan which would just restore the origional files. You might be able to use parts of my script to determine the manufacturer and call wfpreplace.exe.

My goal at this point is to replace the files and have the replacement files protected by WFP.

[vpn-user]

Bezalel, on Jun 5 2006, 09:58 PM, said:

vpn-user, on Jun 5 2006, 04:15 PM, said:

I replace the 4 files after install during the sysprep process using wfpreplace.exe to get around windows file protection. That way Windows is preactivated before Windows Welcome page appears.

This method wouldn't work for me bacause at T-9 setup starts a full scan which would just restore the origional files. You might be able to use parts of my script to determine the manufacturer and call wfpreplace.exe.

My goal at this point is to replace the files and have the replacement files protected by WFP.

I circumvent this problem by copying the I386 folder to the systemdrive and change all necessary setup paths in registry. And the I also replace the oemfiles in this folder which then is the source where WFP will get its replacement files from.

Can you send me your script, anyway? Automating the whole process would be nice

BTW I replace the files AFTER setup during the sysprep process which means after T-0 :-)

This post has been edited by vpn-user: 05 June 2006 - 03:06 PM

[Bezalel]

vpn-user, on Jun 5 2006, 05:03 PM, said:

I circumvent this problem by copying the I386 folder to the systemdrive and change all necessary setup paths in registry. And the I also replace the oemfiles in this folder which then is the source where WFP will get its replacement files from.

Replacing the oembios files in the source won't make WFP use your replacement files (somehow it knows that the replacement files aren't origional) it only prevents WFP from finding the origional files to restore.

vpn-user, on Jun 5 2006, 05:03 PM, said:

Can you send me your script, anyway? Automating the whole process would be nice

The current version is located at http://www.msfn.org/board/index.php?s=&sho...ndpost&p=512579.

[vpn-user]

Bezalel, on Jun 6 2006, 12:30 AM, said:

Replacing the oembios files in the source won't make WFP use your replacement files (somehow it knows that the replacement files aren't origional) it only prevents WFP from finding the origional files to restore.

You' re right. But I don' t really care about WFP because I also use patched uxtheme.dll, tcpip.sys and legitcheckcontrol.dll (all selectable within installer)...

[RogueSpear]

Bezalel, on Jun 5 2006, 03:58 PM, said:

My goal at this point is to replace the files and have the replacement files protected by WFP.

You'll need to somehow register the associated .cat file with WFP. I remember seeing a thread about this issue over RyanVM's forums quite some time ago. You may want to check out certutil.exe (by default located in System32).

[Bezalel]

Sonic, on Jun 1 2006, 04:59 PM, said:

Posting oembios file are okay, isn't it ?
A small package will be interesting ...

I am creating a repository for OEMBIOS files. The entrypoint will be http://www.oembios.net. I don't have the hardware to test these files so PM me letting me know if they work for you or not (if not please specify your PCs model#). If you nedd a specific OEMBIOS set or have one to offer please PM me. I have the following sets and will post them as they are ready:

Acer
Compaq
Dell
Dell (Server)
E-Machines
HP
IBM
Samsung
Sony
Toshiba

Note: I will not be able to reply to all messages but will read them all.

This post has been edited by Bezalel: 29 November 2006 - 09:30 AM

[ZaForD]

Anybody else like the idea of collecting Oemlogo.bmp, Oeminfo.ini and Oem Wallpaper's ?
Incase they can be added to the script later.

[Bezalel]

ZaForD, on Jun 6 2006, 07:58 AM, said:

Anybody else like the idea of collecting Oemlogo.bmp, Oeminfo.ini and Oem Wallpaper's ?
Incase they can be added to the script later.

I plan to add oemlogo.bmp support in later versions and to genererate oeminfo.ini from the SMBIOS table. I have no immediate plans for wallpapers but will provide a method to call a manufacturer specific batch files.

[ZaForD]

Quote

I plan to add oemlogo.bmp support in later versions and to genererate oeminfo.ini from the SMBIOS table.

OK, i'll keep collecting up the Oemlogo's then, i might not bother with the wallpapers. It maybe going a little too far.

[SecretNinja]

Manufacturer: Acer
Model: TravelMate C300
41636572 20202020 20202020 202020

[bober]

i have tested HP pro and home on a HP Pavillon. both work without problems.

my source for Gateway has not come thru,yet.

[FreeStyler]

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

This post has been edited by FreeStyler: 12 June 2006 - 03:03 AM

[ZaForD]

@Bezalel
I was talking an Admin at work about this thread, while trying to get info on the servers.

He asked an interesting question, that I said i'd pass on;
Could the scripts in the activation.rar be limited to using only the first 8 or 10 digits of the Manufacturers Hex ?
That way you shouldn't need a load of OEM filesets for Dell's, Acer's and HP's.

[Bezalel]

ZaForD, on Jun 7 2006, 07:03 PM, said:

Could the scripts in the activation.rar be limited to using only the first 8 or 10 digits of the Manufacturers Hex ?
That way you shouldn't need a load of OEM filesets for Dell's, Acer's and HP's.

You can always add the following line to your own code

MfgHex=Left(MfgHex,8)

I will not be adding this for the following reasons:
It is possible that a manufacturer uses different oembios sets for different lines. (if this becomes an issue I can always rewrite the code to include the model#)
If you are using identical sets they will only be stored once on the CD
Limiting your self to 8 characters only compares the first 4 charachters of the name and once I go over 8 charachters, I don't care how far I go

If there are users who have a problem with long file names than I'd suggest hashing the manufacturer string with CRC32 (I was origionally hoping to use CRC32 but vbscript doesn't have the correct datatypes to perform CRC32)

[ZaForD]

Thanks Bezalel, i'll pass on the info.

[druiddk]

Packard Bell are AFAIK manufactured by NEC.
The Packard Bell computers i have seen says NEC on the XP license label

Has anyone actually gotten this to work automaticly yet?

This post has been edited by druiddk: 08 June 2006 - 02:36 AM

[FreeStyler]

ZaForD, on Jun 8 2006, 01:03 AM, said:

@Bezalel
I was talking an Admin at work about this thread, while trying to get info on the servers.

He asked an interesting question, that I said i'd pass on;
Could the scripts in the activation.rar be limited to using only the first 8 or 10 digits of the Manufacturers Hex ?
That way you shouldn't need a load of OEM filesets for Dell's, Acer's and HP's.

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?

[ZaForD]

FreeStyler,
I have both Toshiba and IBM pro filesets dated 2001, if thats any good to you ?

[vpn-user]

This just came into my mind: What about product keys?!?

Can you use just one OEM key for all manufacturers or do I have to somehow find out each manufacturers master key?

I wonder because WGA also checks the product key and it would be easy for Microsoft, to have a list of master keys matching only to appropriate manufacturer.

Is there a master key list or is this completely unnecessary?

[Bezalel]

vpn-user, on Jun 8 2006, 08:06 PM, said:

This just came into my mind: What about product keys?!?

Can you use just one OEM key for all manufacturers or do I have to somehow find out each manufacturers master key?

I wonder because WGA also checks the product key and it would be easy for Microsoft, to have a list of master keys matching only to appropriate manufacturer.

Is there a master key list or is this completely unnecessary?

The keys are mostly interchangable between manufacturers. (I've heard of isolated cases where keys were not interchangable but I am more inclined to beleive there was a user error in these cases.) For the benefit of businesses that no longer have access to the manufacturer's keys there are a few keys published at http://www.microsoft.com/technet/prodtechn...y/oempreac.mspx. Before Feb 2005 manufacturers did not always include their keys in the recovery media because the sticker-key could be used to activate online. (They only cared about the first boot experiance, not recovery experiance.)