These are the instructions for replacing the Windows XP License Key on an existing system.

http://www.mwright.plus.com/xp.htm

http://support.microsoft.com/newsgroups/default.aspx? NewsGroup=microsoft.public.win2000.networking&SLCID=US& ICP=GSS3&sd=GN&id=fh;en-us;newsgroups

(Remove the spaces)

http://support.microsoft.com/newsgroups/default.aspx?NewsGroup=microsoft.public.win2000.networking&SLCID=US&ICP=GSS3&sd=GN&id=fh;en-us;newsgroups

To change the licensing mode for a server to Per Seat licensing

1.. Open Licensing.
2.. On the Server Browser tab, expand the domain name.
3.. Right-click the site license server in the domain, and then click Properties.
4.. On the Products View tab, click the product, and then click Edit.
5.. In Choose Licensing Mode, click Per Seat, and then click OK.
6.. After reading the information in Per Seat Licensing, select the check box to agree to be bound by the license agreements for this product, and then click OK.

Notes

a.. To open Licensing, click Start, point to Settings, and then click Control Panel. Double-click Administrative Tools, and then double-click Licensing.
b.. The Per Seat licensing mode requires a client access license for every computer that connects to the selected server product. Once a computer is licensed, it can access any computer running the product. This is usually more economical on networks where clients connect to more than one server.
c.. If you are uncertain which mode to use, leave the server product in Per Server mode. The license agreement allows a one-time, one-way option to change from Per Server to Per Seat licensing. You are not permitted to switch back.
d.. If you are performing a one-time change from Per Server to Per Seat licensing mode, the Client Access Licenses allocated to the server in Per Server mode can be added to the pool of Per Seat licenses available for client computers accessing the server product on any computer in the site.
e.. To perform this procedure locally on a server, click Licensing in Control Panel.

There’s a .csv file from Microsoft here:

http://www.microsoft.com/windows2000/techinfo/reskit/ErrorandEventMessages/

Download windbg tools from http://www.microsoft.com/whdc/ddk/debugging/default.mspx

Symbol server technology is built into Debugging Tools for Windows. Microsoft is now providing an internet symbol server that contains symbol files for the Microsoft Windows 2000, Windows XP, Windows Server™ 2003 operating systems, and some other Microsoft products. When you set your symbol path to use the symbol server, the debugger will download symbols as needed during the debugging session. The symbols are downloaded to a directory location that you specify and then the debugger loads them from there.

The documentation that comes with Debugging Tools for Windows describes the symbol server technology in more detail. To use the internet symbol server, follow these steps:

Install the latest Debugging Tools for Windows package and start a debugging session. Pick a location to store the symbols that are downloaded. The documentation refers to this location as a “downstream store”. This can be a local drive or a UNC path.

Add SRV*downstream store*http://msdl.microsoft.com/download/symbols to your symbol path, substituting your own downstream store path for downstream store.

For example, if you want the symbols to be placed in c:\websymbols, then set your symbol path to this: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

Please note that the site http://msdl.microsoft.com/download/symbols is not browseable and is only intended for access by the debugger. Continue with your debugging session.

The internet symbol server is currently populated with a tremendous variety of Windows symbols for Microsoft Windows operating systems, including hot fixes, Service Packs, Security Rollup Packages and retail releases. Symbols for current Betas and Release Candidates for Windows products are also available on the server.

Symbols from a variety of other Microsoft products, for example, Internet Explorer, are also available on the server.

Debugging Help – For help with debugging issues please submit a request for online help or use the additional resources at DDK Developer Support.

——————————————–
Summary:

Add this to the symbol path to use windbg crash debugger:

SRV*c:\temp*http://msdl.microsoft.com/download/symbols

How do I recover from a corrupt Event log?

When you run the Event Viewer, any of the following messages usually indicate a currupt event log:

The handle is invalid Dr. Watson Services.exe Exception: Access Violation (0xc0000005), Address: 0x76e073d4

When you click OK or cancel on the Dr. Watson error message, you may also receive the following error message: Event Viewer Remote Procedure Call failed.

The Event Logs (Sysevent.evt, Appevent.evt, Secevent.evt) are always in use, so you can not delete or rename them.

Use any of the following methods:

** Alternate Install
Boot the alternate install, delete the Event logs from the %Orig_SystemRoot%\system32\config folder.

** Logon Locally
Use Control Panel / Services / Eventlog to configure Startup as Disabled.
Shutdown / Restart Windows NT.
Delete the Event logs from %SystemRoot%\system32\config.
Use Control Panel / Services / Eventlog to configure Startup as Automatic.
Shutdown / Restart Windows NT.

** Connect remotely
Use Regedt32 to alter the Start of the EventLog service to 0×4 (Disabled).
Use Shutdown from the Resource Kit to restart the computer.
Delete the Event logs (remotely or locally).
Use Regedt32 to alter the Start of the EventLog service to 0×2 (Automatic).
Shutdown / Restart Windows NT.

Here is the link for our memory diagnostic utility:

http://oca.microsoft.com/en/windiag.asp

enter this command in windbg to get help

.hh dbgerr004