Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ames!ncar!gatech!ncsuvx!ece-csc!rss
From: rss@ece-csc.UUCP (ML)
Newsgroups: comp.sys.amiga
Subject: Re: Loading Workbench from the Hard Drive
Keywords: Workbench, Boot, Hard Drive
Message-ID: <3673@ece-csc.UUCP>
Date: 25 Jun 88 01:02:54 GMT
References: <782@rover.UUCP>
Reply-To: rss@ece-csc.UUCP (ML)
Organization: the loony bin
Lines: 52

In a previous article mph@rover.UUCP (Mark Huth) wrote:
>Okay, I know that this has been answered before, but what is the magic
>sequence required to boot a hard drive system and load Workbench from
>the hard drive?  What I want to do is have the floppy sequence be as
>short as possible....
...
>When the script gets to the loadwb command I get a requestor telling
>me that the disk isn't validated yet, and of course, the disk
>validator is running (for about 10 -15 minutes - 40 meg disk).  After
>the validator finishes, workbench loads and the script completes.
>
>How do I get this script to work without having the validator hold
>things up forever.  It doesn't happen if I just boot the cli and
>shell, or if the loadwb command is located before all the assigns to
>the hard disk (ie it is loaded from the boot floppy.)


As I understand it, the guilty culprit here is the "execute" command
which is writing a temporary file on your hard drive which is eventually
the cause of the tremendous delays incurred by the disk validator
when you issue the LoadWB command.  Rather than using "execute";
do a "NewCli FROM file".   Here's my startup sequence from df0:s

************************* cut here ****************************************
Wait 5				; Allow hard drive to come up to speed
Mount DH0:			; Bring it online
Assign LIBS: DH0:Libs		; Assignments to LIBS and L are so that
Assign L:    DH0:L		; I can run the ARP commands on DH0.
Assign DEVS: DH0:Devs		; To get at MountList before using ConMan
Assign C:    DH0:C
ConMan > NIL: -w
NewWsh "CON:0/10/640/190/Master Wshell/c" From DH0:S/BootSequence
EndCli > NIL:
************************* snip snip ***************************************

The initial "Wait 5" I put there because sometimes I found the "Mount"
command would fail when I first turned on the machine, apparently 
because the drive wasn't ready yet.  The initial ASSIGN statements (except
perhaps C: to DH0:C) aren't necessary if you are running your machine
with standard Amiga commands; they're only there in my sequence because
(a) I have the ARP commands installed on my hard drive, and they need
a run-time library in LIBS:, and (b) I use ConMan, which has a handler
in L:, plus an entry in DEVS:MountList.

Of course, like you, the bulk of my startup stuff is on the hard drive
(in DH0:S/Bootsequence), where I do all the usual sorts of things 
(load AREXX, AmiCron, DMouse [love that Dmouse!], CD DH0:, LoadWB, etc) 
and all works quickly.

Hope this helps,

      Mark Lanzo
thru  ..mcnc!ece-csc!rss