Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!mips!news.cs.indiana.edu!purdue!sage.cc.purdue.edu!ericm
From: ericm@sage.cc.purdue.edu (Eric Mulholland)
Newsgroups: comp.sys.apple2
Subject: Re: ProTERM vs. Sys 5.0.3
Message-ID: <5570@sage.cc.purdue.edu>
Date: 29 Dec 90 20:27:09 GMT
References: <20207.netnews.info.apple@pro-novapple>
Organization: Purdue University Computing Center
Lines: 21

In article <20207.netnews.info.apple@pro-novapple> dales@pro-novapple.cts.com (Dale Smith) writes:
>In-Reply-To: message from whitewolf@gnh-starport.cts.com
>
>Tae, I am puzzled as I run ProTERM out of System 5.0.3 ALL the time and never
>have character loss EXCEPT when some DA or INIT comes along that I try only to
>find that it's playing with the interrupts causing character loss -- BLAM!!
>
>all play with interrupts in ways that ProTERM can't handle.  Even El Macro CDA

ProTerm is one great program with one big flaw (in my option).  The authors
decided to POLL the serial port instead of using INTERUPTS to grab the data.
As you have pointed out, as long as there is no interupt driven routines
running in memory, ProTerm is able to recieve all the data.  With interupts
going off all over, this spreads the time between ProTerm's polling, causing
it to miss data.  If the authors of kermit can do it (thanks!) then why
can't ProTerm; it's obvious that they have the talent.
-- 
     ____
 Y_,_|[]|   Eric Mulholland
{|_|_|__|   ericm@sage.cc.purdue.edu
//oo--OO    ...!pur-ee!sage.cc!ericm