Xref: utzoo comp.binaries.ibm.pc.d:353 comp.sys.ibm.pc:16157
Path: utzoo!attcan!uunet!unisoft!hoptoad!dasys1!wfp
From: wfp@dasys1.UUCP (William Phillips)
Newsgroups: comp.binaries.ibm.pc.d,comp.sys.ibm.pc
Subject: Re: Source code newsgroup for MS-DOS
Keywords: ARC CRC error-checking news
Message-ID: <4802@dasys1.UUCP>
Date: 4 Jun 88 06:15:15 GMT
References: <7985@brl-smoke.ARPA> <2277@rpp386.UUCP> <1785@van-bc.UUCP>
Reply-To: wfp@dasys1.UUCP (William Phillips)
Organization: This Techie For Hire (tm)
Lines: 22

In article <1785@van-bc.UUCP> skl@van-bc.UUCP (Samuel Lam) writes:

>With the current scheme, if an ARC file got hit during transmission, there
>is no easy way to detect this before you start unARCing, since none of those
>CRC's are of any use until you have got the *unARCed* content of the ARCed
>files.

Not true.  You have the very useful option with both arc and pkxarc to
_test_ your .arc file before you ever unarc it.  This is exactly what
I do with every .arc file I download.

pkxarc -t foo.arc
or
arc /t foo.arc  (I think this is the syntax -- I don't use arc any more)

It's fast, it's easy, and it works.


-- 
William Phillips                 {allegra,philabs,cmcl2}!phri\
Big Electric Cat Public Unix           {bellcore,cmcl2}!cucard!dasys1!wfp
New York, NY, USA                !!! JUST SAY "NO" TO OS/2 !!!