Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!philmtl!philabs!ttidca!troeger From: troeger@ttidca.TTI.COM (Jeff Troeger) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: PAK v2.10, part 1 of 2 Message-ID: <7572@ttidca.TTI.COM> Date: 10 Nov 89 16:23:27 GMT References: <5292@cps3xx.UUCP> <7407@sdcsvax.UCSD.Edu> <5327@cps3xx.UUCP> <7569@ttidca.TTI.COM> Reply-To: troeger@ttidcb.tti.com (Jeff Troeger) Organization: Citicorp/TTI, Santa Monica Lines: 26 In article <7569@ttidca.TTI.COM> troeger@ttidcb.tti.com (Jeff Troeger) writes: >Well, I just downloaded PAK210.EXE, and tried to unpack it and PAK.EXE was >corrupted (BAD CRC) and would not unpack. This is one of the reasons why >comp.binaries.ibm.pc is moderated, and why I'm not taking PC binaries from any >where else from now on. At least from there I have a high degree of >confidence that what I'm downloading is actually going to work. Living 60+ >miles from work makes phone bill rather large and taking the time and expense >of downloading stuff that doesn't work makes for a rather poor use of that >time and expense. Looks like I'm gonna have to eat a little crow on this one. Turns out that I used the script I normally used when decoding binaries from the moderated group on PAK210, and because the cut marks were different, the script didn't work right and unfortunately uudecode didn't complain about it. Although I haven't downloaded it yet, there is a good indication that it will not have a problem. I'm still going to disregard binaries posted here though. It is too much a pain in the butt when there is no consistancy in how files are split and encoded. -- Jeff Troeger - Citicorp (+) TTI "Of all the things I've lost, 3100 Ocean Park Bl. I miss my mind the most" Santa Monica, Ca. 90405 (213) 450-9111 x3153 Path: {retix|philabs|csun|psivax}!ttidca!troeger or troeger@ttidca.tti.com