Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!rpi!dragon From: dragon@pawl.rpi.edu (Carl L. Norden) Newsgroups: comp.sys.apple2 Subject: Re: Copying System 5.0 to /ram5 Message-ID: Date: 4 Sep 90 04:12:00 GMT References: <1990Aug31.123449.16156@mintaka.lcs.mit.edu> <44454@apple.Apple.COM> <13181@netcom.UUCP> Sender: Dragon Organization: Rensselaer Polytechnic Institute, Troy NY Lines: 31 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? >And copying file-by-file with Copy II Plus did not work. There is a good reason for that. GSOS writes some files a slight bit different from Prodos 8 & 16. The only files that act 'dangerous' on these older systems seems to be 'FINDER.DATA' (& ROOT) and sometimes ICN files. If can avoid copying these, C2+ should have no trouble. >It would seem that /ram5 is automatically formatted on startup though; >that is the only plausible reason why my machine sits there for 3 seconds >before booting the 3.5 drive when it's at 800k, and 6 seconds when it's >at 1600k. Not really at startup. Anytime the Apple GS is turned on, it will. Hitting cntl-Reset, or Open apple Reset WON'T usually do it. (Though Open apple/ Closed Apple/Cntl-Reset Will. This totally destroys EVERYTHING in memory.) That delay is not just formatting the ramdisk. That takes less time than you can imagine. Think about how fast C2+ formats them...) Most of the time is spent by the Memory Manager while it allocates and verifies the memory. But that is really unimportant. P.S. Does anyone out there know how to use the Memory_Manager StartUp routine? Every time I use it, I keep getting an error of $201, which isn't possible!! (That's without using GSOS or ProDOS 16. I prefer ProDOS 8... Tis faster }:) -Dragon