PC will not boot on ATA100 HD: How do I go about in installing...?

aa_koch

Senior member
Jan 10, 2001
730
0
0
A while ago, I completed the purchase of parts for my new system. Although it's currently set up, I've still not been able to add the IBM Deskstar drive. (I'm still using two Western Digital Caviar drives that are connected to the Primary and Secondary EIDE controllers.) I am not a newbie, but I've never worked with ATA100 drives before. I really didn't think there'd be much of a difference from installing a regular ATA66 drive, but I've run into problems setting up the system with this HD. FYI: I am using an ASUS A7V motherboard, running an AMD Duron 700MHz w/128MB PC-133 RAM.

Initially, I wanted to boot from the Windows 98SE CD-ROM, partition and format the HD, and install the OS. But apparently the W98SE CD-ROM is not bootable. (My DVD-ROM drive won't boot from it; when I use the Norton Ghost CD-ROM, it will. But aren't all W98SE CD-ROMs bootable?) So I decided to use the W98SE boot floppy instead. Although this allows me to access the drive and partition/format it, I get an error upon reboot. (I choose support for large disks, and I also used the "format c: /s" command. The system files are there, but it keeps coming up with the boot error "Insert system disk.")

So my question would have to be: If I want to install my shiny new 30.7GB HD, which steps should I take to install the drive properly? I enabled detection of the Promise controller, but it doesn't even get to there.

At the moment, I am using the following devices attached to the EIDE interface:

Primary Master: WD 1.6GB
Primary Slave: WD10.2GB
Secondary Master: Toshiba DVD-ROM
Secondary Slave: HP CD-Writer Plus 7100i

When I remove the two HDs and replace them with the (partitioned AND formatted) Deskstar, the following is shown:

Primary Master: none
Primary Slave: none
Secondary Master: Toshiba DVD-ROM
Secondary Slave: HP CD-Writer Plus 7100i

Immediately after, the error is displayed. When I boot from the Western Digital HD, the system tries to detect a ATA100 drive, but says the BIOS was not loaded 'cause a drive was not found. When I boot from the Deskstar, I get an error immediately after the Primary and Secondary EIDE controller information is displayed, and it doesn't even bother detecting a ATA100 drive.

What am I doing wrong?
 

AU Tiger

Diamond Member
Dec 26, 1999
4,280
0
76
Only NT and 2000 CDs are bootable.

ATA100 drives are backwards compatible with older motherboards and should run based on the controller it is connected to.

Can you tell if the IBM drive is spinning up? Sounds like power may not be getting to the drive or it is faulty.

Can BIOS detect the drive from the BIOS menu?

What cable are you using with the drive? Your existing ATA66 cable or the ATA100 cable. I believe you should use the ATA66 cable.

And last, check jumper settings on the drive.
 

aa_koch

Senior member
Jan 10, 2001
730
0
0
AU Tiger: Thanks for your response. I'll have to check a few things first before I can give you all the answers, but here's what I know to be certain:

- In my BIOS, the drive is not detected. (I believe this to be because it's not connected to the "regular" IDE controller, but to the onboard Promise ATA100 controller.) I can only choose between accessing Primary Master, Primary Slave, Secondary Master, and Secondary Slave. Correct me if I'm wrong, but isn't the reason it doesn't show up in the BIOS that it's not connected to any of the IDE controllers?

- I am using the ATA100 cable that came supplied with my ASUS A7V. It's one with a single blue connector, and two black connectors. (Yes, the blue connector is plugged into my motherboard. I have my HD connected to the black connector.) I don't think I can use an ATA66 cable and plug it into my onboard Promise ATA100 controller, can I?

I'll try and see what happens when I connect the drive to the regular IDE connector (Primary Master). I know the jumpers are set correctly, because it's the only drive in my system at the time and I verified that Primary Master settings = Single Drive settings. I'll be back soon, I hope... :)
 

AU Tiger

Diamond Member
Dec 26, 1999
4,280
0
76
After reading your last post I see that many of my earlier suggestions aren't that helpful. Using Deja I was able to find more possible solutions. Via Deja I found that a lot of people recommend installing the OS while the drive is connected to the primary controller and moving the drive to the promise controller after the VIA drivers and the Promise drivers had been installed. I also ran across the following post:

I can't believe the guessing that is occurring on this. This
appears to be a problem which has been known for weeks and has
been thoroughly documented on the newsgroup. Beginning with the
initial 1005 BIOS, it has been necessary to enable boot virus
detection in the BIOS in order to boot from a drive on the ATA100
controller.

A7V BIOS: 1005C


If you want to read more check out Deja.

[edit]Good luck[/edit]
 

aa_koch

Senior member
Jan 10, 2001
730
0
0
Well, I did exactly that (albeit only because I was running out of ideas... :)). I hooked up the IBM Deskstar to the regular IDE connector, inserted the W98SE boot disk, and re-partitioned and re-formatted the HD. I'm glad to see that is working, because at least I know the drive is not faulty.

Anyway, I then continued to install W98SE, but have not installed the Promise/VIA drivers, yet. So that's what I'll be doing now...

Thanks for you time, and er... I'll be back! :p
 

aa_koch

Senior member
Jan 10, 2001
730
0
0
Alright!!

Well, boys and girls... I am pleased to report that all is well. :)

I installed the Promise ATA100 drivers, the Via 4-in-1 (which I doubt was really necessary -- I think I only needed to install one of the four drivers that came with the package), and even decided to upgrade the BIOS to revision 1005c. I then commenced to booting from the IBM Deskstar on the ATA100 controller -- and it worked! (Note: I had to reset the BIOS (load default settings) after flashing it to the latest version, then forgot to indicate that the ATA100/SCSI device is part of the boot sequence. If anyone has problems booting from their ATA100 HD, be sure that the ATA100/SCSI device is selected, in the menu that indicates which device you boot from (floppy, CD-ROM/DVD-ROM, HD, ATA100/SCSI device...). That should solve the problem ultimately.

Anyway... AU Tiger, thanks for your help, I appreciate it. (Especially since you're the only one who seemed to have an idea... :))