From: atbowler AT thinkage DOT on DOT ca (Alan Bowler)
Newsgroups: comp.os.msdos.djgpp,comp.os.cpm,alt.folklore.computers
Subject: Re: EOF char.  (Was C++ and RHIDE)
Date: 7 Jul 1998 17:13:35 GMT
Organization: Thinkage Ltd.
Lines: 18
Message-ID: <6ntkvv$4g3$1@nntp2.uunet.ca>
References: <359FFF58 DOT 71CE272E AT alcyone DOT com> <6nr1nh$6su$1 AT nntp2 DOT uunet DOT ca> <35A13F08 DOT 23950102 AT tnglwood DOT demon DOT co DOT uk>
NNTP-Posting-Host: 192.102.11.4
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

In article <35A13F08 DOT 23950102 AT tnglwood DOT demon DOT co DOT uk> Robert Billing <unclebob AT tnglwood DOT demon DOT co DOT uk> writes:
>Alan Bowler wrote:
>
>> to start the paper tape reader going, and the reader would stop
>> when it read the next X-OFF.  Alternately, the machine use a timeout
>> mechanism to decide when there was no more paper tape.
>
> The timeout on no tape I don't remember, the ASR33 simply had a plastic
>peg that popped up and killed the reader at end of tape. 

The timeout I referred to was not on the TTY.  It was used on
operating systems that had a "paper input mode".  The program issued
some sort of "read paper tape input" command, and the OS would put
the line in paper tape mode, it often came out of this mode based on
a timeout of some sort (tape ran out so no more characters arrived),
and then the program would process all the data received.
Often the OS looked after collecting the data to disk in some
raw fashion during paper tape mode.