braner@batcomputer.tn.cornell.edu (braner) (05/10/87)
[] 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.