@database Arc64
$VER: Arc64_Guide 1.0
@node main "Arc64 documentation"


			   Arc64 V1.0
		  © 1996 by John 'Graham' Selck


			@{" Disclaimer    " link disclaimer}
			@{" About         " link about}
			@{" Requirements  " link requirements}
			@{" How to use    " link use}
			@{" Future        " link future}
			@{" Thanx to...   " link thanx}
			@{" Known Bugs    " link bugs}
			@{" History       " link history}
			@{" Contact       " link contact}
@endnode
@node disclaimer "Disclaimer"

Arc64 is written and copyright © 1996 by @{"John Selck" link contact}.

This program is freely distributable unless no changes
are made to the archive.

The author is not liable for any damaga/problems/loss of data
this program might directly or indirectly cause.

No parts of this program may be altered or resourced in any way.
@endnode
@node about "About Arc64"

Arc64 is a program designed to give you fast access to files
stored in c64 archives and 1541 disk images.

It was mainly written because 'UNd64' (© by Jess Sosnoski) didn't
support ZipCode archives.

However, Arc64 is meant as an alternative towards UNd64.

In comparision Arc64 has the following advantages:

- ZipCode support
- only 5400 bytes length
- less textoutput
- c64-like directory output
@endnode
@node requirements "Requirements"

Arc64 has been tested on the following configurations:

A500/512KB Chip/Kick1.3
A500/512KB Chip/512KB Fast/Kick2.04
A1200/2MB Chip/12MB Fast/Kick3.0 (68030/50MHz)
A1200/2MB Chip/16MB Fast/Kick3.1 (68060/50MHz)

Someone can test it with Kick1.1???
@endnode
@node use "How to use Arc64"

Arc64 is used via CLI.


Arc64 {command} {archive name}

Commands are: l = List directory/archived files
	      x = Extract files from archive
	      c = Convert ZipCode to D64 / D64 to ZipCode
	      a = Add directory to logfile

Example:

Arc64 x HD2:D64/vendetta.d64

...will extract all files from the d64 image into the actual
directory.

Arc64 c DH1:1!Demo_archive

...will convert the ZipCode archive "Demo_archive" into a plain
d64 archive. (This also works the other way round...)

I recommend that you use Arc64 from DirOpus or something similar.

If you wonder about the 'a' command, i have to say that i included
this one for myself.


Arc64 a CD0:Arc/xxx.d64

will basically do the same as

Arc64 l CD0:Arc/xxx.d64 >Arc64_Log

with the difference that the name of the actual archive will still
be written onto the screen.

(The logfile will be created on the actual path as 'Arc64_Log'.)


Errors which may appear while extracting:

Illegal Track/Sector:
- The most common one. Here a block of a file is linked to a block
  which is not existing in 1541 format.

Looped Filestructure:
- This one would force a real 1541 to reread the end of the file
  endlessly.

Corrupted EOF:
- This one only appears when the last block has no valid byte size.

Skipped...:
- This is no error. This means either that a file which was about to
  be extracted already existed or (only for Lynx archives) that the
  file length is 0.

Errors which may appear while listing:

Illegal Link
- Same as Illegal Track/Sector, only for the directory structure.

Looped Directory
- This happens quite often since people always used to play around
  with the directory.
@endnode
@node future "What is still left to do?"

- T64 support (I just started to work on it.)
- maybe P00 support (if somebody gives me a good reason...)
- memory optimizations
@endnode
@node thanx "Thanx to..."

Thanx to...

Geert Verschueren (Sorex/WOW)

... for that strange Lynx file with that 0 blocks USR files

Paul Gardner-Stephen (Highlander/FLT)

... for his encouragement giving me information on ZipCode
    (although i found out myself...)

Jess Sosnoski

... for UNd64
@endnode
@node bugs "Bugs"

Known Bugs/Problems

No bugs known yet...

For bugreports, press @{"this one" link contact}...
@endnode
@node history "History"

History

1.0 - Initial Release
@endnode
@node contact "How to contact the author"

Contact me at:

John Selck (Graham/Oxyron)
Suederholz 13
24885 Sieverstedt
Germany

E-Mail: j.selck@flensburg.netsurf.de

Or visit our homepage:

http//www.amigasupport.com/oxyron/
@endnode