Path: utzoo!attcan!uunet!convex!killer!ames!ll-xn!mit-eddie!mit-amt!mit-caf!ct From: ct@mit-caf.MIT.EDU (Curtis Tsai) Newsgroups: comp.sys.apple Subject: Suggestions for improving a //c system Message-ID: <1367@mit-caf.MIT.EDU> Date: 27 Sep 88 01:53:54 GMT Reply-To: ct@mit-caf.UUCP (Curtis Tsai) Distribution: na Organization: Microsystems Technology Laboratories, MIT Lines: 36 After reading this newsgroup for a while, I've noticed that many of you have made additions to your hardware, improving the performance of your system. I'm beginning to experience some limitations with my system and would like suggestions from those who have made enhancements. My system consists of a Apple //c with and external 5.25" drive and a 9" monochrome monitor. I primarily use the system as a terminal to a VAX, but I often edit files locally with AMACS and use Kermit for file transfers. Some of the additions that I'm interested are listed below, but feel free to add to the list. Information about performance, compatibility with software, and approximate cost would be most appreciated. 1. Hard disks--Since the 5.25" floppies only hold 140K, I get tired of searching through a countless number of disks for the files that I want. Or should I settle for a 3.5" Unidisk? 2. More RAM--I heard of putting more memory into the //c. Is the memory only useful as a large RAM disk? 3. Faster CPU--The Zip Chip and other replacements microprocessors sound wonderful. Do these chips have hardware and software compatibility problems that I should be aware of? 4. Clocks--I heard of the No Slot Clock, what exactly is it? It would be nice to have a non-volatile clock. Please email responses to me (if you can, otherwise post) and I will post a summary of responses. Thanks for reading, Curtis Tsai ARPA: ct@caf.mit.edu 18.0.62.232 Usenet: {ihnp4,harvard,seismo,rutgers}!mit-eddie!mit-caf!ct