Click above to get retro games delivered to your door ever month!

                               ZORLIB

ZORLIB  is the Zortech library manager utility. It is compatible  with
the Microsoft linker and library manager, as well as with the  Zortech
linker.  Libraries  can  be created, and object files  can  be  added,
removed or substituted.

ZORLIB is intended to make the best use of the large amounts of memory
available  in  modern PCs and is very fast, but it's design  makes  it
unsuitable  for handling very large libraries i.e. those  larger  than
500k.

Using ZORLIB
ZORLIB  can  be invoked on the command line, in a batch  file,  or  by
MAKE. There are two ways of passing arguments to ZORLIB: on the ZORLIB
command  line  or via a response file, similar to  a  linker  response
file. There is NO interactive mode.

The ZORLIB command line has the following format:
[d:][path]ZORLIB lib-file [switches][,action-files][,list-file][;]
where: ([] indicates optional parameters)
[d:] and [path]
are the disk drive and path on which DOS can find ZORLIB
lib-file
is  the filename of the library file to be created or amended.  If  no
extension is given the extension .lib is assumed.

[switches]
can be one or more of the following:

/C    CREATE     If the library does not already exist then  you  must
include  this  switch  to confirm that you want a new  library  to  be
created.

/N    NO BACKUP   Normally when ZORLIB updates a library file it  will
save the old file as a backup file (.bak). This is sometimes  valuable
when  you regret a change, but extra disk space is required, and  this
may not always be available, especially on systems which do not have a
hard  disc  drive.  If you do not wish to keep  backup  versions  then
specify the /N switch.

/B    BOTH CASES     Upper- and lower-case letters will be treated  as
distinct.  This applies only to public symbols. Names for modules  are
always converted to upper case since they must be interchangeable with
MSDOS file names.

[action-files]
These  are  one  or more object files, which must be  in  the  current
directory  .  If no extension is supplied then .obj will  be  assumed.
When  the  objects  are placed in the library, ZORLIB  will  create  a
module name equal to that of the object file (without the  extension).
At least one of the characters '-', '+' or '*' must appear before each
object  file name. In some cases two of these characters can be  used.
Their meanings are:

-
Remove  the  named object from the library. This will cause  an  error
message and be ignored if the object is not in the library.

+
Add the named object to the library. This will cause an error  message
and be ignored if an object of that name is already present, or if the
named file cannot be found.

*
Make a copy of the object as a separate .obj file outside the library.
This  will cause an error message and be ignored if the object is  not
in the library.

Some pairs are legal:
+- or -+
This  will  replace  an existing object with a new  version,  the  '-'
operation being performed first.

-* or *-
This  will  remove an object from the library while at the  same  time
making  a  separate  external  copy of it as an  .obj  file.  The  '*'
operation is always performed first.

[list-file]
The optional list file name may be any MSDOS pathname. If no extension
is given then .lst is taken as the default. This file will be produced
by  ZORLIB and gives you a list all of the object files which  are  in
the library together with the public symbols that they provide. If  no
list file name is given, then no listing will be generated. If a  list
file is named, then the listing will be generated even if there are no
actions specified.

Using ZORLIB with Interactive Prompts
If  you  invoke ZORLIB with no arguments, the program  will  enter  an
interactive mode, with the user being prompted for the required input.
The & character can be used to continue input on a new line.

Using Response Files
ZORLIB  can also be invoked with the address of a response file.  This
is  a  file  which  contains the responses  that  the  compiler  would
normally  require if it were in interactive mode. An example  response
file contain :

\ZORTECH\LIB\MYWINDOW.LIB /C
+WINOPEN +WINBLANK +WINMOVE +WINHIDE &
+WINSHOW +WINPUTS +WINGETS +WINPRINT
\ZORTECH\MYWIN.LST;

If  the response file were called makewin.rsp, the library manager  is
invoked thus:

ZORLIB @MAKEWIN.RSP
Note  that  you  must not have any filename beginning with  a  @  when
working with ZORLIB, because it will be mistaken for a reference to  a
response file.