OEMScan - Automated Multi Manufacture Pre-Activation Utility

[FreeStyler]

>I have the files for Fujitsu Siemens-->http://rapidshare.de/files/37244969/FUJITSU.rar.html

This is Fujitsu set 10045CFA. You need to decompress them before taking the CRC32. Renaming them to remove the underline does not decompress them.

Nothing to download here, move along!

ok, I see...

If I write " expand OEMBIOS. BI_ OEMBIOS.BIN " ,the bin file will be ok to use?

@FreeStyler

Thankyou, that was good help for me!!!

@Floppy, yes you need them to expand like that, eg.

expand oembios.cmd

expand oembios.bi_ oembios.bin
expand oembios.ca_ oembios.cat
expand oembios.da_ oembios.dat
expand oembios.si_ oembios.sig

Edited October 18, 2006 by FreeStyler

[Floppy]

@FreeStyler

Ok, I have done that.

In the oemscan.ini I have added;

;
;	Fujitsu Siemens OEMBIOS Files
;	SLP = FUJITSU
;
[FUJITSU]
PATH=".\FUJITSU\"
RANGE=""
MATCHARG=""
CMD=""

;
;	Fujitsu Siemens OEMBIOS Files
;	SLP = FUJITSU-PC
;
[FUJITSU-PC]
PATH=".\FUJITSU\"
RANGE=""
MATCHARG=""
CMD=""

;
;	Fujitsu Siemens OEMBIOS Files
;	SLP = Fujitsu Siemens
;
[FUJITSU SIEMENS]
PATH=".\FUJITSU\"
RANGE=""
MATCHARG=""
CMD=""

I have copied the files to "FUJITSU" directory.

What do I need this info for?<red>

Manufacturer: Fujitsu Siemens

Model: K series

46554A49 54535520 5349454D 454E53

Edited October 18, 2006 by Floppy

[FreeStyler]

You do NOT need that info

[Floppy]

Here is the expanded ver. of Fujitsu Siemens OEMBIOS Files.

http://rapidshare.de/files/37304961/Fujitsu_Siemens.rar.html

Can I execute the oemscan.exe in the cmdlines.txt at T-12?

Edited October 19, 2006 by Floppy

[FreeStyler]

Yes you can, eg.

$OEM$\CMDLINES.TXT

[commands]
"oemscan.exe"

[Floppy]

Yes you can, eg.

$OEM$\CMDLINES.TXT

[commands]
"oemscan.exe"

Thanks, do not give up on me now!!!

I have one last question before testing live on a Fujitsu Siemens PC....

Ins winnt.sif file, I have this;

[UserData]
	ProductKey=""

In that way I have to type in the key, and then the unattended instalation goes seamless.

My DVD will contain many OEMBIOS files (DELL,HP,....).

What do I enter for "ProductKey="""....?

Edited October 19, 2006 by Floppy

[FreeStyler]

That depends....if you use oobeinfo.ini to load manufacturer specific SLP key into the system as i mentioned a few post back this can be any OEM COA (single user license) or SLP product key.

Else you can use any XP Home Factory key and for XP pro you can peek here

[Floppy]

Hey

I have tried this on a Old COMPAQ PC (6 years old)

I have this;

oemscan.ini

;
;	HP / Compaq OEMBIOS Files CRC32 = 06D652A4, CD4E1902, 00A1EECB
;	SLP = Compaq, Hewlett, HP Pavilion, Hewlett-Packard
;
;CRC32 = CD4E1902
[Compaq]
PATH=".\HPQ\"
RANGE=""
MATCHARG=""
CMD=".\HPQ\OEMCOPY.CMD"

oemcopy.cmd

copy oemlogo.bmp %SystemRoot%\System32\
copy oeminfo.ini %SystemRoot%\System32\
copy oobeinfo.ini %SystemRoot%\system32\oobe
copy OEMLOGO.JPG %SystemRoot%\system32\oobe\images

The oemlogo.bmp & oeminfo.ini works fine!

I have a unattended WinXP Home cd.

After OS install I run oemscan.exe, it identifies COMPAQ, and seems to do it's thing.

Then I reboot, but the aktivation thing stays on.

Then I manualy copied the 4 OEMBIOS files from HPQ to their directories.

Then I reboot, but the aktivation thing stays on.

The oobeinfo.ini looks like this;

[Version]
ProductKey="MK48G-CG8VJ-BRVBB-38MQ9-3PMFT"

[Branding]
OEMName="PC"
OEMLogo="OEMLOGO.JPG"

It does not work....is the pc to old?

Can some one see somthing wrong?

Help

Edit:

I used a tool called rockxp.exe(key Changer),Used the same key as before--->activation ok...

Does this mean that the oobeinfo.ini did not come through?

Edited October 20, 2006 by Floppy

[xehqter]

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

[FreeStyler]

oobeinfo.ini

[Floppy]

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

I DL'ed magicaljellybean and the key stays the same, that's a good sign for me because then the key works.

I had another key in wiNT.sif.....or should I leave that key blank?

oobeinfo.ini

Thanks, I have read most of it...I will get it .....slowly B)

[Floppy]

Success

On a ComPaq pc.

No key in winnt.sif

and;

cmdlines.txt

COMMANDS]
"./Preaktiver/oemscan.exe"

Thanks to FreeStyler xehqter for helping me out

Edited October 21, 2006 by Floppy

[sn3ak]

xehqter, first let me say thank you for your work on OEMScan, it has been extremely helpful to me.

I am having a problem with oemscan v1.3 crashing on some machines. the hardware seems to be good, and passes my other diagnostics. v1.21 works fine on these machines. how can we go about trouble shooting this?

as far as it gets is OEMBIOS Scanner v1.3 by Jeremy (xehqter), then windows pops up with the normal send bug report message.

Unfortunately these are customer machines, and I have just sent out the last one that had this problem, but I would like to be prepared for the next time it comes up.

[xehqter]

xehqter, first let me say thank you for your work on OEMScan, it has been extremely helpful to me.

I am having a problem with oemscan v1.3 crashing on some machines. the hardware seems to be good, and passes my other diagnostics. v1.21 works fine on these machines. how can we go about trouble shooting this?

as far as it gets is OEMBIOS Scanner v1.3 by Jeremy (xehqter), then windows pops up with the normal send bug report message.

Unfortunately these are customer machines, and I have just sent out the last one that had this problem, but I would like to be prepared for the next time it comes up.

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"

Edited October 24, 2006 by xehqter

[sn3ak]

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"

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.