init from sf.net libxad, without some testfiles

libxad/AUTHORS

@@ -0,0 +1,31 @@
+This document gives credit to all the people involved in development
+of the XAD library system. If your or an other name is missing, contact the
+developers, so the file may be updated.
+
+Current Maintainer:
+
+  Dirk St�cker <[email protected]>
+
+Developers of current version:
+
+  Andrew Bell <[email protected]> (unix port)
+  Stuart Caie <[email protected]> (unix port)
+  Dirk St�cker <[email protected]> (design)
+  Sigbj�rn Skj�ret <[email protected]> (MorphOS version)
+
+Developers of unfree version (1998 to 2004, version 1.0 to 12.1):
+
+  Dirk St�cker <[email protected]> (main author)
+  Ronald van Dijk <[email protected]> (conversion tables, external clients)
+  Stuart Caie <[email protected]> (design help, external clients)
+  Andrew Bell (Voodoo-X GUI, external clients)
+  AmiS (external TR-DOS client)
+  Mikolaj Calusinski (design help, external RAR client)
+  Mariusz Danilewicz (polish translation)
+  Herv� Dupont (french translation)
+  Stefan Haubenthal (external Cpio client)
+  Michal Jarzynski (external oe4 client)
+  Matthew T. Russotto (CAB Quantum and StuffIt 15 algorithms source)
+  Sigbj�rn Skj�ret (external idPAK client)
+  Daniel Sternik (polish proofreader)
+  David Tritscher (LZX code)

libxad/COPYING

@@ -0,0 +1,13 @@
+This library is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2 of the License, or
+(at your option) any later version.
+
+Parts of the library can be redistributed and/or modified under the
+terms of the GNU Lesser General Public License as published by the
+Free Software Foundation; either version 2.1 of the License, or
+(at your option) any later version as well. See the source code files
+to find out if LGPL can be used or not.
+
+The GNU Lesser General Public License is included in file lgpl.txt.
+The GNU General Public License is in file gpl.txt.

libxad/amiga/X-Systems.TXT

@@ -0,0 +1,114 @@
+                           *****************
+                           *               *
+                           * The X-Systems *
+                           *               *
+                           *****************
+
+Now there are 6 library systems starting with an X in their name and 3 of
+them end in master.library. I think a bit of information is needed to
+know what they are. Note that these systems are shared libraries and thus
+useless without an application program using them. XPK, XFD and XAD have
+some easy application programs included in the distribution, but most
+important are all the other applications using them.
+
+xprxxxxx.library: (XPR = eXternal PRotocol)
+
+First of all there was the idea to implement program independent transfer
+protocols to make different transfer system support a lot better than it
+was this time. The xprxxxxx.libraries were invented. Most of the protocols
+are wellknown from mailbox times (Z-Modem, X-Modem, Y-Modem, Kermit, ...).
+Before the XPR libraries existed, the programs supported the protocols
+directly and most time only some of them and always missing the one you
+needed yourself. XPR made an end to that. You only copy the specific
+library to LIBS: and select it in the terminal program (like Term) and
+know you can use it. The libraries can be developed by different authors
+and totally independent from any terminal program.
+To be able to do so, all the libraries use a standard interface, which
+does not differ in  all the libraries. So the terminal programm does
+not need to do anything special, but only call the requiered function
+and the XPR library is doing its work.
+
+xemxxxxx.library: (XEM = eXternal EMulation)
+
+Like the XPR libraries, these libraries can be developed totally independant
+from terminal programs. They present a set of different terminal emulations
+(VT100, VT340, RIP, ...) and are designed a lot like the XPR libraries.
+
+xpkxxxx.library: (XPK = eXternal PacKer)
+
+This system was developed by Urban Dominik M�ller and some other persons
+and is continued by Dirk St�cker. Its main concept is taken from XPR, but it
+is used totally different. It is no longer used with terminal programs, but
+with any program. XPK is a system to pack and unpack data in a standardized
+data format XPKF. XPK consists of one xpkmaster.library, which does all
+the work you need to do to support packing (data handling, file format
+creation, parameter checking, ...) and a lot of sub libraries, which are
+equal to the XPR libraries. They have an standardized interface and are
+stored in LIBS:compressors directory. Normally you call the master library
+when you need to pack or unpack something. You also may use the sub
+libraries directly (like for XPR). The sub libraries all implement
+different packing or encrypting algorithms. In an application program the
+user only needs to select one of the libraries and the program now uses
+that algorithm.
+This allows applications to use up-to-date compression/encryption without
+spending a lot of work implementing these in the program itself. And the
+user is able to select parameters like "low packrate - high speed" or "best
+rate - lower speed" or any other combination he likes.
+
+xfdmaster.library: (XFD = eXternal File Decruncher)
+
+Another system developed by Georg H�rmann. This system allows to decrunch
+any type of crunched Amiga data (executable programs, data files). Unlike
+XPK, which only decrunches its own types, XFD decrunches data of all the
+other packer system developed over the years. XFD cannot crunch data,
+only decrunch. Like XPK it consists of one xfdmaster.library doing all the
+work. Unlike XPK the slaves can no longer be accessed directly, as they are
+no longer libraries. Each slave is either internally in the library or
+an extern file in LIBS:xfd. The extern slaves are normal Amiga executable
+files with a standard interface allowing xfdmaster.library to call their
+functions. These extern files can be developed independend from
+xfdmaster.library by different authors, like it is for the other 4 systems.
+Like for XPK, Dirk St�cker is now the author of the XFD system at least
+until Georg wants back the authorship.
+
+xadmaster.library: (XAD = eXternal Archive Decruncher)
+
+XAD was developed by Dirk St�cker. It is much like XFD system, but it
+dearchives file and disk archives instead of files. The xadmaster.library
+gives application programs a standard interface to extract files from file
+archives (lha, lzx, ...) or unarchive disk archives (dms, zoom, ...). Like
+XFD, the XAD system has library internal clients and extern clients stored
+in LIBS:xad directory. These extern clients are Amiga executable files
+like for XFD, but they have a totally different interface.
+
+xvs.library (XVS = eXternal Virus Scanner)
+
+This library is unlike all the others, as it is not possible to write any
+extra slaves/clients for the library, all virus-scanning routines are
+stored in the library itself and are even protected so they can't be
+altered. If they could, viruses would no doubt alter them. This library is
+the work of Georg H�rmann, who seperated the virus scanning functionality
+out of his VirusZ tool, and made a library that any application could call.
+This way, Amiga users can enjoy many more interfaces to virus-scanning
+functionality -- for example, in web and FTP downloading tools, archive
+extractors, as well as the usual graphical virus scanning applications.
+
+Additional words:
+As XPK and XFD both decrunch data, they are linked a bit. XFD always
+decrunches XPKF files by calling xpkmaster.library. XPK itself asks
+xfdmaster.library, wheather a certain format is known to it and if it is,
+XPK calls XFD to decrunch it. In this way XPK can decrunch some of the
+non-XPK file types using XFD. As XPK needs to know which size the file
+will have after decrunching, before the file is really decrunched, not
+all of XFD's slaves are supported by XPK. Only slaves for crunched data
+files which return uncrunched size on recognition are supported.
+
+Also XAD clients may call XPK or XFD system to decrunch their data.
+
+"Clients" (XAD), "Slaves" (XFD) and "Sub Libraries" (XPK) are different
+words for the same thing: The parts really doing the work.
+
+Dirk St�cker <[email protected]>
+Stuart Caie <[email protected]>
+
+20th November 2002

libxad/amiga/docs/english/exe2arc.doc

@@ -0,0 +1,60 @@
+NAME
+	exe2arc 1.5
+
+SYNOPSIS
+	exe2arc FROM/A,TO,TYPE/K
+
+DESCRIPTION
+	This program extracts the archive data from self extracting
+	archive files. You can afterwards use that archive with xad
+	or any other unarchiver. It equals the executable file, except
+	the exe header is stripped and offsets are corrected. It works
+	with all executable formats, which contain valid archive data.
+
+	Currently Zip, Rar, LhA, Cabinet, Arj and Ace are supported.
+	Always test the extracted archive, as it may be damaged.
+
+	FROM specifies the exe file archive that should be handled.
+
+	TO is the name of destination archive file. This is automatically
+	created, if not given. It also maybe the name of a directory, where
+	the file should be stored.
+
+	TYPE allows to specify the archive type (if known). You always
+	need to specify the TYPE keyword. The type may be specified using
+	the archive format extension or the type name displayed, when
+	archives are found.
+
+EXAMPLE
+	Shell> exe2arc pk204g.exe
+
+HISTORY
+	exe2arc 1.5
+	- fixed Enforcer hit
+
+	exe2arc 1.4
+	- now supports destination directories
+
+	exe2arc 1.3
+	- added TYPE keyword
+
+	exe2arc 1.2
+	- added Rar, LhA, Cabinet, Arj, Ace
+	- renamed tool
+
+	exe2zip 1.1
+	- now supports somewhat faulty exe files.
+
+	exe2zip 1.0
+	- First public release.
+
+COPYRIGHT
+	exe2arc is freely distributable for noncommercial use.
+
+AUTHOR
+	Dirk St�cker
+	Geschwister-Scholl-Stra�e 10
+	01877 Bischofswerda
+	GERMANY
+
+	Dirk Stoecker <[email protected]>

libxad/amiga/docs/english/xad2lha.doc

@@ -0,0 +1,84 @@
+NAME
+	xad2lha 1.3
+
+SYNOPSIS
+	xad2lha FROM/A,TO,PASSWORD/K,NE=NOEXTERN/S,QUIET/S,HEADER0/S
+
+DESCRIPTION
+	xad2lha extracts data from other archives and stores it in an
+	lha archive.
+	This program transfers all additionally information, like UNIX
+	owner stuff and protection bits.
+
+	FROM specifies the file archive that should be handled.
+
+	TO is the name of destination lha file. When not specified, the
+	source name extensions are stripped and .lha is added.
+
+	PASSWORD can be used to supply a password for unarchiving of
+	encrypted archives. This argument requires the keyword PASSWORD.
+
+	NOEXTERN prohibits the use of external clients for
+	recognition purposes.
+
+	HEADER0 uses header level 0. This header is older and does not
+	have special information.
+
+	The QUIET option makes the program really silent.
+
+DATA FORMAT
+	This tool normally creates files using header level 2.
+	Uncompressable files are stored using -lh0-, all the others use
+	-lh5- identifier. Directories use -lhd- identifier. The OS-ID is
+	set to 'A', which is used by other Amiga lha programs.
+	Following header information is included:
+
+	0x00 CRC		  always
+	0x01 file name		  except it is an directory
+	0x02 directory name	  except the file name has no directory part
+	0x50 UNIX protection bits if there are group or other bits
+	0x51 UNIX owner ID's	  only if user or group ID is not zero
+	0x52 UNIX group name	  if exists
+	0x53 UNIX user name	  if exists
+	0x54 UNIX date		  always, except if source archive had no
+				  date (no UTC correction, but local time)
+	0x71 comment		  if exists
+
+	When HEADER0 ist used, then directories are stored using -lh0- and
+	a slash at name end. Comments are included in file name field and
+	are seperated by a zero byte. Additionally header information is not
+	supported with that format.
+
+	Standard protection bits and time stamp are always included in both
+	headers.
+
+EXAMPLES
+	Shell> xad2lha archive.tar
+		Make an lha archive from tar archive.
+
+	Shell> xad2lha archive.lha archive2.lha
+		Recreate the lha archive.
+
+HISTORY
+	xad2lha 1.3
+	- Added support for disk images.
+
+	xad2lha 1.2
+	- Fixed compression bug causing illegal compressed files.
+
+	xad2lha 1.1
+	- Now also parses and converts disk archives.
+
+	xad2lha 1.0
+	- First public release.
+
+COPYRIGHT
+	xad2lha is freely distributable for noncommercial use.
+
+AUTHOR
+	Dirk St�cker
+	Geschwister-Scholl-Stra�e 10
+	01877 Bischofswerda
+	GERMANY
+
+	Dirk Stoecker <[email protected]>

libxad/amiga/docs/english/xadLibInfo.doc

@@ -0,0 +1,61 @@
+NAME
+	xadLibInfo 1.6
+
+SYNOPSIS
+	xadLibInfo
+
+DESCRIPTION
+	xadLibInfo displays the name, flags, ID, required xadmaster version,
+	version and revision of all clients in xadmaster.library.
+
+	Meaning of the abbrevations:
+	ID  - internal client ID
+	MV  - required master version
+        VER - client version and revision
+
+	The Flags field gives information about the different flags set
+	in the client.
+
+EXAMPLE
+	Shell> xadLibInfo
+
+	Clients of xadmaster.library 3.0
+
+	Name              |  ID  | MV |  VER  | Flags
+	--------/.../-----+------+----+-------+------------------------------
+	xMash             | 1000 |  3 |  1.4  | DISK,FREE(DI,TI,TEXT)
+	[...]
+
+HISTORY
+	xadLibInfo 1.6
+	- added FREE(STR) flag
+
+	xadLibInfo 1.5
+	- added lots of new flags
+
+	xadLibInfo 1.4
+	- added NOCHECKSIZE flag
+
+	xadLibInfo 1.3
+	- added FILESYSTEM flag (named FILESYS)
+
+	xadLibInfo 1.2
+	- added new FREE(SI) flag, shortened DISKARCHIVER and FILEARCHIVER
+	  and reduced output width
+
+	xadLibInfo 1.1
+	- added new FREE flags
+
+	xadLibInfo 1.0
+	- First public release.
+
+COPYRIGHT
+	xadLibInfo is freely distributable for noncommercial use.
+
+AUTHOR
+	Dirk St�cker
+	Geschwister-Scholl-Stra�e 10
+	01877 Bischofswerda
+	GERMANY
+
+	Dirk Stoecker <[email protected]>