Bezalel

Changing an upgrade to a retail or something? Changing an upgrade to a full install would be illegal in cases where the user doesn't qualify for an upgrade. In this discussion the user does qualify for an upgrade.

I had copy files created by CollectFiles.rar and the files from activation.rar to the $oem$ folder of the CD. I deleted OEMBIOS.BI_ OEMBIOS.DA_, OEMBIOS.SI_ from the CD and I removed all lines referencing any of the OEMBIOS files (including OEMBIOS.CAT) from txtsetup.sif and dosnet.inf. I had rebuild XP HOME CD. After install this to other pc still give me to activate. What is wrong? The contents of my $OEM$ directory is: 53616D73756E6720456C656374726F6E696373.BIN 53616D73756E6720456C656374726F6E696373.CAT 53616D73756E6720456C656374726F6E696373.DAT 53616D73756E6720456C656374726F6E696373.SIG cmdlines.txt CreateBatFile.vbs RestoreOEMFiles.bat RestoreOEMFiles.tmp smbios2.exe Does your other computer also report "Samsung Electronics"? Where did you get the Key you used to install? Do the OEMBIOS files exist in your %SYSTEMROOT%\System32 directory? What message did you get when you tried to activate?

Did you once have the media or did your PC never include the media? Is you computer made by a Royalty OEM (COA will have manufacturer's name or logo) or a System Builder (COA will say "OEM Product")? Is your PC currently working?

REG SAVE KeyName Filename

REG ADD "HKLM\System\CurrentControlSet\Control\Session Manager\Enviroment" /v "EnviromentVariableName" /d "EnviromentVariableValue"

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

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.

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)

You don't need to replace any files. WPA.BAK doesn't exist until the PC is activated.

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.

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.

It's WPA.BAK that you need to save not WPA.DBL (WPA.DBL get recreated every time you start your PC). This method no longer works (unless your media doesn't have any service packs).

Yes. You understand correctly. 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.

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.

The files are interchangable between Home and Pro.

The MCE remote works by emulating a keyboard. If your remote sends keystrokes when you press the keys it will work in MCE. Of course there will be some special buttons that are mapped differently on each remote so don't expect 100% compatibility.

Is this PC setup to boot from the floppy before the CD?

Microsoft Baseline Security Analyzer http://www.microsoft.com/technet/security/...s/mbsahome.mspx

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?

From what you already posted it looks like you have a Pro SP2 Retail Uprage CD. You need to mak a few changes to turn this into a HP Pro SP2 OEM CD. Replace all the OEMBIOS files in the I386 directory with the ones found on your HP CD. Replace the last line of the setupp.ini file with the following Pid=76487OEM Use a CD-Key from http://www.microsoft.com/technet/prodtechn...y/oempreac.mspx

So the scripts collect the files from the upgrade version, not the OEM version. Because it overwrites the files when you upgrade, is that right ? Yes. It will collect the files and key from the current installation (Pro Retail Upgrade).

Is your HP CD an installation CD or a recovery CD? The scripts that ZaForD linked to will not work in the current state of your PC. (Actaully they will work but will not produce the files you need.)

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?

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?

You need to run winnt32 with the /makelocalsource switch. I do this for all computers I without a cdrom drive.