Browsing "Windows XP"

How can I change a BSOD (Blue Screen Of Death) to another color?

When you receive a STOP error, Windows displays the STOP on a Blue screen, hence the name BSOD (Blue Screen Of Death).

If you prefer a Red screen with White text, or any other color combination that is easier for you to see:

1. Open %SystemRoot%SYSTEM.INI in Notepad.exe.
2. Locate the [386enh] section.
3. If the MessageBackColor= and MessageTextColor= entries are present, change them. Otherwise, add them to the end of the section. To have a Red screen with White text, use:

MessageBackColor=4
MessageTextColor=F

Using the following codes (case is important):

0 = black
1 = blue
2 = green
3 = cyan
4 = red
5 = magenta
6 = brown
7 = white
8 = gray
9 = bright blue
A = bright green
B = bright cyan
C = bright red
D = bright magenta
E = bright yellow
F = bright white

4. Save the changes to the %SystemRoot%SYSTEM.INI file.
5. Shutdown and restart your computer.

Windows XP Product Key Viewer

The Magical Jelly Bean Keyfinder is a freeware utility that retrieves your Product Key (cd key) used to install windows from your registry. It has the options to copy the key to clipboard, save it to a text file, or print it for safekeeping. It works on Windows 95, 98, ME, NT4, 2000, XP, Server 2003, Office 97, and Office XP.

Download Here

Free Windows Live Messenger Invites!!

Yes I have some MSN Messenger Live invites to give out.

Want one?

Its easy, just leave a comment and explain why you prefer Windows over Unix.

I will pick the best replies and mail the invites out.

Good luck !

How can I burn a CD-ROM image from the command line?

The Windows Server 2003 and Windows XP resource kits provide the cdburn.exe utility, which, like the dvdburn.exe utility, can burn an ISO file to a physical CD burner drive and uses the format

cdburn <drive>: <image>

Typing cdburn with no parameters will list the utility’s Help information, which includes additional options related to the speed of the burn, type of write mode (e.g., session-at-once instead of the default track-at-once), and sector postgap options.

How can I migrate shares and their data between servers?

Microsoft provides the Microsoft File Server Migration Toolkit (FSMT), which you can download from Here . The tool lets you migrate shares and data from any server running Windows NT 4.0 or later to a Windows Server 2003 (or Windows Storage Server 2003) machine.

The utility also interfaces with DFS, which lets you maintain the original UNC path of the data and avoid complications with accessing data once it has been migrated. However, Windows Server 2003 Enterprise Edition lets you maintain the original UNC path, and if the old UNC path doesn’t need to be maintained, DFS isn’t required.

Mar 6, 2006 - General, Windows XP    No Comments

When you attempt to install Office 2003 on Windows XP, you receive ‘ERROR 1921’?

While installing Office 2003 on Windows XP, you receive a message similar to:

ERROR 1921
Service ‘MDM’ could not be stopped. Verify that you have sufficient privileges to stop system services.

This behavior occurs if the Machine Debug Manager service is not configured to start automatically.
To resolve this problem:

1. Open a CMD.EXE window.
2. Type the following command and press Enter:
REG ADD “HKLMSYSTEMCurrentControlSetServicesMDM /V Start /T REG_DWORD /F /D 2
3. Shutdown and restart Windows XP.
4. Install Office 2003.

Are there any registry keys or files that the account specified for a performance alert requires?

When you create a performance alert, by default it runs as the Network Service account. However, you can specify a different account for its execution. If you specify another account, ensure that the named account has the following rights:

* Read access to HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionPerflib
* Full Access to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesSysmonLog and its subkeys
* Read access to the files %windir%system32PERFC*.dat and %windir%system32PERFH*.dat

Can I disable the Message Transfer Agent (MTA) on Microsoft Exchange Server 2003?

Microsoft has changed its stance about disabling the MTA on Exchange Server 2003. In Exchange 2000 Server, you couldn’t disable the MTA, but because of limitations with the MTA in cluster environments and because its primary use is for communicating with Exchange 5.5 servers, Exchange 2003 lets you disable the MTA.
The main problem with maintaining the MTA is that in a cluster, only one Exchange Virtual Server hosts the MTA resource, which is responsible for all mail transportation to Exchange 5.5 servers or third-party connectors for all databases hosted on the entire cluster. But the MTA can communicate with only 50 databases (60 with a change to the system; see the Microsoft article “How to increase the number of databases that are supported by the MTA service when Exchange Server 5.5 coexists with a server cluster that is running Exchange Server 2003” here ). Because each node in a cluster can host 20 databases (five database over four storage groups), if you have more than three active nodes the MTA can’t communicate on behalf of all the databases in the cluster. For more information about disabling the MTA, see the Microsoft article “MTA Stacks service supportability guidelines for Exchange 2000 Server and Exchange Server 2003” here
If you don’t require Exchange 5.5 communication or third-party connectors, and you want more than 60 databases in a cluster, you need to disable the MTA

Related Posts Plugin for WordPress, Blogger...