MAKING BOOTABLE DISKS
                          ---------------------


   <> 34 <%> 34 <%> 34 <%> 34 <%> 34 <%> 34 <%> 34 <%> 34 <%> 34 <%> 34 <>


   The first thing you need to do is install a boot block on the disk. You
  can do this from Shell/CLI simply by typing install (device), eg. install
  df0:. Alternatively, most GOOD Disk Utility programs allow you to install
  a disk. A perfect example of such a utility is Directory Opus by Jonathan
  Potter.

   WARNING: Some disks, especially commercial game disks use non-standard
  boot blocks, and require these to function properly. If you install a new
  boot block over one of these, the chances are you just made yourself an
  expensive blank disk. If you are unsure, don't. It's best to only install
  your own work disks, unless you have confidence in what you are doing.

   Once you have your boot block installed, the next thing you need to do is
  put S: and C: directories on it. Again, most good utilities should allow
  you to makedirs, as does Directory Opus mentioned above. If however you
  are working from Shell/CLI, simply type in the commands, 'makedir s' and
  'makedir c'. If you are using my Cybershell, you could abbreviate this to
  mkdir to save some typing.

   Once you have these in place, you need to put in the appropriate files
  required for the disk to boot. So use your Disk utility to copy these
  files over from your source disk (such as your system (workbench) disks) or
  with Shell/CLI, use the copy command.

   The following files are the bare minimum require for the C: directory.

                  LoadWB
                  EndCLI

   Not many huh? That's right. To copy them using Shell/CLI, go into the C:
  directory that contains them and type in the following if you are using two
  floppy drives or a HardDrive (I'll assume that the disk you are making
  bootable is in DF1:)...

      copy loadwb df1:c/
      copy endcli df1:c/

   If you are using a single disk system and you have a RAM: drive, do the
  following, making sure that you start in the C: of the disk that contains
  the files....

      copy endcli ram:
      copy loadwb ram:
      cd ram:
      (change the disk in DF0: to the new disk you are making bootable)
      copy loadwb df0:c/
      copy endcli df0:c/

   Now that you have the necessary files in place, all you have to do is
  create a startup-sequence to carry out the booting. This is where the S:
  directory comes into play.

   Using your favourite text editor, edit a new file called startup-sequence
  in the s:directory of the new disk. If you don't know how to use a text
  editor, then from Shell/CLI, change to the S: directory and type 'ed
  startup-sequence'.

   Once you are editing, you simply have to type the following lines:

   loadwb
   endcli

   Once you have finished, save the file and exit. If you are using ed, hit
  the [esc] key and then hit 'x' and [return]. This will save the file and
  exit from the program.

   Once all that is finished, you are now the proud owner of a bootable disk.
  You can experiment with adding other things into your startup sequence as
  you become more experienced and confident with what you are doing.

     Cheers
        Scott English

   --- Directory Opus, mentioned in this article, is written by Jonathan
  Potter, and is a fine Australian product indeed. The latest version, 4, is
  available from him at PO Box 289, Goodwood, SA 5034, Australia, or from any
  self respecting retailer.

   --- CyberShell is an extension of Shell and works fully in conjunction
  with it.  It is freely distributable and is available from me at 59 Thomas
  Coke Drive, Thornton, NSW 2322, Australia for $3.50.



   <> 34 <%> 34 <%> 34 <%> 34 <%> 34 <%> 34 <%> 34 <%> 34 <%> 34 <%> 34 <>