Download (direct link):
10. False. See the section entitled 'Recovery Console' for more.
Your first introduction to Windows XP system recovery may be an early one if the setup process fails to complete correctly.
Several situations or conditions can cause the Windows XP setup program to fail at various different points. The following list describes common failure modes along with recommended fixes:
* Inadequate disk space: The general rule is that you should have 2GB of free space on the partition (not necessarily disk!) to which you're installing Windows XP Professional.
* Failure to detect essential hardware: For example, if the setup program doesn't recognize your CD-ROM drive, you can start an upgrade from Windows 98 but you may not be able to continue it after the first reboot. In such a case, you may need to use a different drive (one that's on the Hardware Compatibility List) or install Windows from a network distribution server.
* Conflicts with running applications: If you're upgrading from an earlier version of Windows, you may need to disable any third-party power management, antivirus, disk quota, and networking software before running setup. (Note that this includes BIOS-based antivirus software!)
* Failure to find server(s): If you tell setup that you want to join an existing domain, a domain controller and DNS server (they may be the same machine) must be up and connected to the PC where you're installing Windows XP Professional. You also have to get the domain name correct when running the setup program and make sure that the local computer name is unique among other computer names, domain names, and workgroup names.
* Flaky hardware: If a disk controller, memory module, or other essential piece of hardware isn't performing up to spec, Windows XP Professional may consistently fail to install. Any newly added hardware is suspect. Consider updating device firmware (such as a SCSI controller's BIOS) before tossing the hardware in the trash bin.
The trail of crumbs
The setup program makes a number of plain-text log files as it goes along, recording the things that go right as well as those that go wrong. You don't have to memorize all of them (the list is quite long). Here are the key ones you should know for the exam (the list assumes you install Windows XP into the default folder C:\WINDOWS):
* C:\WINDOWS\SETUPACT.LOG is a chronological list of pretty much every action the setup program takes, after its graphical mode begins, and any errors that the program encounters. Microsoft sometimes calls this the "action log."
* C:\WINDOWS\SETUPERR.LOG, or simply the "error log," just has the errors in it, along with severity codes.
* C:\WINDOWS\WINNT32.LOG records the checking of available disk space and the copying of temporary boot files (for example, from the installation CD-ROM to the hard drive's system partition).
* C:\WINDOWS\DEBUG\NETSETUP.LOG covers network connection steps.
* C:\WINDOWS\SECURITY\LOGS\SCESETUP.LOG includes details of access control settings on Registry keys and files. (The "SCE" part of the filename stands for Security Configuration Editor.)
* C:\WINDOWS\SETUPAPI.LOG includes details on processing of *.INF files, that is, a whole lot of hardware device driver information.
* C:\WINDOWS\COMSETUP.LOG includes details on installation of COM+ (Component Object Model) modules.
Warning Most of the log files live in C:\WINDOWS but a few live elsewhere. Don't ask me why, just memorize the exceptions.
Sometimes Windows XP installs okay, but one or more applications that worked under Windows 98, Me, or NT don't work right anymore. Four ideas:
* You may be able to fix such problems with upgrade packs, which are typically DLL files that you get from the application supplier.
* You can also experiment with the settings on the EXE file's property sheet, in the Compatibility tab. You can fool the application into thinking that it's running under Windows 95, 98/Me, NT 4.0 SP5, or Windows 2000; you can also force the program to run in a restricted display mode.
* The application may expect users to have rights and access permissions that they no longer have because the Windows XP 'Users' group is more tightly restricted than in Windows NT 4.0. Try running the application when logged on as a member of the Power Users group. If that's not practical, consider applying the COMPATWS.INF security template.
* If the application is consistently crashing, check C:\Documents and Settings\All Users\Application Data\Microsoft\DrWatson\ DRWTSN32.LOG. If the log mentions an executable file that's part of your cranky application, e-mail the log to the software manufacturer for analysis and (perhaps) a fix.
Separate from setup problems are problems that occur when Windows XP boots. True, these problems may occur immediately after a fresh installation, but they may also crop up at later dates, and they often require different troubleshooting approaches.