Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!alberta!sask!skatter!kuo From: kuo@skatter.UUCP Newsgroups: comp.sys.ibm.pc Subject: Re: Recent postings in comp.binaries.ibm.pc Message-ID: <331@skatter.UUCP> Date: Fri, 10-Jul-87 19:11:55 EDT Article-I.D.: skatter.331 Posted: Fri Jul 10 19:11:55 1987 Date-Received: Sun, 12-Jul-87 10:34:13 EDT References: <327@skatter.UUCP> Organization: Accelerator Lab, Saskatoon, Sask. Lines: 26 Keywords: binaries, bad, PKXARC (v3.4) Summary: Trouble fixed, HACK'ing! In article <327@skatter.UUCP>, kuo@skatter.UUCP (Dr. Peter Kuo) writes: > I am having trouble unARCing the two recent postings in comp.binaries.ibm.pc: > HACK36EX.ARC and RHM.ARC. PKXARC (v3.4) complain that they are not valid > archives. I have no trouble unARCing previous postings, such as CGPLT.ARC > and even the new version of PK{X}ARC. So I am suspecting the recent postings > could have been corrupted somewhere along the line. Can someone please > confirm this one way or another? > > What got me suspicious was that Part 3/8 of HACK, the posting says it has > 750 lines, but after I deleted all the headers and trailers, I got 751 lines! > The last line looked like this: "MZ\ ". I really don't like the > looks of it! (NEVER saw a uuencoded line with only two bytes on the line; > ignoring the starting byte). > I thank all those who responded to my message above. Indeed Part 3 of HACK was bad when it arrived at sask here. Someone (thanks again, Beverly!) send me the last few lines in Part 3, and upon comparison I found that the 751st line came out from no where, and a few bytes were lost from the "real" last line. The lost bytes were not at the end (ie truncated trailing blanks), they were something WITHIN the line! Now we have HACK 3.6 up and running and are all happy HACK'ing away! ... Peter/