Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site mcrware.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!stolaf!umn-cs!isucs1!mcrware!kim
From: kim@mcrware.UUCP (Kim Kempf)
Newsgroups: net.micro.6809
Subject: Re: Making room in RAM
Message-ID: <141@mcrware.UUCP>
Date: Mon, 14-Oct-85 23:02:20 EDT
Article-I.D.: mcrware.141
Posted: Mon Oct 14 23:02:20 1985
Date-Received: Thu, 17-Oct-85 01:28:39 EDT
References: <8700002@hpvcla.UUCP>
Organization: Microware Systems Corp., Des Moines, IA
Lines: 30

In article <8700002@hpvcla.UUCP> Dave Lowe writes:
> 
> Topic: OS9 level 1
> 
> Question: How do I get more memory for my C compiler?
> 
The best thing to do is to create a bootdisk that has no pipe and null
file managers/drivers/descriptors.  Every little bit helps.  Gaining a single
page of memory may be all it takes to get something to compile.  When memory
is REALLY tight, list the c.com file and enter the commands by hand into the
shell.  This saves the memory required for a shell to execute the commands
from a procedure file.

> Another related questions. Which modules must reside in memory? Will OS9
> load device diver or device descriptor modules when it needs them?  Or do
> they have to be in memory?
>
Driver/descriptor modules must be in memory; OS-9 does not automatically
load them.

> My system has a disk driver with a /d0 and /d1
> descriptor modules, an ACIA driver with /t0 and /t1 descriptors, a PIA
> dirver with /p, and a windows driver with a /term descriptor.  I use them
> all and like to have them all active, but I also hate to use up precious
> memory with some of them which are used infrequently.  Can I have the
> best of both worlds and only have the drivers loaded when I need them?
> 
Driver/descriptor modules can be loaded and executed at any time.  Be aware
that when the driver requests static storage for the device the remaining
system memory may become fragmented, depending on the driver used.