Xref: utzoo comp.unix.questions:29878 comp.dcom.modems:8991 comp.mail.uucp:6199
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!atha!aunro!aupair.cs.athabascau.ca!lyndon
From: lyndon@cs.athabascau.ca (Lyndon Nerenberg)
Newsgroups: comp.unix.questions,comp.dcom.modems,comp.mail.uucp
Subject: Re: Data range used by UUCICO?
Keywords: uucico
Message-ID: <1570@aupair.cs.athabascau.ca>
Date: 25 Mar 91 19:43:43 GMT
References: <1991Mar22.102630.1057@abekrd.co.uk>
Followup-To: comp.unix.questions
Organization: Athabasca University
Lines: 21

garyb@abekrd.co.uk (Gary Bartlett) writes:

>Can anyone tell me the range of data values sent by two communicating UUCICO
>processes.  Is it a full 8-bit range (0-255), a full 7-bit range (0-127) or
>a selected range of characters (eg 32-126)?

The g and t protocols use all eight bits. Presumably e and x do so as well,
although you shouldn't really use them ...

>I am most interested in finding out whether it uses the ASCII values for DC1/3.

The default (g) protocol does. This is a problem when running over X.25 
through a PAD, thus was born the f protocol. Essentially it encodes 
non-printable characters into printable ones, and it explicitly wants 
XON/XOFF flow control.

-- 
    Lyndon Nerenberg  VE6BBM / Computing Services / Athabasca University
           atha!cs.athabascau.ca!lyndon || lyndon@cs.athabascau.ca
                    Packet: ve6bbm@ve6bbm.ab.can.noam
      The only thing open about OSF is their mouth.  --Chuck Musciano