
--------------------------------------------------------------------------
311-312.UPD -- 19960222 -- Info on Upgrading a NetWare 3.11 server to 3.12
--------------------------------------------------------------------------

	Feel free to add or edit this document and then email
	it back to faq@jelyon.com




3.12 Patch archives Edition 2 Sept 1994
---------------------------------------


WARNING
*******

Please read and understand all documentation that is included with the
patches listed here before applying them to your system.


At the end of September 1994 the updates directory includes the
following files:


LANDR3.EXE   233,437  17/02/94   9:07  LAN Server drivers
TCP187.EXE    90,826  24/03/94  12:56  TCP/IP Protocol stack
NAM312.EXE    26,011  02/05/94   8:58  Macintosh namespace driver
NFS193.EXE   290,151  04/07/94  12:41  NFS 1.2c update
VLMUP2.EXE    76,165  04/07/94  12:41  VLM workstation shells updates
CDROM2.EXE   116,363  01/07/94  13:32  CD-ROM NLM 2
312PT1.EXE    46,303  01/07/94  13:32  3.12 Patch Manager/patches 1
STRTL2.EXE   160,330  04/07/94  12:48  STREAMS.NLM updates
LIBUP3.EXE   501,918  04/07/94  12:43  Server library update
SBACK2.EXE   389,358  04/07/94  12:41  SBACKUP.NLM updates
AFPFX8.EXE    69,682  08/07/94  16:02  Apple Talk Filing Protocol Fix
PSERV6.EXE   161,131  08/07/94  16:13  Printing utilities
BTR61 .EXE   947,265  11/07/94   9:17  Btrieve 6.1c
312PT2.EXE    47,266  08-01-94  3:33p  3.12 Patch Manager/patches 2
CDROM3.EXE   117,609  07-22-94  9:08a  CD-ROM NLM 3
312DU1.EXE   188,415  09-26-94  8:56a  Updated FCONSOLE & SESSION
ASPICD.DSK     9,294  06-08-93  4:15p  CD-ROM disk driver support
CDNASPI.DSK   17,743  06-16-93  2:41p  CD-ROM disk driver support


One of the main problems Netware administrators face is keeping their
systems upto date with the latest software.  The following pages provide
details of currently available patches and fixes for Netware 3.12.  Note
that some of the archives also contain the equivalent software for
version 4.01.  Some also contain modules common to both platforms.  Read
the documentation carefully before applying patches.  Details of all
available updates for NW 3.12 are maintained by the Micro Facilities
Team.

These files are located on the guest account in

ucs-ml0/guest:pc\novell\updates

I have not patched the base 3.12 installation as I do not know what is
relevant to your installation.  This may or not be a popular decision.
I welcome your comments.  Once you have installed the 3.12 files then
check the UPDATES directory.  If you have fallen behind with patching
your system then now is a good time to get back upto date.

A base 3.12 installation in the context it is used in this document
refers to the 3.12 installation from the master disks held by the Micro
Facilities Team.  A copy of this installation is also held on fileserver
UCS-ML0.  Contact MFT for access.  A LOGIN, SYSTEM and PUBLIC
directories complete with Macintosh support are stored here for the
upgrading across the network of existing 3.11 fileservers.  As with the
master disks this source has not been updated.  Once an installation has
been completed the uupdate archives listed here must be applied.

My advice is to create a sub-directory SYS:SYSTEM\UPDATES and copy and
expand the files into there.  From here only the relevant ones can be
moved into SYS:SYSTEM replacing older versions.  This keeps those files
not relevant to the current installation out of the SYSTEM directory.
The Supervisor can then clear out the updates directory once satisfied
that all necessary files have been relocated correctly.  You may find it
useful to keep the .txt files here as a reminder to what you have
installed.  All updates will be maintained on the guest account of
UCS-ML0 should you wish to obtain a full copy at a later date.

Delete all .LAN drivers in SYS:SYSTEM except those needed for the
installed adapter cards and IPTUNNEL.LAN which may be useful to some
installations. A full copy will be maintained on the guest volume of
UCS-ML0.

flag *.lan +rw
flag NE3200.lan +ros
flag IPTUNNEL.LAN +ros
del *.lan

The .LAN drivers occupy 1,028,096 on a 4K block SYS: volume and are
not needed.

Add CONLOG.NLM to the begining of the AUTOEXEC.NCF right after the
internal net number and UNLOAD CONLOG at the end.  This NLM which ships
with 3.12 provides a listing of console messages and is useful for
checking the load sequence along with the version numbers of the modules
you have currently installed.  It must be unloaded in order for it to
close the file which is located in

SYS:ETC\CONLOG.LOG

FILE SERVER NAME UCS-ML0
IPX INTERNAL NET 81D77031
LOAD CONLOG
...
UNLOAD CONLOG


The system administrator can load the CONLOG.NLM back up from the
fileserver console and unload it at intervals in order to backup the
CONSOLE.LOG file.

A useful tip is to run the MODULES command from the fileserver console
while CONLOG is loaded. Unload CONLOG and save the file. It will contain
a complete list of currently installed modules on your server complete
with version numbers.

Ensure that you have a bootable disk which contains the contents of
your DOS server boot partition. This is always useful to have in the
event of replacing drivers that then cause problems.

After a base 3.12 installation has been installed, add the following
archives. NFS193.EXE should only be applied if NFS 1.2c is already
installed. AFPFX8.EXE and NAM312.EXE should only be applied if Netware
for Macintosh 3.12 has previously been installed. All others should be
installed according to the documentation. All archives are self-extracting.


THE UPDATES
-----------

The order of installation is not all that important provided you ensure
that you are not replacing newer modules with older ones.  Some archives
do contain files that are different versions from those contained in
others.  Sometimes these files are older, sometimes newer.  Some in fact
are the same versions as the 3.12 base installation.  Since this present
document - 1st edition - will be revised as new archives are made
available there is no recommended order in which to install these
updates.  Current version lists are being compiled and will be available
from the Micro Facilities Team by August 1994. These should be used
to check your own system once the updates have been completed.

If installing BTR61.EXE note that the CLIB.NLM and AFTER311.NLM are
older than those contained in LIBUP3.EXE. Also the NWSNUT.NLM in
BTR61.EXE is older than the one included with the base 3.12
installation. The BTR61.EXE contains almost 80 files some of which are
the same versions as the 3.12 base installation. It is simpler just to
replace all modules with those in the archives, provided you keep in
mind the above exceptions.

The PM312.NLM (patch manager) and the SPXDDFIX.NLM in STRTL2.EXE are
superceded by those contained in the 312PT1.EXE.

I'm often asked "Do I have to load all the patches and fixes? Are there
any I can do without yet?" The answer is really yes and no] Naturally
there are specific fixes for specific server configurations that may not
apply to your server. When appropriate this document highlights what has
been loaded up on to UCS-ML0, the Computing Services fileserver in order
to guide you in patching your own systems. If you do not use the
Macintosh support then the AFPFX8.EXE and the NAM312.EXE archives will
not be of interest. Likewise, sites not using the NFS software will not
need NFS193.EXE. If you do not use SBACKUP then SBACK2.EXE will not be
relevant. However, if you wish to make use of the CD-ROM support then I
would advise installing CDROM2.EXE. On UCS-ML0 I use a product called
BINDVIEW NCS which needs the Netware BTRIEVE modules so the BTR61.EXE
was of particular interest to me. Does you site use the MERCURY NLM for
e-mail? If so then the TCP187.EXE should be used.

You never know when you may wish to utilise a specific piece of
software.  My advice is to update everything that is currently installed
on your systems regardless of whether you are actually using it at the
present time.  Know your system and update anything that can be updated.

If you choose not to I would ask that you consider the following
archives as 'must haves'.  The 'must have' archives for all Netware
sites at Edinburgh include

PSERV6.EXE
LANDR3.EXE
312PT1.EXE
312PT2.EXE
STRTL2.EXE
LIBUP3.EXE

as these contain new LAN drivers, libraries, operating system patches
and printing utilities.

Fileserver UCS-ML0 has Macintosh, NFS, CD-ROM, Mail and Btrieve support
installed. This means all available archives have been utilised in
keeping the server upto date.

A number of archives now contain support for Netware 3.1x and 4.x. These
archives may also contain modules common to both platforms. Check the
documentation for details. Where this is the case, appropriate
sub-directories have been created to store version specific modules.

The rest of this document provides some guidelines to installing the
various patches. It should be used in conjunction with the instructions
that accompany each archive. It should not be used in place of the
instructions that Novell have issued.

PSERV6.EXE
----------

PSERVER.EXE   109,714  02-11-94   2:46p  3.77
PSERVER.NLM    52,566  08-11-93   3:19p  3.76
PSERVER.VAP    65,218  06-15-92   2:46p  1.26
RPRINTER.EXE   64,532  05-04-93   2:31p  3.75
RPRINTER.HLP    5,038  05-04-93  12:39p  3.75


After the base 3.12 installation was complete the only file that needed
to be updated was PSERVER.EXE.


TCP187.EXE
----------

The docs state that the patch TCP162.EXE must have been applied prior to
installing this update. Netware 3.12 is already upto the necessary revision
level so this does not apply.

This archive only contains

TCPIP.NLM     193985   03-08-94   10:30a


LANDR3.EXE
----------

The only relevant files for a fileserver with the NE3200 ethernet card
are NE3200.LAN, MSM31X.NLM and ETHERTSM.NLM.  Apart from a different
ethernet card it is unlikely that any Edinburgh University Netware
server will have different requirements.

When loading up the latest .LAN files, they now use for an ethernet
installation the following NLM's.

MSM31X.NLM
ETHERTSM.NLM

When updating the .LAN driver ensure that these .NLM's are also updated.
Note that in the list produced by the modules command from the console
and from within the MONITOR.NLM the MSM31X.NLM is displayed as MSM.NLM.

MSM31X   NLM - 3.11 and 3.12 Media Support Module (MSM)
ETHERTSM NLM - Ethernet Topology Support Module (TSM)
NE3200   LAN - Novell NE3200 Bus Master Ethernet Card driver

ETHERTSM.NLM   8,841  09-28-93   2:41p
MSM31X.NLM    16,483  10-04-93   1:04p
NE3200.LAN    13,811  10-08-93  10:51a


312PT1.EXE
----------

I have created a sub-directory SYS:SYSTEM\PATCHES.  I expect the
contents of this directory to be updated in the future and since it
contains numerous NLM's I feel it is easier to maintain if it is kept in
a separate area.

One of the patches BCKTTSFX.NLM needs to be loaded after the PM312.NLM
(the 3.12 patch manager) from the STARTUP.NCF in order for it to
function correctly. Therefore these two NLM's need to be placed on the
DOS boot partition of your server and the relevant load lines added to
the STARTUP.NCF file.

In order to load these patches a search mapping needs to be establised
at boot stage. This is done by adding the following line to the
AUTOEXEC.NCF.

SEARCH ADD 2 SYS:SYSTEM\PATCHES


The 312PT1.EXE contains numerous patches for the server operating
system.  All relevant patches should be loaded. On UCS-ML0 the only
patches that are not loaded from this archive are:


IPXRCVFX.NLM
SYNCMFIX.NLM



PM312.DOC      3,683  06-29-94   8:59a
PM312.NLM      9,221  03-24-94  11:06a
GNSFIX.NLM     1,099  03-28-94   8:47a
ELEVFIX.NLM    1,717  02-22-94   3:46p
SPXFIX2.NLM    1,035  11-23-93   9:13a
BCKTTSFX.NLM     985  03-28-94   8:29a
CRDIRFIX.NLM   1,361  02-22-94   3:44p
DIRSPCFX.NLM   1,212  02-22-94   3:41p
EAACCFIX.NLM     970  01-18-94  12:27p
EADATFIX.NLM   1,181  03-28-94   8:44a
EAREPLFX.NLM   1,182  02-22-94   3:57p
GLOCKFIX.NLM   1,080  03-09-94   8:30a
IPXRCVFX.NLM     976  02-04-94   9:23a
MMACCFIX.NLM   1,010  11-09-93  10:57a
PBWANFIX.NLM   3,028  04-19-94   9:41a
REALMFIX.NLM   3,207  02-08-94   9:14a
RTCHGFIX.NLM     984  12-21-93  11:30a
SPXDDFIX.NLM   1,148  11-23-93   9:19a
SYNCMFIX.NLM   1,025  11-09-93  11:01a
UNLDIRFX.NLM   1,914  02-22-94   4:01p
UNLOADFX.NLM     992  11-11-93   2:32p
WSMSGFIX.NLM   1,132  12-16-93  10:00a


312PT2.EXE
----------


Patches SPXDDFIX.NLM and SPXFIX2.NLM are contained in 312PT1.EXE. These
are loaded on UCS-ML0. These patches do not appear in 312PT2.EXE. They
have been kept in place until further notice. All other patches from
312PT1.EXE have been replaced with those from 312PT2.EXE.

IPXRCVFX.NLM and SYNCMFIX.NLM from 312PT1.EXE were not loaded. These are
still present in 312PT2.EXE but are still not being loaded.

312PT2.EXE contains 3 new patches:

DIRSRCFX.NLM
RKIELFIX.NLM
RTRTIME.NLM

Of these only DIRSRCFX.NLM is not being loaded.

Of the present patch list loaded from AUTOEXEC.NCF two new entries were added

RKIELFIX.NLM
RTRTIME.NLM

The patch BCKTTSFX.NLM along with the patch manager PM312.NLM have been removed
from the AUTOEXEC.NCF and included in the STARTUP.NCF as the BCKTTSFX.NLM needs
to be loaded from here.


PM312.DOC      3,683  06-29-94   8:59a
PM312.NLM      9,221  03-24-94  11:06a
GNSFIX.NLM     1,099  03-28-94   8:47a
ELEVFIX.NLM    1,717  04-26-94   9:08a
RTRTIME.NLM    2,054  02-23-94   4:19p
BCKTTSFX.NLM     985  04-26-94   9:00a
CRDIRFIX.NLM   1,361  04-26-94   9:03a
DIRSPCFX.NLM   1,212  04-26-94   9:06a
DIRSRCFX.NLM   1,087  05-09-94  11:00a
EAACCFIX.NLM     970  04-26-94   9:06a
EADATFIX.NLM   1,181  04-26-94   4:33p
EAREPLFX.NLM   1,182  04-26-94   9:00a
GLOCKFIX.NLM   1,080  03-09-94   8:30a
IPXRCVFX.NLM     976  04-26-94   9:04a
MMACCFIX.NLM   1,006  04-26-94   8:54a
PBWANFIX.NLM   3,028  04-19-94   9:41a
REALMFIX.NLM   3,207  02-08-94   9:14a
RKIELFIX.NLM   1,044  05-04-94   2:38p
RTCHGFIX.NLM     984  12-21-93  11:30a
SYNCMFIX.NLM   1,025  04-26-94   8:58a
UNLDIRFX.NLM   1,973  04-26-94   8:52a
UNLOADFX.NLM     992  11-11-93   2:32p
WSMSGFIX.NLM   1,132  12-16-93  10:00a



Current patch list for UCS-ML0:


;STARTUP.NCF
;312 Patch Manager plus 312 patch to fix server hang after backing
;out more than 263 TTS files is loaded.

LOAD PM312
LOAD BCKTTSFX



;AUTOEXEC.NCF

;load patches upto revision 312PT2
;---------------------------------
LOAD CRDIRFIX
;312 patch to fix directory creation problems.(940426)

LOAD DIRSPCFX
;312 patch to correctly limit vol space for the DET and Extended DET.(940426)

LOAD EAACCFIX
;312 patch to fix Extended Attributes access with RF rights.(940426)

LOAD EADATFIX
;312 patch to fix invalid data Extended Attribute Errors.(940426)

LOAD EAREPLFX
;312 patch to fix invalid reply length with Extended Attributes.(940426)

LOAD ELEVFIX
;312 patch to fix elevator corruption.(940426)

LOAD GLOCKFIX
;312 patch for Get Locks problem (940309)

LOAD GNSFIX
;312 patch to allow reconnection when connection table is full.(940328)

LOAD MMACCFIX
;312 patch to fix disk I/O halt on file read aheads.(940426)

LOAD PBWANFIX
;312 patch to fix Packet Burst packet storms on WANs.(940419)

LOAD REALMFIX
;312 patch for IOCTL aborts during real mode execution (940208).

LOAD RKIELFIX
;312 patch to fix Richard Kiel memorial abend # 27 message.(940504)

LOAD RTCHGFIX
;312 patch to fix stop signing on route change problem (931221).

LOAD RTRTIME
;312 patch for RIP/SAP timeout configuration (940223).

LOAD SPXDDFIX
;Patch for SPX data delivery during termination and connection request retrys

LOAD SPXFIX2
;Patch to handle SPX terminate acks on non-existent sessions.

LOAD UNLDIRFX
;312 patch to fix Abend:UnLockDirectoryEntry called with entry that was already
;unlocked.(940426)

LOAD UNLOADFX
;312 Patch to Fix GPPE when Unloading NLM'S (931111)

LOAD WSMSGFIX
;312 patch to fix double byte broadcasts for NetWare J (931216).

;End of patches





BTR61.EXE
---------

This archive is a bit of a hassle to install.  When expanded it creates
serveral sub-directories so choose a safe location - another volume,
local hard disk etc to expand into first before applying the upgrades.

The CLIB.NLM and AFTER311.NLM are older than those contained in
LIBUP3.EXE.  Also the NWSNUT.NLM in BTR61.EXE is older than the one
included with the base 3.12 installation.  All other files are either
the same or newer versions than those from the base 3.12 installation.
When you expand the archive these files are contained in a sub-directory
called NW3.  Delete it] Also delete the NW4 directory as this is not
relevant to you.

A SYSTEM and PUBLIC directories are also created. The PUBLIC directory
also contains a WIN and OS2 directory. I just moved the NWLOCALE.DLL
from the WIN directory into SYS:PUBLIC on my server and the NWLOCALE.DLL
from the OS2 directory into SYS:PUBLIC\OS2 which already existed.

The PUBLIC directory contains the following extensions:

A, DLL, DOC, EXE, INS, MSG, O, SO

Flag all files with these extensions in your SYS:PUBLIC directory as RW
and move the new stuff over. Remember to flag back again as ROSDIRI.

The SYSTEM directory contains the following extensions:

HLP, MSG, NCF, NLM

Again flag appropriate files as RW and move the stuff over remembering
to flag them back again. Note that your .NCF files maybe different so be
carefull. I don't know if you have changed them - you should]


\
BTR61.TXT
BTR61.DOC      72,979  01-06-94   8:35a

\NW3\
CLIB.NLM      308,030  11-10-93   3:56p !Do not install as
NWSNUT.NLM    160,519  06-04-93   9:32a !these are older
AFTER311.NLM   25,290  08-02-93   4:16p !

\NW4\
CLIB.NLM      197,722  11-10-93   3:08p

\PUBLIC\
LIBBTRV.A      21,432  02-05-93   6:08p
LIBCOMM.A      19,120  02-05-93   6:08p
NOVDB.INI       2,460  11-06-92  10:48a
LIBBTRV.SO     18,268  02-05-93   6:08p
LIBCOMM.SO     18,596  02-05-93   6:08p
PBROLL.EXE     54,768  08-26-93  10:56a
UNXCBTRV.O      1,420  11-30-92  11:40a
WBROLL.EXE     45,824  11-16-93   5:08p
BTRUNIX.DOC    12,231  06-23-93  10:08a
NDBCNVT.EXE    18,192  01-29-93   1:40p No change
NDBCOMM.DLL    20,343  10-26-93   1:16p
BREQUEST.EXE   60,746  12-09-93   9:08a
BREQUEST.MSG    1,180  12-09-93   9:08a
BREQUTIL.EXE   29,801  10-28-93   1:40p
BREQUTIL.MSG    1,091  10-20-93   1:00p
BROLLFWD.EXE   79,104  10-11-93   2:08p
BROLLFWD.MSG    3,739  09-16-93  12:32p
BTRCALLS.DLL   17,944  06-11-93   9:32a No change
PBTRVRES.DLL   13,360  06-30-93  11:08a
WBROLLRS.DLL   11,984  11-16-93   5:08p
WBTRCALL.DLL   13,131  05-13-93   4:00p No change
WBTRVRES.DLL   22,912  01-30-93  12:16p No change
WNDBCNVT.EXE   30,926  01-30-93  12:08p No change

\PUBLIC\OS2\
NWLOCALE.DLL   34,480   05-18-93    1:00p

\PUBLIC\WIN\
NWLOCALE.DLL   38,800   05-18-93    1:00p

\SYSTEM\
BSTOP.NCF          49  04-21-92   2:40p
BUTIL.MSG       9,333  09-20-93  10:08a
BUTIL.NLM     200,411  10-25-93   5:16p
BSETUP.HLP     31,141  12-18-92   9:08a No change
BSETUP.MSG      7,972  11-25-92  11:48a
BSETUP.NLM     72,329  01-07-93  11:00a No change
BSTART.NCF         99  11-05-92   4:24p
BTRMON.HLP     37,065  01-22-93   4:32p No change
BTRMON.MSG      6,468  01-28-93   2:24p
BTRMON.NLM     75,022  01-28-93   2:24p No change
BDIRECT.MSG     3,665  01-26-93   3:00p
BDIRECT.NLM    15,609  01-26-93   3:00p
BROUTER.MSG       472  08-24-93   5:08p
BROUTER.NLM    21,101  08-27-93  10:24a
BSPXCOM.MSG     1,716  11-23-93   4:40p
BSPXCOM.NLM    23,665  11-24-93  10:40a
BTRIEVE.MSG     2,245  11-19-93   9:48a
BTRIEVE.NLM   188,660  11-19-93   9:48a
BDROUTER.MSG      472  05-17-93   3:48p
BDROUTER.NLM   22,685  05-17-93   3:48p
BREBUILD.MSG    5,028  08-19-93   5:16p
BREBUILD.NLM   40,745  08-26-93   1:32p
BSPXSTUB.MSG      235  05-05-93   1:24p
BSPXSTUB.NLM    1,254  05-20-93   3:48p No change
BTRVSTUB.NLM      950  08-27-93  10:32a
RSPXSTUB.MSG      243  05-05-93   1:24p
RSPXSTUB.NLM    1,743  05-20-93   3:48p



STRTL2.EXE
----------

The PM312.NLM and the SPXDDFIX.NLM are superceded by those contained in
312PT1.EXE so for a 3.12 installation you only need to replace the
STREAMS, SPXS, TLI and IPXS NLMs from the 3.1X directory.

\3.1X\
STREAMS.NLM   53,566  07-20-93   4:19p In sys:system - replace
SPXS.NLM      24,145  09-14-93  10:11a "     "
TLI.NLM       12,474  09-14-93  10:43a "     "
IPXS.NLM       8,149  08-10-93   7:53a "     "

\3.1X\3.11\
SPXDDFIX.NLM   1,636  09-20-93   8:18a
SPXFIX2.NLM    1,599  08-20-93   2:14p
SPXFSFIX.NLM   1,155  08-20-93   2:16p
SPXLISFX.NLM   1,016  08-20-93   2:22p
XMDFIX.NLM     1,496  09-15-92   3:29p
PCHMN230.DOC   5,930  11-30-93  10:27a
PATCHMAN.NLM   9,632  02-04-93  10:38a

\3.1X\3.12\
SPXDDFIX.NLM   1,254  09-20-93   8:20a !This directory is superceded
PM312.DOC      3,477  11-30-93  11:21a !by 312PT1.EXE
PM312.NLM      8,909  11-11-93  11:52a !

\4.01\
STREAMS.NLM   63,201  09-14-93  10:12a
SPXS.NLM      33,219  09-14-93  10:03a
TLI.NLM       24,795  09-14-93  10:17a
SPXDDFIX.NLM   1,048  09-20-93   8:22a
IPXS.NLM      10,363  08-23-93   8:13a
PM401.NLM      8,113  08-26-93  10:38a
PM401.DOC      3,477  11-30-93  11:19a



LIBUP3.EXE
----------

This archive differs from the others in the fact that it comes with its
own installation routine. This program will in fact allow the updating
of all servers that you are currently attached to and providing you have
the correct permissions.

I suggest you use the install program.  You can run it with parameters
to test the installation first.  For example to test

install /n /p0 /l2

This will create a log file indicating what modules will be replaced. To
actually install the modules

install /l2 /a

will run the procedure for real and append the output to the existing
log file.


DETAILS.DOC     4,544  06-24-94   3:20p
INSTALL.DOC    18,744  11-10-93   5:08p
INSTALL.EXE    40,196  04-28-94   5:39p

\3.X\
CLIB.NLM      342,950  05-19-94  10:27a
A3112.NLM      12,425  03-29-94   1:49p
MATHLIB.NLM    12,458  05-19-94   9:12a
AFTER311.NLM   14,651  03-29-94   1:48p
MATHLIBC.NLM   16,832  05-19-94   9:11a

\4.X\
CLIB.NLM      207,535  05-25-94  11:37a
DSAPI.NLM      43,361  06-03-94   1:38p
MATHLIB.NLM     9,076  05-25-94  10:51a
MATHLIBC.NLM   11,657  05-25-94  10:51a


Installation Instructions:

This Server Library Update comes with an installation utility that will
install the appropriate version of the NetWare 3.x and 4.x NLMs into the
SYS:SYSTEM directory of one or more servers.

For additional information on the installation utility, see the INSTALL.DOC
file.

There follows the output of the installation carried out on fileserver UCS-ML0.




Novell Server Library Update Install Utility v1.00a
Tue Jul 05 11:41:55 1994


Candidate Files for NetWare 3.x NCP Servers:

   File: MATHLIBC.NLM   Version: 3.12.07          Built: 05/19/1994
   Desc: NetWare C NLM Runtime Math Library (fp calls) v3.12g
   Size: 16832

   File: AFTER311.NLM   Version: 4.10.01          Built: 03/29/1994
   Desc: NetWare 3.x Locale Compatibility Support
   Size: 14651

   File: MATHLIB.NLM    Version: 3.12.07          Built: 05/19/1994
   Desc: NetWare C NLM Runtime Math Library (387 Support) v3.12g
   Size: 12458

   File: A3112.NLM      Version: 4.10.01          Built: 03/29/1994
   Desc: NetWare 3.x NUT Compatibility Support
   Size: 12425
   File: CLIB.NLM       Version: 3.12.07          Built: 05/19/1994
   Desc: NetWare C NLM Runtime Library v3.12g
   Size: 342950


Candidate Files for NetWare 4.x NCP Servers:

   File: DSAPI.NLM      Version: 4.01.04          Built: 06/03/1994
   Desc: NetWare Directory Services API Library v4.01d
   Size: 43361

   File: MATHLIBC.NLM   Version: 4.01.05          Built: 05/25/1994
   Desc: NetWare C NLM Runtime Math Library (fp calls) v4.01E
   Size: 11657

   File: CLIB.NLM       Version: 4.01.05          Built: 05/25/1994
   Desc: NetWare C NLM Runtime Library v4.01E
   Size: 207535

   File: MATHLIB.NLM    Version: 4.01.05          Built: 05/25/1994
   Desc: NetWare C NLM Runtime Math Library (387 Support) v4.01E
   Size: 9076


NCP Server UCS-TEST is being updated
UCS-TEST is running NetWare v3.12.00
UCS-TEST/SYS: has 29950 available 4K blocks
Rights to UCS-TEST/SYS:SYSTEM are RWCEMFA
Candidate MATHLIBC.NLM is newer than MATHLIBC.NLM in SYS:SYSTEM
MATHLIBC.NLM needs 5 of 29950 available blocks
Resetting attributes of SYS:SYSTEM/MATHLIBC.NLM
Transferring T:\SYSTEM\UPDATES\TMP\3.X\MATHLIBC.NLM to UCS-TEST\SYS:SYSTEM\MATHLIBC.QRM
Renaming SYS:SYSTEM/MATHLIBC.NLM to SYS:SYSTEM/MATHLIBC.BAK
Renaming SYS:SYSTEM/MATHLIBC.QRM to SYS:SYSTEM/MATHLIBC.NLM
Marking SYS:SYSTEM/MATHLIBC.BAK as Read-Only
Marking SYS:SYSTEM/MATHLIBC.NLM as Read-Only
MATHLIBC.NLM update completed
Candidate AFTER311.NLM is newer than AFTER311.NLM in SYS:SYSTEM
AFTER311.NLM needs 4 of 29945 available blocks
Resetting attributes of SYS:SYSTEM/AFTER311.NLM
Transferring T:\SYSTEM\UPDATES\TMP\3.X\AFTER311.NLM to UCS-TEST\SYS:SYSTEM\AFTER311.QRM
Renaming SYS:SYSTEM/AFTER311.NLM to SYS:SYSTEM/AFTER311.BAK
Renaming SYS:SYSTEM/AFTER311.QRM to SYS:SYSTEM/AFTER311.NLM
Marking SYS:SYSTEM/AFTER311.BAK as Read-Only
Marking SYS:SYSTEM/AFTER311.NLM as Read-Only
AFTER311.NLM update completed
Candidate MATHLIB.NLM is newer than MATHLIB.NLM in SYS:SYSTEM
MATHLIB.NLM needs 4 of 29941 available blocks
Resetting attributes of SYS:SYSTEM/MATHLIB.NLM
Transferring T:\SYSTEM\UPDATES\TMP\3.X\MATHLIB.NLM to UCS-TEST\SYS:SYSTEM\MATHLIB.QRM
Renaming SYS:SYSTEM/MATHLIB.NLM to SYS:SYSTEM/MATHLIB.BAK
Renaming SYS:SYSTEM/MATHLIB.QRM to SYS:SYSTEM/MATHLIB.NLM
Marking SYS:SYSTEM/MATHLIB.BAK as Read-Only
Marking SYS:SYSTEM/MATHLIB.NLM as Read-Only
MATHLIB.NLM update completed
A3112.NLM not currently installed in SYS:SYSTEM
A3112.NLM needs 4 of 29937 available blocks
Transferring T:\SYSTEM\UPDATES\TMP\3.X\A3112.NLM to UCS-TEST\SYS:SYSTEM\A3112.QRM
Renaming SYS:SYSTEM/A3112.QRM to SYS:SYSTEM/A3112.NLM
Marking SYS:SYSTEM/A3112.NLM as Read-Only
A3112.NLM update completed
Candidate CLIB.NLM is newer than CLIB.NLM in SYS:SYSTEM
CLIB.NLM needs 84 of 29933 available blocks
Resetting attributes of SYS:SYSTEM/CLIB.NLM
Transferring T:\SYSTEM\UPDATES\TMP\3.X\CLIB.NLM to UCS-TEST\SYS:SYSTEM\CLIB.QRM
Renaming SYS:SYSTEM/CLIB.NLM to SYS:SYSTEM/CLIB.BAK
Renaming SYS:SYSTEM/CLIB.QRM to SYS:SYSTEM/CLIB.NLM
Marking SYS:SYSTEM/CLIB.BAK as Read-Only
Marking SYS:SYSTEM/CLIB.NLM as Read-Only
CLIB.NLM update completed
NCP Server UCS-TEST update is complete





NAM312.EXE
----------

Only the one file to replace

          MAC.NAM      15107   09-20-93    9:58a


Ensure that the copy on the DOS boot partition of the server and the one
in SYS:SYSTEM are replaced. This means some downtime but a server
re-boot is necessary to implement this update.



AFPFX8.EXE
----------

AFP5.RTP      2,851  04-01-94  10:28a
PATCH.EXE    45,450  01-01-28   1:00a
AFP200.RTP    2,906  04-01-94  10:30a

Your Macintosh users should be logged out before installing this update.


Installation Instructions:

1.   At the file server, UNLOAD AFP.

2.   From a DOS workstation, copy *.RTP and PATCH.EXE to the SYS:SYSTEM
     directory.

3.   At the DOS prompt, type PATCH.

      A prompt will ask which file you would like to use.

4.   If you have the NetWare for Macintosh 3.12 5-user version, type
     AFP5.

     If you have the NetWare for Macintosh 200-user version, type AFP200.

 5.   At the file server, LOAD AFP.

      Note that the version has been changed from 3.12a to 3.12c.




SBACK2.EXE
----------

SBACKUP is probably not in use at your site. With the introduction of
Netware 3.12, SBACKUP includes the facility to backup workstations
across the network.



SMDR.NLM       41,362  10-28-93   5:11p Not in sys:system
WS_MAN.NLM     35,146  12-16-93  10:51a Later version
TAPEDAI.DSK    34,231  05-18-93   8:36a No change
TSA_DOS.NLM    77,820  11-08-93   8:46a Later version
TSA_OS2.NLM     7,814  11-02-93   5:20p Not in sys:system
TSA_SMS.COM    17,724  10-18-93   4:37p New file - sys:public
\3.12\
TSA311.NLM    129,464  11-05-93   2:36p In sys:system - replace
TSA312.NLM    129,461  11-05-93   2:28p In sys:system - replace
DIBIDAI.NLM    17,033  06-11-93   4:12p In sys:system - no change
SMDR31X.NLM    41,649  10-28-93   5:14p In sys:system - replace
\4.0X\
TSA400.NLM    122,492  11-05-93   2:20p
SBACKUP.NLM   234,976  08-17-93   1:56p




CDROM2.EXE
----------

Only install if CD-ROM installed


NWPA.DSK      70,437  02-01-94   2:06p
CDROM.NLM     87,855  04-13-94   4:49p
NPA312.DSK    62,169  02-01-94   2:00p

Installation Instructions:

1.   Rename the existing CDROM.NLM to .OLD.

2.   Copy the NWPA.DSK file (for NetWare 4.0x) or the NPA312.DSK file (for
     NetWare 3.12) and the CDROM.NLM file to the SYS:SYSTEM subdirectory.

3.   Load HBA driver (for example, AHA1540.DSK).

4.   Load ASPICD.DSK or CDNASPI.DSK. (ASPICD.DSK is required to use the ASPI
     transport with an ADAPTEC controller, for generic ASPI transport use the
     CDNASPI.DSK file.  Other controller cards should (hopefully) come with
     their own ASPI transport .DSK file.

5.   If NetWare 3.12 is being used, load the AFTER311.NLM.

6.   Load the NWPA.DSK (4.0x) or the NPA312.DSK (3.12) file before loading the
     CDROM.NLM file.

7.   Load the CDROM.NLM file.

8.   For a list of available CDROM.NLM commands, type CD HELP at the SYSTEM
     CONSOLE prompt.


The files contained in CDROM2.EXE will only work with NetWare 3.12 and 4.0x.

NWPA.DSK
This is a support file for the CDROM.NLM running on a NetWare 4.0x server.

NPA312.DSK
This is a support file for the CDROM.NLM running on a NetWare 3.12 server.

CDROM.NLM
This is the updated CDROM.NLM only for Novell NetWare 3.12 and 4.0x.

NOTE:     The current version of the CDROM.NLM needs to have AFTER311.NLM,
STREAMS.NLM and CLIB.NLM files loaded before it will load (this is only with
NetWare 3.12).  You can accomplish this by loading the AFTER311.NLM file at
the server console.  The CLIB.NLM and STREAMS.NLM files will be automatically
loaded.



CDROM3.EXE
----------


CDROM.NLM for NetWare 3.12 and 4.01.  The CDROM.NLM now supports CD's with
greater than 1824 directories and more than 58,368 files, along with other
enhancements.


CDROM3.TXT
NWPA.NLM       64575  04-22-94   3:50p
CDROM.NLM      96467  05-24-94   8:50a
NPA312.NLM     64101  04-22-94  11:49a

Installation Instructions:

1.  Rename the existing CDROM.NLM to *.OLD.

2.  Copy the NWPA.NLM file (for NetWare 4.0x) or the NPA312.NLM file (for
NetWare 3.12) and the CDROM.NLM file to the SYS:SYSTEM subdirectory.

3.  Load HBA driver (for example, AHA1540.DSK).

4.  Load ASPICD.DSK or CDNASPI.DSK file if it is needed.

5.  Based upon your version of NetWare use the following load statements:

      NetWare 3.12       NetWare 4.x

      Load AFTER311.NLM       ------------
      Load NPA312.NLM         Load NWPA.NLM
      Load CDROM.NLM          Load CDROM.NLM

6.  For a list of available CDROM.NLM commands, type CD HELP at the SYSTEM
CONSOLE prompt.


----------------------------------------------------------------

The files contained in CDROM3.EXE will only work with NetWare 3.12 and 4.0x.

Explanation of files:

NWPA.NLM
This is a support file for the CDROM.NLM running on a NetWare 4.0x server.

NPA312.NLM
This is a support file for the CDROM.NLM running on a NetWare 3.12 server.

CDROM.NLM
This is the updated CDROM.NLM only for Novell NetWare 3.12 and 4.0x.

NOTE:     The current version of the CDROM.NLM needs to have AFTER311.NLM,
STREAMS.NLM and CLIB.NLM files loaded before it will load (this is only with
NetWare 3.12).  You can accomplish this by loading the AFTER311.NLM file at
the server console.  The CLIB.NLM and STREAMS.NLM files will be automatically
loaded.  The "S" revision of the CDROM.NLM (included in this file) will not
use any previously created index files.  An index file is created the first
time a new CD is mounted as a NetWare volume.  Novell recommends that you
execute the CD PURGE command at the server console to purge all previous index
files.  The CD PURGE command should only be executed when no CD's are mounted
as NetWare volumes.  Executing the CD PURGE command requires that each CD
re-build its index files the first time it is mounted as a NetWare volume.
When mounting CDs with the new CDROM.NLM the /R parameter should be used to
rebuild the index files.  This will result in a slight delay.




NFS193.EXE
----------

Only install if running NFS 1.2c.

DOS needs to be enabled at the fileserver which may mean a restart with
the REMOVE DOS line commented out of the AUTOEXEC.NCF if appropriate.

PKERNEL.NLM left as RW

This is an update to NetWare NFS 1.2C.  It contains bug fixes as well as
enhancements.


SPACE.DAT            9  08-03-93   3:35p
PFILES.DAT       1,595  06-21-94   9:04a
PCONFIG.DAT      3,263  06-21-94   9:08a
PCONFIG.HLP      2,183  07-29-92   1:27p
PCONFIG.NLM     15,938  11-08-93   6:39p
PINSTALL.HLP     6,798  06-21-93   2:53p
PINSTALL.NLM   130,422  11-08-93   6:39p
P_UNINST.HLP       892  07-27-92  12:02p
P_UNINST.NLM    72,042  11-08-93   6:40p

\PUBLIC\
$RUN.OVL         2,400  07-13-89   9:30a
IBM$RUN.OVL      2,400  07-13-89   9:30a
SYS$ERR.DAT      9,170  12-10-90   1:37p
SYS$MSG.DAT     25,138  01-30-91   3:10p
SYS$HELP.DAT    14,092  01-29-91   2:39p

\SYSTEM\
PLPD.NLM        44,900  05-04-94  10:29a
LOCKD.NLM       63,824  05-04-94  10:24a
FTPSERV.NLM     70,283  05-04-94  10:35a
NFSSERV.NLM    142,357  05-04-94  10:22a
LPR_PSRV.NLM    57,067  05-04-94  10:35a
NFSADMIN.NLM    82,585  05-04-94  10:24a

Installation Instructions:

If installation is from floppy disk, give the disk a label of NFS1 and copy
the self extracting file NFS193.exe to the root of the floppy disk.  If
installation is from the server copy the self extracting file NFS193.exe into
a subdirectory called NFS1 on any valid NetWare volume. Type NFS193 to extract
the files.


======================================
Installing patch locally at the server
======================================

1.  Run UNISTOP to unload NFS.

2.  From the server console, type the following command:
        LOAD INSTALL <Enter>

3.  At the Install NLM screen, select Product Options.

4.  Press <Insert> to add a new product.

5.  At the prompt, insert the Upgrade diskette in the disk drive. If the
diskette is not in drive A:, change the drive letter to the correct letter
(NetWare_Volume:NFS1). Then, press <Enter> to start the installation.

6.  When installation is complete, Press <Esc> to get to the Main menu.

7. Press <Esc> to exit the Install NLM.

8. Bring down the server by typing the following commands:
        DOWN
        EXIT

9. Restart the server by typing the following command:
        SERVER

The patch is now installed on the server.

==============================
Installing the patch remotely
==============================

To install the patch from a workstation, complete the following steps:

1.  Run RCONSOLE.

2.  Choose the server you wish to install the patch on.

3.  Follow steps 1 through 7 above.

4.  Exit RCONSOLE and go to server console where the patch has been installed.
Bring down the server by typing the following commands:
        DOWN
        EXIT

5. Restart the server by typing the following command:
        SERVER

The patch is now installed on the server.



VLMUP2.EXE
----------

This archive applies only to the PC workstation running the Virtual
Loadable Modules (VLMs).

This file contains the following v1.11 VLMs that have been updated since the
v1.10 client kit was released:  VLM.EXE, AUTO.VLM, CONN.VLM, FIO.VLM,
GENERAL.VLM and REDIR.VLM.  It also contains an updated IPXODI.COM file for
use with drivers that need to set a NET:NODE address dynamically.


FIO.VLM        17,914  04-12-94  11:06a
VLM.EXE        36,635  03-14-94  10:55a
AUTO.VLM        4,479  03-14-94  10:57a
CONN.VLM       10,705  03-14-94  10:56a
REDIR.VLM      13,665  04-12-94  11:06a
IPXODI.COM     30,126  03-14-94   8:43a
GENERAL.VLM     4,203  03-14-94  10:58a


Installation Instructions:

1.  Make a backup copy of the existing VLM files located in the workstation's
\NWCLIENT directory.

2.  Make a backup copy of the existing IPXODI.COM file located in the
workstation's \NWCLIENT directory.

3.  Copy the updated VLMs and IPXODI.COM files to the workstation's \NWCLIENT
directory.


312DU1.EXE
----------


This SESSION.EXE v3.76 and FCONSOLE.EXE v3.76  for NetWare v3.12 addresses the
problem of listing an incomplete connection list whenever the connections are
not in consecutive order.

SYMPTOM

The previous SESSION.EXE and FCONSOLE.EXE files produced an incomplete
connection list when the connections were not in consecutive order viewing
connections from the User List option.  This would occur most often when a
not-logged-in connection was cleared using FCONSOLE on a client or MONITOR on
the file server console.

CAUSE



SOLUTION

Apply the 312DU1.EXE file.

Self-Extracting File Name:  312DU1.EXE     Revision:  A

Files Included     Size     Date      Time

\
312DU1.TXT
FCONSOLE.EXE   214,014  03-24-94   9:08a
SESSION.EXE    150,863  07-19-94  10:03a


Installation Instructions:

NOTE:  Always make a backup of applicable files before applying new fixes.

1)  Flag SESSION.EXE and FCONSOLE.EXE contained in the PUBLIC directory normal
or sharable, read/write.

2)  Rename SESSION.EXE and FCONSOLE.EXE contained in the PUBLIC directory to
allow an original copy.

3)  Copy the SESSION.EXE and FCONSOLE.EXE provided with this update into the
PUBLIC directory.

4)  Flag the new files sharable, read only.


Garry Scobie
LAN Support Officer
Micro Facilities Team
EUCS
e-mail: g.scobie@ed.ac.uk

26/09/94

------------------------------

Date: Wed, 21 Feb 1996 15:58:47 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: A call for opinions

>Is Netware v3.12 really a "patched" v3.11?  Are there real reasons
>for upgrading?  To borrow a phrase, what is the "ROI."
----------
	ROE, Rules Of Engagement is more like it.
	No, NW 3.12 is not just a "patched" NW 3.11. It is much more like
NW 4 under the covers than NW 3.11, but it isn't quite (still has the NW
3 memory pools troubles, for example).
	My own view is NW 3.12 is a solid mature performer, difficult to
beat then and now and for some time in the future. It is the pinnacle of
the workgroup server in the sense it is independent of all the other
servers on site. If one were to take NW 4.10 and remove directory services
then NW 4.1minus would be the champ in this role because it has further
refinements to its kernel.
	NW 3.11 is long in the tooth and patching can do only so much.
The kernel, server.exe, is set in its ways and can't be redesigned by
patches alone. NW 3.11, though, is a good system and continues to yield
dependable fast service.
	The choice of upgrading to 3.12 or not thus becomes one of staying
with current technology and improvements or not. NW 4 is just plain
different, not an upgrade, but a much different way of doing business;
folks with version-itis disease should be warned away.
	Joe D.

------------------------------

Date: Thu, 22 Feb 1996 09:08:43 +0000
From: Phil Randal <philr@HWCCES.DEMON.CO.UK>
Subject: Re: A call for opinions

>Is Netware v3.12 really a "patched" v3.11?  Are there real reasons for
>upgrading?  To borrow a phrase, what is the "ROI"?

Yes - it includes the SEC* patches, PBURST, and some internal limits
have been increased.  Disk caching strategies have been tweaked too.
It also includes a copy of Basic MHS, which is next to useless if
you have more than one server on your LAN.

------------------------------

