Path: utzoo!attcan!uunet!husc6!mailrus!ames!ncar!noao!nud!rover!mph From: mph@rover.UUCP (Mark Huth) Newsgroups: comp.sys.amiga Subject: Loading Workbench from the Hard Drive Keywords: Workbench, Boot, Hard Drive Message-ID: <782@rover.UUCP> Date: 24 Jun 88 17:04:35 GMT Reply-To: mph@rover.UUCP (Mark Huth) Organization: Motorola Microcomputer Division, Tempe, Az. Lines: 40 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. Currently, the startup-sequence on df0: is: system/FastMemFirst BindDrivers execute dh2:s/startup-sequence dh2:s/startup-sequence: cd dh2: execute dh2:s/startup-assigns setmap usa1 dmouse rslclock Loadwb shell from s:shell-startup The startup-assigns assigns sys: to dh2: and all the rest of the logical devices found when a floppy Workbench boot has the assign command execute (ie, c: s: l: devs: fonts:, etc.). Also, the startup-assigns file sets the path to include current directory, sys:system, sys:utilities, ram:, and sys:. 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.) Thanks, Mark Huth