Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!pasteur!ucbvax!TCGOULD.TN.CORNELL.EDU!halp
From: halp@TCGOULD.TN.CORNELL.EDU ("Bruce P. Halpern")
Newsgroups: comp.sys.apple
Subject: Re:  AppleWorks and Unidisk Query
Message-ID: <8805051219.AA28654@tcgould.TN.CORNELL.EDU>
Date: 5 May 88 12:19:28 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 29

A Unidisk 3.5 on a //c works very nicely.  If you plan to use unenhanced 
AppleWorks 2.0, you certainly will have room for quite a few data files. If
you plan to use the AppleWorks only on //c (or other machines with Apple
type memory cards, you can make a little extra room by removing, from the 
**COPY** of the original software, SEG.RM (needed only on //gs) and 
SEG.00 (needed only on native //e or //e with non-Apple type memory
expansion [such as Applied Engineering].

If you have a //c with the needed ROMS to run a Unidisk 3.5, you may also
have a motherboard that allows memory expansion. If so, bringing up your 
memory to about 400K will allow AppleWorks 2.0 to automatically load all of 
itself (except the printer module) into memory, and give you a desktop of 
about 250-300K.

When/if you decide to enhance your AppleWorks, the full (present) set of 
Beagle Bros. enhancements (the Timeout series [wonderful]) plus a calendar
file (and AppleWorks, of course, will largely fill a 800K disk. At this point, having 
enough memory to hold AppleWorks will allow 800K data disks in a single 
Unidisk 3.5 drive, with the system disk needed only for printing and access 
to Timeout modules.

****DISCLAMER: My comments, etc., are my own shakey opinions ********



  |  Bruce P. Halpern  Psychology & Neurobiology & Behavior Cornell Ithaca    |
  |  INTERNET:halp@tcgould.tn.cornell.edu  BITNET:D57J@CORNELLA  D57J@CRNLVAX5|
  |  UUCP:{vax135,rochester,decvax}!cornell!batcomputer!halp                  |
  |  PHONE: 607-255-6433    Uris Hall, Cornell U., Ithaca, NY 14853-7601      |