Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!pro-novapple.cts.com!dales
From: dales@pro-novapple.cts.com (Dale Smith)
Newsgroups: comp.sys.apple2
Subject: ProTERM vs. Sys 5.0.3
Message-ID: <20207.netnews.info.apple@pro-novapple>
Date: 28 Dec 90 12:34:05 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 24

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!!
it's gone.  I will not tolerate anything in my system that adversely affect
ProTERM.  Anyway, when in ProTERM you're not running under GS/OS -- but I'm
sure you knew that.
 
I have found that Control Panel NDA, FontDA.Installer NDA, BRK Cursor INIT,
FasText INIT, GraphSpeed INIT, and Shadow INIT do not conflict with ProTERM. 
But some of the RAM5 drivers (RAMdrive.Manager CDA and /RAM5.Driver) do
conflict, anything that does timing (Twilight, screen blankers, etc.) and such
all play with interrupts in ways that ProTERM can't handle.  Even El Macro CDA
has a conflict - too bad it would be nice to have that to make up for the lack
of macros in the PT Editor, but I can't have it conflicting.
 
 Later ...
                                        - Dale -
proline: pro-novapple!dales 
uucp: crash!pro-novapple!dales 
arpa: crash!pro-novapple!dales@nosc.mil 
Internet: dales@pro-novapple.cts.com 
Northern Virginia Apple Users Group >pro-novapple< 703-671-0416/300-2400 baud