[Bilou_Gateux]

RogueSpear, on Sep 27 2006, 09:44 PM, said:

Just wondering if there would be an advantage to running this from DetachedProgram rather than svcpack or cmdlines. With some things in Windows setup, the earlier the better.

RIS install + run @DetachedProgram =

ristndrd.sif

[GuiUnattended]
DetachedProgram=".\system32\cmd.exe"
Arguments="/Q /C FOR /F %I IN (%SystemRoot%\SYSTEM32\$WINNT$.INF) DO (FOR %J IN (%I\$OEM$) DO (IF EXIST %J (%J\NirCmd.exe exec hide %J\OCA_MRK.CMD)))"

OCA_MRK.CMD

@FOR /F %%a IN (%SystemRoot%\SYSTEM32\$WINNT$.INF) DO (FOR %%b IN (%%a) DO (IF EXIST %%b (SET DOSPATH=%%b)))

:oemscan
%dospath%\$oem$\oemscan.exe>%systemdrive%\oemscan.log
%dospath%\$oem$\oemscan.exe

oemscan.log

Quote

OEMBIOS Scanner v1.21 by Jeremy (xehqter)

Matched: Compaq
Checking Authenticity of OEMBIOS files
OEMBIOS files pass Validation
Copying C:\$WIN_NT$.~LS\$oem$\HP\OEMBIOS.BIN : Successful
Copying C:\WINDOWS\system32\DllCache\OEMBIOS.BIN : Successful
Copying C:\$WIN_NT$.~LS\$oem$\HP\OEMBIOS.SIG : Successful
Copying C:\WINDOWS\system32\DllCache\OEMBIOS.SIG : Successful
Copying C:\$WIN_NT$.~LS\$oem$\HP\OEMBIOS.DAT : Successful
Copying C:\WINDOWS\system32\DllCache\OEMBIOS.DAT : Successful
Importing C:\$WIN_NT$.~LS\$oem$\HP\OEMBIOS.CAT : Successful
OEMBIOS Scanner v1.21 by Jeremy (xehqter)

Congratulations Jeremy for your OEMScan utility.

[xehqter]

Version Bump

[FreeStyler]

Working great, thx for the update

One question though, do we need to process the gateway files in a ordered way?
Lets say first scan for the specific range and if that fails scan for the whole range with for example the different set?
eg,

[GATEWAY]
PATH=".\oemfiles\GATEWAY\A04597C6\"
RANGE="0x000F32F0:20,0x000FE840:20"

[Gateway]
PATH=".\oemfiles\GATEWAY\C86378C7\"

This post has been edited by FreeStyler: 03 October 2006 - 02:31 PM

[Siginet]

FreeStyler, on Oct 3 2006, 05:22 AM, said:

Working great, thx for the update

One question though, do we need to process the gateway files in a ordered way?
Lets say first scan for the specific range and if that fails scan for the whole range with for example the different set?
eg,

[GATEWAY]
PATH=".\oemfiles\GATEWAY\A04597C6\"
RANGE="0x000F32F0:20,0x000FE840:20"

[Gateway]
PATH=".\oemfiles\GATEWAY\C86378C7\"

I was wondering the same thing. Allthough I know in autoit if you have 2 sections with the same name in an ini file only the first instance is read. I am not sure with C+ though. If this is the case I suppose we could search for:

[GATEWA]
PATH=".\oemfiles\GATEWAY\A04597C6\"
RANGE="0x000F32F0:20,0x000FE840:20"

[Gateway]
PATH=".\oemfiles\GATEWAY\C86378C7\"

What do you think xehqter?

[xehqter]

@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\"

This post has been edited by xehqter: 03 October 2006 - 07:06 PM

[RogueSpear]

xehqter, on Oct 3 2006, 08:59 PM, said:

Today I came across a gateway 450MHZ P3 with the latest bios (March 2000) that didn’t have the word gateway in the bios.

I come across a ton of Gateway computers from that era. That seems to be when they really made long lasting machines. Unfortunately I have noticed the same thing with Toshiba and HP/Compaq laptops that are from around 2000. I don't think anybody started to make their BIOS with the royaly program in mind until Dell started to do it.

[FreeStyler]

xehqter, on Oct 4 2006, 02:59 AM, said:

@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\"

Thx for clearifying

[twig123]

I just activated a system with your OEMSCAN utility (which is a life saver) and I noticed that for some reason it makes a copy of the 'OEMBIOS.CAT' file in the root of the C: drive... anyone else notice this?

[FreeStyler]

xehqter, on Sep 27 2006, 04:08 PM, said:

@vpn-user: The original OEMBIOS.CAT file is backed up to SystemDrive when it validates the OEMBIOS files being copied over. If validation fails it restores the original .CAT file. The file should be deleted if validation passes. Something to fix in the next release.

Do you use the latest (1.3) version? it looks like your using 1.21

[xehqter]

discountpc, on Oct 11 2006, 02:46 PM, said:

I just activated a system with your OEMSCAN utility (which is a life saver) and I noticed that for some reason it makes a copy of the 'OEMBIOS.CAT' file in the root of the C: drive... anyone else notice this?

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.

[twig123]

FreeStyler, on Oct 11 2006, 03:51 PM, said:

xehqter, on Sep 27 2006, 04:08 PM, said:

@vpn-user: The original OEMBIOS.CAT file is backed up to SystemDrive when it validates the OEMBIOS files being copied over. If validation fails it restores the original .CAT file. The file should be deleted if validation passes. Something to fix in the next release.

Do you use the latest (1.3) version? it looks like your using 1.21

DOH! I'm sorry guys, I coulda swore I had the latest... I guess I'm just losing my mind, its been a long week...
Thanks

PS: any chance of a silent switch in a future revision?

This post has been edited by discountpc: 11 October 2006 - 06:20 PM

[merlin01]

hello,

I hope I don't get flamed or anything, but I've got to ask.

What do I do with oemscan? Do I burn it to the image file for xp and setup will just pick it up or do I need to do something special before trying to install xp?

I offered to reformat a lady's computer for her but she didn't have her dell cd and I figured, no worries I'll use my cd and her key but it will not accept her Dell key. (that's the small version of it).

Thanks

[xehqter]

@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.

[twig123]

xehqter, on Oct 11 2006, 09:50 PM, said:

@discountpc
If you want to hide the window that runs oemscan why not use cmdow or something similar.

Isn't CMDOW only for batch files? because you have to add a line of code to the batch for it to hide, right? or am I just stressin from another long day syndrome?
...from what I have seen this program uses an exe that is coded from C++

[WoRdUp48]

Ok, I am a little bit confused, so I'd just like to ask for some clarification.

I have a laptop that I always have to call MS to get activated. I am using a normal XP OEM CD rather than the crap recovery ones that came with my laptop (I do not like all the extra junk that the recovery CDs have on them). With this tool, can I somehow make it so that I would not have to call MS every time after a format? BTW, when I install I use the original CD key that is on the sticker on the bottom of my laptop, if that helps.

Please go easy on me. I am new at doing any sort of mods to and XP CD; I have not gotten into the unattended stuff, but that will be next.

Anyway, I look forward to your replies.

Thanks!

wordup48

This post has been edited by WoRdUp48: 11 October 2006 - 10:50 PM

[Floppy]

Hey

I have read this topic...and it's still not clear to me.

I have to install winxp on sevral PC's.
And this tool seems to be a workarond for the problem with Special Pc's.

How do I add this to the UnWinXpCd that I use for all my PC's?

Do I have to make on for DELL and one for HP and so on?

I realy want this utillity to work, it's a time saver DeLux.

[xehqter]

@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.ms...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.

[Floppy]

@xehqter

In WinNt.sif under [GuiRunOnce] I install all my apps, can I just add OEMSCAN there. And when I want to activate WinXp, the OEMSCAN has done it's job...?
I have this in wnnt.sif;
[GuiRunOnce]
command9="start.cmd"

[xehqter]

@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.

[Floppy]

xehqter, on Oct 12 2006, 11:28 AM, said:

@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.

Thanks