README FILE FOR NWL003.ZIP

The files listed below are used to patch NetWare Lite v1.0. These files
have completed software test.

These files will also be distributed under the NOVLIB
forum on Compuserve and will also have the name NWL00x.ZIP where "x"
will indicate the revision of the patch and will be incremented each
time new patches are added.


The following files are included in this revision:

NWL003 DOC (This file)
5E03 PAT 877 11-26-91 5:55p
LOSTRESP PAT 1747 11-26-91 1:36p
PTIMEOUT PAT 1170 11-22-91 3:37p
WRBEHIND PAT 1178 11-22-91 3:37p
RDCACHE PAT 1052 11-22-91 3:18p
UPATCH EXE 19690 1-16-92 9:35a



NWL003.ZIP contains several patches that are explained in the text
below.

NOTES:


1. Only one PATCH diskette is needed to patch all copies of NetWare Lite.
You Do Not need a separate PATCH diskette for each copy of NetWare
Lite.

2. Do not patch the original NetWare Lite program and driver diskette files.

For each machine that has NetWare Lite software on a hard disk,
patch the files in the C:\nwlite directory.

For each machine that only uses a floppy diskette, patch the files on
each workstation's NetWare Lite floppy diskette.

3. To get consistent results from the network, patch all copies of NetWare
Lite on the network. If a server or client is not patched, it will
continue with the erratic behavior that the patch corrects.

4. We recommend that you apply all the patches using UPATCH. However,
you can apply a specific patch to a file using "UPATCH patchname" or
apply a patch to a specific file using "UPATCH filename."

5. You may apply patches before or after running NetWare Lite, but the
changes will not take affect until the computer is rebooted and the patched
files are loaded into memory.



USE OF UPATCH.EXE TO PATCH FILES:

***************************************************************************
TO APPLY PATCHES ON A HARD DISK SERVER/CLIENT
---------------------------------------------
To patch a server, server/client, or client software on a hard disk, do the
following:

1. Insert the PATCH disk into a disk drive (A: or B:).

2. At the DOS prompt, type the disk drive letter (A: or B:) and press
.

3. To apply all patches to all applicable files, type "UPATCH" and press
.

To apply a specific patch to its applicable file, type "UPATCH
patchname" and press .

To apply applicable patches to a target file, type "UPATCH filename"
and press .

NOTE: The patches are applied to each applicable file and the old
file version is retained with an ".OLD" file extension. If
necessary, the ".OLD" version can be renamed and executed.

4. Reboot the computer.

***************************************************************************
TO APPLY PATCHES ON A FLOPPY CLIENT
-----------------------------------
To patch the client software on a client that uses a floppy, do the
following:

1. Insert the client diskette in drive B.

2. Insert the PATCH diskette into drive A:.

3. At the DOS prompt, type "A:" and press .

4. Type "UPATCH B:CLIENT.EXE," press , and follow the
instructions displayed on the screen.

NOTE: The patches are applied to each applicable file and the o/ file version is retained with an ".OLD" file extension. If
necessary, the ".OLD" version can be renamed and executed.

5. Reboot the computer.

***************************************************************************
TO GET HELP
-----------
To get help, do the following:

1. Insert the PATCH disk into a disk drive (A: or B:).

2. At the DOS prompt, type the disk drive letter (A: or B:), and press
.

3. To get help, type "UPATCH HELP," and press .

NOTE: The Universal Patch Program help screen appears with
usage information and the DOS prompt appears.

***************************************************************************
TO GET A LIST OF PATCHES
------------------------
To get a list of patches that can be applied by UPATCH, do the following:

1. Insert the PATCH disk into a disk drive (A: or B:).

2. At the DOS prompt, type the disk drive letter (A: or B:) and press
.

3. Type "UPATCH LIST" and press .

NOTE: The patch list and the DOS prompt appear.

***************************************************************************
TO VERIFY PATCHES APPLIED
-------------------------
To determine if a file has been patched by UPATCH, do the following:

1. Insert the PATCH diskette into a disk drive (A: or B:).

2. At the DOS prompt, type the disk drive letter (A: or B:) and press
.

3. Type "UPATCH VERIFY" and press .

NOTE: A list appears that shows each patch that can be applied by
UPATCH, its target file, and whether or not the file has
been patched. The DOS prompt also appears.


***************************************************************************

To get the latest NetWare Lite information on patches, application
compatibility, hardware compatibility, upgrades and updates, top ten
support issues, NetWare Lite product information, and so on, customers in
the U.S. and Canada can call Novell's 24-hour automated fax service. To
access this service, dial (800)NETWARE [(800)638-9273] and press the star
(*) key during the recorded message.

***************************************************************************
PRINTING THIS FILE
------------------
To print this file to a local printer, do the following:

1. Type "a:" and press .

2. Type "COPY PRN:" and press .

To print this file to a network printer, do the following:

1. Create or modify a network printer as explained in the NetWare Lite
manual.

2. Type "a:" and press .

3. Type "NET PRINT NETPRINTER" and press .




INFORMATION ON SPECIFIC PATCHES

===================================================================
RDCACHE.PAT - NetWare Lite Server read-ahead cache patch.

File: SERVER.EXE
Checksums: BF0, 3EF, BF0

Problem: The server makes an invalid entry in the read-ahead cache
when a read is issued past the end of the file. The invalid
entry contains no data, and could be returned after the file
is extended and a subsequent read is made to the same area of
the file in a short period of time.

Symptoms: If you have a database program which incorrectly reports that
the end-of-file has been encountered, or exhibits problems
reading or updating the index file for a database, you may
have this problem. Programs compiled under FoxBase and Clipper
are known to make I/O call sequences which result in the error.




===================================================================
LOSTRESP.PAT - NetWare Lite Server lost response patch.

File: SERVER.EXE
Checksums: D4D, 17B8, 416, 3A3, D4D, 17B8

Problem: The last function result is not saved correctly in the
server's connection table. This results in non-reproduceable
functions (like OPEN FILE) being reproduced at the server when
a server response packet is lost. This ends up exhausting the
server's resources after a long period of sustained activity.

Symptoms: You may have this problem if DOS or your application reports
the error "Too many open files" after running continuously for
several hours/days. Another symptom is that, after continuous
operation, one of the machines freezes, or reports a DOS function
failure.



===================================================================
WRBEHIND.PAT - NetWare Lite Server write behind patch.

File: SERVER.EXE
Checksums: D1E, 3B0, D1E

Problem: The server write-behind offset is corrupted when a packet is lost
on the wire. This results in data being written in the wrong
place in a file when the underlying network drops a packet. This
only occurs with certain combinations of buffer sizes,
application write sizes, and write offsets.

Symptoms: If you have file data corruption under particularly heavy load,
or if you have a particular machine or particular application
which appears to corrupt data when it is used, you may have
this problem.




===================================================================
PTIMEOUT.PAT - NetWare Lite Client printer (PRN) timeout patch.

File: CLIENT.EXE
Checksums: 1166, 50B, 1166

Problem: Client program fails to imply a print job timeout on a PRN
port capture.

Symptoms: If you print from an application, but the job does not start
printing at the server until you exit the application, you may
have this problem. Check to see if the banner page on the
delayed print job indicates that the "Client printer port or
filename" is "PRN capture". If so, this is an indication that
theapplication is using PRN and not LPT1 for its printing.
Programs compiled under Clipper are known to print through PRN,
and thus are affected by this problem.



===================================================================
5E03.PAT - NetWare Lite Client DOS 5E03 invalid parm patch.

File: CLIENT.EXE
Checksums: 55F, 509, 57

Problem: When DOS interrupt 21h, function 5E03 (Get Printer Setup String)
is used on a disk device, the client returns an error code of 1
(invalid function). Software from Computer Associates
International, Inc. expects an error code of 87
(invalid parameter).

Symptoms: If you are running software from Computer Associates, you may note
that networking features do not work. CAI software expects a
different error code on function 21, 5E03 than NetWare Lite
currently returns.


*****************************************************************************
DISCLAIMER

Novell, Inc. makes no representations or warranties with respect to any
NetWare software, and specifically disclaims any express or implied
warranties of merchantability, title, or fitness for a particular purpose.

Distribution of any NetWare software is forbidden without the express
written consent of Novell, Inc. Further, Novell reserves the right to
discontinue distribution of any NetWare software.

Novell is not responsible for lost profits or revenue, loss if use of the
software, loss of data, costs of re-creating lost data, the cost of any
substitute equipment or program, or claims by any party other than you.
Novell strongly recommends a backup be made before any software is
installed. Technical support for this software may be provided at the
discretion of Novell.
*****************************************************************************