Post-Startup Errors

 < Day Day Up > 

Just because Windows starts correctly doesn't mean you're home free. The following sections discuss the causes and solutions for typical errors you might see after the system starts.

Invalid working directory Error

If a Windows or MS-DOS program is set to use a folder that isn't available, the Invalid working directory error might be displayed.

The following are solutions to this error:

  • Adjust the program's operation to use a folder that is available using the program's properties sheet.

  • If the working folder is on a network drive, make sure the user is logged on the network.

  • If the working folder is a removable-media drive, the user must insert the correct disk or CD-ROM before starting the program.

System Lockups

System lockups can result from any of the following causes:

  • Programs that stop responding

  • Hardware that stops responding or has conflicts

  • Exhaustion of Windows's user heap or GDI resources (9x/Me)

Press Ctrl+Alt+Del to display the Close Program dialog box (Windows 9x/Me) or the Windows Task Manager application tab (Windows NT 4.0/2000/XP) as shown in Figure 20.4) to determine if a program has stopped working.

Figure 20.4. The Windows XP Task Manager (left) and Windows 98 Close Program dialog (right) enable you to shut down a program that has stopped responding.

graphics/20fig04.gif

Programs and background tasks in memory are displayed. Programs or tasks with [not responding] at the end of the listing have stopped working; select each one and click Close Program to shut them down. You will need to close each unresponsive program separately.

Can't Log On to Network

A user must be on the list of authorized users to log on to a network managed by a Windows NT/2000/2003 server or Novell NetWare server. To access shared resources on a peer-to-peer Windows 9x/Me network, the user must log on to the network and provide passwords for password-protected resources.

If the user has not logged on to the network, the user should click Start, Shutdown, and Logoff the System. All open programs will be closed, and a new logon screen will be displayed. The user should make sure to enter the correct username and password. Pressing the Escape key or clicking Cancel does not log the user onto the network, although the logon screen is removed from the desktop.

After the correct username and password are entered, the user will have access to any Windows NT/2000/2003/NetWaremanaged resources that the user is authorized to use. However, the user will need to provide a password the first time a peer-shared resource on a Windows 9x/Me network is used; if the password is stored in the user's password cache, it will not need to be entered again unless the password for the resource is changed.

TSR Program Error

Terminate-and-Stay-Resident ( TSR ) programs, such as mouse drivers, CD-ROM drivers, and others, were common when MS-DOS was the predominant operating system. However, all versions of Windows covered by the A+ Certification Exams typically use 32-bit drivers. Only Windows 9x still supports 16-bit drivers through its use of Config.sys and Autoexec.bat and MS-DOS mode.

You can set a particular MS-DOS application that must run from the MS-DOS mode to use TSRs or device drivers by editing the Advanced features of its Program properties sheet (see Figure 20.5). Add or remove drivers, TSRs, or other commands from the default settings listed for Config.sys or Autoexec.bat . The options set here will be run when the program is started and are removed from memory when the user returns to the Windows GUI.

Figure 20.5. If you are running an MS-DOS program that needs particular device drivers or TSRs to work in MS-DOS mode (Windows 9x), specify the MS-DOS configuration you need.

graphics/20fig05.gif

Can't Install Applications

If you can't install an application, here are some reasons whyand some solutions!

  • Not enough disk space on C: drive Use the Custom Installation option, if available, to choose another drive, delete old files in the default Temp folder, or delete .chk files created by ScanDisk or Chkdsk in the root folder to free up space.

  • Computer doesn't meet minimum requirements for RAM or CPU speed Check for installation program switches to turn off speed and RAM checks, or, better still, upgrade system to meet or exceed minimums.

  • No more space available in root folder A FAT16 drive with 256 folders and files in the root folder cannot create any more folders or files in the root. Install to another folder, or convert the drive to FAT32 or NTFS to eliminate this limitation.

graphics/note_icon.gif

Even if you choose another drive rather than the default system drive (usually C:) for the application, a severe shortage of space on the system drive can still prevent a successful installation. That's because shared files are often installed to the Windows\System folder or other shared folders on the default system drive.


Print Spooler Stalled

Windows NT 4.0/2000/XP run the print spooler as a service . To restart it from the list of local services, with Windows 2000/XP, use this procedure:

  1. Open Control Panel and select Administrative Tools.

  2. Open the Services shortcut.

  3. Scroll to the Print Spooler entry.

  4. Right-click and select Restart from the right-click menu.

tip

graphics/tip_icon.gif

The Spool folder is hidden by default. To display it, change default View settings in Windows Explorer as described in Chapter 18 to show all files and show protected operating system files.


In Windows NT 4.0, open the Services icon in Control Panel to locate the print spooler. Select Stop, Start.

To fix stalled print spooler problems in Windows 9x/Me

  1. Open the C:\Windows\Spool\Printers folder.

  2. Delete the files in the folder.

  3. Resend any print jobs not completed.

 < Day Day Up > 


Absolute Beginners Guide to A+ Certification. Covers the Hardware and Operating Systems Exam
Absolute Beginners Guide to A+ Certification. Covers the Hardware and Operating Systems Exam
ISBN: N/A
EAN: N/A
Year: 2004
Pages: 310

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net