XP Troubleshooting Guides

	During this session, we will describe the new tools that ship in Microsoft Windows XP as well as the support tools, and how they can be used by support professionals. This session assumes that you have introductory-level knowledge of the command shell, Cmd.exe, and how command-line tools work; prior knowledge of the tools is not required. There are more than 40 new tools in Windows XP that can help you identify and troubleshoot issues, as well as automate routine maintenance tasks. We will discuss these tools as well as the batch and script language that can be used to automate the tools.
	ADPlus is a tool from Microsoft Product Support Services (PSS) that can troubleshoot any process or application that stops responding (hangs) or fails (crashes). Frequently, you can use ADPlus (ADPlus.vbs) as a replacement tool for the Microsoft Internet Information Server (IIS) Exception Monitor (6.1/7.1) and User Mode Process Dump. These are two separate tools that PSS frequently uses to isolate what causes a process to stop responding (hang) or quit unexpectedy [sic] (crash) in a Microsoft Windows DNA environment. What does ADPlus do? When should you use ADPlus? When should you not use ADPlus? Where do you obtain ADPlus? How does ADPlus work? Hang mode Crash mode First chance exceptions Second chance exceptions ADPlus command line switches Run ADPlus for the first time Typical ADPlus usage scenarios Process stops responding or consumes 100 percent CPU utilization Process quits unexpectedly MTS or COM+ server application quits unexpectedly Run in crash mode remotely In Crash Mode, ADPlus automatically configures the debugger to monitor for the following types of exceptions: Invalid Handle Illegal Instruction Integer Divide by Zero Floating Point Divide by Zero Integer Overflow Invalid Lock Sequence Access Violation Stack Overflow C++ EH Exception Unknown Exception
	When you start your computer, you may receive one of the following error messages: STOP: 0x0000007B (parameter1, parameter2, parameter3, parameter4) INACCESSIBLE_BOOT_DEVICE Setup has encountered a fatal error that prevents it from continuing. Contact your product support representative for assistance. The following status will assist them in diagnosing the problem. (0x4, 0x1, 0, 0) Setup cannot continue. Power down or reboot your computer now.
	Describes how to troubleshoot startup problems in Windows XP if you receive an error message during startup, or your computer stops responding during startup, or, after an upgrade, programs that previously loaded during startup no longer start.
	Describes how to troubleshoot problems that occur when you write to CD-R and CD-RW discs, including hardware and device driver compatibility issues, and specific error messages.
	This article is intended to help you use the DVD Troubleshooter that is included in Windows XP Help and Support Center. The DVD Troubleshooter includes step-by-step instructions to troubleshoot the following DVD problems in Windows XP: You do not hear any sound, or you receive a message about audio. You have a problem when you use closed captioning or subtitles. When you try to play a DVD, nothing happens. When you play a DVD, the video is choppy. You receive a message about analog copy protection. You receive a message about screen resolution and color quality settings. You receive a decoder error message. You receive a message about digital copy protection. When you play a DVD, the screen is black, or there is some other display problem. You receive a region error message. You receive a video error message.
	Troubleshooting Disks and File Systems Hard disk and file system errors can result from a variety of problems, such as hardware failures, power outages, poor system maintenance, viruses, and human error. When troubleshooting problems related to disks and file systems, refer to this chapter for information about troubleshooting tools, volume and disk error conditions, viruses, and stop messages. You can also use this chapter to obtain detailed descriptions of the master boot record (MBR), the GUID partition table (GPT), and the boot sectors: New in Troubleshooting Disks and File Systems Maintenance and Troubleshooting Tools Disk and Volume Status Descriptions Viruses That Affect the MBR and Boot Sectors Repairing Damaged MBRs and Boot Sectors in x86-Based Computers Stop Messages for Disks and File Systems Other Disk Problems Disk Sectors Critical to Startup
	Windows XP Professional Resource Kit - Tools for Troubleshooting The relevant sections of the article are: Disaster Recovery Tools Disk and Maintenance Tools System File Tools
	This article lists basic steps for troubleshooting Institute of Electrical and Electronics Engineering (IEEE) 1394 devices and host controllers.
	When a device driver for a device is not available, Device Manager displays the device as Unknown Device and puts it in the Other devices branch. This is very common with universal serial bus (USB) and Institute of Electrical and Electronics Engineering (IEEE) 1394 composite devices. Also, a status of Error Code 1 or Error Code 10 may be displayed when you view the properties of the device in Device Manager.

	Lists various causes for network connectivity problems and provides troubleshooting steps.
	Many issues that you may experience on a Windows XP-based computer occur because of an incompatible or corrupted program. To determine whether this is the case, you can either perform a clean boot or restart Windows without starting the program in question. This article explains how to perform advanced clean-boot troubleshooting to determine whether the problem in question is affiliated with the core operating system or with a program that is loading in the Windows environment.
	This article describes how to troubleshoot configuration errors in Microsoft Windows XP by using the System Configuration utility (Msconfig.exe). Use this tool to modify the system configuration by selecting check boxes to eliminate issues that do not pertain to your configuration.
	Driver Verifier is included in Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver. This article describes how to use Driver Verifier to isolate and troubleshoot a driver in the system.
	Microsoft Windows XP Service Pack 2 (SP2) includes Microsoft Windows Firewall, the updated firewall software that replaces Internet Connection Firewall (ICF). If Microsoft Windows Firewall is blocking a port that is used by a service or by a program, you can configure the Windows Firewall to create an exception. Windows Firewall may be blocking a program or a service if the following conditions are true: Programs do not respond to a client's request; Client programs do not receive data from the server.
	This article describes how to perform basic troubleshooting for issues that involve the System Restore tool in Microsoft Windows XP.

	This article describes how to troubleshoot registry corruption issues. If your computer does not restart, the registry hives may be corrupted. The error messages may vary. They can include any of the following: Windows could not start because the following file is missing or corrupt:\WINNT\SYSTEM32\CONFIG\SYSTEM.ced Windows could not start because the following file is missing or corrupt:\WINNT\SYSTEM32\CONFIG\SYSTEM Windows could not start because the following file is missing or corrupt:\WINNT\SYSTEM32\CONFIG\SOFTWARE System hive error Stop 0xc0000218 (0xe11a30e8, 0x00000000, 0x000000000, 0x00000000) UNKNOWN_HARD_ERROR Stop: 0xc0000218 {Registry File Failure} The registry cannot load the hive (file): \SystemRoot\System32\Config\CorruptHive or its log or alternate. It is corrupt, absent, or not writable.
	Microsoft Windows XP supports 802.11b wireless networking with the Wireless Zero Configuration service. With 802.11b wireless networking, you can enable easy configuration and you can switch between wireless networks. To use this support, you must have a wireless network adapter that is compatible with Windows XP.
	This article describes some general troubleshooting steps for network printing issues that you may encounter in Windows XP. The article then describes symptoms and a resolution of some common network printing issues that can occur in Windows XP.
	This article describes how to troubleshoot the most common program compatibility issues that you may experience on your Windows XP-based computer. Program compatibility issues are often called application compatibility issues.
	To troubleshoot common problems that may occur when you use a fax modem or an all-in-one printer/scanner/copier/fax device to send or to receive faxes in Windows XP, follow these steps, in the order in which they are presented.
	This article explains how to troubleshoot problems you may experience with Microsoft Windows XP Home Networking. Learn how to perform the following troubleshooting tasks: How to use the Home and Small Office Networking Troubleshooter; How to determine your network structure (topology); How to troubleshoot either basic connectivity or file and printer sharing issues.
	Troubleshooting methods are provided for general issues and for any one of the following specific issues: You receive a file copy error while the Setup program is running; The Setup program stops responding; Your computer stops responding, and a black screen appears; You receive a stop message when you run the Setup program.
	This article describes how you can troubleshoot issues reading CD-ROM or DVD-ROM optical discs. This article also discusses how to troubleshoot common issues with CD-R and CD-RW devices. The steps in this article apply to compact disc (CD-ROM) drives, compact disc recordable (CD-R) drives, compact disc re-writable (CD-RW) drives, and digital video disc (DVD) drives.
	is article describes how to troubleshoot problems with your CD-ROM drive in Microsoft Windows XP.
	Many issues that you may experience on a Windows XP-based computer occur because of an incompatible or corrupted program. To determine whether this is the case, you can either perform a clean boot or restart Windows without starting the program in question.
	A number of security lockdown changes in Microsoft Windows XP Service Pack 2 (SP2) may cause problems with Windows Management Instrumentation (WMI), especially in remote scenarios. For example, Windows Firewall is enabled by default in Windows XP SP2. Also, DCOM restrictions in Windows XP SP2 are different from DCOM restrictions in earlier versions of Windows.
	This article describes how to troubleshoot the following message in Microsoft Windows XP: A network cable is unplugged. You may receive this message when you use a network cable to connect to a local area network (LAN) or to the Internet.
	Many different 16-bit programs designed to run under Microsoft Windows 3.1 have been tested with Windows XP. When you troubleshoot a 16-bit Windows-based program that is not working properly under Windows XP, consider the following items...
	How to Troubleshoot RAM Installations RAM is one of the most crucial elements installed in the computer. RAM temporarily holds data that applications need, and applications use RAM to perform tasks quickly. The more RAM a system has the less it has to access the hard drive to swap out data, the longer the hard drive will last, and the faster the system will perform.
	This article describes how to troubleshoot connection issues when you try to connect an Xbox 360 console to a Microsoft Windows XP-based computer that is running Microsoft Windows Media Connect.
	This article defines the term "black hole" router, describes a method of locating black hole routers, and suggests three ways to avoid the data loss that can occur because of a black hole router. On a TCP/IP-based wide area network (WAN), communication over some routes may fail if an intermediate network segment has a maximum packet size that is smaller than the maximum packet size of the communicating hosts--and if the router does not send an appropriate Internet Control Message Protocol (ICMP) response to this condition or if a firewall on the path drops such a response. Such a router is sometimes known as a "black hole" router. You can locate a black hole router by using the Ping utility, which is a standard utility that is installed with the Microsoft Windows TCP/IP protocol. You can then use one of three methods of fixing or working around black hole routers. When a network router receives a packet that is larger than the size of the Maximum Transmission Unit (MTU) of the next segment of a communications network, and that packet's IP layer "don't fragment" bit is flagged, the router is expected to send an ICMP "destination unreachable" message back to the sending host. If the router does not send a message, the packet might be dropped, causing a variety of errors that vary with the program that is communicating over the unsuccessful link. (These errors do not occur if a program connects to a computer on a local subnet.) The behaviour may seem intermittent, but closer examination shows that the behaviour can be reproduced, for example, by having a client read a large file that is sent from a remote host.
	This article describes ways to diagnose and resolve issues that can cause problems when you try to use one of the following to communicate with servers on the Internet: Internet browser File Transfer Protocol (FTP) Telnet
	This article describes some Simple Network Management Protocol (SNMP) service startup issues. This article also describes how to troubleshoot these SNMP service startup issues.
	This article describes how to troubleshoot common sound problems in Windows XP.
	This article describes how to troubleshoot issues that you may experience when you use the Microsoft keyboards that are listed in the "Applies to" section.
	This article describes how to troubleshoot situations where you cannot connect to SSL Secured (128-Bit) Web sites (https://) by using Microsoft Internet Explorer in Windows XP.
	Windows Media Player support for DVD playback is dependent upon the presence of a supported decoder, either hardware or software, and a supported DVD drive. When these are present, Windows Media Player provides DVD features and configuration options in the user interface. The playback for DVD, which is provided by DirectShow, uses advanced features of your video hardware, such as the Video Mixing Renderer (VMR).
	This article provides information to help you troubleshoot Layer 2 Tunnelling Protocol (L2TP) and Internet Protocol Security (IPSec) in Windows XP.
	This article is intended to assist you in using the Internet Connection Sharing Troubleshooter that is included in Windows XP Help and Support Center, and to provide a list of online support services that may help you solve your problem.
	This article discusses the Modem Troubleshooter that is included in the Microsoft Windows XP Help and Support Center. Additionally, it will give you a list of online support services.
	When you try to dial out by using your modem, you may receive an error message that is similar to the following: Error 680: There is no dial tone This article describes how to troubleshoot "no dial tone" issues in Windows XP.
	This article describes how to troubleshoot difficulties that may occur when you try to print to a network printer in Windows XP. This article is intended for advanced computer users.
	This article does not provide in-depth information about how to troubleshoot printing problems over a network, but it does provide many important basic troubleshooting steps that you can use to help diagnose your printing problems. The troubleshooting steps that are listed in this article may also help you verify that your network printing problem is not being caused by a local problem.
	Discusses issues that may occur with your Bluetooth device after you install Microsoft Windows XP Service Pack 2 (SP2).
	You may receive the following Stop error message during or after the installation of Microsoft Windows XP: Stop: 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL*** Address x has base at x - filename The parameters refer to the specific issues that are involved.
	When you are running Windows XP, you may receive the following error message: Stop 0x00000077 KERNEL_STACK_INPAGE_ERROR This article describes how to troubleshoot these error messages.
	When you start your computer, you may receive one of the following error messages: STOP: 0x0000007B (parameter1, parameter2, parameter3, parameter4) INACCESSIBLE_BOOT_DEVICE Setup has encountered a fatal error that prevents it from continuing. Contact your product support representative for assistance. The following status will assist them in diagnosing the problem. (0x4, 0x1, 0, 0) Setup cannot continue. Power down or reboot your computer now.
	After you install a new hardware device or new software, your computer may start to restart spontaneously, or you may receive error messages on a blue screen.

	When a computer enters or leaves hibernation or standby, you receive a Stop message that is similar to the following: 0x0000009F: DRIVER_POWER_STATE_FAILURE
	You may receive the following error message: STOP: c000021a {Fatal System Error} The Windows Logon Process system process terminated unexpectedly with a status of 0xc0000034 (0x00000000 0x0000000) The system has been shutdown. Note The parameters in parentheses are specific to your computer configuration and may be different for each occurrence.
	Describes how to determine the cause of TCP/IP networking problems by using the basic and advanced diagnostic tools that are included in Windows XP.
	This article describes TRACERT (Trace Route), a command-line utility that you can use to trace the path that an Internet Protocol (IP) packet takes to its destination. This article discusses the following topics: How to Use the TRACERT Utility; How to Use TRACERT to Troubleshoot; How to Use TRACERT Options.
	This article describes an action plan for administrators and for support professionals to follow when domain controllers that are running Microsoft Windows 2000 or Microsoft Windows Server 2003 cannot replicate Active Directory because of DNS lookup failures. Administrators who are troubleshooting replication or other component failures that occur because of a lack of DNS name resolution should follow this action plan. This article also discusses two new events, event ID 2087 and event ID 2088, that are logged by destination domain controllers that are running Windows Server 2003 with Service Pack 1 (SP1). These events occur when a lack of DNS name resolution prevents the inbound replication of Active Directory directory service partitions. More significantly, in this problem scenario, Windows Server 2003 SP1-based destination domain controllers will use the source domain controller's fully qualified domain name in DNS or the source domain controller's NetBIOS computer name in Windows Internet Name Service (WINS). The goal of the enhancements in Windows Server 2003 is to minimize the effect of DNS client or DNS server configuration errors on Active Directory replication.
	This article discusses some of the common causes of Event ID 8021 and Event ID 8032 on a master browser system. The article also provides different methods that you can use to work around the issue.
	n a peer-to-peer workgroup, when you try to connect to the network resources of a computer that is running any of the products listed at the beginning of this article, you may receive one of the following error messages: Operating system error 71. No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept. System error 71 has occurred. This remote computer has reached its connection limit, you cannot connect at this time. This problem occurs when a computer reaches the maximum number of host connections that are allowed. In this case, when a NULL session connection is generated in the Microsoft Windows 2000 client, this NULL session connection is counted as one session on the Microsoft Windows XP-based server. Therefore, the error messages occur that are mentioned in this "Symptom" section, even if the number of connections to computers do not exceed the limit. In addition, when multiple NULL sessions are generated from a single Windows 2000 client computer, the multiple NULL sessions are counted as multiple sessions. However, a NULL session appears as a single session when you run the net session command. In this case, when the RestrictAnonymous registry entry is set, and the NULL session connection is rejected, this symptom still occurs.
	This article describes how to troubleshoot problems with cable modems in Microsoft Windows XP.
	After you run the Microsoft Windows Malicious Software Removal Tool, you receive a message that states that errors were found during the scan, and you are directed to this article for more information. Note Some of these errors are informational messages or minor issues and may not require additional action. Specifically, failures that are marked as a warning in the log are less serious than failures that are marked as an error.
	This article describes how to troubleshoot Windows XP Media Center 2004 if the Media Center Guide remote does not correctly change the channel on your cable box.
	When a service crashes intermittently in Windows XP, little information is generated about the cause. Therefore, it may be difficult to determine what is causing the problem. This step-by-step article describes how to use "Debugging Tools for Windows" to troubleshoot intermittent service crashes.

	This article describes troubleshooting methods that you can use if information similar to the following examples is recorded in the system log: Event ID: 9 Source: Aic78xx Description: The device, \Device\ScsiPort0, did not respond within the timeout period. Or Event ID: 11 Source: Aic78xx Description: The driver detected a controller error on Device\ScsiPort0. The name of the source can be the name of any controller, for example, Atdisk or ATAPI.
	Portqry is a command-line utility that you can use to help troubleshoot TCP/IP connectivity issues, which you can run on Windows 2000 and Windows XP. The utility reports the port status of target Transition Control Protocol (TCP) and User Datagram Protocol (UDP) ports on a remote computer. You can also use Portqry in the following ways: To troubleshoot Active Directory issues in which you have to verify basic TCP/IP connectivity, which can be especially useful in environments with firewalls. To verify connectivity to TCP/IP ports that are used by Active Directory for Lightweight Directory Access Protocol (LDAP), remote procedure call (RPC), and Domain Name Service (DNS).
	This article describes how to use the DNSLint utility to troubleshoot Active Directory replication issues. The Active Directory is a distributed database. It is used to store information about objects on a network and to permit users to access this information. Active Directory replication is used to synchronize partition replicas among domain controllers in an Active Directory forest. This replication process permits users to access information from wherever they are on the network. When this replication process does not work as designed, users may experience an interruption in the services that rely on information from the Active Directory: domain logon and access to network resources, such as files and printers.
	This article provides information to help you to troubleshoot issues with the User State Migration Tool (USMT) and the Files and Settings Transfer Wizard (FSTW).
	This step-by-step article describes how to troubleshoot scheduled tasks in Windows XP and in Windows Server 2003. If scheduled tasks do not run, you can use several methods to determine the source of the problem. Note Administrators or users with administrator permissions can configure the Task Scheduler to send a notification when a scheduled task does not run as you set it to run. To do so, click Notify Me of Missed Tasks on the Advanced menu.
	If you are using SMS and you try to connect to the site server, you may receive a "Connection Failed" message. Or, the nodes may not be displayed after you are connected. Additionally, errors that are similar to the following may be logged in the AdminUI.log file on the server: Error: Possible UI connection error code is -2147023174 [0x800706ba] Error: Possible UI connection error code is -2146959355 [0x80080005] Error: Possible UI connection error code is -2147217394 Error: Possible UI connection error code is -2147217389[0x80041013] Failed to execute method GetProviderVersion! Function GetProviderVersion returns empty string of ProviderVersion. Wbem call failed: T_WbemSyncEnumToContainer_Core, return code: -2147217389 We fail to get the ProviderVersion. SiteCode - SiteServerName , Provider Version : Failed to set the connection. error code: -2147217389 Error(ConnectServer): Possible UI connection error code is -2147024891 Error: Possible UI connection error code is -2147024891 [0x80070005] [994][<date> <time>]:Error(CheckForDisconnect2): Invalid service pointer. WMI connection has been dropped. : -2147024891 [0x80070005] This article describes how to troubleshoot a new or an existing SMS Administrator console to determine why it cannot connect to the site server.
	This article shows you methods of troubleshooting Safe Mode video problems. In Safe mode, the computer does not start the video adapter driver that is used during normal operations, so you need to use Device Manager to discover, update, roll back, or uninstall the video driver instead of accessing the Display properties.
	This article describes how to use the Memory Pool Monitor utility, Poolmon.exe, as a troubleshooting tool to monitor memory tags. Poolmon displays data that the operating system collects about memory allocations from the system paged and nonpaged kernel pools and about the memory pools used for Terminal Services sessions. The data is grouped by pool allocation tag. This information can be used by Microsoft Technical Support to find kernel mode memory leaks. A memory leak is caused by an application or by a process that allocates memory for use but that does not free the memory when the application or process finishes. Therefore, available memory is completely used over time. Frequently, this condition causes the system to stop functioning correctly.
	This article describes how to troubleshoot configuration errors in Windows XP by using the System Configuration utility (Msconfig.exe). The System Configuration utility helps you find problems with your Windows XP configuration. It does not manage the programs that run when Windows starts. The methods in this article are intended for advanced computer users.
	This article describes how to troubleshoot issues that may occur when you try to install a new or a second CD or DVD drive into your existing computer in Windows XP. Windows XP may not recognize the new CD or DVD drive.
	This article describes advanced troubleshooting tips for universal serial bus (USB) devices in Windows XP.
	This article describes how to troubleshoot MS-DOS-based programs in Windows.
	This article provides the [sic] troubleshooting information on Windows Defender application.
	This Support WebCast session provides an overview of how the NetBIOS Browsing mechanism operates on a Microsoft Windows-based network and how to troubleshoot it when systems are missing from the browse lists. This WebCast also introduces the NetBIOS Browsing Console, a new utility to make troubleshooting easier.
	Application Verifier (AppVerifier) is included in Windows XP to promote stability and reliability. You can use this tool to troubleshoot application issues. This article describes how to use Application Verifier to isolate and troubleshoot a program in Windows XP.
	In this session, we will cover the basics of "blue screen" errors, what they mean, and some common methods to troubleshoot the problems. We will provide some background information about blue screen errors, and we will talk about how to interpret the information, as well as how to recover from these errors.
	This article describes how to troubleshoot difficulties that may occur when you try to shut down Windows XP. This article is intended for advanced computer users.
	This article provides steps that you can use to troubleshoot hardware configuration problems by using Device Manager. You can use Device Manager to examine and change software-configurable devices. Note that if your hardware device uses jumper pins or dip switches, you must configure the device manually.
	This article describes advanced troubleshooting for network adapters. Typical error messages include the following: Error 55: "The specified network resource is no longer available" (ERROR_DEV_NOT_EXIST). Error 64: "The specified network name is no longer available" (ERROR_NETNAME_DELETED). Error 121: "The semaphore timeout period has expired" (ERROR_SEM_TIMEOUT). Error 1231: "The remote network is not reachable by the transport" (ERROR_NETWORK_UNREACHABLE).
	In this Support WebCast session, you will learn how to troubleshoot issues related to common problems that may occur when you start and shut down your computer using Microsoft Windows XP boot.
	This article describes how to perform troubleshooting steps for issues that may occur when you try to use the System Restore tool in Windows XP.
	This article helps you use the Games and Multimedia Troubleshooter that is included in Windows XP Help and Support Center. This article also lists the online support services that may help you solve your problem: You are having a problem with a Universal Serial Bus (USB) device. You are having a problem with the installation of DirectX. Windows starts only in Safe mode after you installed your game or multimedia program. Your DirectX, multimedia, or game program has stopped responding. You are experiencing video problems or receive messages about DirectDraw. You are having a problem with a joystick or another game device. You see a black screen or black patches around the mouse pointer. Or, the mouse pointer leaves old images of itself behind. You have a problem with sound. You have a problem when you try to play a DVD. You receive the following error message: Set Display Mode: DDERR_GENERIC
	When implementing the Microsoft Windows XP or Server 2003 High Security templates included with the Windows XP and Server 2003 Security Guides, various enterprise applications may lose functionality, or fail to operate properly or as expected. In many cases it will appear that communication is broken between the client and the enterprise management console. In other cases a service may fail to start properly, or an access denied or cannot connect error from within the enterprise management software. Enterprise management applications include network backup software, patch management software, software distribution and inventory applications.
	When you log off a computer that is running Microsoft Windows Server 2003, Windows XP, Windows 2000, or Windows NT 4.0, you may experience one or more of the following symptoms: A user profile does not unload. A roaming profile does not reconcile. You reach the registry size limit (RSL). You take a long time to log off, and you receive the following message: Saving settings… Backups may not start. There are no errors in the Application log from the Backup program.
	After you upgrade to Microsoft Windows XP from Microsoft Windows 98, Microsoft Windows 98 Second Edition, Microsoft Windows Millennium Edition (Me), Microsoft Windows NT 4.0, or Microsoft Windows 2000, you may receive one of the following error messages in America Online (AOL) when you try to connect to AOL: The network has stopped responding. Unable to initialize modem. Configuring Network adapter. Please wait. When you try to connect to AOL by using a modem, the computer may redial several times because it cannot connect. When this behaviour occurs, you receive an "Unable to initialize modem" error message, AOL dials, receives a carrier signal, and then hangs up. The status bar displays an "Unable to make a connection" message. Connections over TCP/IP work correctly.
	This Support WebCast session will discuss application compatibility issues in Microsoft Windows XP and how to troubleshoot them. Specific topics will include the Upgrade Advisor, Program Compatibility mode, and Compatibility tools in Windows XP.
	This WebCast provides an overview of Internet connectivity support in Microsoft Windows XP, along with information about how to troubleshoot an Internet connection. This discussion includes the use of Modem Diagnostics, Network Diagnostics, IPConfig, Ping, and other troubleshooting tools to test the connection, as well as some general guidance about sharing an Internet connection with other computers on a home or small office network.
	This article describes how to use the Printing Troubleshooter that is included in Microsoft Windows XP Help and Support Center. This article also provides a list of online support services that may help you solve your printing problem.
	This article is intended to help you use the Video Display Troubleshooter that is included in Windows XP Help and Support Center. This article also provides a list of online support services that may help you solve your problem. The Video Display Troubleshooter includes step-by-step instructions for troubleshooting the following display problems in Windows XP: You receive the following error message: Display problems. This program can't continue. Your display flickers or is garbled. You cannot install your monitor. You are having a problem with the multiple-monitor feature. Videos or animations do not work correctly. You cannot set the video resolution above 640 X 480 with 16 colors.
	This article describes how to troubleshoot difficulties that may occur when you try to print to a local printer in Windows XP. This article is intended for advanced computer users.
	When you try to run a game on a Microsoft Windows XP-based computer that is using a dual-core processor, game performance may be poor. For example, you may experience any one of the following symptoms: The game stops responding during game play. The game stops responding during the rendering process. Game performance is slow.