Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!sdd.hp.com!ucsd!ucbvax!agate!darkstar!ucscb.UCSC.EDU!unknown
From: unknown@ucscb.ucsc.edu (The Unknown User)
Newsgroups: comp.sys.apple2
Subject: Reply to an old post about System Disk on /ram5
Message-ID: <6282@darkstar.ucsc.edu>
Date: 23 Aug 90 22:17:26 GMT
Sender: usenet@darkstar.ucsc.edu
Organization: University of California, Santa Cruz; Open Access Computing
Lines: 28


	I was calling my UNIX account on a toll call when I read the message
originally, so I didn't reply then. (I'd call up my account, read 
comp.sys.apple2 into my scrollback as fast as possible, then read it offline).

	In the post that I'm referring to, someone tried to give a solution
to the widespread problem of copying System Disk 5.02 to /RAM5 and making it 
bootable.

	Their solution was to use ProDOS 8 based programs to copy the 
system to /ram5.. Well that is not a solution because it doesn't work.

	I have been using DigiCopy GS all along to (try) to copy 5.02
to an 800K /ram5.. I think the problem's been around since the original
System Disk 5.0... I'm virtually positive the problem didn't exist on
System 4.

	Oh yeah, specifically, when you try to boot, it says something
like "Error reading boot volume name, $0028"...

	And this has happened with not only the SYSTEM disk itself (a 
virgin copy), but it's happened when I've copied any other System 5
based programs... Other programs DO work when copied to the ramdisk..
For example, Task Force is much quicker when I copy disk1 to an 800K
ramdisk.. (no disk switching needed)
-- 
        /  Apple II(GS) Forever!     unknown@ucscb.ucsc.edu  \
        \    Computer engineering student seeking a job.     /