quickstart.txt file for BitBox v0.3.0

See also: README for general information

Requirements: zlib 1.1.3  (You must have the zlib.h header
and libz.a files from this version of zlib available to compile
and run BitBox 0.2.0.)

To compile: Switch to the directory with the BitBox files and
use the "make" command.  This will build a program "bitbox" in 
the current directory.

To test the program, enter the command:

./bitbox --box --input bitbox --output dummy --compress --verbose --numboxes 5

This should produce about a dozen lines of output telling you that
the file bitbox has been boxed into 5 files (dummy.bitbox plus 
dummy.bb001 through dummy.bb004), and what the original and 
compressed sizes of the input file were.

Next, unbox the files with the command:

./bitbox --unbox --input dummy --output bitbox_copy --verbose

Finally, verify that everything worked as expected:

diff bitbox bitbox_copy

(No output from diff means the files are the same.)

Usage samples:

Display help and examples: 
  bitbox --help

Break up the file fred.txt into 10 boxes with the base name ziggy, and
use zlib compression: 
  bitbox --box --input fred.txt --output ziggy --compress --numboxes 10

Break up the file fred.txt into boxes with at most 10,000 bytes each: 
  bitbox --box --input fred.txt --output ziggy --size 10000

Join the ziggy* BitBox files into fred2.txt:
  bitbox --unbox --input ziggy --output fred2.txt

Join the ziggy* BitBox files into the original file name (which is
stored in ziggy.bitbox):
  bitbox --unbox --input ziggy

Same as the first example, but in addition store the contents of the 
file "comment.txt" as a comment in ziggy.bitbox:
  bitbox --box --input fred.txt --output ziggy --compress --numboxes 10 --comment comment.txt

Display the comment that was stored in the input file:
  bitbox --showcomment --input ziggy

Note that all options current can be used with a single-dash and
single-letter format that's the same as the first letter of the 
long option format, e.g. you can use "-b" instead of "--box", 
and that all options are case sensitive.

The special parameters for the size/s option--the trailing k or m,
or the "floppy", "zip100", or 'zip250" options are not case sensitive, 
though.






