Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Probably SERIAL.DEVICE bug.
Message-ID: <8704300002.AA28012@cory.Berkeley.EDU>
Date: Wed, 29-Apr-87 20:02:31 EDT
Article-I.D.: cory.8704300002.AA28012
Posted: Wed Apr 29 20:02:31 1987
Date-Received: Sat, 2-May-87 04:31:45 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 25


	I think I've found a bug in the serial.device ... You can crash your
Amiga by doing the following:

	-Set terminal program and modem @ 1200 baud
	-	Make sure it is NOT using the RAD_BOOGIE bit
	-Tell modem to send it's help screen (or test chars..) continuously.
	-While the modem is sendin, change the baud rate of the terminal
	 program (and thus serial.device) to 20000

	Your Amiga should freeze up.  Using RAD_BOOGIE seems to fix the
the problem.  This is a *real* bug because it would seem that changing the
the baud rate to anything, at any time when the serial.device isn't using
RAD_BOOGIE creates a window or something...  (20000 almost always causes
a crash.  1200->2400 does so every once in a while)

	I have no idea why RAD_BOOGIE seems to fix the problem... perhaps the
bug in the serial.device is associated with parity checking?????

******* People using DTERM should use the -f option to force DTERM to use
the RAD_BOOGIE bit.  DTERM is particulary sensitive since one usually programs
the state machine to automatically reset the baud rate to the highest his
modem can take on disconnect....

					-Matt