READ_ME.TOO						    11/13/91

		      TLIB 4.12, Network Version

TLIB's Local Area Network support is very generic: it simply uses
the DOS "file sharing" modes (supported by the standard DOS program
SHARE.EXE) to ensure controlled access to shared TLIB libraries.

This means that the network version of TLIB is compatible with nearly
all LANs, if DOS SHARE (or its equivalent) is loaded.  SHARE is a "TSR"
(terminate and stay resident) program which consumes about 6K of RAM.

Note: "file sharing" is often called "file and record locking."



Novell Netware, 3com 3+ or 3+Open, DSC NEXOS:

You needn't use SHARE with these networks under DOS 3.x or 5.x. SHARE is
required only if you are using DOS 4.x and a hard disk partition larger
than 32 megabytes.  DOS 4.x needs SHARE to operate correctly with large
disk partitions.



3com EtherSeries:

3com EtherSeries users should upgrade to 3+.



IBM PC Network and Token Ring:

You must run SHARE on each PC.



Sun PC-NFS:

You needn't run SHARE unless you are using DOS 4.x and a hard disk
partition of more than 32 megabytes.  Instead, use the "/share" option
on your "net use" command to mount the remote file system.  Do not use
the "/mustshare" or "/readonly" options.  For example:

	net use i: \\hostname\path /share

Once, long ao, we had a report of problems related to the testing and
changing of file attributes under a version of PC-NFS.	TLIB must test
and change file attributes if "READONLY Y" is configured.  If you see
the message "Error: could not set file date" while using TLIB, please
call us for instructions: (919) 233-8128.  Ask for "technical support".



Locus Computing PC-Interface:

Be sure you have PC-Interface version 2.8.7 or later.  Version 2.8.0
does not support file and record locking.  You needn't run SHARE.EXE
unless you're also using DOS 4.x and a hard disk partition of more
than 32 megabytes.  Be sure that the MS-DOS users are given read and
write permissions on the Unix server.  (Note: PC-Interface is also sold
by Prime Computer, Inc., and other vendors.)



Alloy NTNX:

Users of Alloy's NTNX "network in a box" should install Alloy's
SIMSHARE.COM utility on each workstation, to support the DOS file
sharing modes, before using TLIB.  (SIMSHARE is available on Alloy's
public bulletin board system, or directly from Burton.)



DOS-Merge/386:

Please contact us if you are using TLIB under UNIX via a DOS-Merge
utility.





	HOW TO TEST TLIB'S NETWORK SUPPORT WITH YOUR LAN


Users of less-popular networks can test TLIB with the network's file
sharing support as follows:


1) This test should be performed with the default TLIB configuration
   parameters, so remove or rename your TLIB configuration file.


2) Create a large TLIB library containing many versions, preferably
   with big differences between the versions (so that the TLIB "L" (list)
   will run more slowly).  One way to do this is with two dissimilar text
   files, file1 and file2, and a simple .bat file that looks like this:

	REM tst.bat
	TLIB P TST.TLB N file1 dummy-comment
	:LUPE
	TLIB P TST.TLB U file2 dummy-comment
	TLIB P TST.TLB U file1 dummy-comment
	GOTO LUPE

   Run this .bat file.	After 25-30 versions have been created, abort it
   with Ctrl-Break.  The result will be a large TLIB library named "tst.tlb".


2) On one network station, use TLIB to list the versions in tst.tlb,
   like this:

	TLIB P TST.TLB L TST

   While the versions are scrolling up the screen, press ctrl-S to
   stop the display.


3) On another network station, try to add another version to the
   TLIB library, like this:

	TLIB P TST.TLB U file3 dummy-comment

   If the LAN file-sharing support is working correctly, then you
   should see the message "awaiting access..." displayed repeatedly
   on the screen, as TLIB waits for the other station to close the
   library.  TLIB will continue to "await access" for at least a full
   minute before giving up.  If TLIB adds the new version without
   "awaiting access", or if TLIB issues an immediate "Can't append"
   error message, then the LAN file-sharing support is not working;
   call "technical support" at Burton and we will help you resolve the
   problem (if we can't solve it, you can return TLIB for a refund).


4) While the second station is "awaiting access", return to the first
   station and press ctrl-Q to allow the L command to resume.  When
   the L command finishes, TLIB will close the library file and the
   second station should (finally) obtain access to the TLIB library
   so that its U (update) command can complete.


5) Make the library file read-only, like this:

	ATTRIB +R TST.TLB


6) Repeat step 3, except use the following command:

	TLIB C "READONLY Y" P TST.TLB U file3 dummy-comment


7) Repeat step 4.


Note: to get rid of TST.TLB, you'll need to do:

	ATTRIB -R TST.TLB
	DEL TST.TLB

