Path: utzoo!attcan!uunet!aplcen!samsung!cs.utexas.edu!yale!quasi-eli!cs.yale.edu!fischer-michael From: fischer-michael@CS.YALE.EDU (Michael Fischer) Newsgroups: comp.sys.atari.st Subject: Re: TOS 1.6 & Re: Hold that computer... Message-ID: <25560@cs.yale.edu> Date: 13 Jul 90 14:34:47 GMT References: <1990Jul6.190229.19792@sun.soe.clarkson.edu> <10766@chaph.usc.edu> <2236@atari.UUCP> Sender: news@cs.yale.edu Reply-To: fischer-michael@CS.YALE.EDU (Michael Fischer) Organization: Yale University Computer Science Dept, New Haven CT 06520-2158 Lines: 19 In article <2236@atari.UUCP> apratt@atari.UUCP (Allan Pratt) writes: >Believe me, people, I tried to come up with a solution which didn't >involve a simple delay. It turns out that hard disks vary widely in >their spin-up time, and also in their responses to commands between the >time they are powered up and the time they are ready. Unfortunately, the solution you describe seems to preclude using configurable software solutions such as duck31 that others have devised. Is there any way to disable the 90 second delay, or has that been made the official MINIMUM time for booting an unattended machine, regardless of how fast your hard disk spins up? Will a bootable floppy allow one to bypass the delay? ================================================== | Michael Fischer | | Arpanet: | | Bitnet: | | UUCP: | ==================================================