Path: utzoo!attcan!uunet!wuarchive!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!pro-generic.cts.com!sysop
From: sysop@pro-generic.cts.com (Matthew Montano)
Newsgroups: comp.sys.apple
Subject: Re: Need help with ORCA/C editor
Message-ID: <8910161218.AA11997@trout.nosc.mil>
Date: 15 Oct 89 19:39:45 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 20

Network Comment: to #6191 by att!cbnews!jmb@ucbvax.berkeley.edu


  If you are looking on your original ORCA/C disks, check the release.notes
file on your disk, I believe they moved it to another disk just before release
for more room.

  It should be all loaded on an HD anyways, right?

  If not you should consider building a dedicated C compiler disk. Where you
have taken out all the prizm stuff, the help files and utilities your never
likely to use. Then change the login file to make your ram disk a prefix for
temporary storage, and then keep your own source files on the ram disk.
Compile them to ram disk, copy them off the ram disk before running, but work
from the ram disk.. it makes things SO much faster.


UUCP: crash!pro-generic!sysop
ARPA: crash!pro-generic!sysop@nosc.mil
INET: sysop@pro-generic.cts.com