G
Guest
Hey there~
I need a SCSI / XP expert!
In short, my problem is - Windows is not seeing a new Cheetah SCSI drive
installed on an Adaptec 29160 controller.
My system is a Dell 530 Workstation with a couple of Xeon 2.4G chips.
Win XP Pro, SP1
No Internet, etc.... bare bones for Audio Engineering apps...
2 HDs are ATA-100... no problem there...
The 3rd HD is SCSI with a separate controller and that's where my problem
lies...
I'd been using the 29160 controller with an IBM 10K Ultrastar forever, but
the IBM just took a dump... so I replaced it with a Cheetah 10K.7 (Seagate,
73GB, 10K, 68 pin)
Bios sees the set-up as~
SCSI ID 0 Seagate ST373207LW
SCSI ID 7 Adaptec 29160
....same SCSI IDs as before...
The Adaptec card communicates with the Seagate drive in DOS using the
Seagate utility program.... and I can format the drive with (the most
current) Adaptec utility. So, the controller and drive seem to be chatting
OK at low level... I can also see the system acknowledge the card/drive with
a 160 negotiated speed during regular boot-up... so, everything seems cool as
it fires-up...
But, If I boot into plain-jane DOS (not using the Adaptec utulity)... no
drive...
And in Windows... no drive.
The drive is still in it's basic/factory configuration... no pin
changes/etc... seems no need since communication is happening at that
low-level OK (?)
So, I'm really stumped! I've combed through all the manuals,
knowledge-bases, etc., several times. I just can't tell for sure where the
problem lies, but it seems to me it's most likely a Windows issue (?)
Many thanks for any ideas / insight!!
~Cheers~
I need a SCSI / XP expert!
In short, my problem is - Windows is not seeing a new Cheetah SCSI drive
installed on an Adaptec 29160 controller.
My system is a Dell 530 Workstation with a couple of Xeon 2.4G chips.
Win XP Pro, SP1
No Internet, etc.... bare bones for Audio Engineering apps...
2 HDs are ATA-100... no problem there...
The 3rd HD is SCSI with a separate controller and that's where my problem
lies...
I'd been using the 29160 controller with an IBM 10K Ultrastar forever, but
the IBM just took a dump... so I replaced it with a Cheetah 10K.7 (Seagate,
73GB, 10K, 68 pin)
Bios sees the set-up as~
SCSI ID 0 Seagate ST373207LW
SCSI ID 7 Adaptec 29160
....same SCSI IDs as before...
The Adaptec card communicates with the Seagate drive in DOS using the
Seagate utility program.... and I can format the drive with (the most
current) Adaptec utility. So, the controller and drive seem to be chatting
OK at low level... I can also see the system acknowledge the card/drive with
a 160 negotiated speed during regular boot-up... so, everything seems cool as
it fires-up...
But, If I boot into plain-jane DOS (not using the Adaptec utulity)... no
drive...
And in Windows... no drive.
The drive is still in it's basic/factory configuration... no pin
changes/etc... seems no need since communication is happening at that
low-level OK (?)
So, I'm really stumped! I've combed through all the manuals,
knowledge-bases, etc., several times. I just can't tell for sure where the
problem lies, but it seems to me it's most likely a Windows issue (?)
Many thanks for any ideas / insight!!
~Cheers~