fwvo@idca.tds.PHILIPS.nl (Ferdinand van Ommen) (10/14/88)
When attaching a dumb vt100-terminal to the Amiga-500's serial port I succeeded in starting up the communication.(I started newcli ser:). However, the following problem arose: If you want a command to be executed it seems to be necessary to fill the serial port's buffer (which has a minimum of 1/2kilobytes according to 'preferences') with newlines. I expect a new driver will be needed for full interactive use. Question is: is there a way to use the standard driver for the communication or will a quite differing one be needed. Second question then is: Does anyone have a better one, or do you know where to get it? I sincerely hope for a solution. regards -- -- Ferdinand van Ommen -- fwvo@idca.tds.philips.nl -- ..!mcvax!philapd!fwvo --
papa@pollux.usc.edu (Marco Papa) (10/15/88)
In article <585@ssp15.idca.tds.philips.nl> fwvo@idca.tds.PHILIPS.nl (Ferdinand van Ommen) writes: |When attaching a dumb vt100-terminal to the Amiga-500's serial port I |succeeded in starting up the communication.(I started newcli ser:). |However, the following problem arose: |If you want a command to be executed it seems to be necessary to fill |the serial port's buffer (which has a minimum of 1/2kilobytes according to |'preferences') with newlines. Get 1.3. It contains the AUX: device that will do the job you need. -- Marco Papa 'Doc' -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= uucp:...!pollux!papa BIX:papa ARPAnet:pollux!papa@oberon.usc.edu "There's Alpha, Beta, Gamma and Diga!" -- Leo Schwab [quoting Rick Unland] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
mlelstv@faui44.informatik.uni-erlangen.de (Michael van Elst ) (10/28/88)
In article <585@ssp15.idca.tds.philips.nl> fwvo@idca.tds.PHILIPS.nl (Ferdinand van Ommen) writes: >When attaching a dumb vt100-terminal to the Amiga-500's serial port I >succeeded in starting up the communication.(I started newcli ser:). >However, the following problem arose: >If you want a command to be executed it seems to be necessary to fill >the serial port's buffer (which has a minimum of 1/2kilobytes according to >'preferences') with newlines. That is not the serial buffer that must be filled but the CLI's command line buffer. >I expect a new driver will be needed for full interactive use. >Question is: is there a way to use the standard driver for the communication >or will a quite differing one be needed. The standard driver will pass READ requests to the serial.device. So if you READ a buffer of 512 bytes the request returns if the serial.device has copied 512 bytes into your buffer. You have to abort reading if a linefeed is found in the serial.device input stream. SER: doesn't use this. Also, serial.device doesn't know anything about command-line editing and BREAK signals (CTRL-C to CTRL-F). >Second question then is: Does anyone have a better one, or do you know where to >get it? Yes, there is a PD handler you can find on a Fishdisk. I don't know the number, but I tested it. Metacomco sells one with there Toolkit. WB 1.3 has a handler that can be used. I don't have this one but it should be available now. Michael van Elst E-mail: UUCP: ...uunet!unido!fauern!faui44!mlelstv