saj@chinet.chi.il.us (Stephen Jacobs) (05/23/89)
Well, Vance at BMS solved yesterday's question of why my ST and the new
ST-296N were studiously ignoring each other: Seagate ALWAYS ships these
drives jumpered for device 0; use parity. The BMS-100 requires the jumper
to be set for no use of parity. I feel more angry than stupid than that one
because I'd called Seagate's vaunted customer service center Thursday to ask
basic precautionary questions (including what parity means on SCSI), and
reached a message passer--the promised tech person still hasn't gotten back
to me.
Now for today's mystery: having formatted the drive with Supra's software,
I find that I must turn my 1040 ST on before turning the ST-296N on; then
I can run the hard disk driver manually. If I follow the normal procedure
of letting the hard disk spin up, then turning on the ST with a 'suitable'
disk in its internal drive, the machine comes up unable to read hard disk
OR FLOPPY DISK. Any suggestions?
Just to show that I'm not an advice-hog, I'll throw in something I solved
on my own: Supra's formatter seems to reject a disk with >999 bad sectors.
The effective size of my disk is smaller than Supra's default parameters
suggest (by > 999 sectors). R-ing TDM I learn that one can disable mapping
of bad sectors during formatting (click on drive type in the configuration
menu). If I want to prevent attempted access to sectors past the end, they
don't need to be included in a partition.
Steve J.Xorg@cup.portal.com (Peter Ted Szymonik) (05/27/89)
I was told by the folks at ICD to always set Seagate drives to even SCSI numbers in order to have them work properly with the STs. Peter Szymonik Xorg@cup.portal.com