NP Troubleshooting Guide
Updated 30
May 2002
Click
Here To Contact Nishan
General
failure reading drive A, Abort, Retry, Fail?
1.
An
error in the application you are currently running.
2.
The
system BIOS/CMOS setup may not correctly configured.
3.
The
power supply.
4.
The
cable from the floppy controller to the drive.
5.
The
drive read/write head might be dirty.
6.
Floppy
drive problem.
7.
Floppy
drive controller problem.
Non-System
disk or disk error. Replace and strike any key when ready
This
error message appears when you are booting from a disk that does not have the
operating system on it. Replace the disk and try to boot again.
This
error message appears when DOS is loading, and the two hidden files are present
but COMMAND.COM is not present, is corrupt, or is the wrong version. Boot from
bootable disk that has COMMAND.COM and then copy the file to the disk that you
want to be bootable.
This
error message appears when you are trying to access a drive that the operating
system does not know is available.
This
error occurs when the disk in drive A is not readable. Maybe the disk is
missing or is inserted incorrectly. The
disk may have a bad boot record, errors in FAT, or bad sectors. Try using
McAfee utilities to examine the disk corruption.]
This
massage typically appears when you are trying to format a disk using the wrong
disk type.
Write-Protect
error writing drive A:
This
error occurs when the disk is write-protected and the application is trying to
write to it.
Try following:
1.
Try
using a bootable floppy disk, then log on to drive C:. If you have a Windows95
rescue disk, you can use SCANDISK, CHKDSK, or
FDISK to examine the system.
2.
If
PC will not boot from the boot disk, verify that the boot disk is good. Try
using it in a different computer.
3.
Check
to be sure that the power cable and disk controller cable connections are good
and are correctly oriented.
4.
Check
the power supply.
5.
System
files (COMMAND.COM, IO.SYS, MSDOS.SYS) may be damaged, missing, or mismatched,
which can keep a hard disk from booting. You can see if they are of the same
version by typing DIR/AH. This will
show the hidden system files and their dates. If COMMAND.COM and the hidden
files have different dates, then they are usually mixed and incompatible
versions. Boot a Rescue (startup) or system DOS disk from drive A (make sure
you are using the same DOS version).
*Restore hidden system files on drive C: by typing
A:\>Sys c:
6.
Check
for Active partition by typing A:\>Fdisk (Normally a Primary DOS
partition should be set active).
This
may be caused by fragmented files that have been updated, modified, and spread
over different portions of the disk. Run DEFRAG to rewrite fragmented files to
contiguous sectors.
Also,
verify that the hard disk drives are properly installed.
Computer
will not recognize a newly installed hard disk
1.
Has
the Fdisk utility been successfully
run? Choose "Display partition information" from the Fdisk menu to verify the status.
2.
Format C:/s is the last required "format" step.
Has this been done?
3.
Has
the CMOS setup been correctly configured?
4.
Are
there any drives to install?
5.
Are
there any Jumpers or DIP switches that must be set?
6.
Has
the data cable been properly connected? Verify that the cable stripes (red
color line side) are connected to pin 1 on the edge connectors of both the
mainboard/ card and cable.
The error message (Invalid drive specification) appears
while trying to access the drive
1. Check that there are no errors in the command lines in the CONFIG.SYS or
AUTOEXEC.BAT file according to the documentation tat came with CD-ROM. Did you
get an error message during booting, such as Bad Command or File Not Found?
2. Check the cable connection.
3. The MSCDEX.EXE program may not be loaded (or may not correctly install
the drive.try to install the drive). Is the entry placed too late in the
AUTOEXEC.BAT after the command to load Windows?
4. Try different version of MSCDEX.EXE. Look for this file in the
\Windows,\DOS,\…, directory and change the path in front of the filename in
AUTOEXEC.BAT to point to that version.
The Install process is terminated wit the message
"MSCDEX.EXE" not found
MSCDEX.EXE must be copied onto the hard dive. Put it in
the \Windows,\DOS directory, then restart the install process. Sometimes
MSCDEX.EXE is placed in the newly created CD-ROM directory.
Problems when installing the CD-ROM drive.
CD-ROM drives can be loaded from the AUTOEX.EXE and
CONFIG.SYS files. See the CD-ROM installation guide for specific commands for
your drive. Here are two examples:
In the CONFIG.SYS file: DEVICE=C:\CDSYS\SLCD.SYS/D:MSCD001
In AUTOEXEC.BAT: C:\DOS\MSCDEX.EXE/D:MSCD001/L:D/M:8
Try creating a bootable disk with these commands and the
referenced files. (Modify the paths to point to drive A.)
The error message "Not Enough Drive Letters"
appears during booting
Increase the number of allowed drive letters with the
LASTDRIVE line in CONFIG.SYS:
e.g.
LASTDRIVE=Z
These will appear during booting as error messages, or
they will cause some other device to fail to operate. The IRQ and I/O address
of your CD-ROM should be in the documentation. If not, call the manufacturer's
technical support for this information.
