Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!tut.cis.ohio-state.edu!rutgers!mcdchg!falkor!heiby
From: heiby@falkor.UUCP (Ron Heiby)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Source code newsgroup for MS-DOS
Message-ID: <167@falkor.UUCP>
Date: 10 Jun 88 00:22:02 GMT
References: <1785@van-bc.UUCP> <4802@dasys1.UUCP> <1790@van-bc.UUCP>
Reply-To: heiby@mcdchg.UUCP (Ron Heiby)
Organization: Luck Dragons, Magic, & Friends
Lines: 21

Samuel Lam (skl@van-bc.UUCP) writes:
> Therefore, testing an archive before extracting does not provide any
> protection which extracting right away won't give.

Of course, with a version of arc on my Unix box, I can concatenate the
parts, uudecode it, and test the archive before I go to the trouble of
downloading the (possibly corrupt) arc file to my pc.  Often, I want
to extract the documentation files for printing on the laser printer,
but have no interest in extracting the whole works.

BTW, it peeves me that so many packages assume that my printer has
a certain set of attributes.  Most seem to think that all printers deal
with 66 line pages, even though the document may use only 60 lines per
page.  There are an extra six blank lines to skip over the fold.  Of
course, with a 63 line per page laser printer, this causes more problems
than it solves.  Better would be to use formfeeds.  Recently, some fancy
"swiss army knife" directory lister came over assuming that I had an
Epson printer.  That was a real thrill.  Oh, well.  Enough steam.
-- 
Ron Heiby, heiby@mcdchg.UUCP	Moderator: comp.newprod & comp.unix
"I believe in the Tooth Fairy."  "I believe in Santa Claus."
	"I believe in the future of the Space Program."