Path: utzoo!attcan!uunet!husc6!uwvax!oddjob!ncar!ames!pasteur!ucbvax!UCONNVM.BITNET!SEWALL From: SEWALL@UCONNVM.BITNET (Murph Sewall) Newsgroups: comp.sys.apple Subject: re: "multitasking" Message-ID: <8806200247.aa09779@SMOKE.BRL.ARPA> Date: 20 Jun 88 06:14:57 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 26 >Well, why does anyone want multi-tasking in the first place? I mean >*REALLY*? Think about it... > >Ok, sometimes I want to have my //e call up the vax and download a file or >something silly like that. Then I would have two processes, one doing the >download, the other at my disposal. Or maybe I want to compute a >mandlebrot, and also hack at same time. Again, two processes. Gee, I discovered the solution to that a couple of years ago. It's called a //c! You just buy one (from 47th Computer - it'll cost you MUCH less that the DRAM and hassle multi-processing on a IIgs would involve) and plop it down on the desk next to the //e or IIgs. You let the //c download files whilst "creating" on the IIgs, or let the faster IIgs calcluate the mandelbrot while you play Zaxxon on the //c. The real beauty of a //c as a "multiprocessor" is if one program crashes, the other isn't hung. Even a SEVERE hardware crash necessitating a visit to the Apple-doctor doesn't wipe out both systems (lightning bolts excepted). --------------------- Disclaimer: The "look and feel" of this message is exclusively MINE! (subject to change without notice; void where prohibited) ARPA: sewall%uconnvm.bitnet@mitvma.mit.edu Murphy A. Sewall BITNET: SEWALL@UCONNVM School of Business Admin. UUCP: ...ihnp4!psuvax1!UCONNVM.BITNET!SEWALL University of Connecticut