The normal boot sequence can be used to run anything that you want loaded
before the desktop is started, such as:
* modules that define extra VDU modes
* obey files that define aliases, paths, set the library, etc.
* a BBC font file, replacing the system font
* sprite files to load replacements for Wimp sprites
* toolsprite files, for customized window borders
* some utilities that must be loaded before the desktop starts, e.g.
ToEdit, Larger
* obey files that set the Wimp$Path variable, to make the Wimp load
non-standard templates
The desktop sequence usually contains:
* applications that you want "seen" by the filer, e.g. !System,
!Fonts, !Paint or !ArcFS. That way the Wimp knows where to find modules
or fonts, and what to do when you double-click a Sprite or Archive file.
* applications that you want running after startup, because you use
them a lot: a backdrop program (!Menon, !PlaceIt, etc.) or your
favourite text editor.
* directories that you want to have opened, because they contain
files or applications that you are working on.
In the scheme above, the desktop boot sequence was called DeskBoot. In fact,
this file can have any name you choose, but it must be located in the same
directory.
Using the program
-----------------
The program is started by double-clicking on its icon in a filer window.
First it tries to read the existing boot sequences, from the disk it is
stored on. After that, the application installs itself on the icon bar.
Clicking with the Select button on the icon opens two windows, containing
the boot sequences. Clicking with Adjust closes them again.
Pressing the Menu button over the icon bar icon brings up the main menu.
Apart from the usual "Info" and "Quit", the main menu has three items:
Re-read files To read the boot sequences again, e.g. after you have
changed the file names, or messed up the sequences a bit.
File names Leads to a submenu-window in which you can view and edit
the file names of the sequences. The first name is that
of the boot directory itself, the second is the leafname
of the desktop sequence (the leafname of the first
sequence must be "!Run").
Save all Saves both sequences.
Loading the boot sequences
--------------------------
Two ways to load the contents of the boot sequences have already been
mentioned (at program startup, and with "Re-read files" from the menu).
A third way is to drop the icon of the directory $.!Boot on the icon bar
icon. This can be useful if MakeBoot is not run from the same disc as the
boot disc.
Editing the boot sequences
--------------------------
The sequence windows show the boot sequences. Each sequence consists of a
list of items (files, applications or directories). The window shows each
item as an icon with a leafname. To the right of this, you can see the
action, shown in red. This action is the command that is executed on the
item when the sequence is run.
Inside a sequence window, you have the following possibilities to edit:
* To add a new item to a sequence: drag a file or application from a Filer
window to the !MakeBoot sequence window. The new item is inserted into the
sequence; a default action is attached to the item (it depends on the type
of the item which action that is)
* To change the order of the items in the sequence: drag the item to the new
position. It is moved to just before the item that the mouse pointer was on
when you dropped it.
* To move an item to the other sequence: drag it to the other window
* To change the action that is attached to an item: click on the action with
Select or Adjust.
* You can "deactivate" an item. A deactivated item is shown in grey. Deactivated items are saved with the rest of the sequence, but they are not run: they are commented out (with a "|") in the file. This can be handy when you are experimenting with the contents of a sequence. Items are deactivated by clicking on their name with Adjust, or from the menu.
Clicking the Menu button above a sequence window brings up a menu with a
couple of choices:
Item ⇨ Inactive Toggles the "deactivated" setting for the item (see
above)
Item ⇨ Arguments ⇨ A writable submenu where you can enter the
command-line arguments that are attached to the item.
Item ⇨ Open parent Opens a Filer window on the parent directory, in
which the item is located.
Item ⇨ Change to root Changes the name of a directory to "$". This option
is needed if you want a Filer_OpenDir on the root
directory: there is no icon of the root directory that
can be be dragged to the window! In that case, drag
another directory in the sequence, and choose this
option.
Item ⇨ Delete Removes the item from the sequence.
Sequence info ⇨ Gives some info about this sequence.
Save sequence Saves this sequence to disc.
To !Boot
--------
Archimedes users with some experience probably know how to make their
machine run a boot sequence, but for those who don't, here is how to get it
done.
1) Create a directory called !Boot in the root directory of your harddisc.
2) Press F12, to go to the command line and enter the following commands:
*Configure Boot
(this tells your computer to boot from disc; the default is
NoBoot)
*Opt 4 2
(selects the boot action: the !Boot application will be run)
Before entering the last command, you should make sure that the
current directory is somewhere on the harddisc.
3) Depending on what kind of hardisc you have, you may need to set
some more configurations, e.g.:
*Configure FileSystem SCSIFS (or IDEFS)
(to set the file system that is booted from; the default is ADFS)
*Configure Drive 4 (or 5)
(to select the ADFS drive to boot from; the default is 0)
Setting the language with ResFind
---------------------------------
!MakeBoot adapts automatically to the configured language if the corresponding messages etc. are available. For this purpose a Resources directory is contained in the application in which a subdirectory for each language supported resides. If the language you need isn't in there, please feel free to duplicate any of these language directories and translate the contents.
When you run the program a utility called ResFind is called which reads the language your computer is configured to and then looks for the corresponding language directory. If this fails the program will run in English (UK). By setting several system variables (best done in your system's !Boot file) you can change the language looked for. With this you can make sure a program runs in a certain language, e.g. to avoid a weird translation. Furthermore it is possible to name several languages you prefer to English.
This is controlled by three system variables:
MakeBoot$Language, ResFind$LanguagesPref und ResFind$Languages$Suff.
When running the application ResFind looks for the first language supported along the following list of languages:
1. Contents of the variable MakeBoot$Language
2. Contens of the variable ResFind$LanguagesPref
3. The configured language
4. Contens of the variable ResFind$LanguagesSuff
5. UK
Take a Norwegian user for example (lots of great programs come from there) whose computer is configured to 'Norway'. Since this language isn't too common in Europe most programs won't support it - except for Norwegian ones. But our user is pretty good in German and French but not too fond of English. Therefore he prefers these languages to UK and would thus put the following line in his system's !Boot file:
*Set ResFind$LanguagesSuff Germany,France
Running an applications (such as this one) using ResFind the list of languages looked for is 'Norway,Germany,France,UK'.
In case this user hat an application calles !Pete supporting the languate 'Humorous' the line
*Set Pete$Language Humor
in the !Boot file makes sure !Pete will run humorous.
Known bugs and possible future additions
----------------------------------------
No known bugs.
Copyright notice
________________
This program is FreeWare. If you like it, you may copy it and distribute it,
provided that you do not charge anything for it. Use of the program is
entirely at your own risk. You may change the program to suit your own
needs, but you may not give a modified copy to someone else. If you think
your changes are an improvement, then please send them to the address below,
so that I can incorporate them in a new version. Also, if you have any
questions, bug reports or suggestions for improvements, you can contact me
