Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!ut-emx!mjl
From: mjl@ut-emx.UUCP (mjl)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Noclick on the A3000
Message-ID: <35191@ut-emx.UUCP>
Date: 5 Aug 90 10:22:27 GMT
References: <1990Jul26.144452.8771@cbnewsl.att.com> <1990Jul27.050454.11169@cbnewsm.att.com> <1990Jul31.155439.21621@IRO.UMontreal.CA> <1990Aug1.051429.1978@msuinfo.cl.msu.edu>
Reply-To: mjl@emx.UUCP (Maurice LeBrun)
Distribution: na
Organization: UTexas Computation Center, Austin, Texas
Lines: 18

In article <1990Aug1.051429.1978@msuinfo.cl.msu.edu> dailey@kira.uucp (Chris Dailey) writes:
>
>Couldn't you just reset the BootPri for the hard drive to a higher
>value?  Then it would work no matter what on a WARM reboot, right?
>Any gurus out there care to verify that?
>
>  /~\  Chris Dailey   (CPS Undergrad, SOC Lab Coord, AMIG user group Secretary)

Could lead to trouble.  If you somehow trashed your drive so that it
would boot but then hang, you'd have no recourse but to physically
remove the drive in order to get your system back up again.  I've had
that happen with RAD: when I set its BootPri greater than than of df0:
-- but at least in that case turning off the machine gets rid of the
problem.  Still, the odds of that happening to your hard drive are
probably small (at least I hope so :-).

Maurice LeBrun                Institute for Fusion Studies  
mjl@fusion.ph.utexas.edu      University of Texas at Austin