Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!agate!darkstar!ucscb.UCSC.EDU!unknown
From: unknown@ucscb.ucsc.edu (The Unknown User)
Newsgroups: comp.sys.apple2
Subject: Re: Copying System Disk to /ram5
Message-ID: <6560@darkstar.ucsc.edu>
Date: 4 Sep 90 05:11:05 GMT
Sender: usenet@darkstar.ucsc.edu
Organization: University of California, Santa Cruz; Open Access Computing
Lines: 31


>In some article or another Carl Norden said:
>In article <13181@netcom.UUCP> avery@netcom.UUCP (Avery Colter) writes:
>>I was able to make System.Disk run last night on an 800k /ram5, by
>>using Copy II Plus and the Copy Whole Disk function.
>I hate to sound silly, but why do you want to do this?

	Someone would want to do this because then you can boot from 
the RamDisk (by setting Ramdisk the boot "slot" from the Control Panel).
This way it's REALLY fast booting into the System.

	But as I've said [and other people have, I'm just the most vocal
about it because it's so darn weird], it won't work for me! It hasn't
worked since System 5.0 came out.. It works with 4.0 and ProDOS 16,
just doesn't work with 5.0... VERY strange in my opinion.

	It gives me an Error $0028, Error Reading Boot Disk Name
[the phrase is something like that].

	It admittedly worked for me -once- after I got a new copy of the System
Disk but then wouldn't work again, even though my virgin copy of the System
was write protected and never altered the whole time! I've verified that
my RAM is fine too.  Just seems like some weird kind of a bug.

	As I said other people posted about the problem too.. But could
someone out there try copying System Disk 5.0 (or 5.02) to an 800K ramdisk
with DigiCopy and see what it does for you? Then mail me about it or post i
please...
-- 
        /  Apple II(GS) Forever!     unknown@ucscb.ucsc.edu  \
        \    Computer engineering student seeking a job.     /