Path: utzoo!attcan!uunet!lll-winken!csd4.milw.wisc.edu!leah!rpi!rpi.edu!deven From: deven@pawl.rpi.edu (Deven Corzine) Newsgroups: comp.sys.amiga Subject: Re: More 1.4 whishes Message-ID: Date: 2 Mar 89 01:38:56 GMT References: <5442@abo.fi> <2020@cps3xx.UUCP> <1265@hub.ucsb.edu> Sender: usenet@rpi.edu Reply-To: shadow@pawl.rpi.edu Organization: RPI Public Access Workstation Lab, Troy NY Lines: 23 In-reply-to: armhold@topaz.rutgers.edu's message of 1 Mar 89 22:50:11 GMT In article 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? No. More often it is to reset the system to a known state, and a significant percentage of the reboots are accidental, resulting from GURUs and crashes which don't even GURU but just display neat fireworks displays. Having resident programs recoverable would be VERY valuable. Not automatically; do it similarly to RAD: - a "resident recover" command in the startup-sequence or some such. Of course, the resident seglists should be protected by 32 bit CRC's so you don't end up with corrupted versions because of the last crash. In short, I strongly agree: Make resident commands recoverable!! Deven -- ------- shadow@pawl.rpi.edu ------- Deven Thomas Corzine --------------------- Cogito shadow@acm.rpi.edu 2346 15th Street Pi-Rho America ergo userfxb6@rpitsmts.bitnet Troy, NY 12180-2306 (518) 272-5847 sum... In the immortal words of Socrates: "I drank what?" ...I think.