Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!usc!apple!agate!darkstar!ucscb.UCSC.EDU!unknown
From: unknown@ucscb.UCSC.EDU (The Unknown User)
Newsgroups: comp.sys.apple2
Subject: Re: Reply to an old post about System Disk on /ram5
Message-ID: <6335@darkstar.ucsc.edu>
Date: 25 Aug 90 05:00:41 GMT
References: <6282@darkstar.ucsc.edu> <1990Aug24.190830.6671@laguna.ccsf.caltech.edu>
Sender: usenet@darkstar.ucsc.edu
Organization: University of California, Santa Cruz; Open Access Computing
Lines: 32


In article <1990Aug24.190830.6671@laguna.ccsf.caltech.edu> toddpw@tybalt.caltech.edu (Todd P. Whitesel) writes:
>Has anybody tried booting into finder (from 3.5) and dragging the boot disk
>onto /ram5 (assuming /ram5 is 800K)?
>
>Set the boot slot to RAM disk and away you go.
>
>Works for me...
>
>Todd Whitesel
>toddpw @ tybatl.caltech.edu


Yes I've tried that... It doesn't work for me.. Mainly I'm trying to
be able to copy to /ram5 and boot so I don't have to boot AT ALL from a
floppy.. Thus prodos 8 solutions are best.  Other people have had this
same problem so I'm not insane or anything (well, that's another matter..
heh heh)..

I've tested RAM.. no problems..

With this being a seemingly widespread problem, it seems like it might
be a bug in the system somehow.

I will say though that after I got a new copy of 5.02 a few weeks ago,
copying system to /ram5 worked ONCE.. The copy was never un-write
protected even up until I tried it another time, so that's an even
stranger occurence.

-- 
        /  Apple II(GS) Forever!     unknown@ucscb.ucsc.edu  \
        \    Computer engineering student seeking a job.     /