CompuServe Messages

I'm using my WarpEngine's FAST SCSI-2 controller. It comes with a version of HDToolBox for the WarpEngine, which I tried, and a program called ScsiTools, which I tried. I also tried C='s HDToolBox. All three gave me the same results – they failed to write to the drive, and if I tried to Initialize the drive – ScsiTool's lingo – or Low Level Format it – HDToolBox's – the drive light would go on, but there would be no drive activity, and that would be the end of that. I also tried the drive on my 3000's motherboard SCSI controller, with the WarpEngine removed from the machine. Same results. I tried the drive on the middle connector on the internal ribbon cable with the Maxtor still up and running, and on the end of the ribbon cable with the Maxtor removed. When the Maxtor was in, I disabled termination on the Seagate; when it was out, I left the Seagate in its factory default termination settings – termination on, termination power supplied by the drive. I also tried termination power provided by the SCSI bus. All gave me the same results. The Seagate is brand spanking new. I ran a pd utility called ProbeSCSI which I got here in the libs. It reported that the drive actually has 104 blocks per track, not the 109 I had guessed. I changed the Drive Type values to reflect this, but this did not solve the problem. ProbeSCSI also told me that there was a read error off the drive. Most of its output, though, was Greek to me. Does this give you any idea what's going on? I appreciate your time and efforts. Thank you. Mr. Zombie