SCSI drive help.

[Garrett]

I recently decided I was going to get into this SCSI stuff, since I'm a student its hard to afford this stuff as you might imagine.
Its used, but I grabbed an external zip, an adaptec adaptor, and a small hard drive.
i got the zip drive to work fine, but the hard drive is giving me trouble.
If I plug it in right, when I boot to windows (2k) I get a kernel fault error, every time (blue screen). Unplug it and it works fine.
its a 50 pin, 1 gig, IBM, and the ribbon cable I have for it only has two connectors, ones in the adaptor, the others in the drive.
Uh..of note, the adaptor doesnt have a bios. I imagine that means I cant boot from my SCSI devices.
What the heck am i doing wrong?

[Hale]

What are the SCSI ID's of the drives and Controller? Sharing a SCSI ID across 2 devices is usually bad mojo. You should be able to number them 0-6 thru jumpers or switches.

[Garrett]

Thanks, but thats not it.
Unless i failed to make heads or tails of the jumper diagram. it was pretty vague.
i tried it three more times, to the same effect.

the exact error is this:

(blue screen of death)
Stop 0x000000000) <several times in fact
Unexpected kernel more trap
beginning dump of physical memory

[Garrett]

AH, nevermind man, the drive bogus. good thing it was cheap.

[Zorro]

Sounds like you've already concluded the drive is bad, but I have a couple of suggestions:

1. Check termination. If you have an external device make sure that the external bus and the internal bus (assuming your drive is internal) are terminated at both ends AND that the card's termination is turned off.

2. Check the boot IDs of the drive in question... SCSI ALWAYS interprets a drive with the boot ID of 80 to be your primary drive, 81, your secondary... If your BIOS is configured such that it initiates the SCSI BIOS prior to your onboard controllers, it could confuse Windows since it would see an LZ on one drive with a bootable partition and a device ID of 80 on another non-bootable partition, it might confuse itself... The boot.ini file on the root of your bootable drive points to a particular directory to locate the ntoskrnl.exe file. The SCSI drive could potentially be hampering that process...

[Garrett]

It as terminated correctly. on both ends. the external zip has two device ID's 5, and 6. and a terminate switch, which is cool.

ive checked the jumper settings several times, and had someone else double check to make sure i was reading it right. still produced the same error. no biggie. i had it set to SCSI ID 0, and terminated.

the adaptor i have doesnt have a BIOS, its a cheapie. so it cant boot form the SCSI devices.

The weird thing is i can feel the drive spin up, but i guess the controller doesnt work. i had a dude who knows his SCSI stuff over to have a look, so i assume its dead.