faq.gif (5012 bytes) 

 

 

  1. Right-click the "MY COMPUTER" icon.
  2. Select "PROPERTIES."
  3. Select the tab labeled "PERFORMANCE."
  4. Does the PERFORMANCE area display that you are using Microsoft® DOS® compatibility mode? Does PERFORMANCE display that something has modified the boot sector? If the answer to either of these questions is yes, then it is likely you have a virus.
  5. Select START | PROGRAMS | MS-DOS PROMPT.
  6. Once at the DOS prompt type:  CHKDSK[Enter]
    You should now get a report that will show you some information about your hard drive as well as memory.
  7. Look at the 4th row from the bottom where the line reads:
    655,360 total bytes memory

    If the number is not 655,360 or 651,264 and you answered yes to any part of step 4 then chances are very high that you have a virus that is causing the CD-ROM to not be seen.

    What you should do is to try an anti-virus program and get rid of the virus.

    If there is no virus, then there can be several other causes. If it is an IDE or SCSI drive, does the CD-ROM drive appear listed on the screen when the system is booting, shortly after the hard drive is detected? If it does not, the most common cause of this is that a reinstall of Windows® 95 or Windows® NT was done from a different version of the Operating System than the original install. This causes the system to turn off the CD-ROM controller (the PIIX 3 chip). There is a patch available from Intel to correct this at [http://www.intel.com/], or from the Intel® BBS (503-264-7999). Download this utility and follow the instructions to update the hard drive configuration file. If the problem did not appear immediately after an install, then there could be a problem with the CD disk, the drive itself, the controller or the cable. Try reseating the cable on both the drive and motherboard ends. If it still is not detected during the boot process then there is a possibility that there is a hardware problem.

    If it IS detected and is not seen in DOS or Windows® then it's probably a driver issue. Make sure that the appropriate drivers are installed in the CONFIG.SYS and AUTOEXEC.BAT files.



Return to the