Further to my hard drive issue please..?

Question

Please take a look at this ..

PhoenixBIOS 4.0 Release 6.0
Copyright 1985-2000 Phoenix Technologies Ltd.
All Rights Reserved
Version 2.02

CPU= Intel (R) Clelron (TM) processor 633 MHz
255M System RAM Passed
0128K Cache SRAM Passed
System BIOS Shadowed
Video BIOS Shadowed
UMB upper limit segment address: E807
Mouse initialized
Fixed disk 0: Maxtor N40P
Fixed disk 1: Quantum FireballP AS40.0
WARNING
ERROR
0200: Failure fixed disk 0

Press to setup, to resume

Now - First question.. From looking at that would you say that I actually have 2 physical hard drives inside my case? (because I cant see the other one..) and my second one is this .. I swapped over a hard drive - I added the maxtor one that you can see listed but - I removed a fireball one (which is also still listed) What else do I need to do in the bios or whatever when I change a hard drive? Also - how the hell do I tell which drive has failed?

Thanks for all as usual ..

Samantha

Answer 1

Hi Sam
Looks to me like your BIOS is still looking for the drive that you removed ... if you go into the BIOS can you set the "Identify ide drives" (or something like that)... to Auto detect your hard-drive ... if not ... you may well have to set the Cylinder Head and Sectors manually ... but I would think a 633mhz processor should be in a board that would auto detect .... the other thing is to make sure your new drive is set to Master and NOT to slave ... if it came out of another machine as a spare drive it may well still be set as a Slave
Good Luck
P.S. What happens if you hit to resume?

Answer 2

when you get the message saying press F1 to run setup, press the F1 key, and you will enter the BIOS setup page. In the BIOS you should see some setting that has the hard drives listed. It may be under a menu or an icon, sometmes it under BASIC, or SETUP or something like that.
When you find the place where the drives are listed, go to the one that is the Fireball drive that you removed and change it to read 'none'

Every BIOS setup is different, so I can't be more specific about where it will be listed. Some BIOS have a DETECT IDE setting are, and you could go to that place, and tell it to auto detect, and it should only find the Maxtor drive.

It looks as if, from the text you listed, the Maxtor drive is the one that is not working, since it says fixed disk 0, and the Maxtor is listed as fixed disk 0, but I would try resetting the BIOS settings to eliminate the fireball drive if you removed it from the computer, as having it listed when it isn't there may be causing the computer to mistake the Maxtor as being messed up.

If your computer has a DETECT IDE setting in the BIOS setup, use that as it will not only remove settings for the fireball drive, it will also find and setup the Maxtor properly.

If this does not help, you can email me with more questions at [e-mail]

Answer 3

First of all, your operating system should tell you which disk or disks are failing. You need to open the tower case to confirm that there are two separate drives. (It may also be a second partition within the primary drive for restoration purposes.) Enter your bios and check that auto hard drive detection is on if equipped, if not, you will need to manually enter the drives size, parameters, sectors, cyl.s, etc.

Answer 4

The above answer is good. Hit F1 , there should be some 'Auto Detect IDE' option in setup once you do enter.

I dont know about your hard drive settings but if you still have problems you might want to check the jumpers on the drives to make sure the one you boot from is set to master, and the other to slave.

Answer 5

If you have removed one of the drives, go into setup (BIOS) and do an auto IDE device detection.
It should find the existing drive and remove the other drive.
hard drive zero is the primary disk on the primary IDE channel.

Answer 6

Try auto-hard drive detection for all in BIOS, if you see the option. good luck.

Answer 7

sounds like an out of date computer, you would bebetter off buying a new one, maybe you should just reboot it