Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!unmvax!pprg.unm.edu!hc!ames!sgi!scotth@harlie.SGI.COM
From: scotth@harlie.SGI.COM (Scott Henry)
Newsgroups: comp.sys.amiga
Subject: Re: Autoconfig HD controllers
Message-ID: <22532@sgi.SGI.COM>
Date: 28 Nov 88 22:44:08 GMT
References: <5691@louie.udel.EDU>
Sender: daemon@sgi.SGI.COM
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 27

From article <5691@louie.udel.EDU>, by aimania%killer.dallas.tx.us%CERNVAX.BITNET@cunyvm.cuny.edu:
> 
>  I've read quite a few messages on the net about autobooting disk controllers.
>  But as far as I am concerned, there is no overriding benefit of an autobooting
>... 
>  Only minor inconvenience is that you have to take any disk out of df0:
>  otherwise the system will try to reboot from floppy without trying RAD:.
>  Is there something you can patch in your startup sequence to force loading
>  from RAD: instead of trying the floppy first?

All it takes is a non-bootable disk in DF0: (ie: a "data" disk). I have been
using a very tiny RAD: for non-floppy re-boots with my Microbotics StarDrive
for several weeks now. I frequently have a non-bootable disk in DF0:, and
RAD: boots right up (it access both/all floppies first, as usual).
> 
> --
> Walter Rothe at the UNIX(Tm) Connection, Dallas, Tx
> UUCP: {rutgers}!smu.killer.aimania


              Scott Henry 

#include 
--
              Scott Henry  {or, also on the Internet:}
                          
#include