Hard drive installation problem

  • Thread starter Thread starter XModem
  • Start date Start date
X

XModem

Sure hoping someone can help me. My setup: AMD T-Bird 1.4 on Gigabyte
GA-7DXR board. Latest BIOS.

Bought a WD 160 GB drive to replace a too small 40 GB. Pulled my 40,
installed the new one, and ran WD's setup program (20 GB and 150 GB
partitions.) Installed a known good image, and now boot hangs just after the
XP splash screen disappears. OK, tried installing XP from scratch, and it
hangs too, part way into installation.

Booting the good image on the new drive in safe mode, it hangs at
'WINDOWS\SYSTEM32\DRIVERS\AMDAGP.SYS' line.

Ran WDs diagnostics, and drive comes back fine. Tried different jumper
settings and tried to see anything relevant in BIOS.

If it matters, my primary master and secondary master (IDE1 & IDE2) are
optical drives. Hard drive has always been on IDE3 as cable select. My
Windows setup requires Promise drivers when booting. When I reinstall my 40
GB, everything is back to normal?

I'm stumped. TIA for any assistance.
 
Sure hoping someone can help me. My setup: AMD T-Bird 1.4 on Gigabyte
GA-7DXR board. Latest BIOS.

Bought a WD 160 GB drive to replace a too small 40 GB. Pulled my 40,
installed the new one, and ran WD's setup program (20 GB and 150 GB
partitions.) Installed a known good image, and now boot hangs just after the
XP splash screen disappears. OK, tried installing XP from scratch, and it
hangs too, part way into installation.

Booting the good image on the new drive in safe mode, it hangs at
'WINDOWS\SYSTEM32\DRIVERS\AMDAGP.SYS' line.

Ran WDs diagnostics, and drive comes back fine. Tried different jumper
settings and tried to see anything relevant in BIOS.

If it matters, my primary master and secondary master (IDE1 & IDE2) are
optical drives. Hard drive has always been on IDE3 as cable select. My
Windows setup requires Promise drivers when booting. When I reinstall my 40
GB, everything is back to normal?

I'm stumped. TIA for any assistance.
Click to expand...

Further to this, I tried installing the new drive as slave, and booting my
good 40 GB. It hung on bootup.
 
Sure hoping someone can help me. My setup: AMD T-Bird 1.4 on Gigabyte
GA-7DXR board. Latest BIOS.

Bought a WD 160 GB drive to replace a too small 40 GB. Pulled my 40,
installed the new one, and ran WD's setup program (20 GB and 150 GB
partitions.) Installed a known good image, and now boot hangs just after the
XP splash screen disappears. OK, tried installing XP from scratch, and it
hangs too, part way into installation.

Booting the good image on the new drive in safe mode, it hangs at
'WINDOWS\SYSTEM32\DRIVERS\AMDAGP.SYS' line.

Ran WDs diagnostics, and drive comes back fine. Tried different jumper
settings and tried to see anything relevant in BIOS.

If it matters, my primary master and secondary master (IDE1 & IDE2) are
optical drives. Hard drive has always been on IDE3 as cable select. My
Windows setup requires Promise drivers when booting. When I reinstall my 40
GB, everything is back to normal?

I'm stumped. TIA for any assistance.
Click to expand...

Why does it require promise drivers? You have the drive
connected to the promise controller? It's ATA100, yes? Did
the Gigabyte bios notes mention an update to the Promise
RAID bios? Perhaps you need install a newer Promise driver
that is 48bit LBA capable? Are you running Windows XP SP1
or pre-SP1?
 
Why does it require promise drivers? You have the drive
connected to the promise controller? It's ATA100, yes? Did
the Gigabyte bios notes mention an update to the Promise
RAID bios? Perhaps you need install a newer Promise driver
that is 48bit LBA capable? Are you running Windows XP SP1
or pre-SP1?
Click to expand...

After a lot of anguish, it seems my problem is that while the old drive
was recognized on IDE3, the new one wasn't (at least, properly).
I decided to run the new drive as IDE1 master, and damned if it didn't
work tickety-boo. Regarding your question about the Promise drivers - XP
wouldn't recognize the drive where it was installed (IDE3) without loading the
Promise drivers first.
In hindsight, I've no clue at all why the original builder of my system
did it this way, but switching to IDE1 and IDE2 seems to have fixed the
problem.
In any event, thank you, kony, for your response in trying to help me sort
this out.
 
Back
Top