Xref: utzoo comp.sys.ibm.pc:13331 comp.binaries.ibm.pc:616
Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!ucdavis!deneb.ucdavis.edu!ccs002
From: ccs002@deneb.ucdavis.edu (0058;0000074017;300;9999;94;ccs)
Newsgroups: comp.sys.ibm.pc,comp.binaries.ibm.pc
Subject: Re: Standard format for ARCed files
Message-ID: <1474@ucdavis.ucdavis.edu>
Date: 18 Mar 88 00:53:12 GMT
References: <5439@swan.ulowell.edu> <551@sun.soe.clarkson.edu> <21480@teknowledge-vaxc.ARPA>
Sender: uucp@ucdavis.ucdavis.edu
Reply-To: DWHATCHER@ucdavis(David Hatcher)
Distribution: na
Organization: University of California, Davis
Lines: 24

>> Suggestion: Use PKARC with the /oct option to create ARC-compatible
>> archives.  Do not use MAKESFX.  Some arc programs will read self-extracting
>> archives, but some die on them.
>> 
>
>Who care whether the UN*X archive program can read them or not??? This is 
>COMP.BINARIES.IBM.PC, not COMP.UN*X, so whatever you pull off this 
>board is going to end up on a PC anyway. I vote for the self-extracting 

I care that the UNIX archive doesn't work, as I am sure many others
are.  I like to see what I am going to get (read the docs) before 
I bother downloading tons of arced files to a PC and un archiving them. 

How many people get the news ON PC's?  Why not make the arc compatible
with the machines that the news is recieved on?

Also, on the subject of moderation, I would like a 
comp.binaries.ibm.pc.discussion(whatever the syntax is) group, since
comp.sys.ibm.pc is (as stated by others) too busy to keep up with
without the binaries discussions.

	David Hatcher
Internet   DWHATCHER@ucdavis.edu or ccs002@deneb.ucdavis.edu
BITNET     DWHATCHER@ucdavis
UUCP       {ucbvax, lll-crg, sdcsvax}!ucdavis!DWHATCHER or