Reviewing Windows Vista

In this multi-part review of Windows Vista, I will attempt to provide you with the information you need to decide whether you want Windows Vista now, in the near future, or later. (Let's face facts: Not ever upgrading isn't really an option.) I'll explain the differences between the various product editions, discuss each of the major new features, and tell you which I think are valuable and which you can safely ignore. I'll discuss Vista's hardware and software compatibility prowess (or lack thereof) and explain why you may want to hold off on that x64 version you've been considering. And by the time I'm done--sometime in the days ahead, but well ahead of Vista's general availability--I hope I'll have communicated why this major new Windows version is so important and, ultimately, so desirable.
The review will be broken down into several parts, which I'll publish over time. This first part of the review is largely introductory material. In Part 2, I'll explain the different Vista product editions and provide you with the simple information you need to determine which version is for you. Part 3 covers the installation process, including interactive setup, upgrading from XP, and even corporate deployment. In Part 4, I'll highlight what I think of as the Vista experience, explaining what you get in the box, the overall look and feel of the new Vista UIs, and how its performance compares with that of previous Windows versions.
Part 5 of this review will focus on new Windows Vista features, including the advances Microsoft has made in digital media, networking and Internet, and security

. In Part 6, I'll look at compatibility, both hardware and software, and on both 32-bit (x86) and 64-bit (x64) systems. Part 7 will discuss the dark side of Vista, the inconsistent and undesirable features that will leave you shaking your head. And finally, I'll wrap it up in Part 8 with information about availability and pricing and my conclusions.

A quick look back over the past five years

In mid-2001, my son Mark was three and my daughter hadn't even been born yet. We lived in a different, smaller, home, and the tragedies of 9/11 were still ahead of us. Today, over five years later, much has changed. My son is now over 8 years old and his soon-to-be-five-year-old sister Kelly is like a bossy buddy he can't quite shake. We live in a different house, and though it's supposed to be a better neighborhood, I'm haunted daily by the never-ending sounds of lawn machines, leaf-blowers, or snow removal equipment, depending on the time of year. Put simply, a lot has changed.
In the wider technology world, by mid-2001, Microsoft was getting ready to ship Windows XP and Apple had recently shipped the first version of Mac OS X, a product that was so woefully inadequate that even it's most ardent supporters ruefully referred to it as a public beta. Every year, it seemed, the Linux desktop was poised to take off. That, still, has never happened.
Apple and its supporters will tell you that Apple spent the past five years churning out major new Mac OS X versions while Microsoft fumbled around trying to finish Windows Vista. This is completely untrue. Though I use and respect Mac OS X, virtually every version Apple has shipped since 2001 has been a minor update, akin to a Windows 98 SE or Windows XP Service Pack 2 (SP2). Meanwhile, Microsoft has pushed an amazing variety of Windows versions out the door since 2001. Some highlights include Windows XP Embedded, Windows XP Media Center Edition (MCE), Windows XP MCE 2004, Windows XP MCE 2005, Windows XP Tablet PC Edition (TPC), Windows XP Tablet PC Edition 2005, and Windows XP Professional

x64 Edition. It has also shipped major updates to its digital media software, including three major updates to Windows Media Player, a major IE release--IE 7--major new client-based security applications and services, including Windows Defender and Windows Live OneCare. And this is just a partial list. The point here is simple: Microsoft hasn't sat still, contrary to the FUD you read online.
So why did Vista take so long? Microsoft will tell you that Vista has really only been in active development since mid-2004, when it "reset" the original Longhorn project and restarted development on the Windows Server 2003 code base. I'd argue that this is a convenient misstatement of the facts: Windows Vista is Longhorn and Longhorn is Windows Vista. In short, Microsoft did take five years to bring Longhorn--sorry, Windows Vista--to market.

As it turns out, the reason why is simple. Microsoft screwed up, plain and simple. Each version of Windows is based on the version that came before it and because Windows Vista was envisioned as a kitchen sink release that would include every major new feature imaginable, it eventually teetered and fell under the weight of the technology Microsoft was heaping upon it. That Vista is now based on the Windows Server 2003 code based and not that of Windows XP is meaningless. When the project started, back in 2001, it was based on Windows XP.

After the reset, Microsoft scaled back the Vista feature-set dramatically and ensured that features were added in a more logical fashion. The two year development time that Microsoft refers to in this case is the most recent two years, the period of time during which Vista got back on track. This is a period of time that Microsoft should be justifiably proud of. The previous three years? Trust me, we'd all like to forget that.
But the problem with the five year gestation isn't that OS X and Linux have caught up and in some ways surpassed Windows, which of course they have in some respects. The problem isn't even that Microsoft promised us the world and then failed to deliver. No, the problem is that there's another OS out there that runs just fine on over 400 million computers around the world. That system is stable, secure, and gets the job done. It's Windows Vista's biggest competitor. To be fair, it's Windows Vista's only competitor. Maybe you've heard of it: It's called Windows XP.

How to perform and automatic repair of Windows Vista using Startup Repair

If you are having problems starting Windows Vista, then your first step is to use the automated repair tool called Startup Repair. Startup Repair is a diagnostic tool that can be accessed via the Windows Recovery Environment. In order to start the Windows Recovery Environment you must boot your computer off of the Windows Vista DVD that you purchased or that came with your computer. To start this process, insert the Vista DVD into your DVD drive and turn your computer on. Your computer will start and you should see your BIOS listing your hardware and other information. When that information is cleared, your computer will see that a bootable DVD is inserted and present a prompt ...
As you want to boot the computer from the Windows Vista DVD you need to press a key, and any key will do, on your keyboard when you see the above prompt. After you press the key, you should hear your DVD reader spinning up and then you will see a black screen with a white status bar at the bottom stating Windows is loading files.... After a while, the status bar will turn completely white and you will see a screen stating that Windows is loading. The Windows Setup environment will continue to load and when finished you will be presented with a screen At this screen you should configure the Language to install, Time and currency format, and Keyboard or input method options so that they are set correctly. When done, press the Next button. You will now be at the main Windows Vista setup screen where you would normally install Vista on to a computer.
As we want to repair the computer, you should click on the Repair your computer option. This will bring you to a new screen where the repair process will look for all Windows Vista installations on your computer. When done you will be presented with the System Recovery Options dialog box.

Select the Vista installation you would like to repair and if there are drivers you need to load in order for Vista to access any of your drives or other components , then you should click on the Load Drivers button to load them. When ready, press the Next button to continue.

If the repair process does not detect any problems starting Vista, it will display a list of recovery tools. These recovery tools are discussed further in the Advanced Tools Overview section below. As we want to perform an automated repair, we would click on the Startup Repair option under this list of tools. It should also be noted that if the repair process detected that you previously had problems starting Vista, instead of displaying the list of recovery tools, it would have automatically started the Startup Repair tool for you. When the Startup Repair tool starts, it will scan your Vista installation for any problems. If problems are found it will attempt to fix these problems automatically.

The automatic repair process can take quite a while. So please be patient as Vista attempts to find and repair any problems on your computer. During this process your computer may reboot multiple times, which is normal and nothing to be worried about. During this process you may also be presented with a dialog box asking if you would like to restore your computer using System Restore.

You should click on the Cancel button at this prompt because there is a better System Restore option that can be used from the advanced tools list which we will cover later. For now, just click on the Cancel button and continue with the Startup Repair process. The repair process will now continue to scan your installation for errors to fix. Once the repair process has completed, if it could not find any problems, you will be given an option to send your information to Microsoft.

When sending this information, it is important to note that you will not receive a response back from Microsoft with a solution. Instead they use this information to determine if this is a bug that a lot of people are having and that they need to rectify or if they need to create a support article on how to fix it. If you wish to send the information, then click on the Send information about this problem (recommended) option. Otherwise, click on the Don't send option. You will now be at a summary screen.

You can now click on the Finish button to reboot your computer to exit the repair process or if you would like to try some more advanced options then click on the View advanced options for system recovery and support. We recommend that you try the advanced tools if the Startup Repair tool could not fix your problems. You can also reach the advanced tools at any time during a Startup Repair scan by clicking on the Cancel button. An overview of the advanced tools can be found with links to their individual tutorials.

Advanced Tools Overview

Vista provides advanced repair tools that you can use to fix problems with your Windows Vista installation. To reach this list of tools you would start your computer using the above process and either press Cancel during the Startup Repair process, or if no problems were detected, the list will automatically be shown. The repair process will now display the System Recovery Options screen.

This screen provides access to five tools that can help you repair your Vista installation. These tools are:

Startup Repair

Startup Repair is an automated repair process that scans your Vista installation for problems and attempts to automatically fix them. When you select to repair Vista from the Vista setup screen, and Vista detects problems, this process will be started automatically. You can cancel this process at any time to access the other repair tools described below. The Startup Repair process has already been introduced above when we discussed performing an automated repair.

System Restore

System Restore allows you to restore your computer's configuration, driver information, and programs to a previous state while leaving your existing data intact. Using this option can typically fix a installation's problem if it is not associated with faulty hardware. In order to use this option, you must have had System Restore enabled in Vista so that there are restore points available to restore to. To learn how to use this feature you should read this tutorial: Using System Restore from the Vista Windows Recovery Environment.

Windows Complete PC Restore

Complete PC Restore is a feature that allows you to restore your entire computing environment from a backup image that you created previously. The ability to create backup images for Complete PC Restore is only available in Windows Vista Business, Ultimate, and Enterprise. If you have tried all possible steps to repair your computer, and have a Complete PC Restore backup image available from when your computer was operating properly, then you can use this repair option to restore that image. To learn how to use this feature you should read this tutorial: Using Windows Complete PC Restore to restore your computer.

Windows Memory Diagnostic Tool

Windows Vista comes with a diagnostic tool that allows you to check the memory installed in your computer for errors. This will allow you to determine if the actual memory (RAM) hardware installed in your computer is creating errors. To learn how to use this feature you should read this tutorial: How to use the Vista Windows Memory Diagnostics Tool.

Command Prompt

The Command Prompt repair tool allows you to open a command prompt that you can use to access the files and registry information on your computer. This is an invaluable tool for removing security threats such as worms, rootkits, and other malware from your computer and to be able to access files when Vista fails to boot up.To learn how to use this feature you should read this tutorial: How to use the Command Prompt in the Vista Windows Recovery Environment.

Conclusion

With the knowledge that these tools exist and how to use them, you now have the capability to repair your Windows Vista installation in the event that problems occur. No longer should you feel held captive to your computer, but rather in control of how it operates. If you have any questions on how to use the automated repair or the advanced repair tools, please ask us in the Windows Vista Help Forum.

Users Cannot Connect to a Windows Server 2003 Domain by Using a VPN Connection

SYMPTOMS

Users cannot connect to a Windows Server 2003 domain by using a virtual private networking (VPN) connection. This problem occurs if the following conditions are true:

•	The users try to connect to the domain through a Cisco router.
•	The Cisco router uses Kerberos authentication to authenticate the users against a Windows Server 2003-based domain controller.

Back to the top

CAUSE

This problem occurs because the Key Distribution Center Service returns the wrong user name format to the router.

Back to the top

RESOLUTION

Hotfix Information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451 (http://go.microsoft.com/?linkid=6294451)

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Prerequisites

No prerequisites are required.

Restart Requirement

You must restart your computer after you apply this hotfix.

Hotfix Replacement Information

This hotfix does not replace any other hotfixes.

File Information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time   Version      Size     File name   Platform
  -------------------------------------------------------------------
  30-Sep-2003  20:21  5.2.3790.89  225,792  Kdcsvc.dll  x86
  30-Sep-2003  20:20  5.2.3790.89  584,704  Kdcsvc.dll  IA-64

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

Back to the top

MORE INFORMATION

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Back to the top

---

APPLIES TO

•	Microsoft Windows Server 2003, Standard Edition (32-bit x86)
•	Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)

Back to the top

Keywords:

kbhotfixserver kbqfe kbbug kbfix kbqfe kbwinserv2003presp1fix KB829074

To Install the Remote Access Service Server

If the remote access service server is a member of a domain, it must be a member of the RAS and IAS Servers group in that domain.

If you are not a member of the Domain Admins group, a member of that group must add this server to the RAS and IAS Servers group.

If you are a member of the Domain Admins group, the server is automatically added to the RAS and IAS Servers group after you complete the procedures that are included in this document.

To Enable the Routing and Remote Access Service and Configure a VPN Interface

1.	Click Start, point to Administrative Tools, and then click Routing and Remote Access.
2.	Click the server that matches the local server name in the left pane of the console. If the icon has a red circle in the lower-left corner, the Routing and Remote Access service is not enabled. Go to step 3. If the icon has a green arrow pointing up in the lower-left corner, the service is enabled. If so, you may want to reconfigure the server. To reconfigure the server, you must first disable Routing and Remote Access. To do this, right-click the server, and then click Disable Routing and Remote Access. Click Yes when you are prompted with an informational message.
3.	Right-click the server, and then click Configure and Enable Routing and Remote Access to start the Routing and Remote Access Server Setup Wizard. Click Next.
4.	Click Remote access (dial-up or VPN) to enable remote computers to dial in or connect to this network through the Internet. Click Next.
5.	Click VPN for virtual private access, or click Dial-up for dial-up access, depending on the role you want to assign to this server.
6.	On the VPN Connection page, click the network interface that is connected to the Internet, and then click Next.
7.	On the IP Address Assignment page, do one of the following: • If a DHCP server will be used to assign addresses to remote clients, click Automatically, and then click Next. Go to step 8. • To give remote clients addresses only from a pre-defined pool, click From a specified range of addresses. In most cases, the DHCP option is simpler to administer. However, if DHCP is not available, you must specify a range of static addresses. Click Next. The wizard opens the Address Range Assignment page. a. Click New. b. In the Start IP address box, type the first IP address in the range of addresses that you want to use. c. In the End IP address box, type the last IP address in the range. Windows calculates the number of addresses automatically. d. Click OK to return to the Address Range Assignment page. e. Click Next.
8.	Accept the default setting No, use Routing and Remote Access to authenticate connection requests, and then click Next.
9.	Click Finish to enable the Routing and Remote Access service and to configure the server to run Routing and Remote Access.

You can now configure the server as a VPN server.

Setting Up a Client for Remote Access

After you set up the server to receive dial-up connections, you must set up a remote access client connection on the user's workstation.

To Set Up a Client for a Dial-Up Connection

To set up a client for dial-up access, follow these steps on the client workstation.

NOTE: Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

1.	Click Start, click Control Panel, and then double-click Network Connections.
2.	Under Network Tasks, click Create a new connection, and then click Next.
3.	Click Connect to the network at my workplace to create the dial-up connection, and then click Next.
4.	Click Dial-up connection, and then click Next.
5.	On the Connection Name page, type a descriptive name for this connection, and then click Next.
6.	On the Phone Number to Dial page, type the phone number for the remote access server in the Phone Number dialog box.
7.	Do one of the following, and then click Next: • If you want to allow any user who logs on to the workstation to have access to this dial-up connection, click Anyone's use. • If you want this connection to be available only to the currently logged-on user, click My use only.
8.	Click Finish to save the connection.

To Set Up a Client for a VPN Access Connection

To set up a client for VPN access, follow these steps on the client workstation:

NOTE: Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

1.	Click Start, click Control Panel, and then double-click Network Connections.
2.	Under Network Tasks, click Create a new connection, and then click Next.
3.	Click Connect to the network at my workplace to create the dial-up connection, and then click Next.
4.	Click Virtual Private Network connection, and then click Next.
5.	On the Connection Name page, type a descriptive name for this connection, and then click Next.
6.	Do one of the following, and then click Next: • If the computer is permanently connected to the Internet, click Do not dial the initial connection. • If the computer connects to the Internet by way of an Internet service provider (ISP), click Automatically dial this initial connection, and then click the name of the connection to the ISP.
7.	Type the IP address or the host name of the VPN server computer (for example, VPNServer.SampleDomain.com).
8.	Do one of the following, and then click Next: • If you want to allow any user who logs on to the workstation to have access to this dial-up connection, click Anyone's use. • If you want this connection to be available only to the currently logged-on user, click My use only.
9.	Click Finish to save the connection.

To Connect to the VPN Server

After you create a VPN connection on your local workstation, you can connect to the server. To do this, follow these steps.

NOTE: Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

1.	Click Start, point to Connect To, and then click the new connection that you created.
2.	In the User Name box, type your user name. If the network to which you want to connect has multiple domains, you may have to specify a domain name. If this is the case, use the domain_name\user name format in the User Name box.
3.	In the Password box, type your password.
4.	If you use a dial-up connection, check the phone number that is listed in the Dial box to make sure that it is correct. Make sure that you have specified any additional numbers that you must have to obtain an external line or to dial long-distance.
5.	Click Dial or Connect (for VPN connections). Your computer establishes a connection to the remote access server. The server authenticates the user and registers your computer on the network.

Configuring the Server to Accept Remote Clients and Granting Remote Access Rights to Users

In Windows Server 2003, authorization is granted based on the dial-in properties that you set in the user account in Active Directory and on the remote access policy that you set for the remote access server. With remote access policies, you can grant or deny authorization based on criteria, such as the time of day, day of the week, the user's membership in Windows Server 2003 security groups, or the type of connection that is requested.

When you install the Routing and Remote Access service and you configure the server that will run it, Windows creates a default policy that grants access to all users, provided that dial-in permissions have been enabled (these permissions are configured on a user-by-user basis). For users to be able to dial-in and authenticate to a remote access server, these settings must be enabled in their user accounts.

When the server is a member of a domain, you can set these settings by using the users' domain accounts.

When the server is a standalone server or member of a workgroup, the users must have local accounts on the remote access server.

To Allow the Server to Accept Remote Access Clients

1.	Click Start, point to Administrative Tools, and then click Routing and Remote Access.
2.	Double-click the server object, and then click Remote Access Policies.
3.	Right-click Connections to Microsoft Routing and Remote Access server, and then click Properties.
4.	Click Grant remote access permission, and then click OK.
5.	Close Routing and Remote Access.

To Grant Dial-up Access Permission to Individual Users

1.	Click Start, point to All Programs, point to Administrative Tools, and then click Active Directory Users and Computers.
2.	Right-click the user account for which you want to enable remote access, and then click Properties.
3.	Click the Dial-in tab, click Allow access, and then click OK.
4.	Close the UserAccount Properties dialog box.

To Grant Remote Access Permission to a User Group

1.	Create a group with members who are permitted to create VPN connections.
2.	Click Start, point to Administrative Tools, and then click Routing and Remote Access.
3.	In the console tree, expand Routing and Remote Access, expand the server name, and then click Remote Access Policies.
4.	Right-click the right pane, point to New, and then click Remote Access Policy.
5.	Click Next, type the policy name, and then click Next.
6.	Click VPN for virtual private access, or click Dial-up for dial-up access, and then click Next.
7.	Click Add, type the name of the group that you created in step 1, and then click Next.
8.	Follow the on-screen instructions to complete the wizard.

If the VPN server already permits dial-up networking remote access services, do not delete the default policy; instead, move it so that it is the last policy to be evaluated.

Troubleshooting

If You Receive an Error Message That the Specified Destination Is Not Reachable

Verify that the client is connected to the network. To test whether the remote server can be contacted, follow these steps:

1.	Click Start, point to Programs, point to Accessories, and then click Command Prompt.
2.	At the command prompt, type the following, and then press ENTER: pingservername

If the ping request times out, try pinging the IP address of the remote server to see if there is a Domain Name System (DNS) name resolution issue.

If You Can Contact the Server, but You Cannot Successfully Authenticate

Verify that the user account that you are using has been granted permission to dial in and authenticate with Active Directory. The server that you are contacting must be a member of the RAS and IAS Servers group.

---

APPLIES TO

•	Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
•	Microsoft Windows Server 2003, Standard Edition (32-bit x86)
•	Microsoft Windows Small Business Server 2003 Premium Edition
•	Microsoft Windows Small Business Server 2003 Standard Edition

Keywords:

kbnetwork kbnetwork kbsecurity kbhowtomaster KB324747

This file is set up to automatically select the "1ST TRY THIS" choice after 30 seconds. Try it first, if it was the wrong selection, you will likely get one of these four errors:

1. Windows could not start because file "\system32\hal.dll was missing or corrupt

2. Windows could not start because of a computer disk hardware configuration problem. Could not read from the selected boot disk. Check boot path and disk hardware. Please check the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information.

3. I/O Error accessing boot sector file multi(0)disk(0)fdisk(0)\BOOTSECT.DOS

4. Immediate reboot

If you get the immediate reboot or some other weird error, try pressing F8 at the "1st Try This" selection screen, it will give you a prompt where you can select Safe Mode, and then try the "1st Try This" option again. Safe Mode is a special "minimal" version of Windows that doesn't load certain parts of the operating system that might have caused the problem.

One of the choices should eventually boot you back into Windows. (What if none of the options worked?) .

Use windows to fix the boot files on the hard drive.

If you got back into Windows, stop whatever you are doing and backup your most important information from this computer.

Now that you are done backing up the most important info, try to change back whatever you were last doing and boot normally, it that doesn't work, put the floppy back into the broken computer and double click the fixntldr.bat file on the floppy drive, if it asks you to overwrite a file, just type in y for yes (the file copies boot.ini, ntldr, ntdetect.com from the floppy to the C:\ drive and removes the read only attributes). That process take a few minutes, then remove the floppy and reboot.

If you are using the cd or usb solution, copy the boot.ini, ntldr, and ntdetect.com files to My Computer > Local Disk C:\ > and overwite whatever files might be there, then right click each file, choose properties, uncheck the Read Only attribute, and click OK.

If you get back into Windows again, you can change that "1st Try This" menu by going into Start > Control Panel > System > Advanced tab > Startup and Recovery section, Settings button > System Startup; then change the "Default Operating System:" to the selection that worked for you, and change the box that says "Time to display list of operating systems" to however many seconds you want (usually 1 second). Click OK twice. (What if the bootdisk worked, but I can't get into Windows without it?) .

NTLDR missing, press any key to restart

How to fix: NTLDR is missing, press any key to restart

What happened?

When your computer starts, the BIOS attempts to find the primary hard drive's active partition to read the first sector for the MBR (Master Boot Record), it uses that info to load the rest of the OS. For Windows NT4/2k/XP the NTLDR (New Technology Loader) takes it from there. If you get the "NTLDR is missing, press any key to restart" what's most likely going on is the BIOS either didn't look for the right drive, didn't find the right partition, it wasn't active, didn't find the MBR, or the MBR didn't list NTLDR in the right place, the location of NTLDR changed, or you are looking at a hardware failure situation (memory/cables/drive/motherboard/etc). Windows Vista does not boot this way, you can still use my floppy to boot into an existing installation of 98/nt/xp, but I've not had a chance to test Windows Vista.

If possible, try to change back whatever hardware or software change you just made (this could be as simple as leaving a floppy disk in the drive or you need to recheck the cables). (What if I made new changes that I want to keep?).

Make a NTLDR boot disk to get back into Windows.

The quick test to make sure your OS installation is still good is to create an MBR and NTLDR on a floppy disk and check your partitions, this disk will check many of the partitions for a working windows installation. Here are the instructions to do this:

1. Get a blank floppy (whatever is on it will be erased), and put it into a working computer (What if the computer doesn't have a floppy drive?).

2. Download fixntldr.exe onto a working computer (fixntldr-winnt if you are using Windows 2000 or Windows NT4) (What if I don't want to download a file from a website I don't trust?). (What if my backup system is Mac / Linux or another alt OS?).

3. Run the fixntldr.exe file by double clicking it. Click OK to overwrite the blank floppy disc in the working computer, you should see some screens about writing a new floppy disk.

4. Do you remember if the folder you had your Windows installation in was named "Windows"? If you can't remember just keep going (What if it was not named Windows but WINNT like in NT4 or 2000?) .

5. Put the new floppy (or cd/usb drive) you have just created into the computer that gets the NTLDR is missing error message, turn the broken computer off.

Using the boot disk in the computer with the "NTLDR is missing" error.

remove login password

Direct Bootup Without Typing Password

1. At a command prompt, type "control userpasswords2" and press Enter to open the Windows 2000-style User Accounts
application.
2. On the Users tab, clear the Users Must Enter A User Name And Password To Use This Computer check box and then
click OK.
3. In the Automatically Log On dialog box that appears, type the user name and password for the account you want to be
logged on each time you start your computer.

Remove Login Password

Control Panel/Administrative Tools/Local Security Settings/Minimum Password Length/Reduce it to 0 (No password required). Control Panel/User Account/Your Account/Remove Password.

Cannot Change the Administrator Password in Control Panel

After you log on as an administrator to a computer that is not a member of a domain, when you double-click User Accounts in Control Panel to change the password for the built-in Administrator account, the Administrator account may not appear in the list of user accounts. Consequently, you cannot change its password.

This behavior can occur because the Administrator account logon option appears only in Safe mode if more than one account is created on the system. The Administrator account is available in Normal mode only if there are no other accounts on the system. To work around this behavior:

- If you are running Windows XP Home Edition, restart the computer and then use a power user account to log on to the
computer in Safe mode.

- If you are running Windows XP Professional, reset the password in the Local Users and Groups snap-in in Microsoft
Management Console (MMC):

1. Click Start, and then click Run.
2. In the Open box, type "mmc" (without the quotation marks), and then click OK to start MMC.
3. Start the Local Users and Groups snap-in.
4. Under Console Root, expand "Local Users and Groups", and then click Users.
5. In the right pane, right-click Administrator, and then click Set Password.
6. Click Proceed in the message box that appears.
7. Type and confirm the new password in the appropriate boxes, and then click OK.