Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!oliveb!pyramid!batcomputer!braner
From: braner@batcomputer.tn.cornell.edu (braner)
Newsgroups: comp.sys.atari.st
Subject: NITE and SCACHE interaction bug
Message-ID: <944@batcomputer.tn.cornell.edu>
Date: Sun, 10-May-87 14:40:56 EDT
Article-I.D.: batcompu.944
Posted: Sun May 10 14:40:56 1987
Date-Received: Mon, 11-May-87 03:30:51 EDT
Reply-To: braner@tcgould.tn.cornell.edu.UUCP (braner)
Organization: Cornell Theory Center, Cornell University, Ithaca NY
Lines: 17
Summary: micro-C-Shell's fault?

[]

I finally experienced the reported bug of getting two cherry bombs when
trying to access drive A: after the ST sitting for hours with NITE blanking
the screen and SCACHE also active.  That was from micro-C-Shell.  Doing
a 'logout' (to the RAMdisk!) and accessing drive A: from the desktop cured
it completely: I could then run mCS again (from the RAMdisk!) and keep
accessing drive A.  I have done this _twice_ since last time I booted my ST,
with no ill effects.  Is it mCS's fault?  Explanation?

- Moshe Braner

PS: I boot with AUTODISK, copying mCS and all into the RAMdisk.  I then
run mCS, and the login.sh file does "set home=D:\" and "set path=D:\".
When I 'logout', it returns to the desktop and the window it was invoked
from, i.e. the RAMdisk.  I find that very convenient.  I can always
remove mCS from the RAMdisk (even from inside mCS!) to gain space if needed.