Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!ames!mailrus!tut.cis.ohio-state.edu!osu-cis!att!mtune!rkh
From: rkh@mtune.ATT.COM (Robert Halloran)
Newsgroups: comp.dcom.modems
Subject: Re: 'g' & packet sizes & extensions
Message-ID: <7832@mtune.ATT.COM>
Date: 2 Sep 88 12:32:54 GMT
References: <7272@bigtex.uucp> <10500003@osiris.cso.uiuc.edu> <6452@chinet.UUCP>
Reply-To: rkh@mtune.UUCP (Robert Halloran)
Organization: AT&T ISL Middletown NJ USA
Lines: 23

In article <6452@chinet.UUCP> les@chinet.UUCP (Leslie Mikesell) writes:
>Has anyone tried using the "e" protocol that is built into the
>AT&T SysVr3.x uucp for use over networks over a trailblazer or
>other error-correcting modem? Results?

If your machine has trouble keeping up with a steady data stream, using
'e' might be a problem; uucico basically sends a packet with the final
file size then does write()'s.  The modems may deliver a clean line but 
if the receiver's port drops bytes you'll never know it until it's too late.

>Also, the attmail machine offers protocols "d" and "v".  Does
>anyone know what these are (and why the rest of use don't have them)?

'd' protocol is for use over the Datakit network; useful chiefly within
AT&T.  I'm unfamiliar with any 'v' protocol.

>Les Mikesell

						Bob Halloran
=========================================================================
UUCP: att!mtune!rkh				Internet: rkh@mtune.ATT.COM
Disclaimer: If you think AT&T would have ME as a spokesman, you're crazed.
Quote: "History is made at night.  Character is what you are in the Dark."
	- Dr. Lizardo/John Whorfin, "Buckaroo Banzai"