Path: utzoo!attcan!uunet!husc6!mailrus!ames!oliveb!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga
Subject: Re: Modem/VT100 problem
Keywords: vt100 Avatec modem help
Message-ID: <57252@sun.uucp>
Date: 20 Jun 88 20:24:27 GMT
References: <6512@jhunix.HCF.JHU.EDU> <1108@damask.UUCP>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 30

In article <6512@jhunix.HCF.JHU.EDU>, (Daniel Jay Barrett) writes:
> Ever since I've been using my new Avatec 2400-baud modem and VT100 v2.8,
> I've been having problems when I exit VT100.
> Shortly after I click the close gadget and turn off my modem, the
> system either locks up, 

In article <1108@damask.UUCP> hardie@damask.UUCP (Peter Hardie ) writes:
> I have a Hayes smartmodem 1200 and have had this problem for a long time
> now with several other modem/terminal programs. 

Actually, I suspect the problem is in the serial.device. There are a couple
of bugs that seem to bite people and I have hypothesized some ideas although
Bryce will have to be the definitive source of information on these.

A) The serial.device really dislikes getting junk for input, particularly
when it has been closed. For Daniel I would suggest you *not* switch off
your modem. That will probably keep the system from crashing. 

B) Changing the serial.device parameters when it is receiving a character
is a known bug that Matt has a great test case for (the original DTerm).

One hypothesis is that there is a race condition when the serial device is
being unloaded (due to space constraints) and it gets unloaded before it's
interrupt server gets removed from the IntServer chain. Character comes in,
it calls the now unloaded possibly corrupt serial device, poof crash-ola.


--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.