Hard Drive Not Recognized in BIOS

edited May 2009 in Hardware
I've run into a problem when adding a second drive to an eMachine T2542 2.5 GHz with XP Home.

The first drive (Maxtor Fireball 3, ATA/133 40GB) worked until I added a second drive as a slave (Western Digital WD400, EIDE 40 GB). The first was attached to Master, the second to Slave. Neither drive is recognized in the BIOS (Phoenix BIOS), and the "No operating system found" error appears on screen. I pulled both drives, reset the jumper on the first, reattached it, and the first drive does not register now.

Here's some further info that might help:
  • A series of two beeps occur shortly after booting.
  • Hard drive is listed in the BIOS priority list.
  • The defaults are reset in BIOS.
  • Cables are attached properly--master, slave, power.
  • Jumper in each drive set according to spec on drive for master and slave.
  • When Jumpers on both drives were reset to CS, they failed to work.
  • None of the jumper settings work on the first drive.
  • The CD-ROM will boot, but it won't find the HDD.
  • I've only a Win98 CD (it's a second hand computer).
  • There's a fresh battery on the motherboard.
  • The HDD CDs/floppy disks are NOT available.
How might I fix this problem?

Thanks,
Domer94

Comments

  • MAGICMAGIC Doot Doot Furniture City, Michigan Icrontian
    edited May 2009
    Do you have them on the same cable?
  • Mt_GoatMt_Goat Head Cheezy Knob Pflugerville (north of Austin) Icrontian
    edited May 2009
    Have you tried using the ROM drive as slave with the original HD as master to see if it is the controller or cable? Have you swapped cables to make sure the cable is good? Have you tried the new HD as master to test it by itself?
  • edited May 2009
    Thanks for the replies. Sorry to answer so late. Here's an update:

    I've swapped the ribbon cable and have the same result.
    I put the original HDD as master to the ROM drive and neither loaded.
    I've tried the new HDD as master and buy itself and it won't show up.
    Tomorrow I'll call Maxtor and WD to see what they say 'bout their drives.

    Am I missing something simple or did I ruin both drives somehow?
  • MAGICMAGIC Doot Doot Furniture City, Michigan Icrontian
    edited May 2009
    Doesn't recognize the drive by itself, maybe you got a doa hard drive...?
  • LeonardoLeonardo Wake up and smell the glaciers Eagle River, Alaska Icrontian
    edited May 2009
    Something else to try:

    Put the original 40GB drive on the primary position on the cable. Put the second, new drive on the secondary position - just as you had them with your first attempt. Set both drives' jumpers to CS or Cable Select. Some ATA drive configurations just won't detect properly without setting the jumpers to CS.

    And while we're on this topic:
    The first was attached to Master, the second to Slave.
    In addition to the position on the cable, did you set the hard drives jumpers to Master and Slave?
Sign In or Register to comment.