Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!aplcen!boingo.med.jhu.edu!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.sys.apple2
Subject: Re: Multitasking on a II
Message-ID: <14742@smoke.brl.mil>
Date: 14 Dec 90 21:26:24 GMT
References: <10548@ucrmath.ucr.edu> <14720@smoke.brl.mil> <90347.210619AABENSON@MTUS5.BITNET>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 20

In article <90347.210619AABENSON@MTUS5.BITNET> AABENSON@MTUS5.BITNET writes:
>I don't have any idea what kind of performance those terminals or whatever
>they were you mentioned have... (Oooo, bad sentence.)
>Could you fill us in?

You have to see them in action to appreciate them.  The fact that I
have a choice between SGI and Sun workstation human interfaces and
using an AT&T 630 (Blit descendant), usually choosing to use the
630 for most work, should offer some practical reference point.
At least the user interfaces are comparably convenient, and much
better than the Macintosh/Apple IIGS desktop, especially with
regard to concurrent processes.

>By the way, if you're using a IIgs, you can have a timer interrupt.

Yes, but since Apple's system software and toolbox don't expect to be
reentered while executing, you would have to mask interrupts while
using Apple's system software.  It is simpler to use nonpreemptive
task switching, which works just about as well for this kind of
multitasking environment.