Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!udel!rochester!rit!cci632!sjo
From: sjo@cci632.UUCP (Steve Owens)
Newsgroups: comp.sys.amiga
Subject: Re: 3000 autobooting a 1096N
Summary: What's the big deal?
Message-ID: <39490@cci632.UUCP>
Date: 24 Aug 90 16:57:54 GMT
References: <760.26C795C2@weyr.FIDONET.ORG> <1990Aug14.124847.6818@funet.fi> <229@iphase.UUCP>
Organization: Computer Consoles Inc. An STC Company, Rochester NY
Lines: 31

In article <229@iphase.UUCP>, steve@iphase.UUCP (Steve Kappes PER) writes:
> >There's no problem with the A3000 and A2091.  The problem is entirely in
> >Seagate drives.  The SCSI standard (SCSI-2 at least) specifies a maximum
> >time from poweron to when a device should respond to selection. Why
> >	Markku Kolkka
> >	mk59200@tut.fi
> 
> Actually the SCSI-2 spec recommends a time of 10 seconds.  The time is
> a recommendation, not a requirement.  I don't remember even a recommendation
> in SCSI-1 which I believe both the host adapter and drive in question are.

	Excuse me if I'm being ignorant, but.....

	I don't understand what the big deal is.  Why not simply use a
	DIP switch set or jumper set to allow the customization by the
	user?  Do it by powers of two, with the base being two seconds,
	in order to allow any power-up time required by the drive.
	If required, it could be done for each HD in the subsystem, or it 
	can be done for the worst case drive in the entire system.

	And before someone jumps down my throat saying "That's the
	drive manufacturer's problem," why not do it on both ends?  This
	would allow the user total flexibility to configure his system
	the way he wants it.  Obviously there must be industry-wide
	recommendations for the default settings, but at least it would
	be easy to change.


> Steve Kappes  Interphase Corp.  uunet!iphase!steve

						SJO