home *** CD-ROM | disk | FTP | other *** search
-
- ; Your entire user-startup script consists of running DAUTOSTART
- ; redirected to a ram file which is then executed. DAUTOSTART will
- ; build a startup script by scanning all mounted filesystems (it runs
- ; the INFO program to get a list of mounted filesystems) looking for
- ; files named 'boot-sequence.1'
- ;
- ; Only one directory level is searched allowing boot-sequence.1 files
- ; in the root of each filesystem and in any sub-directory of each
- ; filesystem. Further levels of sub-directories are searched only
- ; when a boot-sequence.1 file is actually found, and so on.
- ;
- ; Also, if boot-sequence.1 is found DAUTOSTART will also look for
- ; boot-sequence.2 and so on .. up to boot-sequence.9, allowing
- ; multiple startup scripts at different priorities (see DAUTOSTART.DOC
- ; for information on prioritization) to apply to a given installation
- ;
- ; So, for example, you might have
- ;
- ; DH1:boot-sequence.1
- ; DH1:src/boot-sequence.1
- ; DH1:src/boot-sequence.2
- ; DH1:src/fubar/boot-sequence.1
- ;
- ; All of which will be found automatically by DAUTOSTART, but without
- ; DAUTOSTART searching the rest of the directory tree for DH1.
- ;
- ; The order in which DAUTOSTART finds boot-sequence files does not
- ; generally effect the output script since each boot-sequence file
- ; may have a priority. DAUTOSTART sorts the files before constructing
- ; the combined script.
-
- ; run dautostart to generate script to ram:auto, then run the script
-
- path reset
- sys:bin/dautostart >ram:auto
- execute ram:auto
- cd sys:
- delete ram:auto
-
- ; save the directory path constructed by the startup script so
- ; shell-startup can access it without having to hardwire paths
-
- sys:bin/savepath
-
-