Saturday, 21 August 2010

Are you tired of fighting with OEM reinstalls? (Who isn't)

A collection of essentials


Product keys are version-specific

http://windows-xp.itags.org/windows-xp/289546/


Well, you don't necessarily need the *original* installation CD, but you will need to obtain a replacement CD of the identical type (OEM vs. Retail Full Vs. retail Upgrade), if you want to use the same Product Key.

Product Keys are bound to the specific type and language of CD and/or license (OEM, Volume, retail, full, or Upgrade) with which they are purchased. For example, a WinXP Home OEM Product Key won't work for any retail version of WinXP Home, or for any version of WinXP Pro, and vice versa. An upgrade's Product Key cannot be used with a full version CD, and vice versa. An OEM Product Key will not work to install a retail product. An Italian Product Key will not work with an English CD.
Bottom line: Product Keys and CD types cannot be mixed & matched.


If it was a retail license and you have proof of purchase:

How to Replace Lost, Broken, or Missing Microsoft Software or Hardware
http://support.microsoft.com/default...B;en-us;326246

If it was an OEM license, you should contact the computer's manufacturer.

Bruce Chambers




How to Perform a Windows XP Repair Install
Author: Michael Stevens

http://michaelstevenstech.com/XPrepairinstall.htm



Backup and Restore XP Activation

http://www.windowsnetworking.com/kbase/WindowsTips/WindowsXP/UserTips/Miscellaneous/BackupRestoreXPActivation.html


When you activate Windows XP, Microsoft stores the data in the Windows Product Activation database files wpa.dbl and Wpa.bak in the folder %systemroot%\system32. If you change the motherboard or make significant hardware changes, XP will require you to reactive. But if you plan to reinstall XP on the same hardware, you can back up the activation status and then restore it after you reinstall and avoid the activation process. You can backup the Windows Product Activation database files to diskette. They are very small. A directory listing from my XP Pro workstation:

C:\WINDOWS\system32>dir wp*
Volume in drive C has no label.
Volume Serial Number is 8447-0571

Directory of C:\WINDOWS\system32

10/24/2001 08:28 PM 12,584 wpa.bak
01/14/2002 09:05 AM 12,642 wpa.dbl

After you reinstall XP, to restore the Windows Product Activation database files:

  • Start XP to Minimal Safe mode

  • Change directory to the \%systemroot%\system32 folder

  • Rename the newly created wpa.dbl to wpa.nonactivated and wpa.bak, if it exists, to wpabak.nonactivated.

  • Copy your backed up wpa.dbl and wpb.bak files to the system32 folder

  • Reboot


This should work if you want to avoid activating XP after a reinstall or restore on the same or very similar hardware. It will not work if the hardware is significantly different from that in place when the Windows Product Activation database files were created. This is not a hack to avoid activating installations.



Version by sticker

http://www.eggheadcafe.com/software/aspnet/31948993/reinstalling-xp-home-oem--product-key-problem.aspx


Those smaller companies use a generic OEM CD so as long as it is a Microsoft CD and not a branded one you should be OK.

One thing you need to watch out for is that you have the correct OEM CD version to go with that key. Right now if someone gives you a CD that has SP2c included your key will most likely not work. Original OEM, Sp1 and SP1a keys will all work with the same media, SP2 will only work with SP2 media, and SP2c will only work with SP2c keys.

Now the question is how the heck do you know if your keycode on the bottom of that laptop is SP1, 1a, 2 or 2c. . If it is rectangular, shiny, and has a blue border with white center and the holograms say "Microsoft GENUINE" at an angle it is most likely SP1 or 1a. If it is an odd bubble shape that is blue, yellow and green and the keycode is on the bottom and the bar codes are on the left and right then you have SP2.




Moral of the story: build up your collection of CDs of as many different versions of OEM and windows versions as you can for use in the future. LABEL them as to what they exactly can do.


This is perfectly legal, and free when users are throwing out their old PCs along with the now increasingly valuable disks (often still in their original shrink-wrap :)


Who said hoarding was a problem

Sunday, 8 August 2010

SATA drives - what you need to know on older systems

Modern motherboard cater well for SATA as do recent iterations of various operating systems, but older pcs can be a challenge.

It's good to understand the basics.

Drivers for the SATA type drive must be loaded in addition to the standard set provided by XP install disks.. see for example this good post on how to chkdsk a troublesome sata drive: http://www.windowskb.com/Uwe/Forum.aspx/windows-xp-support/99602/Running-CHKDSK-on-a-SATA-Harddrive.

The other little conundrum is when a cloning an IDE to a new bigger better faster SATA drive, all goes well until the system is rebooted. Assuming you remember to set the bios boot options to chose the sata disk, then you'd think all would be well.
But if you leave the old ide source disk connected, then Windows in its wisdom enumerates the original partitions drive on the old drive from C, resulting in the new operating system on the sata drive with a drive letter other then C - sometimes way down the alphabet (if there are partitions more or usb media card readers) .

I don't know about you, but I found it unnerving to have windows on the J drive!


Granted it may actually work, but why mess with things you don't gotta mess with? (Especially on a customer's system where you cannot possibly test all the programs)?!

The trick is to UNplug the old ide drive the first time you boot the system after cloning. AND you need to delete the partitions or format the old drive as well before plugging it back in.

Reading here shows others have found this out too: http://www.experts-exchange.com/Storage/Misc/Q_21664352.html?sfQueryTermInfo=1+10+30+drive+id+letter+sata+xp
Summary after cloning, remove the source disk, or else windows will see two identical volume identifiers and assume something is wrong..
So the moral of the story is: (a) clone the drive; (b) switch the drives or remove the source; and (c) THEN reboot. Delete the partition on the source using another PC (or with the destination disk removed). Then put the source back and the now clean original disk which will come up missing but can be added in again using the disk manager. This works even from IDE to SATA (where you want to put the old small IDE disk back in as a backup drive and use the new, fast SATA to boot and work from most of the time).

Another example
http://www.experts-exchange.com/Storage/Misc/Q_21281623.html?sfQueryTermInfo=1+10+30+drive+id+letter+sata+xp

Oh, and one other useful post I found summarises as:
once WinXP has rebooted in after a fresh install of the operating system get your motherboard cd driver disk and install the winxp Sata/ Raid drivers before you install sp2 or anything else.