text
stringlengths
0
99.6k
3) ARC
Creating an Archive.
arc/c <[d:]arcfile[.arc]> <[s:]pattern> [[s:]pattern]]
arc/cx <[d:]arcfile[.arc]> <[s:]pattern> [[s:]pattern]]
Creates an archive on drive d: named "arcfile.arc". As
many as eight patterns may be given. The possible
values for x are:
n - no compression; store only
p - pack only
s - squeeze only
q - squash only
c - crunch only (two passes)
1 - crunch only (one pass)
If you choose option x=1 then part of the information
that ARC needs to unarchive the file must be stored at
the end of the archive entry rather than the beginning.
In particular, this is the files original length and
the checksum.
Unfortunately, ARC needs to know a relative file's
length when it is at the start of the archive entry so
that disk space can be properly allocated. Therefore
ARC will not allow the single pass crunch option for
relative files. If you do select x=1 when archiving a
group of files, any relative files encountered will be
processed as if you had chosen x=c.
ARC VERSION 2.20 PAGE - 20
Some examples:
arc/c a:sq b:sq.* b:usq.*
This example creates an archive named "sq.arc" on
drive a: which includes all files from drive b: whose
names begin with "sq." or "usq."
arc/cs a:test.arc f:*
Archives all files from drive 10,1 to "test.arc" on
drive 8,0 and squeezes all entries.
arc/c seq b:*=s
Archives all sequential files on drive b: to
"seq.arc" on the default drive.
Previous versions of ARC would allow you to encrypt an
archive by specifying a password when creating an archive.
Unfortunately, this creates a number of problems when
crunching files and had to be eliminated. Besides, we never
used it anyway. Did anybody else?
ARC VERSION 2.20 PAGE - 21
Appending to an Existing Archive.
arc/a[x] <[d:]arcfile[.arc]> <[s:]pattern> [[s:]pattern]]
This command is exactly the same as the create
archive command, and all of the above examples apply.
The only difference is that the archive file must
exist, and the new entries are appended to it.
If the archive does not exist, a file not found
message is issued and the program aborts.
Sometimes the number of blocks displayed on a
directory listing does not agree with ARC after an
append. This is a bug in Commodore DOS, and should be
harmless. Oddly enough, if you try to fix this by
validating the disk, you will be wasting your time
since the directory block count will not be affected.
Since ARC can handle any archive created by lower
versions of ARC, it is ok to append to a version 1
archive.
You should exercise some caution when appending to
archives. Every archive must be an integer multiple of