Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!rutgers!daemon
From: prindle@NADC.ARPA
Newsgroups: comp.sys.cbm
Subject: 1581 drive with C-Power 64
Message-ID: <5366@rutgers.rutgers.edu>
Date: Thu, 29-Oct-87 23:41:24 EST
Article-I.D.: rutgers.5366
Posted: Thu Oct 29 23:41:24 1987
Date-Received: Wed, 4-Nov-87 05:08:22 EST
Sender: daemon@rutgers.rutgers.edu
Lines: 20

From: prindle@nadc.arpa (Frank Prindle)

In addition to using the 1581 drive with C-Power 128 (i.e. putting the compiler,
tools, and libraries on the work disk with your own programs), I have also done
the same thing with C Power 64.  As mentioned by someone in a previous posting,
C Power 64 differs from C Power 128 in that it is *copy protected*.  Therefore,
you must figure out how to move that copy protection element onto the 1581
yourself; additionally, since the implementation of that copy protection
scheme uses the DOS job queue, and the prime locations for the job queue are
in different places for the 1581 drive (as documented in it's manual), you
also must modify the copy protection code to use the new job queue locations.
All of this copy protection relates only to the "COMPILER" program.  Once you
have overcome these hurdles, the advantages of this scheme are similar (but
not as great as) to C Power 128.  Compiler passes load 10-20% faster, library
searching is quite a bit faster, compilation itself is slightly faster,
no disk swapping, and room for about 130 files or about 600K of user programs
(whichever comes first) per disk.
Sincerely,
Frank Prindle
Prindle@NADC.arpa