Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!usc!petunia!news
From: cambler@polyslo.CalPoly.EDU (++Christopher();)
Newsgroups: comp.mail.uucp
Subject: g protocol woes
Message-ID: <27c74309.3976@petunia.CalPoly.EDU>
Date: 24 Feb 91 04:37:29 GMT
Reply-To: cambler@polyslo.CalPoly.EDU (++Christopher();)
Organization: Fantasy, Incorporated: Reality None of Our Business.
Lines: 23



The machine I talk to seems to be gakking, but I think it's my fault.
problem:

g protocol packets have 5 header bytes:

type csuml csumh control xor

where xor is the number needed to make an xor of all 5 bytes == 0.

that is,

type ^ csuml ^ csumh ^ control ^ xor == 0

for some reason, all of a sudden, the xor byte is wrong consistantly on
the second data packet I get. Anyone ever seen this happen?

-- 
++Christopher(); --- cambler@polyslo.calpoly.edu --- chris@erotica.fubarsys.com
-----
FSUUCP Mailing list: fsuucp@polyslo.calpoly.edu
Requests to:         fsuucp-request@polyslo.calpoly.edu