Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!topaz!ll-xn!nike!ucbcad!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: net.micro.amiga
Subject: Re: CLI on a terminal.
Message-ID: <8609260632.AA26339@cory.Berkeley.EDU>
Date: Fri, 26-Sep-86 02:32:05 EDT
Article-I.D.: cory.8609260632.AA26339
Posted: Fri Sep 26 02:32:05 1986
Date-Received: Fri, 26-Sep-86 20:43:23 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: University of California at Berkeley
Lines: 24


	On this, does anyone know the criteria for NEWCLI accepting non-windows
for it's window argument?

	On the ser: device... your outa' luck.  The input buffering is a
'feature' of ser:... however, if NEWCLI accepts ser: as an argument, I see
no reason for it to screw up the input processing once it *does* get a
buffer full... try using LineFeeds (^j) instead of Returns (^m).  This is
why you usually attach a newcli to a CON: device and not a RAW: device.

	Also, the CON: device does input buffering and echo.

	The only solution I see to offering a CLI process on the serial
port or on a separate screen is for some brave soul to write a DOS device
driver for it.

-----
Question: Where does OpenWorkbench() go to get it's Screen parameters?
Specifically, the width and height (or am I wishing?)?

				-Matt

Q: What do you get when you hand OpenScreen() a width of 50?
A: FireWorks