Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!burl!codas!cpsc6a!rtech!mark
From: mark@rtech.UUCP
Newsgroups: comp.sys.mac
Subject: Re: Two Problems
Message-ID: <659@rtech.UUCP>
Date: Sat, 14-Feb-87 01:40:19 EST
Article-I.D.: rtech.659
Posted: Sat Feb 14 01:40:19 1987
Date-Received: Sun, 15-Feb-87 00:22:04 EST
References: <1029@ur-tut.UUCP>
Organization: Relational Technology, Alameda CA
Lines: 28

In article <906@unc.unc.UUCP> glassner@unc.UUCP (Andrew S. Glassner) writes:
>
> goes astray, and I get a system bomb alert.  My only choice is to reboot
> the system - which takes a while.  Is there anything I can do, in the
> Finder, System, or my application, that will enable the system to resume
> after such a problem?  I wouldn't mind if it just rebooted itself auto-
> matically, but something more graceful (and fast!) would be nice...

Well, I don't know if there are any other solutions, but I've got a 2Mb
MonsterMac from Levco, and got RamSafe for it (PROMs and a small program
from CJS Systems in Berkeley, CA) that gives me a non-volatile ramdisk.
I no longer bother trying to ExitToShell, since rebooting is now about 4
or 5 seconds!  Besides, ExitToShell can cause problems if the filesystem
or other useful system stuff has been trashed, and sometimes the ExitToShell
code itself has been trashed.

While I'm here, I've noticed that my first reboot doesn't run any INITs
that are not in the system file, but subsequent reboots do.  Any hints?
This is RamSafe 1.1, System 3.2, Finder 5.3.

Mark Wittenberg
Relational Technology
-- 

Mark Wittenberg
Relational Technology
zehntel!rtech!mark
ucbvax!mtxinu!rtech!mark