This is part 1 of a 2 part posting of ARXX. I wrote ARXX because my
version of AR68 was unusable to make own object libraries for use with
LINK68. AR68 could list the contents of a library and extract modules
from the library, but replacing and adding new modules did not work
correctly (e.g. all module names were converted to upper case when adding
to the library, while extracting forced names to lower case -> impossible
to extract modules you added yourself). Below you will find ARXX.DOC and
an example of the output of the -tv option (list contents).

Part 2 will consist of the uuencoded ARXX.ARC containing the sourcefiles,
the program and ARXX.DOC. So if you can use it you only need part 2.

Some things I found out while writing and testting ARXX:
- stderr in ALCYON C (=Toolkit C compiler) uses GEMDOS handle 1, as does
  stdout. So redirecting stdout in Micro C-Shell redirects both stdout
  and stderr.
- You can prevent redirection for the standard GEMDOS handles by using
  negative handles (word size). So writing to handle -1 is what I use
  to write error messages to the screen.
- Detecting if GEMDOS handle 1 is redirected can be done by using

  the GEMDOS FSeek function (trap #1, function $42). When asking for
  the current position FSeek always returns 0 when handle 1 is used
  for the screen. Otherwise it returns a number greater than 0.

                                       