Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cwjcc!ukma!husc6!uwvax!astroatc!nicmad!madnix!rat
From: rat@madnix.UUCP (David Douthitt)
Newsgroups: comp.sys.apple
Subject: Disconnection of /RAM
Message-ID: <464@madnix.UUCP>
Date: 5 Feb 89 16:51:24 GMT
References: <8901262011.AA01800@rice-chex.ai.mit.edu> <2099@netmbx.UUCP>
Reply-To: rat@madnix.UUCP (David Douthitt)
Distribution: na
Organization: ARP Software, Madison, WI
Lines: 23

In article <2099@netmbx.UUCP> blume@netmbx.UUCP (Heiko Blume) writes:
| i'd suggest a minor but important fix to amacs (and many other programs
| that want 128K and disconnect the /ram drive allways, grrr):
| it would be real nice to have a option in the init script that specifies
| whether the /ram drive must me disconnected (thats for prodos' /ram in the
| second 64k) or not. that way many people could use their meg byte /ram's
| which are not in the lower 128K.

Programs should not be confusing the Prodos 64K /RAM volume with any other
/RAM volume - after all, I would suppose that a program would just remove
whatever volume it found in slot 3, drive 2 or somesuch.

What we need is to have programs to put /RAM back where they found it!
And, on the flip side, programs which NEED /RAM (you know who you are)
shouldn't hiccup or stutter when /RAM is missing!

        [david]

-- 
======== David Douthitt :::: Madison, WI :::: The Stainless Steel Rat ========
FidoNet: 1:121/1 or 1:121/2            {decvax|att}!
UseNet:  ...{rutgers|ucbvax|harvard}!uwvax!astroatc!nicmad!madnix!rat
ArpaNet: madnix!rat@cs.wisc.edu      {uunet|ncoast}!marque!