Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!mcsun!ukc!strath-cs!str-va!cadp15
From: cadp15@vaxa.strath.ac.uk
Newsgroups: comp.sys.atari.st.tech
Subject: Re: Memory deallocation after TSR
Message-ID: <1990Dec11.113843.9395@vaxa.strath.ac.uk>
Date: 11 Dec 90 11:38:43 GMT
References: <8381@star.cs.vu.nl> <5208@brahma.cs.hw.ac.uk>
Distribution: comp
Organization: Strathclyde University VAX Cluster
Lines: 25

In article <5208@brahma.cs.hw.ac.uk>, neil@cs.hw.ac.uk (Neil Forsyth) writes:
> In article <8381@star.cs.vu.nl> rfschaa@cs.vu.nl (Schaaf R F ) writes:
>>
>>  I have a problem: I have written a device driver for some virtual
>>device. It performs some initialisations, then quits by using the
>>gemdos(49) call (TSR). After a while, when I don't need the driver
>>anymore I would like to free the memory used up by the driver and
>>give it back for general use. Is there any way this can be done?
> 
> I have had a go at doing this too. I don't think it's possible without
> tinkering with the OS pool entries. That of course would be a highly
> undocumented thing to do and would result in Allan Pratt slapping your
> wrists heavily.

Distributed a while back was a program to speed up GEM (not Quick ST, the other
one) in a demo version.  It removed itself from memory after a certain amount
of use so its possible...

Sorry I can't remember the name of the demo program :-(
-- 
       The Sorcerer is 'Only visiting this planet' but can be found at:
              (cadx862 @ uk.ac.strathclyde.computer-centre-sun)
                      (cadp15 @ uk.ac.strathclyde.vaxb)

          or second star to the right and straight on 'till morning.