[OEMScan - Automated Multi Manufacture Pre-Activation Utility]

@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

[OEMScan - Automated Multi Manufacture Pre-Activation Utility]

>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!

@severach

ok, I see...

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

How do I get the CRC32 from this?

I got this from ww.vbs...

Manufacturer: Fujitsu Siemens

Model: K series

46554A49 54535520 5349454D 454E53

@FreeStyler

Thankyou, that was good help for me!!!

[OEMScan - Automated Multi Manufacture Pre-Activation Utility]

@Siginet

I do understand that, I was wondring where the diffrent files where copyed to..that's all.

------

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

Did not find the here, so I extracted them from my CD, hope it helps!

I have a Q. (yes, Iam a newbe)

-------------------------

[Dell System]

PATH=".\Dell\"

RANGE=""

MATCHARG=""

CMD=""

-------------------------

I it possible to enter somthing after CMD="HERE", ...If I have the SLP cd key, so the "SLP WinKey" i changed according to what system that has been found.

If oemscan.exe find a HP system then the CMD="" makes a change for that SLP key.

I have found most of the key's that are mentioned in the oemscan.ini file

[OEMScan - Automated Multi Manufacture Pre-Activation Utility]

If you still don’t understand and want a simple solution use Siginet’s OEMScan RVM Integrator Addon

This was the info I was looking for!!

My English is bad, I know

» OEMBIOS Method

This method requires an existing installation of Windows that has been pre-activated by a Royalty OEM. (If your computer was manufactured by a royalty OEM the COA sticker will have the manufacturer's name or logo.)

Locate on your hard drive the following 4 files:

%SystemRoot%\system32\OEMBIOS.BIN

%SystemRoot%\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\OEMBIOS.CAT

%SystemRoot%\system32\OEMBIOS.DAT

%SystemRoot%\system32\OEMBIOS.SIG

Locate these files, and compress them with MAKECAB, then simply copy the compressed versions into the I386 directory in your Windows Setup Source folder on your hard drive.

[OEMScan - Automated Multi Manufacture Pre-Activation Utility]

This is MY slow night....

I still don't get it....

If I have a HP Pc.

The customer has lost his org WinXp Cd's.

But the sticker with the XP number is placed on the PC.

I have made a WinXp Cd that askes me to type in a valid WinXp Key.

I types in the number sticking on the pc label.

Then the instal procedure goes on unattended.

When finished , I want to activate WinXp. It fails, and I have to call MS.

MS gives me a new key, and WinXp is activated .

Is the oemscan.exe made to manage this "problem"?

If Yes then;

See picture. If i run oemscan.exe from that directory, and the Pc is any brand listed, it will work?

[OEMScan - Automated Multi Manufacture Pre-Activation Utility]

@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

[OEMScan - Automated Multi Manufacture Pre-Activation Utility]

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

[OEMScan - Automated Multi Manufacture Pre-Activation Utility]

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.

[Slow instal on VM....]

I haven't seen a localized version yet. Never really tried to find one, though, since the English version is working fine.

@Floppy

Please remove msxml2sp6-kb887606-x86-nor.exe.

The 905474 instals fine.

QFECHECK Verifies the Installation of 905474.

Iwill remove msxml2sp6-kb887606-x86-nor.exe, and test i now

[Slow instal on VM....]

Thanks, will test with the rhight files....

The KB905474, is it not multi langual?

[Slow instal on VM....]

It still takes very long time to start

I have tried to see if there is somthing wrong in my HFSLIP setup..

I have bult my HFSLIP according to:http://users.telenet.be/tc76/winup/_winxp.html

This is what I have;

HFSLIP Version - 60924a

HFSLIP Path - F:\hfslip60924a\

OS in SOURCESS - XP SP2 Norwegian

DRIVER.CAB Updated

CD Install Path - Default

===============================================================================

Files in your FIX folder:

Files in your HF folder:

HMTCDWizard_NOR.exe

msxml2sp6-kb887606-x86-nor.exe

msxml4sp2-kb887606-x86-enu.exe

msxmlcab.exe

Windows-KB890830-V1.20.exe

Windows-KB909520-v1.000-x86-NOR.exe

Windows-KB913433-x86-NOR.exe

WindowsInstaller-KB893803-v2-x86.exe

WindowsMedia-KB911564-x86-NOR.exe

WindowsMedia9-KB917734-x86-NOR.exe

WindowsUpdateAgent20-x86.exe

WindowsXP-KB873339-x86-NOR.exe

WindowsXP-KB885626-v2-x86-nor.exe

WindowsXP-KB885835-x86-NOR.exe

WindowsXP-KB885836-x86-NOR.exe

WindowsXP-KB886185-x86-nor.exe

WindowsXP-KB887472-x86-nor.exe

WindowsXP-KB888302-x86-NOR.exe

WindowsXP-KB890046-x86-NOR.exe

WindowsXP-KB890859-x86-NOR.exe

WindowsXP-KB891781-x86-NOR.exe

WindowsXP-KB893756-x86-NOR.exe

WindowsXP-KB896358-x86-NOR.exe

WindowsXP-KB896423-x86-NOR.exe

WindowsXP-KB896424-x86-NOR.exe

WindowsXP-KB896428-x86-NOR.exe

WindowsXP-KB898461-x86-NOR.exe

WindowsXP-KB899587-x86-NOR.exe

WindowsXP-KB899589-x86-NOR.exe

WindowsXP-KB899591-x86-NOR.exe

WindowsXP-KB900485-v2-x86-NOR.exe

WindowsXP-KB900725-x86-NOR.exe

WindowsXP-KB901017-x86-NOR.exe

WindowsXP-KB901190-x86-NOR.exe

WindowsXP-KB901214-x86-NOR.exe

WindowsXP-KB904706-v2-x86-NOR.exe

WindowsXP-KB904942-v2-x86-NOR.exe

WindowsXP-KB905414-x86-NOR.exe

WindowsXP-KB905474-ENU-x86_0aad890762cf263dbd4c825c477ef7ba821a852f.exe

WindowsXP-KB905749-x86-NOR.exe

WindowsXP-KB908519-x86-NOR.exe

WindowsXP-KB908531-v2-x86-NOR.exe

WindowsXP-KB910437-x86-NOR.exe

WindowsXP-KB911280-v2-x86-NOR.exe

WindowsXP-KB911562-x86-NOR.exe

WindowsXP-KB911567-x86-NOR.exe

WindowsXP-KB911927-x86-NOR.exe

WindowsXP-KB912817-v2-x86-NOR.exe

WindowsXP-KB912919-x86-NOR.exe

WindowsXP-KB913580-x86-NOR.exe

WindowsXP-KB914388-x86-NOR.exe

WindowsXP-KB914389-x86-NOR.exe

WindowsXP-KB916595-x86-NOR.exe

WindowsXP-KB917159-x86-NOR.exe

WindowsXP-KB917422-x86-NOR.exe

WindowsXP-KB917537-x86-NOR.exe

WindowsXP-KB917953-x86-NOR.exe

WindowsXP-KB918439-x86-NOR.exe

WindowsXP-KB918899-x86-NOR.exe

WindowsXP-KB919007-x86-NOR.exe

WindowsXP-KB920214-x86-NOR.exe

WindowsXP-KB920670-x86-NOR.exe

WindowsXP-KB920683-x86-NOR.exe

WindowsXP-KB920685-x86-NOR.exe

WindowsXP-KB920872-x86-NOR.exe

WindowsXP-KB921398-x86-NOR.exe

WindowsXP-KB921883-x86-NOR.exe

WindowsXP-KB922582-x86-NOR.exe

WindowsXP-KB922616-x86-NOR.exe

WindowsXP-Windows2000-Script56-KB917344-x86-nor.exe

wmcsetup.exe

wmfdist95.exe

msxml6.msi

Files in your HFCABS folder:

Apr2005_d3dx9_25_x86.cab

Apr2006_d3dx9_30_x86.cab

Aug2005_d3dx9_27_x64.cab

Dec2005_d3dx9_28_x64.cab

Feb2005_d3dx9_24_x64.cab

Feb2006_d3dx9_29_x64.cab

Jun2005_d3dx9_26_x64.cab

LegitCheckControl.cab

MUWEB_SITE.CAB

Files in your HFSVCPACK folder:

Files in your HFSVCPACK_SW folder:

Files in your HFTOOLS folder:

7za.exe

MSICabExtract.exe

MSICabExtract.txt

===============================================================================

HFSLIP run time: 13m58s

[Slow instal on VM....]

From our friend, Google:

http://fabrice.bellard.free.fr/qemu/about.html

Thanks

[Slow instal on VM....]

Is it "normal" that it takes 28min to complete?

Are you using QEMU for the VM? If you are that's probably why. It's known to take it's sweet time under QEMU.

Strangely, with QEMU, if you keep on moving the mouse, Windows Setup may go faster!

Hello

What is QEMU?

[Slow instal on VM....]

Using HFSLIP Version - 60810----------------------->ok

Using DriverPacks BASE 6.08.6 all driverpacks---->ok

In that order

It works, tested on/with VM,laptop and PC.

Approximately instaltime 55min.

Checked with QFECHECK, and this did not get installed;

KB890830

KB905474

KB911564

KB913433

KB917734

But Winupdate said no updates is necessary.....

I will go to sleep now

Edit:

KB890830

KB905474

KB911564

KB913433

KB917734

Checked further, these was instaled. Just dont appear as instaled when checked with QFECHECK.

[Slow instal on VM....]

Slipstream----------->Ok, no problems!

WinXpsp2 instal----->Ok, no problems!

From the last boot during XP instal(VM) to the desktop is ready to use it took 28min.

During those 28min the display was black.

Is it "normal" that it takes 28min to complete?

Tried WinUpdate , no updates necessary!

If Iwant to integrate Bâshrat the Sneaky's DriverPacks, do I do that befor or after HFslip?

Thankyou for your help

[Slow instal on VM....]

HFSLIP Version - 60810

HFSLIP Path - D:\HFSLIP\

OS in SOURCESS - XP SP2 Norwegian

DRIVER.CAB Updated

CD Install Path - Default

That was fun....

The sleapstream went fine.

Doing a instal now.(VM)

[Slow instal on VM....]

There is no Norwegian MSXML4. Same goes for MSXML6.

The problem with the detection of your language is that there's a semi-colon ( ; ) in front of the "Merknad til bruker" string. Either remove it yourself like this:

;

Merknad til bruker: IKKE SLETT ELLER ENDRE DENNE FILEN.

;

...or wait for the next (test) release but then you need to wait a few hours.

I have done the change in the PRODSPEC.INI file.

:thumbup You guy's sure give fast respond...GREAT..

I will do a test now.

[Slow instal on VM....]

Hey

Strange, I have;

msxml4sp2-kb887606-x86-enu.exe

msxml2sp6-kb887606-x86-nor.exe

Should there be a nor ver. of msxml4sp2?

[Slow instal on VM....]

PRODSPEC.INI

;

;Merknad til bruker: IKKE SLETT ELLER ENDRE DENNE FILEN.

;

[sMS Inventory Identification]

Version=1.0

[Product Specification]

Product=Windows XP Professional

Version=5.0

Localization=English

ServicePackNumber=0

BitVersion=40

[Version]

DriverVer=07/01/2001,5.1.2600.0

---------------------------------------------------------------------------------------

Also remove these:

WindowsXP-KB896344-v2-x86-ENU.exe -- for English and Japanese only ----->remove it??

WindowsXP-KB905414-x86-ENU.exe -- get the Norwegian version instead------>Ok

msxml2sp6-kb887606-x86-nor.exe -- you need msxml4sp2-kb887606-x86-enu.exe--->msxml4sp2 add???

msxml6_SDK.msi -- not supported

Either remove msxmlcab.exe or msxml.msi; they are the same.-->ok

[Slow instal on VM....]

Hey

I have removed;

msxmlsdk.exe

spuninst.exe

spupdsvc.exe

msxml6_ia64.msi

msxml6_x64.msi

fsdkreboot.exe

msxml4msms.exe

The slipstream works perfect, will report back how the Instal went.(In an hour)

[Slow instal on VM....]

What exactly do you mean by saying the HFSLIP portion takes 25 minutes? Also, I do not recommend including ENU updates along with NOR updates.

You have files in your HF folder, namely the following, that are unnecessary (there may be some more that I am not familiar with).

msxmlsdk.exe

spuninst.exe

spupdsvc.exe

msxml.msi

msxml6_ia64.msi

msxml6_SDK.msi

msxml6_x64.msi

What is fsdkreboot.exe for?

@Tomcat, can you fix the incorrect detection of a Norwegian source?

25 min ; after the instal of winXp it takes HfSLIP 25min to finito....

What is fsdkreboot.exe for? --> I dont know

I will do a test removing thise files.

msxmlsdk.exe

spuninst.exe

spupdsvc.exe

msxml6_ia64.msi

msxml6_x64.msi

[Slow instal on VM....]

Hey

Iam new to this.

I have WinXP Pro corperated Norwegain.

I takes like 25min after winXp instal to finish the Hfslip part (using VM)

WinXp--->39 min

+

Hfslip--->25min

Winxp says "wait a while" and the screen turns black(VM), there are some disk activity.

Should it take this long to complete the updates?

This is my HFSLIP Log file;

------------------------------------------------

This file is automatically generated by HFSLIP.

HFSLIP Version - 60810

HFSLIP Path - D:\HFSLIP\

OS in SOURCESS - XP SP2 English(It says English, but it is Norwegian)

DRIVER.CAB Updated

CD Install Path - Default

===============================================================================

Files in your FIX folder:

Files in your HF folder:

fsdkreboot.exe

HMTCDWizard_NOR.exe

msxml2sp6-kb887606-x86-nor.exe

msxml4msms.exe

msxmlcab.exe

msxmlsdk.exe

spuninst.exe

spupdsvc.exe

Windows-KB890830-V1.20.exe

Windows-KB909520-v1.000-x86-NOR.exe

Windows-KB913433-x86-NOR.exe

WindowsMedia-KB911564-x86-NOR.exe

WindowsMedia9-KB917734-x86-NOR.exe

WindowsUpdateAgent20-x86.exe

WindowsXP-KB873339-x86-NOR.exe

WindowsXP-KB885626-v2-x86-nor.exe

WindowsXP-KB885835-x86-NOR.exe

WindowsXP-KB885836-x86-NOR.exe

WindowsXP-KB886185-x86-nor.exe

WindowsXP-KB887472-x86-nor.exe

WindowsXP-KB888302-x86-NOR.exe

WindowsXP-KB890046-x86-NOR.exe

WindowsXP-KB890859-x86-NOR.exe

WindowsXP-KB891781-x86-NOR.exe

WindowsXP-KB893756-x86-NOR.exe

WindowsXP-KB896344-v2-x86-ENU.exe

WindowsXP-KB896358-x86-NOR.exe

WindowsXP-KB896423-x86-NOR.exe

WindowsXP-KB896424-x86-NOR.exe

WindowsXP-KB896428-x86-NOR.exe

WindowsXP-KB898461-x86-NOR.exe

WindowsXP-KB899587-x86-NOR.exe

WindowsXP-KB899589-x86-NOR.exe

WindowsXP-KB899591-x86-NOR.exe

WindowsXP-KB900485-v2-x86-NOR.exe

WindowsXP-KB900725-x86-NOR.exe

WindowsXP-KB901017-x86-NOR.exe

WindowsXP-KB901190-x86-NOR.exe

WindowsXP-KB901214-x86-NOR.exe

WindowsXP-KB904706-v2-x86-NOR.exe

WindowsXP-KB904942-v2-x86-NOR.exe

WindowsXP-KB905414-x86-ENU.exe

WindowsXP-KB905474-ENU-x86_0aad890762cf263dbd4c825c477ef7ba821a852f.exe

WindowsXP-KB905749-x86-NOR.exe

WindowsXP-KB908519-x86-NOR.exe

WindowsXP-KB908531-v2-x86-NOR.exe

WindowsXP-KB910437-x86-NOR.exe

WindowsXP-KB911280-v2-x86-NOR.exe

WindowsXP-KB911562-x86-NOR.exe

WindowsXP-KB911567-x86-NOR.exe

WindowsXP-KB911927-x86-NOR.exe

WindowsXP-KB912817-v2-x86-NOR.exe

WindowsXP-KB912919-x86-NOR.exe

WindowsXP-KB913580-x86-NOR.exe

WindowsXP-KB914388-x86-NOR.exe

WindowsXP-KB914389-x86-NOR.exe

WindowsXP-KB916595-x86-NOR.exe

WindowsXP-KB917159-x86-NOR.exe

WindowsXP-KB917422-x86-NOR.exe

WindowsXP-KB917537-x86-NOR.exe

WindowsXP-KB917953-x86-NOR.exe

WindowsXP-KB918439-x86-NOR.exe

WindowsXP-KB918899-x86-NOR.exe

WindowsXP-KB919007-x86-NOR.exe

WindowsXP-KB920214-x86-NOR.exe

WindowsXP-KB920670-x86-NOR.exe

WindowsXP-KB920683-x86-NOR.exe

WindowsXP-KB920685-x86-NOR.exe

WindowsXP-KB920872-x86-NOR.exe

WindowsXP-KB921398-x86-NOR.exe

WindowsXP-KB921883-x86-NOR.exe

WindowsXP-KB922582-x86-NOR.exe

WindowsXP-KB922616-x86-NOR.exe

WindowsXP-Windows2000-Script56-KB917344-x86-nor.exe

wmcsetup.exe

wmfdist95.exe

msxml.msi

msxml6.msi

msxml6_ia64.msi

msxml6_SDK.msi

msxml6_x64.msi

Files in your HFCABS folder:

Apr2005_d3dx9_25_x86.cab

Apr2006_d3dx9_30_x86.cab

Aug2005_d3dx9_27_x64.cab

Dec2005_d3dx9_28_x64.cab

Feb2005_d3dx9_24_x64.cab

Feb2006_d3dx9_29_x64.cab

Jun2005_d3dx9_26_x64.cab

LegitCheckControl.cab

MUWEB_SITE.CAB

Files in your HFSVCPACK folder:

Files in your HFSVCPACK_SW folder:

Files in your HFTOOLS folder:

MSICabExtract.exe

MSICabExtract.txt

===============================================================================

HFSLIP run time: 17m02s

.........................................................................

[Nero Burning ROM v7 installation]

@cn0saj. Works perfect

I started the instalation with Nero-7.2.7.0_nor_no_yt.exe, waited for the MSI to start, then copied the TEMP dir to another place. Stopped the instal. Made SFX with this comment;

----------------------

;The comment below contains SFX script commands

Setup=nero.msi /QB /NORESTART STARTPARAM="CallFromExe" DONOTRUNSETUPX="1" SERIALNUM_USERVAL="xxx-xxx-xxx-xxx-xxx-xxx-xxx-" AGREETOLICENSE="TRUE" ADDLOCAL=NeroSuiteInstallerDD1EB5BC,NeroBurningRomBCAFF604,NeroRecode6035F00C,NeroInfoToolE72D824A,

NeroDriveSpeed7DFFCC12,NeroCDDVDSpeed82602EE0

TempMode

Silent=1

Overwrite=1

-----------------------

No Scout appeared, no reboot, just a plain good unnatended instal

[Nero Burning ROM v7 installation]

Noope....no go....

No response after executing the comand..

[Nero Burning ROM v7 installation]

Nope, no luck.

I dunno why I could do it before and now Nero does not permit it.

Annita

Mabe the only way is to make a MST/MSI........