Help - Search - Members - Calendar
Full Version: Multi Manufacturer Pre-Activation
MSFN Forums > Unattended Windows Discussion & Support > Unattended Windows 2000/XP/2003
Pages: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11

   


Google Internet Forums Unattended CD/DVD Guide
tkmadison
CODE
Manufacturer: None (Seanix Technology)
   Model: D400S
   4E6F6E65


CODE
Manufacturer: Mind Computer Products
   Model: KM266-8235
   4D696E64 20436F6D 70757465 72205072 6F647563 7473
ZaForD
@FreeStyler
QUOTE
if you search manufacturer strings for example "Dell" or as hex "44656C6C" you would have a more variable system that should work on various types of Dell Systems.
Dell PC's come with a randomly named '"System Manufacturer" string, one advantage it always starts with "Dell" eg;
Dell Computer Corp.
Dell Computer Corporation
Dell Computer Corporation.
Dell Inc.
And maybe a whole lot more variations... who knows!
An Admin here asked about the same thing.
On a ramdon check of the Dell's in this office, we had three different 'System Manufacturers'.
So,he wanted to know:
QUOTE
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's reply was to add this line;
QUOTE
You can always add the following line to your own code
CODEMfgHex=Left(MfgHex,8)

I haven't seen him since to find out if it worked for him.
But it should reduce the amount of OEMBIOS files needed to cover this network of Dell's.

p.s. Thanks for the VPC tut. smile.gif
Bilou_Gateux
woot.gif

I have a working solution for Royalty OEM RIS install.
I'm using the first 3 Manufacturer Characters - like: HEW,DEL,MED,ACE,FUJ,ASU,IBM,SON instead of converting Manufacturer string to hex and renaming multiple OEMBIOS.* files.


ristndrd.sif
CODE
[GuiUnattended]
OemSkipWelcome = 1
OemSkipRegional = 1
TimeZone = %TIMEZONE%
AdminPassword = "*"
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\OEMBUILD.CMD)))"

[SetupParams]
UserExecute="\$WIN_NT$.~LS\$OEM$\nircmd.exe script \$WIN_NT$.~LS\$OEM$\fbreseal.ncl"


Destination folder $oem$
copy compname.exe
copy nircmd.exe
for each manufacturer create a subfolder named with the 3 leftmosts chars of the manufacturer string and copy OEMBIOS.* + oemlogo.bmp to this subfolder.
Example for Hewlett-Packard, in $oem$ i have HEW subfolder and inside
OEMBIOS.*
oemlogo.bmp

script launched by DetachedProgram @T39
CODE
@REM ==================================================================
@REM © Copyright 2006 Bill Gates Development Company, L.P.
@REM
@REM  Royalty OEM PCs - RIS (Remote Installation Services) based install
@REM
@REM Credits: Bezalel for initial idea and coding for CD based install
@REM
@REM Credits: idle.newbie hp38guser schalti Pyron a06lp for drivers from CD based install
@REM http://www.msfn.org/board/index.php?s=&showtopic=51406&view=findpost&p=358011
==================================================================

@FOR /F %%a IN (%SystemRoot%\SYSTEM32\$WINNT$.INF) DO (FOR %%b IN (%%a) DO (IF EXIST %%b (SET DOSPATH=%%b)))
@for /F "tokens=2* delims=: " %%i in ('%dospath%\$oem$\compname.exe /s ^|findstr /L /c:"System    manufacturer"') do @set Manufacturer=%%j &@call :oem "%%j" &@call :model
@echo/[General]>%SystemRoot%\System32\oeminfo.ini
@echo/Manufacturer=%Manufacturer%>>%SystemRoot%\System32\oeminfo.ini
@echo/Model=%Model%>>%SystemRoot%\System32\oeminfo.ini
@echo/supporturl=%supporturl%>>%SystemRoot%\System32\oeminfo.ini
@echo/>>%SystemRoot%\System32\oeminfo.ini
@echo/[Support Information]>>%SystemRoot%\System32\oeminfo.ini
@echo/Line1=' '>>%SystemRoot%\System32\oeminfo.ini
@echo/Serial=%Serial%>>%SystemRoot%\System32\oeminfo.ini
@copy /y %dospath%\$oem$\%oem%\oemlogo.bmp %SystemRoot%\System32\oemlogo.bmp >nul

:jump
for %%? in (bi si da ca) do (
 copy /y %dospath%\$oem$\%OEM%\oembios.%%?_ %SystemDrive%\$win_nt$.~ls\i386
 expand -r %dospath%\$oem$\%oem%\oembios.%%?_ %SystemRoot%\system32\
)

:drivers
::  Set Drivers Location Folder
    SET DRV=%SystemDrive%\Drivers
::  Ticker script
    ECHO.exec hide %dospath%\$oem$\Process.exe -r setup.exe >%SystemDrive%\Ticker.ncl
    ECHO.wait 10000 >>%SystemDrive%\Ticker.ncl
    ECHO.exec hide %dospath%\$oem$\Process.exe -p SetupCopyOEMInf.exe high >>%SystemDrive%\Ticker.ncl
    ECHO.exec hide %dospath%\$oem$\Process.exe -s setup.exe >>%SystemDrive%\Ticker.ncl
    ECHO.wait 50000 >>%SystemDrive%\Ticker.ncl
    ECHO.script %SystemDrive%\Ticker.ncl >>%SystemDrive%\Ticker.ncl
::  Pre-Install (Suspend Setup, and Set Setup to Low Priority)
    %dospath%\$oem$\Process.exe -s setup.exe
    %dospath%\$oem$\Process.exe -p setup.exe low
::  If Compressed Drivers Exist, Unzip Them & Change Drivers Location Folder to Hard Drive
    IF EXIST Drivers.7z (
    SET DRV=%SystemDrive%\Drivers
    %dospath%\$oem$\7za.exe x -y -aoa -o"%SystemDrive%\Drivers" "%dospath%\$oem$\Drivers.7z"
    )
::  If Compressed Drivers Exist, Uncab Them & Change Drivers Location Folder to Hard Drive
    IF EXIST %dospath%\$oem$\EC834ET.TAG (
         IF /I "%Model%"=="HP Compaq dc7600 Convertible Minitower" (
      SET DRV=%SystemDrive%\Drivers
      extrac32 /y /l %SystemDrive%\Drivers\Video %dospath%\$oem$\11725988.cab *.*
          extrac32 /y /l %SystemDrive%\Drivers\NIC %dospath%\$oem$\b57win32.cab *.*
          extrac32 /y /l %SystemDrive%\Drivers\Audio %dospath%\$oem$\rtkazaud.cab *.*
         )  
    )
    IF EXIST %dospath%\$oem$\D1944.TAG (
         IF /I "%Model%"=="SCENIC C620" (
      SET DRV=%SystemDrive%\Drivers
      extrac32 /y /l %SystemDrive%\Drivers\Video %dospath%\$oem$\IALMNT5.CAB *.*
          extrac32 /y /l %SystemDrive%\Drivers\NIC %dospath%\$oem$\b57win32.cab *.*
          extrac32 /y /l %SystemDrive%\Drivers\Audio %dospath%\$oem$\smwdmch6.cab *.*
          extrac32 /y /l %SystemDrive%\Drivers\Misc1 %dospath%\$oem$\cmeu0wdm.cab *.*
         )  
    )
::  Run NirCmd Ticker Script (code above)
    START %dospath%\$oem$\NirCmd.exe script %SystemDrive%\Ticker.ncl
::  Install Drivers
    %dospath%\$oem$\SetupCopyOEMInf.exe "%DRV%"
::  Post-Install (Close NirCmd, Setup Priority back to Normal, Resume Setup)
    %dospath%\$oem$\Process.exe -k NirCmd.exe
    %dospath%\$oem$\Process.exe -p setup.exe normal
    %dospath%\$oem$\Process.exe -r setup.exe
::  Delete Ticker File
    DEL %SystemDrive%\Ticker.ncl

goto :eof

:model
@for /F "tokens=1* delims=: " %%k in ('%dospath%\$oem$\compname /s ^|findstr /c:"model"') do @set Model=%%l
@for /F "tokens=1*" %%m in ('%dospath%\$oem$\compname /d ?s') do @set Serial=%%m
@for /F "tokens=1-2*" %%n in ('findstr "%oem%" %~s0') do (set supporturl=%%o)
@goto :eof
:oem
@set oem=%1
@set oem=%oem:"=%
@set oem=%oem:~0,3%
@goto :eof

[Manufacturer]
FUJ http://support.fujitsu-siemens.com/com/support/index.html         : Fujitsu Siemens Computers
HEW http://welcome.hp.com/country/us/en/support.html?pageDisplay=support           : Hewlett-Packard
NEC http://help1.nec-computers.com/main.asp?lang=com           : NEC Computers International
TOS http://www.csd.toshiba.com/cgi-bin/tais/su/su_sc_home.jsp       : TOSHIBA


nircmd script launched by UserExecute @T9
QUOTE
execmd move /y ~$sys.systemroot$\system32\dllcache\oembios.cat ~$sys.systemroot$\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
regsetval sz "HKLM\SOFTWARE\OEM\Image" "" "Royalty OEM Preinstalled Image"
exec show "~$sys.systemdrive$\$win_nt$.~ls\$oem$\zcnclite.exe" "/wmi:~qWin32_BIOS,SerialNumber~q /sn:~qSN-~q /q /forcerun"


[EDIT]

Done some rewrite of the script for RIS
[/EDIT]
FreeStyler
QUOTE (tkmadison @ Jun 13 2006, 09:46 AM) *
CODE
Manufacturer: None (Seanix Technology)
   Model: D400S
   4E6F6E65


CODE
Manufacturer: Mind Computer Products
   Model: KM266-8235
   4D696E64 20436F6D 70757465 72205072 6F647563 7473


Did these 2 come with Windows Xp Preinstalled?
i don't know these brands, oembios files? newwink.gif

PS, Thx for the LENOVO files smile.gif
Djé
A bit like Bilou, I have a solution called from DetachedProgram @T39.
It is not a Compname/batch solution but it uses the RBE.EXE prog (MiTeC ROM BIOS Explorer 2.2) together with a modular AutoIt script.
It is still a bit too alpha for releasing (don't worry Bezalel, I'll start a new thread if ever I do), but here is an idea that I'm implementing and may be found useful by others:

-I use only XP home systems so the productkeys are not the standard one from microsoft. I have to save mines before (thanks to Bezalel's idea). The one paired with the OEMBIOS.* files has to be restored to 'SYSTEM32\$WINNT$.INF' early enough (T12 is too late), hence the T39.
-Althoug it's working with a CD based install, I use winnt(32).exe based installs (network or usb drive), which makes a local source on the sytem. So I don't want to download ALL the oembios sets to the local source since I will use only one.
So @T39, my AutoIt script just writes a batch script that will be run @T12 to connect again to the network (there is no network @T39) and download the files to System32 (and move the cat to \CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}).

It works like a charm. Other features (if someone's interested):
- 1 (double-)click back-up, silent restore!
- Modules allow to backup/import other custom setting that you usually have to fill in winnt.sif:
My winnt.sif is a very standard one with basic infos. So the command to run winnt(32).exe is always the same (no need for a different answer file for each system).
- Current modules cover (at least partially) the Display, NetworkIdentification & UserData sections of winnt.sif. Plus a module for custom commands to be run at T39, T12 or RunOnceEx.
- Backed-up data is stored in a .ini file, easy to edit, manually or with AutoIt.
- oembios.* file and backed-up data can be tagged with either the System's Manufacturer, Model, Version, Serial or UUID (all from type1 smbios, other tables could be implemented).
Bezalel
QUOTE (Bilou_Gateux @ Jun 13 2006, 07:40 AM) *
woot.gif

I have a working solution for Royalty OEM RIS install.


If you delete one of the oembios files from the system32 folder will SFC restore them from the dllcache or will it connect to your RIS and get the generic files?
Bezalel
QUOTE (FreeStyler @ Jun 12 2006, 06:40 PM) *
no, i believe the opposite is true and the benefit of such method will be greater then its limitations...
I'll try to explain...if you search manufacturer strings for example "Dell" or as hex "44656C6C" you would have a more variable system that should work on various types of Dell Systems.


OK. its on my todo list but it won't be implemented until after I implement CRC32.

The next version will be written in Visual Basic. The collection portion will be a wizard written in version 2005 and the deployment portion will be written in version 5.0 with no UI.
RogueSpear
I've put together a nice little MD5 function in VB2005 if you don't mind using that instead of CRC32.
Bezalel
QUOTE (RogueSpear @ Jun 13 2006, 10:52 PM) *
I've put together a nice little MD5 function in VB2005 if you don't mind using that instead of CRC32.


I prefer CRC32 because it would avoid long filenames even though its not as unique as MD5. I have a CRC32 function from freevbcode.com but haven't tested it fully
RogueSpear
Ok, well just let me know if you want to bounce around any ideas. I'm (hopefully) close to releasing the first beta of a utility I've working on for install source preparation and this thread topic is something I'd love to include in it.

If you're interested in seeing what I've got so far just send a PM.
FreeStyler
CODE
Manufacturer: BENQ
   Model: JoyBook 2100E
   42454E51


CODE
Manufacturer: Gateway
   Model: 3250SB CTO PC
   4761746 5776179


CODE
Manufacturer: Founder
   Model: Founder PC
   466F756E 646572


OEMBIOS files that are still on my "wanted" list:
  • Gateway
  • Packard-Bell
  • NEC
  • LG
ZaForD
@FreeStyler,

I hoping to got a set of Parckard Bell OEMBIOS files this weekend, i'll let you know if thery turn up.
Packard Bell and NEC PC's are the same over here in the UK, so the files maybe interchangeable ? unsure.gif

And FYI, I tried the DMI trick on a Gateway it worked the same as on the HP's. It needed the /sm and /bm switches to work.
I also tried it on an Evesham laptop which has an "Insyde Software" BIOS, but it kept generating a 'Floating Point Error' when i tried it. sad.gif
FreeStyler
QUOTE (ZaForD @ Jun 14 2006, 01:48 PM) *
I also tried it on an Evesham laptop which has an "Insyde Software" BIOS, but it kept generating a 'Floating Point Error' when i tried it. sad.gif


This probably means they have "locked" that BIOS string, had this same issue with a INTEL board the other day
herroyuy
sorry for newbie questions..

first of all.. let me paste my details

Manafacturer: Acer
Model: Aspire 5500
41636572 2020202020 20202020 20202020

i wish to install clean windows by not using the recovery cd as it recovers together will hell lot of utilities which i don't need. I tried to do clean installation with OEM windows home cd and used back the preactivated key in my preinstalled windows but i'm still required to activate..

i've used the collectoemfiles to collect the signatures and those... does that tmean after i reinstall with clean winxp i just have to overwrite those file to keep my windows preactivated? or what? i don't really understand on the procedures... can somebody please pm me with the clear steps? and also.. that is T9 T12 T39 blah blah?

please help me... i've been searching the net for this for a long time but can't ifnd a solution. thanks in advance
Bezalel
QUOTE (herroyuy @ Jun 14 2006, 10:57 PM) *
i wish to install clean windows by not using the recovery cd as it recovers together will hell lot of utilities which i don't need. I tried to do clean installation with OEM windows home cd and used back the preactivated key in my preinstalled windows but i'm still required to activate..


This thread is intended for people who have PCs from multiple manufacturers. If you only have one computer or all of your computers are from the same manufacturer see http://www.msfn.org/board/index.php?showtopic=63258 for information relevant to your situation.
FreeStyler
QUOTE (herroyuy @ Jun 15 2006, 04:57 AM) *
Manafacturer: Acer
Model: Aspire 5500
41636572 2020202020 20202020 20202020


Bezalel, above is another example of one which ads multiple spaces after the innitial string, as Acer = 41636572 all 2020202020 20202020 20202020 are useless

CODE
MfgHex=Left(MfgHex,8)

Where could this be added in your script?
So adding this, it will check for strings like: Acer, Hewl , Dell , Comp , Tosh, Leno etc etc ?

BTW, you told you removed all references of oembios.* files from dosnet.inf en txtsetup.sif and removed all oembios files except oembios.ca_ from /I386 folder
What happens if smbios2 can not find matching "oembios" for current install? shouldn't we insert a default set for whenever smbios2 can not find any oembios files matching the System Manufacturer hex-string
Bezalel
QUOTE (FreeStyler @ Jun 15 2006, 02:17 AM) *
BTW, you told you removed all references of oembios.* files from dosnet.inf en txtsetup.sif and removed all oembios files except oembios.ca_ from /I386 folder
What happens if smbios2 can not find matching "oembios" for current install? shouldn't we insert a default set for whenever smbios2 can not find any oembios files matching the System Manufacturer hex-string


Not having any OEMBIOS files has the same effect as having the generic files. If you still want to have the generic files you can put them in \$OEM$\$$\System32.
FreeStyler
Can't i just leave to original "dell" set left in place (both in /i386 dir as in dosnet, txtsetup, doesn't it get overwritten by smbios2 command at t9 of the installation process?
Bezalel
QUOTE (FreeStyler @ Jun 15 2006, 11:12 AM) *
Can't i just leave to original "dell" set left in place (both in /i386 dir as in dosnet, txtsetup, doesn't it get overwritten by smbios2 command at t9 of the installation process?


SFC runs a full scan at T-9. If you leave the origionals where SFC can find then they will be restored.
FreeStyler
QUOTE (Bezalel @ Jun 15 2006, 04:17 PM) *
QUOTE (FreeStyler @ Jun 15 2006, 11:12 AM) *

Can't i just leave to original "dell" set left in place (both in /i386 dir as in dosnet, txtsetup, doesn't it get overwritten by smbios2 command at t9 of the installation process?


SFC runs a full scan at T-9. If you leave the origionals where SFC can find then they will be restored.


Ah, ok...we do not want that newwink.gif
FreeStyler
QUOTE (Bezalel @ Jun 15 2006, 04:17 PM) *
QUOTE (FreeStyler @ Jun 15 2006, 11:12 AM) *

Can't i just leave to original "dell" set left in place (both in /i386 dir as in dosnet, txtsetup, doesn't it get overwritten by smbios2 command at t9 of the installation process?


SFC runs a full scan at T-9. If you leave the origionals where SFC can find then they will be restored.


Are you sure about that?
I just finished a install on HP system with modified Dell Oem CD Media, right files are still in place...thus not being replaced by DELL original oembios.* files SFC at T-9
I md5 compared installed files, it are guaranteed the HP ones and not the original DELL
Bezalel
QUOTE (FreeStyler @ Jun 16 2006, 03:33 AM) *
QUOTE (Bezalel @ Jun 15 2006, 04:17 PM) *

QUOTE (FreeStyler @ Jun 15 2006, 11:12 AM) *

Can't i just leave to original "dell" set left in place (both in /i386 dir as in dosnet, txtsetup, doesn't it get overwritten by smbios2 command at t9 of the installation process?


SFC runs a full scan at T-9. If you leave the origionals where SFC can find then they will be restored.


Are you sure about that?
I just finished a install on HP system with modified Dell Oem CD Media, right files are still in place...thus not being replaced by DELL original oembios.* files SFC at T-9
I md5 compared installed files, it are guaranteed the HP ones and not the original DELL


I'm using a hologrammed CD as my base installation. Do you have any other customizations on your CD such as a hacked sfc_os.dll?
FreeStyler
QUOTE (Bezalel @ Jun 16 2006, 12:54 PM) *
I'm using a hologrammed CD as my base installation. Do you have any other customizations on your CD such as a hacked sfc_os.dll?


Official DELL OEM Media, no other modifications besides "our" vender specific oembios files in \$OEM$ folder
Bezalel
QUOTE (FreeStyler @ Jun 16 2006, 09:28 AM) *
QUOTE (Bezalel @ Jun 16 2006, 12:54 PM) *

I'm using a hologrammed CD as my base installation. Do you have any other customizations on your CD such as a hacked sfc_os.dll?


Official DELL OEM Media, no other modifications besides "our" vender specific oembios files in \$OEM$ folder


I'm going to have to try this out. Which files are in your dllcache? if you delete the files in the system32 folder will it replace them with the files in the dllcache or does it ask for the CD?
FreeStyler
QUOTE (Bezalel @ Jun 16 2006, 05:04 PM) *
QUOTE (FreeStyler @ Jun 16 2006, 09:28 AM) *

QUOTE (Bezalel @ Jun 16 2006, 12:54 PM) *

I'm using a hologrammed CD as my base installation. Do you have any other customizations on your CD such as a hacked sfc_os.dll?


Official DELL OEM Media, no other modifications besides "our" vender specific oembios files in \$OEM$ folder


I'm going to have to try this out. Which files are in your dllcache? if you delete the files in the system32 folder will it replace them with the files in the dllcache or does it ask for the CD?


dllcache, only the *.cat file....others are missing there.....what the hell is going on here?
Bezalel
QUOTE (FreeStyler @ Jun 16 2006, 04:50 PM) *
QUOTE (Bezalel @ Jun 16 2006, 05:04 PM) *

QUOTE (FreeStyler @ Jun 16 2006, 09:28 AM) *

QUOTE (Bezalel @ Jun 16 2006, 12:54 PM) *

I'm using a hologrammed CD as my base installation. Do you have any other customizations on your CD such as a hacked sfc_os.dll?


Official DELL OEM Media, no other modifications besides "our" vender specific oembios files in \$OEM$ folder


I'm going to have to try this out. Which files are in your dllcache? if you delete the files in the system32 folder will it replace them with the files in the dllcache or does it ask for the CD?


dllcache, only the *.cat file....others are missing there.....what the hell is going on here?

It looks like you're not using my current scripts from post 43. http://www.msfn.org/board/index.php?s=&sho...ndpost&p=512579 Which version of my script are you using, or did you modify one of my scripts?
FreeStyler
QUOTE (Bezalel @ Jun 16 2006, 11:01 PM) *
QUOTE (FreeStyler @ Jun 16 2006, 04:50 PM) *

QUOTE (Bezalel @ Jun 16 2006, 05:04 PM) *

QUOTE (FreeStyler @ Jun 16 2006, 09:28 AM) *

QUOTE (Bezalel @ Jun 16 2006, 12:54 PM) *

I'm using a hologrammed CD as my base installation. Do you have any other customizations on your CD such as a hacked sfc_os.dll?


Official DELL OEM Media, no other modifications besides "our" vender specific oembios files in \$OEM$ folder


I'm going to have to try this out. Which files are in your dllcache? if you delete the files in the system32 folder will it replace them with the files in the dllcache or does it ask for the CD?


dllcache, only the *.cat file....others are missing there.....what the hell is going on here?

It looks like you're not using my current scripts from post 43. http://www.msfn.org/board/index.php?s=&sho...ndpost&p=512579 Which version of my script are you using, or did you modify one of my scripts?


No, i'am using current scripts posted in post #43 - No Modifications...i am using "Dutch" Windows XP OEM Media though,so maybe...?
ZaForD
New computer report,
QUOTE
Manufacturer: FUJITSU SIEMENS
Model: D1325
46554A49 54535520 5349454D 454E53

No OEMBIOS i'm affraid, i wasn't quick enough. sad.gif
FreeStyler
@ZaForD you might find FUJITSU SIEMENS oembios files @ my RapidShare folder
  1. Acer
  2. Asus
  3. BenQ
  4. Compaq
  5. Dell
  6. eMachines
  7. Founder
  8. Fujitsu
  9. Fujitsu-Siemens
  10. Gateway
  11. Hedy
  12. Hewlett-Packard
  13. IBM
  14. Legend
  15. Lenovo
  16. Medion
  17. Packard-Bell
  18. Samsung
  19. Sony
  20. Targa
  21. TCL
  22. Tsinghua Tongfang Computer
  23. Toshiba
Wishlist
  • NEC
  • LG
ZaForD
@ FreeStyler,
Thanks for the files.
I don't really need them as this F-S box is a scrapper. But i'll keep them handy, just in case. newwink.gif
Djé
@FreeStyler, thanks for the files.
A question though,

Your files are for XP pro, aren't they?
Because, the Toshiba & Compaq ones have different md5 sums than mines on my XPhome systems.

Corollary: wouldn't it be useful to collect also the XP home files? or am I missing something?
Bezalel
QUOTE (Djé @ Jun 20 2006, 09:45 AM) *
@FreeStyler, thanks for the files.
A question though,

Your files are for XP pro, aren't they?
Because, the Toshiba & Compaq ones have different md5 sums than mines on my XPhome systems.

Corollary: wouldn't it be useful to collect also the XP home files? or am I missing something?


The files are interchangable between Home and Pro.
Djé
QUOTE (Bezalel @ Jun 20 2006, 04:57 PM) *
The files are interchangable between Home and Pro.

Even though they have different md5 hash and XP home and Pro are using different ProductID?

So the OEMBIOS.* files are not related to the ProductID? They are 2 different locks (at least on XP home where the ProductID seems to be more specific)?
FreeStyler
As Bezalel told...both are interchangable between Home and Pro, just try and see for yourself
Bezalel
QUOTE (Djé @ Jun 20 2006, 11:06 AM) *
QUOTE (Bezalel @ Jun 20 2006, 04:57 PM) *
The files are interchangable between Home and Pro.

Even though they have different md5 hash and XP home and Pro are using different ProductID?

So the OEMBIOS.* files are not related to the ProductID? They are 2 different locks (at least on XP home where the ProductID seems to be more specific)?


I've used a number of OEMBIOS files collected from Home Edition to install Pro, this is part of my upgrade procedure. In fact I can upgrade from Home to Pro using the bits from evaluation media and still maintain preactivation and pass WGA. (I will not publish a tutorial so don't even ask.) I never saw the need to use Pro OEMBIOS files to install Home so I never tried it.
Djé
QUOTE (Bezalel @ Jun 20 2006, 11:52 PM) *
I never saw the need to use Pro OEMBIOS files to install Home so I never tried it.

I've just done the test (on my Compaq test machine) and have to confirm that it also works this way. blink.gif
twig123
Question:
So, if I understand correctly... I can use the key from: http://www.microsoft.com/technet/prodtechn...y/oempreac.mspx
on any Royalty OEM XP Pro system along side with the respective OEMBIOS files to preserve pre-activation...

Is there a generic key for Home Ed. as well? or will the same key work for Home?
Bezalel
QUOTE (discountpc @ Jun 21 2006, 12:13 AM) *
Question:
So, if I understand correctly... I can use the key from: http://www.microsoft.com/technet/prodtechn...y/oempreac.mspx
on any Royalty OEM XP Pro system along side with the respective OEMBIOS files to preserve pre-activation...

Yes. You understand correctly.
QUOTE (discountpc @ Jun 21 2006, 12:13 AM) *
Is there a generic key for Home Ed. as well? or will the same key work for Home?

Every Royalty OEM receives a generic key from Microsoft. You need to retreive the key from the registry before you wipe the HDD.

Microsoft doesn't make a publicly available generic key for Home Edition because they expect you to activate by phone. Forcing IT professionals who manage hundreds of computers to call every time they install Windows is not something that Microsoft thinks they can get away with.


There are more generic keys at http://www.microsoft.com/technet/prodtechn...oy/wpadepl.mspx but Microsoft doesn't gaurantee that these keys can be used for preactivation. (They might be blocked in future versions.)

I've also seen posts thet mention that the key in the sample unattend.txt is a generic key but haven't tested this yet.
FreeStyler
QUOTE (discountpc @ Jun 21 2006, 06:13 AM) *
Question:
So, if I understand correctly... I can use the key from: http://www.microsoft.com/technet/prodtechn...y/oempreac.mspx
on any Royalty OEM XP Pro system along side with the respective OEMBIOS files to preserve pre-activation...

Is there a generic key for Home Ed. as well? or will the same key work for Home?


A simple Google search for: "Windows XP OEM SLP" should result in a few keys that can be used for XP Home Edition
twig123
Well, I know I could find keys online.... but are they legit? that is the thing.
The keys that I need, HAVE to be 100% legit and not disabled or blocked from microsoft.
Bezalel
QUOTE (discountpc @ Jun 21 2006, 03:46 PM) *
Well, I know I could find keys online.... but are they legit? that is the thing.
The keys that I need, HAVE to be 100% legit and not disabled or blocked from microsoft.


I guess I shouldn't have struck my previous statement.

Every Royalty OEM receives a generic key from Microsoft. You need to retreive the key from the registry before you wipe the HDD.
FreeStyler
QUOTE (discountpc @ Jun 21 2006, 09:46 PM) *
Well, I know I could find keys online.... but are they legit? that is the thing.
The keys that I need, HAVE to be 100% legit and not disabled or blocked from microsoft.


Then your are lucky, MS isn't likely to block any of those keys as "who know how many" people are still using that key since the day the person in question could own that pc, with other other words if MS decides to block such a key, thousends legit, say DELL owners would be blocked access...
Bezalel
QUOTE (FreeStyler @ Jun 21 2006, 05:31 PM) *
QUOTE (discountpc @ Jun 21 2006, 09:46 PM) *

Well, I know I could find keys online.... but are they legit? that is the thing.
The keys that I need, HAVE to be 100% legit and not disabled or blocked from microsoft.


Then your are lucky, MS isn't likely to block any of those keys as "who know how many" people are still using that key since the day the person in question could own that pc, with other other words if MS decides to block such a key, thousends legit, say DELL owners would be blocked access...

Actually I have no way of knowing if the keys posted on the warez sites are valid generic keys from Royalty OEMs or if they were generated by a key-gen.
FreeStyler
QUOTE (discountpc @ Jun 21 2006, 09:46 PM) *
The keys that I need, HAVE to be 100% legit and not disabled or blocked from microsoft.


Then you should consider to become a official Microsoft OEM-Partner and get your own OEM SLP Key

BTW, Gateway Oembios files added newwink.gif

wishlist:
  • NEC
  • LG
  • Alienware
Bezalel
QUOTE (Bezalel @ Jun 21 2006, 12:32 AM) *
I've also seen posts thet mention that the key in the sample unattend.txt is a generic key but haven't tested this yet.


The key on my Retail Server 2003 SP1 CD installed but didn't pre-avtivate.
The key on my OEM Pro SP2 CD was rejected by setup. (My guess is that it is a retail key)
Bezalel
QUOTE (FreeStyler @ Jun 22 2006, 02:36 AM) *
QUOTE (discountpc @ Jun 21 2006, 09:46 PM) *

The keys that I need, HAVE to be 100% legit and not disabled or blocked from microsoft.


Then you should consider to become a official Microsoft OEM-Partner and get your own OEM SLP Key


In order to become a Royalty OEM you must have purchased from an authorized distributer and installed 1000 cpoies of XP or 100 copies of Server 2003 during the last 12 months.

If in fact you are an OEM you are subject to a much stricter license than end users are and shouldn't be using most of the information on this site for your installs.
twig123
I know this guys, I run a PC Repair shop and already have OEM copies of windows (non-royalty)... that is not the thing I am after.

I am trying to gather "Royalty Pre-Activation" Files and Product Keys, for use on 1 Multi-Boot CD.
Right now I have a CD (CD! not DVD!) that I have compiled and has the following:

XP Home - OEM
XP Pro - OEM
Dell XP Home
Dell XP Pro
Compaq XP Home
Compaq XP Pro
Emachine XP Home
HP XP Home
HP XP Pro
Sony XP Pro

~5.2GB of Data Crammed onto a 700MB CD...
I am in search of other "Royalty OEM" OEMBIOS & Product Keys, but from what I understand is that the you have to have the Original Mass License Key to keep Pre-Acticated status (XP Home) or use the Key Provided by Microsoft for XP Pro.

My end goal is to have a CD that will auto-detect any Royalty OEM system and auto-install the correct OEMBIOS & Key for the selected version on XP (Home or Pro).... But, In order to do so, I need Key's for the Royalty OEM's that I didn't list above.
Bezalel
You already have 4 Home keys, that's 3 keys more than you need. Having the keys from each manufacturer is unnesasary and distributing keys is against the forum rules. (You may have noticed that I never posted a key, I only linked to publis MS pages with keys.) OEMBIOS files are interchangable between Home and Pro so I stopped keeping track of which edition I got the files from. I have a rapidshare folder with OEMBIOS files collected by myself and other members of this forum located at http://rapidshare.de/users/LWN7M8. (I was hesitant about posting these but one of the mods said it was OK.)
bober
@discountpc

did you add driver packs? none of the new driver packs support multi-boots yet sad.gif

my experience with dell,hp,and compaq is they never have the correct drivers in their cds i always end up going to their sites for drivers.
twig123
QUOTE (Bezalel @ Jun 22 2006, 11:20 PM) *
You already have 4 Home keys, that's 3 keys more than you need. Having the keys from each manufacturer is unnesasary and distributing keys is against the forum rules.
... I guess I'm at a loss and not understanding something. could you explain how I would use the existing keys that I have to install other OEM Home copies (ie: Sony, Gateway... etc) and still preserve the pre-activation?!

Thanks.

QUOTE (bober @ Jun 22 2006, 11:29 PM) *
@discountpc

did you add driver packs? none of the new driver packs support multi-boots yet sad.gif

my experience with dell,hp,and compaq is they never have the correct drivers in their cds i always end up going to their sites for drivers.
Right now I am NOT running the latest Driver Packs because there are still a lot of kinks that need to be worked out before I invest my time in compiling another copy with the new GUI.




Google Internet Forums Unattended CD/DVD Guide

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.