Xref: utzoo comp.unix.wizards:25713 comp.unix.programmer:1877
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!dsac.dla.mil!dsacg3.dsac.dla.mil!desc.dla.mil!wright!desire.wright.edu!uoft02.utoledo.edu!malgudi!caen!news.cs.indiana.edu!rutgers!cmcl2!pluto!cat
From: cat@pluto.dss.com (Iain Wacey)
Newsgroups: comp.unix.wizards,comp.unix.programmer
Subject: ptem's limitations
Keywords: ptem
Message-ID: <1991May20.190145.3609@uoft02.utoledo.edu>
Date: 21 May 91 00:01:45 GMT
Lines: 17


 I have been using ptem and ldterm to provide a terminal like
Message-ID: <4333@pluto.dss.com>
Date: 20 May 91 20:42:56 GMT
Followup-To: comp.unix.wizards
Organization: Datability Software Systems, New York, NY
Lines: 9

of some limitation of ptem. It does not handle flow control
leaving it to any lower module or driver to handle STOPI
messages from ldterm. Ptem also doesn't deal with parity. Has
anyone else run into these problems? If so how did you get around
them? Has anyone written a replacement for ptem that handles these
things. In search of a real psuedo physical terminal.

Iain Wacey
cat@pluto.dss.com