Windows XP Activation Fix

-
I ran across a situation where after doing a repair on Windows XP, the system thought the OS had not been activated and that my 30-day grace period was up. In addition, whenever I would click 'yes' I do want to go ahead and activate, the system would reboot itself. It is also not possible to activate from safe mode. I have read that this is something of a common problem with SP3.

It turns out that Microsoft has created an application for system administrators and PC makers that allows you to put the system into a 'factory mode'. The result is that you have an unactivated OS with a 30-day grace period to activate again.

The tool is called SysPrep which you can download with a set of tools provided in a cab file from Microsoft. Here are the steps to follow:

1.) Boot into safe mode with the command prompt option.
2.) Run 'explorer'.
3.) Export the files from the cab file into some location via 'My Computer'.
4.) Run the sysprep executable.
5.) Choose the "factory" option (the system will shut down when the operation completes).
6.) Boot into Normal mode.
7.) Restart the system again (your system may reboot automatically if you try to log in).
8.) You can now use Windows XP for 30 days and/or reactivate.

Note1: If the SysPrep window continues to open every time you restart, rename the folder where you saved the tool to something else.

Note2: This process is repeatable in the event your grace period expires or the activation gets confused again.

Comments

Post a Comment

Popular posts from this blog

Form.Show() From Another THread - C#.Net

-
Today I ran into a mojor headache. I have a main form that instantiates a secondary form from its constructor. I also register to a receive data event that I have based on a socket. Because the socket uses threading, when my event delegate is called, it is being called from the context of another thread. It is inside the execution of the delegate that I ran into trouble. When I receive data from the socket, I want to open the secondary form and do something with it. Immediately I know that I am going to have to use Invoke on the secondary form in order to safely modify it from the other thread. My original attempt looked like this (I will use an inline delegate here to simplify this listing): void dataReceived() { If(secondaryForm.InvokeRequired) { MethodInvoker myDelegate = delegate { secondaryForm.Show(); //do other work on secondaryForm }; secondaryForm.Invoke(myDelegate)
Read more

Hello World

-
This blog will be my attempt to keep track of random coding techniques that I run across, or anything else code related that I find useful. If all goes well, I will begin adding posts soon.
Read more

A Quick Note On Ports and Sockets

-
At this point, most people are familiar with the use of an IP address. Basically it is a unique number used on a network to identify a network computer. When we talk about computers communicating with each other, an IP address alone is useless. A single computer may have many programs running that want to communicate over the network. This means that a single address point (the IP address) is not enough to define what program a remote computer would like to communicate with. This is where port numbers come in. A program can bind itself to one or many open ports (meaning they are not currently in use by another program). Once bound to a port, a remote computer can communicate with a program by addressing the computer's address (IP) along with the program's address on that computer (Port). A common misconception is that a socket represents a bound port on a computer (the IP:Port pair). In reality, this is only half of what a socket represents. In fact, a socket represe
Read more