Path: utzoo!attcan!uunet!cs.utexas.edu!sdd.hp.com!ucsd!nosc!crash!simpact!jeh
From: jeh@dcs.simpact.com
Newsgroups: comp.mail.uucp
Subject: Re: Problems with DECUS UUCP and UUPC communications
Message-ID: <1299.265d4475@dcs.simpact.com>
Date: 25 May 90 21:43:01 GMT
References: <27@thehulk.dmc.com>
Organization: Simpact Associates, San Diego CA
Lines: 18

In article <27@thehulk.dmc.com>, munroe@thehulk.dmc.com
 (Dick Munroe, Doyle Munroe Consultants, Inc.) writes:
> All implementations of UUPC send [an extra null byte preceding each 
> DLE] during the initial g protocol handshake.  ...
> I plan to fix the uucico in DECUS UUCP but it was easier to fix
> the UUPC implementation ...

Your fix to UUPC will of course solve the problem.  In V1.2 of DECUS uucp, we
solve the problem on "our side" -- uucico ignores extra null bytes that occur
between elements of the initial handshake.  V1.2 will be on the Spring 90 SIG
tape, will be available as a separately orderably item in the DECUS Library,
and will no doubt be available via anon. ftp just as V1.1 is now, all within a
few weeks... we hope! 

	--- Jamie Hanrahan, Simpact Associates, San Diego CA
Chair, VMSnet [DECUS uucp] and Internals Working Groups, DECUS VAX Systems SIG 
Internet:  jeh@dcs.simpact.com, or if that fails, jeh@crash.cts.com
Uucp:  ...{crash,scubed,decwrl}!simpact!jeh