Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!decwrl!decvax!ima!cfisun!lakart!dg
From: dg@lakart.UUCP (David Goodenough)
Newsgroups: comp.mail.uucp
Subject: "g" protocol musings
Message-ID: <569@lakart.UUCP>
Date: 12 Jun 89 14:39:54 GMT
Organization: Lakart Corporation, Newton, MA
Lines: 37

A couple of questions:

1. I have implemented a "g" protocol program on my PC at home (don't
ask why I didn't use UUPC - just look up pallio.uucp in the maps). I
have one problem with it - since I can't do parallel disk I/O and
serial I/O, I "shut down" serial I/O when going to the disk. Very
simply, I stop transmitting, and then wait for a second, buffering any
stuff that arrives for later consumption. I then go and read / write
the disk. I would have expected the transmission to start up again just
fine after the break (it's only 3 to 5 seconds, but for some reason the
UNIX end gets in a tangle, and it takes several retries to get
re-started. It always _DOES_ get going again, but it takes a while and
a few wrong packets. This is a timing issue, because on the last read,
I don't always get a full buffer (I read and write in 8K chunks), and
so it goes faster, and sometimes the protocol starts right up again.

Is there something funny in the timing out of uucico that I don't
know about.

..... And .....

2. The UNIX system I talk to responds with a

	"Ptg"

in the uucico startup handshake. Does anyone know anything about the
"t" protocol. As it is, my uucico (on the PC) is under 10K (about 20K
when you add the BSS), so I have all sorts of space to add another
protocol.

		Thanks in advance,
-- 
	dg@lakart.UUCP - David Goodenough		+---+
						IHS	| +-+-+
	....... !harvard!xait!lakart!dg			+-+-+ |
AKA:	dg%lakart.uucp@xait.xerox.com		  	  +---+