Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ukma!psuvax1!psuvm!art100
From: ART100@psuvm.psu.edu (Andy Tefft)
Newsgroups: comp.sys.apple2
Subject: Re: Doing some things with the Ramworks III
Message-ID: <91085.142651ART100@psuvm.psu.edu>
Date: 26 Mar 91 19:26:51 GMT
Organization: Penn State University
Lines: 35
Supersedes: <91085.131940ART100@psuvm.psu.edu>

In article <1991Mar25.024845.20985@ux1.cso.uiuc.edu>, kjs39186@uxa.cso.uiuc.edu
(Kent Squires) says:
>
>Sombebody said that they installed the RAM disk under DOS 3.3, then just PR#'d
>into ProDOS and the RAM disk was kept intact.  I tried this on a //e and it
>DIDN'T work.

[followed by:]

From: bh1e+@andrew.cmu.edu (Brendan Gallagher Hoar)
Date: 25 Mar 91 03:58:00 GMT

>I remember somewhere in the docs that you have to tell DOS 3.3 ram
>drive driver to lock out the bottom 64k of the Ramworks.  Otherwise
>ProDOS will write over the bottom of your DOS 3.3 ramdrive when
>creating it's standard /RAM drive.

I did this; then started up copy II+ v8.3, and it said s3,d2 was
disconnected.  I re-ran the ramdisk driver, changing it to slot 5,
and again, copy II+ didn't recognize it.

However, when I re-booted dos 3.3, the files on the ramdrive
were intact.

Now while this is all fine and good, what I wanted (and am not so
interested in now) was being able to access a dos 3.3 ramdisk
from prodos. Now, it makes sense that this is not possible,
since the ramdisk driver was a temporary modification to dos 3.3 itself,
which is not included in the copy II+ dos 3.3 routines.

As it turned out, I had to use prodos anyway.

But I am *still* interested in getting two ramdisks at the same
time, if it's possible.  If Prodos 8 does it automatically on the GS,
it should be able to be done on the //e as well.