DOS or Other OS Troubleshooting
Some of the problems you see with MS-DOS, or other versions of DOS
are:
- "Bad Command or File Name". This occurs constantly, and people
sometimes realize it is caused by several reasons:
- poor typing (misspelled) - retype the command correctly!
- file does not exist - the file may not have been loaded. You may need
to load it.
- trying to execute a non-executeable file (an extension other than
".bat", ".exe", or ".com".
- "path" statement does not point to the directory where
the file resides.
To run an "executeable" file (one with a ".bat", a ".com", or
a ".exe" extension, you must be in the directory where the file is, OR have a path
statement that points to the directory. Learn what the "path" means.
- "Invalid drive specification".
This is usually caused by entering the drive letter to a drive
that doesn't exist as far as DOS is concerned. You may have a CD-ROM or
other device on the machine, but if you have not loaded its driver in the
"config.sys", the system will not know it exists.
- Different BIOS manufacturers give different messages when boot errors
occur. These errors may mean the same thing- the "boot sector" on the bootable
disk is bad. This can occur in both floppy and hard drives:
- Non-System disk or disk error
Replace and press any key when ready
This message may be caused by some disk other than
the "MS-DOS Setup Disk #1" being in the drive at boot time.
- Disk Boot Failure
- DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER.
- Error loading operating system
- Missing operating system
- Disk Boot fialure
- NO ROM BASIC - SYSTEM HALTED
- 602 - Diskette Boot Record Error
All the above errors occur at boot time. The causes are normally
a problem with the boot sector - either on the floppy or hard drive.
- "C000 ROM Error" or "XXXX ROM Error" - this error is usually
associated with a video adapter ROM BIOS check.
-
-
Write the rest ASAP!!!
Trouble-Shooting PC's