Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!hermes!dzenc
From: dzenc@hermes.ai.mit.edu (Daniel Zenchelsky)
Newsgroups: comp.sys.amiga
Subject: Resident in 1.4
Message-ID: <3291@hermes.ai.mit.edu>
Date: 3 Mar 89 00:58:54 GMT
Reply-To: dzenc@hermes.UUCP (Daniel Zenchelsky)
Organization: The MIT AI Lab, Cambridge, MA
Lines: 34

Newsgroups: comp.sys.amiga
Subject: Re: More 1.4 whishes
Summary: 
Expires: 
References: <5442@abo.fi> <2020@cps3xx.UUCP> <1265@hub.ucsb.edu> <Mar.1.17.50.06.1989.9522@topaz.rutgers.edu>
Sender: 
Reply-To: dzenc@hermes.ai.mit.edu.UUCP (Daniel Zenchelsky)
Followup-To: 
Distribution: 
Organization: The MIT AI Lab, Cambridge, MA
Keywords: 

In article <Mar.1.17.50.06.1989.9522@topaz.rutgers.edu> armhold@topaz.rutgers.edu (George Armhold) writes:
>>have the resident commands survive a warm-reboot.
>
>I don't think that would be a good idea- the reason for warm-booting is
>usually to clear all ram, no?
>
>	-George

All you have to do is add a command "Resident Restore" to recover the list.
that way if you want to clear it, you just don't enter that command. 
Like you don't mount rad: if you don't want it.

-Dan

+-----------------------------------------------------------+
|  ______                                                   |
| ||   |o|  Daniel Zenchelsky  --  dzenc@hermes.ai.mit.edu  |
| ||___| |                                                  |
| |   _  |  "If it's not in the computer, it doesn't exist" |
| \_[]_|_|                                                  |
|                                                           |
+-----------------------------------------------------------+