Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!tut!korppi!mk59200
From: mk59200@korppi.tut.fi (Kolkka Markku Olavi)
Newsgroups: comp.sys.amiga
Subject: Re: 3000 autobooting a 1096N
Message-ID: <1990Aug14.124847.6818@funet.fi>
Date: 14 Aug 90 12:48:47 GMT
References: <760.26C795C2@weyr.FIDONET.ORG>
Sender: news@funet.fi (#News )
Reply-To: mk59200@korppi.tut.fi (Kolkka Markku Olavi)
Organization: Tampere University of Technology, Finland
Lines: 15


In article <760.26C795C2@weyr.FIDONET.ORG> Randy.Coghill@f70.n140.z1.FIDONET.ORG (
Randy Coghill) writes:
>Dave what I would like is to find out if Commodore is going to fix the
>problem (as far as I know there scsi routines are the only ones that
>have this timing problem).

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
should Commodore (or anyone else) hack their firmware to work with
brain-damaged nonstadard devices?  That way we wouldn't ever get any
standard-conforming SCSI devices.

--
	Markku Kolkka
	mk59200@tut.fi