Modem Troubleshooting  Troubleshooting Specific PC Symptoms  Troubleshooting BIOS and Startup problems  Troubleshooting client for Netware Networks  Troubleshooting Communications  Troubleshooting Device Configuration  Troubleshooting Disk Corruption  Troubleshooting Drivers  Troubleshooting Windows95 Start-up  Troubleshooting Applications  Troubleshooting Missing File Systems  Troubleshooting SCSI Device Problems  Troubleshooting Setup Errors  Troubleshooting Specific Startup Errors  Troubleshooting Floppy Disk Systems  Troubleshooting CPU's  Shareware Utilities  BIOS and Beep Codes  CDROMS  Conflict Troubleshooting  Troubleshooting CMOS

Return to Index  HOME

Troubleshooting missing file systems

A missing operating system file prevents the startup process from continuing. If you are missing only the COMMAND.COM file, you can fix this problem from the Startup menu as described in Safe Mode Command Prompt Only, or from a Windows 95 startup disk as described in this section. This section also describes how to check and restore the IO.SYS and MSDOS.SYS system files. Windows 95 uses the same names for the real-mode operating system files as MS-DOS does (IO.SYS, MSDOS.SYS, and COMMAND.COM). However, to support dual-boot, the MS-DOS versions of these files are renamed with a .DOS extension when you install or start Windows 95 after having started the computer with the previous operating system.

To replace or reinstall the real-mode operating system files on drive C

1. Start the computer using the Windows 95 startup disk.

2. At the command prompt for the startup drive, type sys c: to copy IO.SYS, MSDOS.SYS, DRVSPACE.BIN, and COMMAND.COM to drive C. This rewrites the boot sector.

3. Remove the floppy disk, and then restart the computer.

If COMMAND.COM is missing, a message indicates this and prompts you to type the path for the file.

To restore COMMAND.COM using command-line commands

1. Insert the startup disk into the floppy disk drive.

2. At the command prompt, type the following: attrib -r -s -h c:\command.com
copy a:command.com c:\

If the Windows 95 MSDOS.SYS file is missing, a blue screen presents a message: "Invalid Vxd dynamic link call from IFSMGR (03)." This is followed by an error initializing IFSMGR, and startup fails. Errors that appear during system startup related to the Registry, XMS, and IFSMGR, are all caused by invalid syntax in the specification of the [Paths] section of MSDOS.SYS or the WinDir= entry. Setting the WinDir= value causes IO.SYS to use that value to set the following environment variables:

tmp=WinDir
temp=WinDir
path=WinDir;WinDir\command
comspec=WinDir\command.com

If no valid WinDir= entry is found in MSDOS.SYS, the path defaults to C:\WINDOWS, and COMSPEC defaults to C:\COMMAND.COM. If IO.SYS is missing, the computer stalls before the Starting Windows 95 message appears and displays a message. The message says that the system disk is invalid and prompts you to replace it. You must use a bootable Windows 95 disk (such as the startup disk) to start the computer. You will then need to reinstall the real-mode operating system files on drive C as described in the preceding procedure.

You can also restore the COMMAND.COM in Windows 95.

To restore COMMAND.COM using Windows Explorer

1. Restart the computer, press F8 at the Starting Windows 95 message, and then select the Safe Mode option.

2. Insert the startup disk into the startup drive.

3. Using My Computer or Windows Explorer, find COMMAND.COM on the floppy disk drive, and then drag the file from the floppy disk to the root directory of the boot drive.


Modem Troubleshooting  Troubleshooting Specific PC Symptoms  Troubleshooting BIOS and Startup problems  Troubleshooting client for Netware Networks  Troubleshooting Communications  Troubleshooting Device Configuration  Troubleshooting Disk Corruption  Troubleshooting Drivers  Troubleshooting Windows95 Start-up  Troubleshooting Applications  Troubleshooting Missing File Systems  Troubleshooting SCSI Device Problems  Troubleshooting Setup Errors  Troubleshooting Specific Startup Errors  Troubleshooting Floppy Disk Systems  Troubleshooting CPU's  Shareware Utilities  BIOS and Beep Codes  CDROMS  Conflict Troubleshooting  Troubleshooting CMOS

Return to Index  HOME