Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-lcc!ames!ucbcad!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: Mini-review of CLtd 20M disk
Message-ID: <8701052118.AA15235@cory.Berkeley.EDU>
Date: Mon, 5-Jan-87 16:18:58 EST
Article-I.D.: cory.8701052118.AA15235
Posted: Mon Jan  5 16:18:58 1987
Date-Received: Mon, 5-Jan-87 23:07:19 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: University of California at Berkeley
Lines: 24

>Also, While I on the line,
>WHAT THE HECK DOES KICKSTART, and the WORKBENCH Loader do???
>Exactly !!  Basically, I want to write my own Kickstart and Workbench Loader
>That access another device (mainly the Hard drive!).
>Exactly what sectors does kickstart and workbench take from the disk nad where
>should the Boot strap program put these sectors ???

I'm no expert, but here is a little information:  The kickstart loader resides
in ROM (as in the real thing).  As far as a know, it's a simple bootstrap
which loads the first 256K off the kickstart disk into the WCS, then executes
it.

I assume that the OS will then ask for the workbench et all.  Thus, unless
you plan on modifying the boot rom, all you can theoretically do is modify
data in the OS image on the kickstart.  I can see a person being able to
hack up the disk id check (KICKBENCH), and perhaps making the OS look for
the workbench on DF1: instead of DF0: (any takers??).  I don't think you
will be able to hack in making the initial workbench search go to the hard
drive.

As far as the rest of the workbench goes, all you really have to do is
reassign all the logical assignments.

				-Matt