Re: Non-System Disk

Tech-Archive recommends: Speed Up your PC by fixing your registry



This error can be caused by one or more of the below possibilities.

1. Floppy or CD that is not bootable is currently in the
computer.
2. BIOS or CMOS setup is not setup properly.
3. Hard disk drive does not have bootable files on it.
4. The hard disk drive is bad or not connected properly.

Solution:
1. Floppy or CD that is not bootable is currently in the computer

Verify that no floppy diskette or CD is currently in the computer.
If a diskette or CD is in the computer that is not bootable your
computer may attempt to boot from that diskette or CD causing this
error message.

2. BIOS is not setup properly

1). Verify that your hard disk drive is setup and detected
properly in BIOS. You're computer should list a hard disk drive
installed either under the main page or the drives page in BIOS. If
BIOS indicates the drive is not installed or not detected skip to Hard
Disk drive is bad or not connected properly.
2). Verify the boot options are properly set in BIOS, almost
all BIOS setups should contain options specifying how your computer
boots. For example, most computers should have their boot options
setup similar to the below example.

- Floppy drive
- CD drive
- Hard drive

3). Rest your BIOS to default values. Many BIOS will enable
users to reset the values to the default settings. If you've tried the
above options without success try resetting the BIOS.

3. Hard disk drive does not have bootable files on it

It is possible that command.com or another bootable file may be
missing from the hard disk drive. Follow the below steps to possible
resolve your issue.

1). Boot from either your ERD, your bootable Windows CD, or
your bootable restore CD.
2). Once boot attempt to repair Windows. If you're able to
repair Windows remove the disks and reboot the computer.

4. The hard disk drive is bad or not connected properly

If you have attempted all above suggestions and you are still
encountering the same issues, verify the connections are properly
connected to the computer if the hard drive was recently installed or
the computer was moved.

Unfortunately, if all connections are setup properly and all the
above recommendations have been attempted, it is likely that the hard
disk drive is bad and it will need to be replaced.


----FREE diagnosis and repair tools, online forum, knowledgebase
articles, and more at www.DigitalSupportTech.com for your healthy and
speedy PC!
.



Relevant Pages

  • Re: program to map out weak HD sectors?
    ... >>> I don't have a floppy drive or bootable CDROM. ... Bios Date is 1998. ... can't boot from it. ...
    (comp.sys.ibm.pc.hardware.storage)
  • Re: Cpq Presario 906
    ... which comes w/o the internal FDD. ... also has the 26-pin flexprint floppy connector on the mobo, ... properly detected during POST and the BIOS briefly scans the ... floppy in it BUT is too stupid to actually boot from it! ...
    (comp.sys.laptops)
  • Re: UNMOUNTABLE_BOOT_VOLUME
    ... Outside of a BIOS update, ... Windows help - www.rickrogers.org ... I have replaced the floppy drive (found it to be ... I am well aware that XP setup ...
    (microsoft.public.windowsxp.general)
  • Re: Cpq Presario 906
    ... which comes w/o the internal FDD. ... also has the 26-pin flexprint floppy connector on the mobo, ... properly detected during POST and the BIOS briefly scans the ... floppy in it BUT is too stupid to actually boot from it! ...
    (comp.sys.laptops)
  • Re: FC4 and Assembly Language Program
    ... i am about to make a bootable floppy for test ... #objcopy -O binary myos.o BOOT ... Does the BIOS actually contain the software interrupt code you are ...
    (Fedora)