Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!yale!mintaka!dcw
From: dcw@lcs.mit.edu (David C. Whitney)
Newsgroups: comp.sys.apple2
Subject: Re: Copying System 5.0 to /ram5
Message-ID: <1990Aug31.123449.16156@mintaka.lcs.mit.edu>
Date: 31 Aug 90 12:34:49 GMT
References: <6432@darkstar.ucsc.edu>
Sender: daemon@mintaka.lcs.mit.edu (Lucifer Maleficius)
Organization: MIT Spoken Language Systems Group
Lines: 25

In article <6432@darkstar.ucsc.edu> unknown@ucscb.ucsc.edu (The Unknown User) writes:
>
>In response to Mike Aos:
>>I think the thing most of you are forgetting to do is format /RAM5. You're
>>prolly just copying the files there, and that doesn't work.  Think about it
>>for a sec...
>        But if I'm using DigiCopy GS why should I have to format /ram5??

Digicopy no doubt does not copy the boot blocks as they contain
disk-specific info (such as the name of the disk, number of blocks,
etc). When you engage the Ramdisk, it sets aside RAM and turns on a
driver. It also puts a directory on the "disk." It does not put boot
blocks on the "disk," however (perhaps it should). At any rate, the
RAMdisk is not bootable unless you explicitly format it.

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


--
Dave Whitney			| I wrote Z-Link and BinSCII. Send me bug
Computer Science MIT 1990	| reports. I need a job. Send me an offer.
dcw@goldilocks.lcs.mit.edu	| My opinions, you hear? MINE!
dcw@athena.mit.edu		| Are you sure you know what you're doing?