@database "MountRemHD.guide"

@index INDEX

@remark
@remark "$VER: MountRemHD (18.5.97) Svend Daugaard Pedersen"
@remark


@node main "MountRemHD 1.0 ©1997 Svend Daugaard Pedersen - Guide summary"



                     @{b}MountRemHD 1.0 - Guide Summary@{ub} - (18-May-97)

                            by @{" Svend Daugaard Pedersen " link author}


                               @{"   Copyright             " link copyright}
                               @{"   Distribution          " link distribution}
                               @{"   Requirements          " link requirement}
                               @{"   Introduction          " link introduction}
                               @{"   Quick Installation    " link quickinstall}
                               @{"   Preparing a new disk  " link prepdisk}
                               @{"   Mount File            " link mountfile}
                               @{"   Using MountRemHD      " link mountremhd}
                               @{"   Insert/Remove Scripts " link scripts}
                               @{"   Adding search Paths   " link globalpath}
                               @{"   Author's address      " link author}
                               @{"   Warranty              " link warranty}

@endnode

@node copyright "MountRemHD copyright"
@prev main
@next distribution

                 @{b}MountRemHD@{ub}   -  version 1.0   18-May-97

         ©1995-96 @{"Svend Daugaard Pedersen" link author}

         @{i}Compiled with @{" SAS/C ® " link thanks 5} 6.57 and @{" StormC ® " link thanks 7}@{ui}

   MountRemHD, as well as all the accompanying files, is ©1997 Svend Daugaard Pedersen.
   
@endnode

@node warranty "NO warranty for MountRemHD"
@next distribution

   @{b}NO WARRANTY@{ub}

   There is no warranty for this software package. Although the @{" author " link author}
   has tried to prevent errors, he can't guarantee that the software package
   described in this document is 100% reliable. You are therefore using this
   material at your own risk. The author cannot be made responsible for any
   damage which is caused by using this software package.

@endnode

@node distribution "MountRemHD distribution"
@prev warranty
@next requirement

   @{b}DISTRIBUTION@{ub}

   This software package is freely distributable. It may be put on any
   media which is used for the distribution of free software, like Public
   Domain disk collections, CDROMs, FTP servers or bulletin board systems.

   In order to ensure the integrity of this software package, distributors
   should use the complete original distribution. 

@endnode

@node requirement "MountRemHD requirements"
@prev distribution

   @{b}REQUIREMENTS@{ub}

   MountRemHD needs at least System 2.04 to run, and has been developed
   and tested with KS 40.68 and WB 40.42. It should work with other
   versions as well.

@endnode

@node introduction "Introduction to MountRemHD"
@prev requirement

   @{b}INTRODUCTION@{ub}


   @{"MountRemHD" link mountremhd} is a utility that makes it possible to use removable hard
   disks of different sizes in a SyQuest EZ Flyer disk drive. In addition
   @{"script files" link scripts} are automatically executed when disks are inserted or removed.

   Also useful for owners of EZ135 (and may be owners of other drives).

   To be able to use programs that require search paths two small utilities
   @{"AddGlobalPath" link globalpath} and @{"RemGlobalPath" link globalpath} has been included in the archive. They
   are designed to be used in the the @{"script files" link scripts} so that such search
   paths can be added and removed when disks are inserted and removed.


@endnode

@node quickinstall "Quick Installation"
@prev introduction

   @{b}Quick Installation@{ub}

   Edit the @{"mount files" link mountfile} RHD0 and RHD1 (only small modifications
   is necessary) and copy them to DEVS:.

   Copy @{i}MountRemHD@{ui} to WBStartup.

   Copy @{i}MountRemHD.info@{ui} to WBStartup and remove the paranthesis around
   the tool types in this info-file.

   Copy @{i}AddGlobalPath@{ui} and @{i}RemGlobalPath@{ui} to C: (or another place).

   Reboot or just start @{i}MountRemHD@{ui} by double clicking on its icon.

@endnode

@node prepdisk "Preparing a new Disk"
@prev quickinstall

   @{b}Preparing a new Disk@{ub}

   Put a new disk into the drive, start @{i}HDtoolBox@{ui} and select the
   drive.

   Then press @{b}Change Drive Type@{ub} to define parameters.

   Next press @{b}Partition Drive@{ub} and remove any extra partitions
   (use only one partition!). Then select @{b}Advanced Options@{ub} and press
   @{b}Change...@{ub} to @{u}un@{uu}select @{b}Automount this partition@{ub}.

   Press @{b}Ok@{ub} twice and press @{b}Save Changes to Drive@{ub}.

   Finally press @{b}Exit@{ub} to leave the program.

   Format the disk.

@endnode

@node mountfile "Mount File"
@prev prepdisk

   @{b}Mount Files@{ub}

   A typical mount file for a media to SyQuest EZ looks


     /* EZ 135Mb drev */

     Unit = 4
     Device = scsi.device
     Flags = 0
     Surfaces = 1
     BlocksPerTrack = 96      /* 132 for 230Mb  */
     Reserved = 2
     Interleave = 0
     LowCyl = 2
     HighCyl = 2729           /* 3412 for 230Mb */
     Buffers = 64
     BufMemType = 0
     MaxTransfer = 0xffffff
     Mask = 0x7ffffffe
     DosType = 0x444f5303
     Activate = 0


   Normally only the Unit and Devive fields may need changes.

@endnode


@node mountremhd "Using MountRemHD"

   @{b}Using MountRemHD@{ub}

   The program @{i}MountRemHD@{ui} may be started from the shell using the
   @{i}run@{ui} command. The name of one or several @{"mount files" link mountfile} must be given
   as parameter(s).

   Ex.:

              run MountRemHD RHD0 RHD1


   If the files RHD0 and RHD1 are not placed in the DEVS: directory a
   complete path must be given.

   If started from WB the name of the @{"mount files" link mountfile} must be put into
   the tool types of the icon. One file name in each.

   The program is running in back ground waiting for a disk to be inserted
   or removed. When this happens the @{i}diskchange@{ui} command is executed to
   inform the disk handler about this. Then the @{"insert script file" link scripts} or the
   @{"remove script file" link scripts} is executed (if present on the disk).

   The first time a disk of a given size is inserted, the device is mounted
   by executing the @{i}mount@{ui} command with a mount file as parameter.

   If the drive is turned off at startup (external drives) and later turned on,
   the program will detect this (if it fails try to remove the disk and insert
   it again).

   The best place to put the program is the WBStartup drawer.

   See also @{"Quick Installation" link quickinstall}.

@endnode

@node scripts "Insert and Remove Scripts"
@prev mountremhd

   @{b}Insert and Remove Scripts@{ub}

   Script files with the names @{i}Insert.Script@{ui} and @{i}Remove.Script@{ui} placed in
   the root of a disk are executed when the disk is inserted and removed
   (when the disk is inserted the @{i}Remove.Script@{ui} is copied to T:).

   These scripts are typically used to add assigns when a disk is inserted
   and remove them again when the disk is removed again.


   Example: After the installation of @{i}GoldED@{ui} assign commands like the
     following are added to your @{i}user-startup@{ui}:


         ASSIGN >NIL: GOLDED: Disk:GoldED
         ASSIGN >NIL: HISPEED: GOLDED:TOOLS/HISPEED


     If the installation is done on a removable disk, make an insert script
     containing these two commands (and remove them from the @{i}user-startup@{ui})
     and a remove script with the commands

         ASSIGN >NIL: GOLDED: REMOVE
         ASSIGN >NIL: HISPEED: REMOVE


   Some programs need a search path to be set up.


   Example: If you want to place your SAS/C on a removable disk, the insert
     script should look something like:


         ; Make assign for SAS/C

         assign sc: Develop:sc
         assign lib: sc:lib
         assign include: sc:include
         assign cxxinclude: sc:cxxinclude
         AddGlobalPath sc:c

         copy >NIL: sc:env/#? env:sc

     and the remove script like


         ; Make un-assign for SAS/C

         RemGlobalPath sc:c
         assign sc: REMOVE
         assign lib: REMOVE
         assign include: REMOVE
         assign cxxinclude: REMOVE


   The programs @{"AddGlobalPath" link globalpath} and @{"RemGlobalPath" link globalpath} are part of the archive.

@endnode

@node globalpath "Using AddGlobalPath and RemGlobalPath"
@prev scripts

   @{b}AddGlobalPath and RemGlobalPath@{ub}

   Some programs need a search path to be set up. This causes some problems.
   You can't use the @{i}path@{ui} command, since this path will not be global.
   In stead you must use @{i}assign C: yourpath ADD@{ui}, and later the command
   @{i}assign C: yourpath REMOVE@{ui} to remove the search path again.

   But unfortunately this last command will not work in a @{"remove script" link scripts}. The
   system requires that the disk is present when the command is executed!

   The two utilities @{i}AddGlobalPath@{ui} and @{i}RemGlobalPath@{ui} can be used
   in stead of these commands to solve this problem.

   The command formats are

         AddGlobalPath path [path2 path3 ... ]

         RemGlobalPath path [path2 path3 ... ]

   The paths must be spelled in excactly the same way in the two commands
   since the assignment to be removed is found by comparing ascii strings.

   As an example of using the utilities see @{"Insert and Remove Scripts" link scripts}.

   @{i}AddGlobalPath@{ui} and @{i}RemGlobalPath@{ui} manipulates internal lists in AmigaDOS,
   so they are not guaranteed to be 100% safe to use. But they have been
   used by the @{"auther" link author} for some time without problem.

@endnode

@node author "MountRemHD author"
@prev main
@next main

    Send any suggestion, bug report or compliment :-) to:

                         Svend Daugaard Pedersen
                         Hoffmeyersvej 17
                         DK-2000 Frederiksberg
                         Denmark

                         Email: sdp@dk-online.dk


@endnode

@node thanks "MountRemHD's author would like to thank..."
@prev main
@next main

   Amiga                For being the best platform to 'work' on. And still
                        alive in spite of some sad facts.

   SAS/C ®              The compiler I have used for years.

   StormC ®             A C/C++ compiler with an excellent development environment,
                        but still (in ver. 2) with some annoying bugs.

@endnode
           
