Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!princeton!caip!think!nike!ucbcad!ucbvax!PAVEPAWS.BERKELEY.EDU!dillon
From: dillon@PAVEPAWS.BERKELEY.EDU (Matt Dillon)
Newsgroups: net.micro.amiga
Subject: Re: Help for weird error with serial port! (again)
Message-ID: <8606240044.AA09068@pavepaws>
Date: Mon, 23-Jun-86 20:44:00 EDT
Article-I.D.: pavepaws.8606240044.AA09068
Posted: Mon Jun 23 20:44:00 1986
Date-Received: Wed, 25-Jun-86 06:25:16 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: University of California at Berkeley
Lines: 18


>(Paul Higginbottom)
>Dear Mark:
>	It might be comforting for you to know that I have seen this behavior
>exhibited in other terminal programs I have seen.  I personally believe it's
>a bug in the serial.device; i.e., if it receives a NULL it kinda goes weird.
>	For example, turning on a Hayes Smartmodem 1200 seems to make it
>send a NULL to whatever it is connected to.  This will HANG a terminal program
>I use.

	I very much doubt it's a problem with the serial device... My modem
program has no trouble handling NULL's or any other character, neither does
the console device.  Additionaly, the protocols I use send NULL's all the
time so there is some basis to my reasoning.  (Still, if somebody can find
a bug with the serial.device, come forward!  I think, however, that it's
mainly improperly setup iorequest fields for SDCMD_SETPARAMS).

			-Matt