#: 9177 S10/OS9/6809 (CoCo)
    18-Jan-91  17:31:05
Sb: #9170-memory
Fm: Bill Dickhaus 70325,523
To: Everett Chimbidis 76370,1366 (X)

The only way to reorder your boot file is to use os9gen or an equivalent
utility. Its just a matter of making up a file of all system modules (an "ident
-s" of OS9Boot is one way to get the current list of modules) and redirecting
the file as input to os9gen.

If you are having system memory problems, rearranging your boot won't help. Any
(or all) of the following will help. Unless you really need it for something,
remove VDGInt from your boot. Remove any unecessary device descriptors (if your
just running the BBS you will only need a couple of window descriptors, for
example). If you are using serial drivers with large buffers, make sure you
really need all the buffer space (which comes from system memory). Keep the
number of processes to a minimum, don't start up a bunch of shells if you don't
really need them. Keep the number of open paths to a minimum, you can check
this with Kevin's paths command. Make sure you don't have any duplicate modules
in your OS9Boot file (this can't happen if you use cobbler to create the boot
file). Make sure that both GrfInt and WindInt are not in your boot, and unless
you need WindInt functions, you could use GrfInt (which is smaller).

Anything you can do to reduce the size of the OS9Boot file without eliminating
required functions will help.

You can use Kevin's smap utility to display current system memory utilization.
The pmap utility will show which processes are using how much memory, and how
much (in 8K chunks), the system process (PID 1) is using. The dirm utility is
similar to "mdir e", but includes additional information. It is invaluable in
seeing where in memory a system module is relative to another system modules
(and therefore helps in shuffling modules around to fix the BLOB).

Bill