
----------------------------------------------------------------------
NOV-VER.DOC -- 19980228 -- Email thread on NetWare Version Information
----------------------------------------------------------------------

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




Date: Wed, 20 Dec 1995 07:10:36 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: VLMUP4 Withdrawn?

>>>>I've just checked ftp.novell.com /pub/updates/nwos/dsclnt12 and not
>>>>only has vlmup4.exe disappeared, but the vlmkt?.exe files have reverted
>>>>to version 1.20a.
>>>
>>> They are there Monday, Dec. 18 but not all in the same directory.
>>
>>I got everything I needed from ftp.novell.com/pub/netwire/techfiles.
>>And the VLM 1.20b works just fine as does everything else in VLMUP4.
>>Just thought I would pass that along FWIW !!.
>
>Fine, but can someone from Novell Quality Assurance have a look and tell
>us:
>
>1:  Which version of netbios.exe is actually the current one?  The one
>    from techfiles/vlmup4.exe or from vlmkt?.exe (different versions).
>
>2:  Which version of netx.vlm is actually the current one?  The one
>    from techfiles/vlmup4.exe or from vlmkt2.exe (different versions).
>    Oct 95 or Nov 95 datestamp?
>
>3:  Which version of rsa.vlm is actually the current one?  The one
>    from techfiles/vlmup4.exe or from vlmkt?.exe (different versions).
>    Sept 95 or Oct 95?
>
>4:  Why vlmup4.exe in /pub/updates/dosclnt has within it vlmup4.zip
>    with different versions of some files, as above?
>
>Phil Randal
------------

	Rather good questions, actually. I'll add another:

5. Why isn't VLMUP4.EXE in the netwire\novfiles area?

	For what it's worth, here are some internal idents from the
most current (changes by the hour??) VLMUP4.EXE, the one without the
internal .zip file and now located in updates\nwos\dwclnt11. I guess the
"11" part is just a sneaky part of the Treasure Hunt for this material.
Miscellaneous chatter below omitted for brevity.

NetWare Link Support Layer v2.16 (950417)
Novell NE2000 Ethernet MLID v2.05 (950504)
NetWare IPX/SPX Protocol            v3.02  (950808)
VLM.EXE      - NetWare virtual loadable module manager  v1.20 REV B (951002)
CONN.VLM     - NetWare connection table manager  v1.20 REV B (951002)
IPXNCP.VLM   - NetWare IPX transport module  v1.20 REV B (951002)
TRAN.VLM     - NetWare transport multiplexor module  v1.20 REV B (951002)
BIND.VLM     - NetWare bindery protocol module  v1.20 REV B (951002)
NWP.VLM      - NetWare protocol multiplexor module  v1.20 REV B (951002)
FIO.VLM      - NetWare file input-output module  v1.20 REV B (951002)
GENERAL.VLM  - NetWare general purpose function module v1.20 REV B (951002)
REDIR.VLM    - NetWare DOS redirector module  v1.20 REV B (951002)
PRINT.VLM    - NetWare printer redirection module  v1.20 REV B (951002)
NETX.VLM     - NetWare workstation shell module  v4.20 REV B (951121)
						  ^--------- Novell typo??

	These are from a log file generated while starting up the client.
	Joe D.

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

Date: Thu, 28 Dec 1995 13:17:00 GMT
From: Teo Kirkinen <kirkinen@CC.HELSINKI.FI>
Subject: Re: Netware 4.10 patches

>Can someone clarify a few points re patches for NW4.10 -
>first a very simple question - are the patch series 410ptn cumulative
>or does the n+1 th patch file replace the n th patch file.

Yes.

>Why do the patch series 410itn contain static patches, requiring the
>use of the LOADER.EXE,  while the it series do not?
				   ^this should read pt series?

Because the IT series patches haven't yet passed Novell's "integration"
testing.

>Do the static patches in the it series embody all the previous
>patches in earlier versions of the pt series?

I think that they do not because Novell recommends applying both
the latest IT and PT patches.

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

Date: Fri, 29 Dec 1995 03:21:56 GMT
From: "Stephen M. Dunn" <stephen@BOKONON.USSINC.COM>
Subject: Re: Netware 4.10 patches

>Can someone clarify a few points re patches for NW4.10 -
>First a very simple question - are the patch series 410ptn cumulative
>or does the n+1 th patch file replace the n th patch file.

   The n+1th patch file replaces the nth patch file.  The same
goes for all of the other xxxPTn.EXE patch kits for 3.11 and up.

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

Date: Mon, 15 Jan 1996 17:03:18 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: STRTL*.EXE, beware

	You may recall the message earlier today that streams and spxs.nlm
in strtl4.exe killed a server. Well, I'd add that streams.nlm from
strtl3.nlm may well have done so to one of my NW 3.12 servers. I've gone
back to streams.nlm from NLSP material (netwire\novlib\01\ipxrt3.exe),
53,566 07-20-93.
	This suggests that one should treat all strtl*.exe files with much
suspicion.
	In addition, strtl4.exe exists only in the "updates" heirarchy at
this moment, and that heirarchy still suffers from dating every file as
"today." Thus you simply have no way of knowing if Novell has yet again
tricked you by replacing a file with a new one of the same name. Heirarchy
"netwire" is largely free of this strategic mistake. Someday Novell
management must learn to never reissue archived files without renaming the
file and including clear evidence as to vintage and possible replacment of
interior components. Just saying in the docs "this is the latest...," as
has often occurred, is vacuuous.

--------
	I am often asked: which patches/updates to apply, and is it wise to
apply them all. That is a reasonable and important question. My own action
is to apply them all and see what happens, then report on gotcha's. I feel
that most patches are to prevent problems from occuring, so better to be
safe than sorry. Plus, someone needs to try out the new patches. I delay
application onto very important production servers until local testing says
matters seem to be safe.
	We know that Novell issues broken patches now and then, and they
often hide the fact by reissuing the archive file under the same name and
with no further comment. We know that full regression testing to discover
interactions with other systems components is often not done (for reasons
of time if nothing else). We know that some third party NLMs cause big
problems in servers too; virus scanners and tape backup programs come to
mind.
	Touching any xxxITxx.exe or xxxFTxx.exe archived file is playing
with fire. They are not fully tested items, despite what pressures might
exist to get at least something out to customers to solve problems. Be
wary.
	There is a school of thought which says "Don't fix what ain't
broken" and it has much to recommend it. The problem is we are often not
in control of all events and traps will be sprung by mother nature
(evolution).
	To survive one needs to keep careful track of changes made to a
server, and preserve old material in expectation that it may need to be
pressed into service again after a crash. This means making changes slowly
enough to pinpoint the NLM yielding unstable behavior, as say no more
frequently than one change per workday, and to remember/log what changes
were made. Ignoring all updates and patches usually means being overwhelmed
by evolution and existing bugs.
	Joe D.

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

Date:	Mon, 15 Jan 1996 13:57:21 -0800
From:	schoonom@ccmail.sgo.sony.com (Mark Schoonover)
Subject: C.4.5 VLM Version Numbers & Dates

Was at www.novell.com/update and noticed that they released an
updated VLM client kit. New version is 1.20B dated 12DEC95.

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

Date: Tue, 16 Jan 1996 10:02:36 GMT
From: Phil Randal <philr@HWCCES.DEMON.CO.UK>
Subject: Re: STRTL*.EXE, beware

Joe Doupnik <JRD@CC.USU.EDU> writes:
>	You may recall the message earlier today that streams and spxs.nlm
>in strtl4.exe killed a server. Well, I'd add that streams.nlm from strtl3.nlm
>may well have done so to one of my NW 3.12 servers. I've gone back to
>streams.nlm from NLSP material (netwire\novlib\01\ipxrt3.exe): 53,566
07-20-93.
>	This suggests that one should treat all strtl*.exe files with much
>suspicion.

STRTL4.EXE downloaded after January 13 1996 seems to work fine here - the
spxs.nlm has reverted to the earlier (strtl3 and ipxrt3) version.

>	In addition, strtl4.exe exists only in the "updates" heirarchy at
>this moment, and that heirarchy still suffers from dating every file as
>"today." Thus you simply have no way of knowing if Novell has yet again
>tricked you by replacing a file with a new one of the same name. Heirarchy
>"netwire" is largely free of this strategic mistake. Someday Novell management
>must learn to never reissue archived files without renaming the file and
>including clear evidence as to vintage and possible replacment of interior
>components. Just saying in the docs "this is the latest...," as has often
>occurred, is vacuuous.

Agreed.

>	I am often asked: which patches/updates to apply, and is it wise to
>apply them all. That is a reasonable and important question. My own action
>is to apply them all and see what happens, then report on gotcha's. I feel
>that most patches are to prevent problems from occuring, so better to be
>safe than sorry. Plus, someone needs to try out the new patches. I delay
>application onto very important production servers until local testing says
>matters seem to be safe.
>	We know that Novell issues broken patches now and then, and they
>often hide the fact by reissuing the archive file under the same name and
>with no further comment. We know that full regression testing to discover
>interactions with other systems components is often not done (for reasons
>of time if nothing else). We know that some third party NLMs cause big
>problems in servers too; virus scanners and tape backup programs come to mind.

Too true: LIBUP6.EXE plays havoc with Dr Solomon's Anti-virus File Access
Monitor (FAM.NLM) with memory allocation errors when FAM attempts to load.

Fortunately I'm in the process of building up a new server and these
problems haven't affected production servers.

>	Touching any xxxITxx.exe or xxxFTxx.exe archived file is playing
>with fire. They are not fully tested items, despite what pressures might
>exist to get at least something out to customers to solve problems. Be wary.

312IT7, which Novell's web site says should be applied, completely screws
up our servers.

>	There is a school of thought which says "Don't fix what ain't broken"
>and it has much to recommend it. The problem is we are often not in control
>of all events and traps will be sprung by mother nature (evolution).

A new NLM for a third-party product may require a particular NLM which is
not compatible with another third-party product loaded on your server.
What do you do when this occurs?  Scream abuse at your software vendors?

>	To survive one needs to keep careful track of changes made to a
server,
>and preserve old material in expectation that it may need to be pressed into
>service again after a crash. This means making changes slowly enough to
>pinpoint the NLM yielding unstable behavior, as say no more frequently than
>one change per workday, and to remember/log what changes were made. Ignoring
>all updates and patches usually means being overwhelmed by evolution and
>existing bugs.

Well stated, Joe.

Some good news, though.  My limited testing of SMSUP4 with various versions
of Palindrome's backup software shows it to be more stable on our NW 3.12
servers than SMSUP2 or SMSUP3.  But that may not be the case at your site,
folks :-)

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

Date: Tue, 23 Jan 1996 11:36:23 -0800
From: "Robert S. Sfeir" <robert@BUYSIDE.COM>
Subject: Re: novell patches

>We have been advised to install the 4.1 patches to our recently upgraded
>system.  However, after several bloody noses on the system, we are
>reluctant to risk crashing everything.  Does anyone know if this actually
>works?  Installing 28 patches seems like major surgery.

I had the same problem, when I downloaded the PT2 and IT5 files and
installed evrything (a total of 45 patches) the system ran like a charm.
I've been up for 45 days with out a glitch and without having to do any
maintenence on the system!  My recommendation is DO IT, you'll be the
happiest person in the company!

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

Date: Tue, 23 Jan 1996 19:52:38 +0000
From: Richard Letts <R.J.Letts@SALFORD.AC.UK>
Subject: Re: novell patches

>We have been advised to install the 4.1 patches to our recently upgraded
>system.  However, after several bloody noses on the system, we are
>reluctant to risk crashing everything.  Does anyone know if this actually
>works?  Installing 28 patches seems like major surgery.

There are 38 dynamic patches in the current patch kit, and a static patch to
the loader in server.exe

You will probably need to reload your server after applying the current
patch-set, and you MUST have enoughfree disk space on c: to hold a temporary
file created during the static patching of server.exe

We've just installed the patch kit on the crappiest oldest server in
town [a 386/20 ISA system sat in my office that we test such things on
it before causing chaos around the campus]

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

Date: Thu, 15 Feb 1996 12:29:25 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Sbackup

>> SMDR-1.0-10 an internal error has occured.  the TLI transport
>> underlying SMS has fail.
>>
>The TLI [transport Layer Interface] is provided by the streams module.
>I don't have any 3.11 left here; perhaps if you posted the version number to
>the list, together with the cpatches you've applied someone else could help
>further.
>
>[in the meantime, make sure you're running the latest streams]
>
>Richard Letts
------------
	But, a rather large but... strtl4.exe holds a streams module which
crashes my NW 3.12 server every few hours. I recommend bypassing that gem
for the older strtl3.exe (if you can find it) or use what you have. I cannot
speak on the matter for NW 3.11.
	Joe D.

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

Date: Fri, 16 Feb 1996 11:24:51 +0000
From: Phil Randal <philr@HWCCES.DEMON.CO.UK>
Subject: Re: STRTL4.EXE

>Looks like we may have to start swapping console.logs here if this
>looks like being a problem. I put up the contents of STRTL4.EXE 15
>days ago on our main production server (120+ connections most of the
>time, also AppleTalk, NFS, Softrack, Mercury,  were already in
>place) The only error since has been short term memory allocation
>errors but this may be not be related. However, I still haven't
>tracked them down.

We've had to revert to LIBUP5 from LIBUP6 because of apparently
spurious Short Term Memory Allocation errors with LIBUP6.  I say
"apparently spurious", as things work(ed) fine under LIBUP5.

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

Date: Sat, 24 Feb 1996 16:59:28 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: NW 3.1x patch file 312PT7.EXE is available

	Today Novell issued self unpacking file
		updates\nwos\nw312\312PT7.EXE.
	This has the collected patches ("fix" files) to-date. Interestingly,
all the patches are now loaded in startup.ncf, despite the documentation,
and one perceives the intention is to load all the patches rather than
pick and choose. There are several optional patches which should be loaded
in autoexec.ncf.
	The floppy (or equiv) installation method executed by loading
patch312.nlm puts the patch invokation lines at the top of startup.ncf.
I don't like that and I moved them to be below the many SET commands
in that file so the SETs were read before anything loads. Maybe this
is a good idea or not; only Novell knows for sure. Disk drivers etc are
loaded after the patch material.
	Be aware that you may have some of these patch files loaded
via autoexec.ncf from previous patching; please track them down to
avoid conflicts.
	Tried on one server today and all is well so far. Why do I have
this feeling of being tied to a stake in a jungle filled with tigers?
	Joe D.

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

Date: Wed, 28 Feb 1996 08:01:01 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: ...latest patches &  upgrades...

>Good morning ....recently I addressed this group with the question, is
>Netware v3.12 a "patched" v3.11 and what are the reasons for upgrading from
>v3.11 to v3.12.  In the interim I loaded the latest v3.12 patch kit.  With
>this patch kit 52 NLMs are loaded from Startup.ncf.......if my system need
>them or not!.....I must unload two of these patches in the Autoexec.ncf to
>make Inoculan run correctly.

	Apparently the whole virus detector NLM industry has many problems
in servers as the server software evolves. It's difficult to know where the
finger should be pointed; probably at everyone involved.

>  Does Novell believe that v3.12 needs all of
>these patches to run correctly?  This seems a "shotgun" approach at best
>and a case of bad engineering at the least.  I also believe all of these
>NLMs are using quite a bit of memory that should be best used to serve
>files and print requests.

	Cool reason rather than emotion will be more productive here.
There is very little memory consumption, as can be verified by looking at
Monitor. And of course Novell did all this just to annoy you personally.
On the other hand MS products never have bugs, by fiat of Mr Gates; instead
they have version number increases and Service Packs and "buy it again"
messages from users. (GPFs are free and unlimited).
	Joe D.

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

Date: Fri, 1 Mar 1996 17:06:35 UT
From: Dave Kearns <DKearns@MSN.COM>
Subject: New patch files

Note that Novell has released:

Filename: libup7.exe
Abstract:
This file includes the currently released Server C-Library NLM update for
NetWare 3.11, 3.11sft3, 3.12, 4.10.

Filename: 312it8.exe
Abstract:
This file contains the latest operating system test patches for NetWare 3.12.
Included with this prerelease are all patches for all user-versions of NetWare
3.12.  The patches included have not been system tested by
Novell.  For released patches refer to 312PTx.EXE.

Filename: 312pt7.exe
Abstract:
This file contains the latest operating system test patches for NetWare 3.12.
Included with this prerelease are all patches for all user-versions of NetWare
3.12.  The patches included have been system tested by Novell.

Filename: 410it6.exe
Abstract:
This file contains the latest operating system test patches for NetWare 4.10.
Included with this release are all patches for all user-versions of NetWare
v4.10.  The patches included are currently being system tested by Novell. For
the current patches that have been tested by Novell for NetWare v4.10 refer to
the 410PTx.EXE (ie. x will reflect the version of the file.) on COMPUSERVE.
Novell recommends loading ALL patches before contacting Novell for support.

Filename: 410pt3.exe
Abstract:
This file contains the latest operating system patches for NetWare 4.10.
Included with this release are all patches for all user-versions of NetWare
4.10.  The patches included have system tested by Novell. Novell recommends
loading ALL patches before contacting Novell for support.eatures are the
following: New automated installation process.  New patches.txt and
install.txt have been added with this latest update.

Filename: 41mac7.exe
Abstract:
This patch kit contains pre-release update files for NetWare for Macintosh
4.10.

Filename: 41nds7.exe
Abstract:
PLEASE REVIEW ALL DOCUMENTATION CONTAINED IN THIS FILE BEFORE PERFORMING ANY
UPDATES. This update contains version 4.97 of DS.NLM  and version 4.32 of
DSREPAIR.NLM for NetWare version 4.10.   If upgrading from NetWare version
3.1x, you still will benefit by applying the new DS.NLM prior to upgrading.
This file may be updated occasionally as new versions of DS.NLM are released.
As new DS.NLM 's are released the naming format will be 41NDSx, where x
denotes  the revision of the patch file.

Filename: 41nm1.exe
This file contains update name spaces and vrepair for NetWare 4.10. These are
pre-release files.

Filename: dsmnt3.exe
Abstract:
DSMNT3.EXE contains an updated version of DSMAINT.NLM (version 4.92).  This
NLM was originally provided with the DS Enhancement pak distributed in July
1995.

Filename: dsrp41.exe
Abstract:
DSRP41.EXE contains DSRepair version 4.32 for Netware 4.1.   This version of
DSRepair supercedes any previous release of DSRepair.NLM

Filename: os2c4.exe
Abstract:
This file contains the latest field test patches for the v2.11 NetWare OS/2
Requester as of 2-6-96.  These patches have not been submitted to Novell
system test.  Applying these patches will get you to the current code base.

Filename: rplkt3.exe
Abstract:
RPLKT3.EXE which contains Remote Program Load files for NetWare v2.x, v3.1x,
v4.x.

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

Date: Thu, 21 Mar 1996 08:01:51 +0000
From: Garry J Scobie Ext 3360 <GSCOBIE@ML0.UCS.ED.AC.UK>
Subject: NLM Version list updated

The NLM version list for 3.12 has recently
undergone a major update

http://mft.ucs.ed.ac.uk/novell/techsup/nlmver.htm

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

Date: Mon, 15 Apr 1996 21:56:19 -0500
From: Jerry Shenk <jas@COMTECH.NET>
Subject: Re: NetWare Patch Observation and Suggestion

>>Why does it have to be the case that we have to look for and apply each
>>specific patch individually?  This can be a painful process, prone to likely
>>omissions.
>
>You got a point there.
>Seems to me that Novell has a good working INSTALL util.
>If they would modify that a bit so that it is able to do patching
>with any number of downloaded patchfiles Novell would make me very happy.
>Usually a combined number of patchfiles work fine. But I like to allways
>have the option of applying patches on a file per file basis
>(in case of trouble).

I've started a listserver to this end.  I ask that the ONLY thing
posted on it is the location(s) and descriptions for new patches.
There is very little activity (intentionally) - discussions about the
patches can be held here.  Feel free to post the NSD stuff to the
list also.

If you want in, just send a message to
nwpatch@comtech.net with the subject being 'subscribe'.

I'm courting offical Novell participation but if we have a couple
hundred tech's in the field posting new patches, that will be nearly
as good.

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

Date: Tue, 16 Apr 1996 08:54:33 -0700
From: Donovan Bray <dbray@BASS.CUESTA.CC.CA.US>
Subject: List of Patch Updates

For anyone interested Novell IS maintaining a list of suggested
upgrades/patches for Netware 3.11 and higher, including hyperlinks to
download them as well.

http://netwire.novell.com/FileUpdt/patlst.html

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

Date: Sun, 21 Apr 1996 00:56:42 -0400
From: Debbie Becker <dbecker@clark.net>
Subject: LIBUP8

There's now a LIBUP8 available on the novell ftp site.
Check the osfiles area under nw410. File is dated 4/18/96.

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

Date: Mon, 22 Apr 1996 16:38:31 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Netware 4.1 NDS - Unknown objects

>I've just spent an entire weekend helping a client get their network back
>up and running following the loss of a hard drive.
>
>As it turned out, there was no backup of the NDS available at all (they had
>only recently moved to 4.1).  Basically we restored all of the data using
>Arcserve 5.01g and then re-created a new NDS from previous documentation.
>Without an NDS, the trustee file assignments came back with objects which
>didn't co-ordinate with valid NDS objects.  No dramas - I thought this would
>happen.  Hence you can do a RIGHTS /T in various directories and see UNKNOWN
>OBJECT with rights assigned to the file system.
>
>I was not overly concerned but now I want to clean them up as I suspect they
>are causing some minor problems.
>
>When I run DSREPAIR and do a Unattended Full Repair, it reports 80 errors on
>VOL1: and then aborts.  I then tried Advanced, Check Volume Objects & Trustees
>and it gets to approximately the same spot (probably identical) and comes back
>with a "DSREPAIR-4.10-019: Could not read from file: "EMPTY.TMP" offset
>0001F64E.  Program execution could not continue normally."
>
>I then searched for this file on VOL1: and it does not exist.  I also purged
>all deleted files from the problem but it keeps stopping at the same place.
>Does anyone have any suggestions?
>
>The client is presently running DS 4.89c and DSREPAIR 4.29.  Short of trying
>later versions, which I have downloaded but not tried, can anyone shed and
>light on this?  Does anyone know where to find a comprehensive listing of all
>Novell error and warning messages?  I have already done a number of searches on
>the Novell KB on the Net without much success.
-------------
	I'm sure Debbie will have some encouraging words of advice. In the
meanwhile I'll offer two comments about comfort in the future.
	In Green River the SMS group has created a safe/full backup anything
to tape and restore it cleanly/safely facility. One can backup remote
servers, partitions, sub/supersets etc via IPX from a given server. The
ident numbers are kept intact too. TSA410 and TSANDS do the work. It's
impressive.
	Preferred Systems Inc, the folks who make DS Standard, have a new
product for Green River which tracks NDS access rights: who has them, whence
they got them, whence the giver got them, and so on. It too looks like
exactly what is needed to maintain a sane NDS network. I have no idea of
what the price will be.
	Expected release date of Green River is late summer or early fall.
	Joe D.

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

Date: Thu, 2 May 1996 21:54:01 UT
From: Dave Kearns <DKearns@MSN.COM>
Subject: Re: Update Notify via E-Mail how?

>Sometime ago there was an rumor, that it is possible to get
>an update-notify from Novell via E-Mail. Every patch and
>every new file on Novell-Servers for users placed an any
>novell-servers should be notified.
>Is there any way to get it and if how?

Novell doesn't email this info, but there's a new email notification
service due to start soon. Here's the info on it:


    WELCOME to the NetNotify Bulletin and Notification mailing list!

The purpose of this mailing list is simple: to bring time-sensitive and
critical information right to your desktop on a routine basis.

Did you know that there is a new exam currently in beta for your CNE
designation that you can take for free?

Did you know that ABC Networks is offering a free widget with every
copy of their Alphabet NOS purchased before the end of the month?

Did you know that there was a critical patch available for your server
that will resolve abend situations?

Although these are hypothetical questions, they are precisely the types
of issues that NetNotify will address. Each edition of NetNotify will
bring updates, right to your desktop, on issues such as:

- Patches/Fixes that have recently been released.

- Announcements for new networking related hardware/software.

- Announcements for promotions being offered by the top
  vendors in the networking community.

- Announcements for upcoming conferences.

- and much, much more....

As a subscriber to NetNotify, much of the leg work and research is
already done for you. Just sit back, relax, and read a friendly,
informative email bulletin at the comfort of your own desk!

FREQUENCY OF POSTINGS

The NetNotify bulletins will be sent out initially on a bi-weekly
basis, eventually switching to a weekly publication.  Mailings will
be performed on the weekend so, assuming your Internet email is
fairly stable, you can expect a newsletter waiting for you on Monday
morning!

The first edition of NetNotify will be available on Monday, May 6th!

SUBSCRIBE/UNSUBSCRIBE INFO

An individual may subscribe to NetNotify at any time by sending an
email to NETNOTIFY-REQUEST@KI.NET.  In the body of your message, type
"subscribe", without the quotes, and you will automatically be added
to the distribution list.

To unsubscribe to NetNotify, send an email to NETNOTIFY-REQUEST@KI.NET
In the body of your message, type "unsubscribe", without the quotes, and
you will automatically be removed from the distribution list.

REPORTING PROBLEMS

Should you encounter any problems receiving your subscriptions, send an
email to NETNOTIFY-LISTMASTER@NETCENT.COM with a full description of your
problem.

ATTENTION VENDORS

If your organization is holding a special promotion or has a product
announcement that you feel the subscribers of NetNotify would benefit
from, send a message to NETNOTIFY-MARKETING@NETCENT.COM with the
details

Copyright Information - Anyone can subscribe to NetNotify, but under
no circumstances may editions of NetNotify be distributed either
publicly or privately, in whole or in part. Should you feel that someone
you know may benefit from a subscription to NetNotify, please feel free
to pass the subscription information on to them.

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

Date: Fri, 31 May 1996 13:24:07 -0400
From: Rick Troha <rickt@NWSUP.COM>
Subject: DS.NLM v5.01 Now Available

For those running NW4.1, DS.NLM v5.01 is now available in file
41NDS9.EXE.

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

Date: Wed, 5 Jun 1996 10:30:38 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: New files in "updates"

	Two new files are present in the Novell "updates" heirarchy
today: SMSUP5.EXE has new TSA<whatever> files, and NPTR95.EXE is updated.
	Joe D.

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

Date: Tue, 18 Jun 1996 13:21:59 +0100
From: Phil Randal <philr@HWCCES.DEMON.CO.UK>
Subject: STRTL5 SPXS.NLM Crashes NetWare 3.12

Novell have done it again, folks.

The SPXS.NLM included in the 3.1x subdirectory is the NW4.1 version,
and will crash a NW3.12 server in the following situation:

Source server: NW3.12, strtl4 applied.
Target server: NW3.12, strtl5 applied.

Using Palindrome Storage Manager, I restored a file from the source
server to the target server.  The target server crashed and entered
the debugger.

Reverting to STRTL4 solved the problem.

OK, Novell made an honest mistake, but:

The first release of STRTL4 also had the NW4.1 version of SPXS.NLM,
with the results as described above, which I also reported to this
list.

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

Date: Fri, 26 Jul 1996 18:46:10 -0400
From: PowrTekSys@aol.com
To: netw4-l@bgu.edu
Subject: Re: Patch Question

>Will the command PATCHES tell me if they've been applied, or will I have
>to dig deeper?

Maybe; maybe not. Comparing files, dates and versions is your best bet. We
keep a list on each server that shows all this information.  CONFGNUT.NLM
will create this list for you.  It is at:

	ftp://ftp.novell.com/pub/updates/nwos/nw410/tabnd2.exe

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

Date: Tue, 20 Aug 1996 11:56:54 +0100
From: Phil Randal <philr@HWCCES.DEMON.CO.UK>
Subject: 312pt9 now available

Novell have just (19 August 1996) released the NW3.12 patch update
312pt9.  It is available from

  ftp://ftp.novell.com/pub/updates/nwos/nw312/312pt9.exe


The changes from 312pt8:

1: A new loader.exe, which fixes the year 2000 problem.

2: dbldebfx.nlm and ntbiofix.nlm have been withdrawn.

3: a new version of the previously withdrawn zerobfix.nlm has
appeared.

4: macnmfx.nlm and npapatch.nlm have been updated.

5: patch312 now installs the patches in c:\server.312\patches\312pt9

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

Date: Wed, 21 Aug 1996 07:00:00 GMT
From: "Forrest H. Swick" <fswick@MAIL.UNIVNORTHCO.EDU>
Subject: Re: 4.1 Patches

>As a followup to Tony's note, I would appreciate the same
>information for a 4.1 server that hasn't been updated in a year.
>I should note that I've received conflicting opinions about whether
>to apply patches from our more NetWare-aware sysadmins....some
>believe if the server is stable, leave it alone.

Following is the Patches.txt file that is in the 410PT3.EXE off of
netwire. It states that "All OS patches should be loaded for the
respective OS, no exceptions."  Maybe you should print this out for
your more "Netware-Aware" Sysadmins.

I've just installed my 1st 4.10 server and have applied all patches*
(except for LANDR7.EXE -- read why below).  The *.txt files are
particulary interesting in that they tell you exactly why you should
install the patches.  You should check them out.

*In the LANDR7.TXT file it states: "The Novell LAN drivers listed
are not backwards compatible with previous MSM.NLMs or TSM versions.
However LAN drivers written to the 3.20 Assembly Specification are
compatible with the new MSM.NLM and TSM versions."  I have not
researched as to whether my server NIC LAN drivers are written to
the 3.20 Assembly Specification.


						  January 8, 1996

		NETWARE OPERATING SYSTEM PATCHES

Anyone that has called Novell Technical Support with a SERVER
problem has been asked if they have the patches loaded.  This
document will address what the patches are and why Novell insists
they be loaded on your File Server.  There is also a Q/A of the most
commonly asked questions about the patches.

The patches fix minor bugs in the SERVER.EXE code, they do not
re-architect the code. They will fix many problems that an unpatched
server may have and will keep the server up longer.  All OS patches
should be loaded for the respective OS, no exceptions.

Some Novell customers are nervous to load any OS patches unless they
are assured that it fixes their exact problem, and then they will
only load that specific patch.   Since version 3.12 and above Novell
has architected the patches to work together and therefore ALL
patches should be loaded.

The patch kits referred to in this document are a combination of PT
and the IT files.  Novell recommends loading both of these files on
the respective version of the OS.  Loading all patches enables
Novell Engineering to resolve problems faster, since time is not
spent debugging old problems or verifying that a problem is fixed
with a specific patch.  In order to get your critical server issues
resolved in a timely manner, load ALL the patches before calling
Novell Technical Support.

Who should load the OS patches?

EVERYONE.


Why should the OS patches be loaded?

The OS patches contained in the "PT" and "IT" patch kits fix known
problems with the SERVER.EXE file.  NOT loading these patches leaves
the server exposed to known problems.


Why should ALL OS patches be loaded?

The OS patches for 3.12 and the 4.x versions of NetWare have been
engineered to work together, unlike the 3.11 patches.  The 3.11
patches are being re-engineered to function the same way.  Without
all of the patches loaded the system is exposed to known problems
that have already been fixed.


What is the LSWAP.NLM and LSWAP.EXE in the 4.10 patch kit?

The LSWAP is a utility used to exchange the LOADER.EXE contained in
the patch kit with the one contained in the SERVER.EXE.  The new
LOADER fixes various problems with PCI machines as well as other
types of machines.  It is considered a patch and needs to be loaded.
Read the Readme file in the patch kit for an explanation of how to
exchange the LOADER. Running LSWAP will update the SERVER.EXE and
cause it to get the current date and have a slightly larger size.


If the Server is running fine, should the OS patches still be loaded?

Yes.  This will avoid known problems with the SERVER.EXE.  This will
also place you one step ahead in the troubleshooting process.  If you
call Novell Support with a server problem the first thing they are
going to have you do is load the patch kits.  Having ALL the patches
loaded will expedite the troubleshooting process.


What are the ramifications of loading only specific OS patches?

When only loading specific patches, you are only fixing part of the
problems. This still leaves the server susceptible to other known
problems.  When troubleshooting a server problem with Novell
Technical Support,  you will be asked to load the remainder of the
patches, including the IT patches.   Loading both the PT and IT files
will make your server more stable and allow Novell Technical Support
to solve your critical server problem in a timely manner.


What is the difference between "PT" and "IT" patches?

A patch kit for a particular OS consists of a "PT" and an "IT" file.
For example as of January 8, 1996, the current patch kit for 4.10
consists of 410PT2.EXE and 410IT5.EXE.  The PT "Passed Test" patches
are patches that are older, meaning that they were the first problems
found and solved.  The IT "Internal Tested" patches are problems that
have been discovered and solved later than the PT patches.  Before an
OS patch gets into the IT file it has been tested and loaded on
servers throughout Novell on both production and test servers. These
patches have also been loaded on the customers server, who the patch
was written for, and it has fixed the problem. ALL PATCHES IN BOTH
THE PT AND IT FILE HAVE SOLVED CUSTOMER PROBLEMS AND HAVE BEEN DEEMED
NECESSARY BY NOVELL ENGINEERING.


How much memory do the OS patches take when loaded?

With the amount of memory today's servers have the patches take up an
insignificant amount of memory. Loading the 410PT2 and 410IT5 patch
kits take up 400 KB of memory.  A very small price to pay for server
stability.


Do the OS patches affect performance?

Yes.  They allow your server to stay up.  Some patches are
specifically designed to improve Server performance.


All the patches have been loaded on the server and now it is
ABENDing.  What went wrong?

Troubleshoot the problem not the symptom.  The PATCHES DO NOT CAUSE
PROBLEMS, THEY FIX THEM.  If there is a problem with a patch causing
a server to ABEND it will be fixed long before they get into either
the PT or IT patch files.  OS patches are loaded on Novell corporate
server as well as Test servers throughout Novell before they go into
the PT or IT kits.  Also, before they get to the IT file they have
been tested by the customers who the patch was written for and it has
fixed the problem.


Where are the PT and IT files located?

The PT and IT files can be downloaded from either CompuServe or the
Internet.  The IT files are located in the NSD area and are hidden
but you can download the file by using the name. It should be 3
revisions higher than than the PT files.   For example:   410PT2.EXE
and 410IT5.EXE.


NOVELL REQUIRES THAT BOTH THE PT AND IT FILES BE LOADED ON THE SERVER
BEFORE ANALYZING A CORE DUMP OR TROUBLESHOOTING UTILIZATION OR
ABENDING ISSUES.  IN ADDITION, ON 4.X SERVERS THE MEMORY PARAMETERS
"ALLOW INVALID POINTERS", "READ FAULT EMULATION" AND "WRITE FAULT
EMULATION" NEED TO BE SET TO "OFF" BEFORE ANALYZING A CORE DUMP OR
TROUBLESHOOTING UTILIZATION OR ABENDING ISSUES.

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

Date: Thu, 29 Aug 1996 14:11:43 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: NetWare 4.1 TCPIP.NLM

>We recently migrated a 3.x server to 4.1. This seemed to go well except
>for the TCPIP NLM's. They will not load. The error appears as follows
>
>  Loader Cannot Find Public Symbol CSL_ApplGetGroupNameByBoard
>  Loader Cannot Find Public Symbol CSL_Appl...
>  Loader Cannot Find Public Symbol CSL_Appl...
>  Loader Cannot Find Public Symbol CSL_Appl...
>  Loader Cannot Find Public Symbol CSL_Appl...
>
>  Load File Referenced Undefined Public Symbol
>
>  TCPIP.NLM Could Not Be Loaded
>
>I used the given patches from the NetWare patch page, but the problem
>persists. I could not find any answers in the documentation. Has anyone
>had a similar experience? Also is there any known documentation on the
>net that I could be pointed to for further information? Thanks in
>advance for your assistance
-----------
	Best to check some version numbers and date stamps. Here are a
few on a fully patched NW 4.10 server, no MPR, no DHCP, no nutt'in:

TCPIP    NLM       393,157 11-08-94  10:07a     Version 3.00b
TCPIP    PDI           180 06-29-93   6:55p
TCPCFG   NLM       170,851 10-19-94  12:53p
TCPCON   NLM       222,424 10-18-94   4:49p
INETLIB  NLM        34,199 10-19-94   1:26p
INETCFG  NLM       330,230 02-02-95   5:25p
ETHERTSM NLM         9,278 10-17-94  10:11a     Version 2.33
MSM      NLM        20,263 08-23-94   2:33p     Version 2.32
CLIB     NLM       217,743 04-15-96   2:35p     Version 4.10h
CSLSTUB  NLM         3,122 10-19-94   9:40a     Version 2.00a

	You can also try updates\nwos\nw410\TCPN01.EXE, but as the doc
excerpt below indicates, figuring out what to use or ignore is difficult.

 The following TCPIP.NLM versions are included:
 ----------------------------------------------
 - 2.02M; only for NetWare 3.11 servers not running NetWare Connect.

 - 2.75; A TCPIP which has not been officially tested for NetWare 3.11,
 however many NetWare sites have reported successful use of this NLM.

[Yeah, right, but that leaves open everything else...  jrd]
[Grammar: for NetWare 3.11 but has not been tested officially...]

 - 3.10D; for ALL servers running MultiProtocol Router 3.1 (including
 servers running MPR 3.1 and NetWare Connect together).  ONLY to be used on MPR
3.1 servers.

 - 3.0F; only for NetWare 3.12 servers that DO have a version of MPR earlier
than 3.1, loaded (or both an early version of MPR and NetWare Connect).

 - 3.0H for NetWare 3.12 and 4.1 servers that do NOT have NetWare Connect, MPR,
Web Server or DHCP loaded.

	Joe D.

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

Date: Thu, 3 Oct 1996 07:49:45 -0400 (EDT)
From: Dennis Large <wdlarg01@homer.louisville.edu>
To: netw4-l@bgu.edu
Subject: Re: Appropriate server operations

>With these information in mind, I want some feedback on how other
>net. admin. handles these situations.
>
>How do you handle notifying your users of system upgrades and
>maintenance?  SiteMeter requires that the log files be emptied
>periodically.  This process requires unload SiteMeter's two NLMs. To date,
>unload these NLMs (after close of business), emptying the log files, and
>loading the NLMs has not caused any problems.  Since this does not cause
>any problems, I do not send out advanced warning when this happens.  How
>do you handle this?  And for my final question, what are your opinions on
>the fresh reboot after updating NLMs (with the above scenario in mind)?

1) rebooting after most upgrades of that nature is recommended. It's easy to
miss the smaller autoloaded modules that aren't necessarily named. Or in a
case like clib, you have to unload so much to get to it, it's just simpler.

2) I try not to do system stuff during the week as much as possible. If
something has been proven reliable, then I can be a little more flexible.

3) We have weekly PM scheduled at which time we have full reign, but are
expected to be 7x24 otherwise. ergo #2.

4) we're still trying to decide on the best method for notifications. Email
is about it right now.

5) I hope you can find SOME way to tell your boss that his non-communication
greatly hampers your ability to perform your job in a professional manner,
as it seems you very much want to do.

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

Date: Tue, 22 Oct 1996 09:58:55 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Libup9 has returned to the archives

	LIBUP9.EXE has returned. A listing of files within it looks like
the list below. Aside from LIBUP9.TXT I don't notice any changes from the
previous issue.
	Joe D.

Directory of G:\

ICMD     MSG         5,232 08-31-94   8:48a
ICMD     NLM        15,850 05-10-95   3:48p
PI_INIT  NLM         1,491 03-08-96  11:38a
INSTALL  DOC        18,889 03-26-96   3:19p
LIBUP9   IPS         4,256 08-26-96   1:30p
INSTALL  EXE        40,196 04-28-94   5:39p
CHANGES  312         5,113 01-08-96   9:34a
LIBUP9   TXT         7,278 10-21-96   9:34a
4        X   <DIR>         10-22-96   9:48a
3        X   <DIR>         10-22-96   9:48a

Directory of G:\3.X

CLIB     NLM       344,994 12-20-95  11:30a
NWSNUT   NLM       175,546 10-17-94   2:14p
MATHLIBC NLM        16,832 12-20-95  10:27a
AFTER311 NLM        14,952 10-10-95   6:19p
MATHLIB  NLM        12,458 12-20-95  10:27a
A3112    NLM        16,268 10-10-95   6:19p
NWSNUT   MSG         2,984 04-04-94   8:42a

Directory of G:\4.X

CLIB         <DIR>         10-22-96   9:48a
DSAPI        <DIR>         10-22-96   9:48a
MSG          <DIR>         10-22-96   9:48a

Directory of G:\4.X\CLIB

CLIB     NLM        81,464 08-02-96   8:28p
FPSM     NLM        16,547 08-02-96   9:02p
THREADS  NLM        84,984 08-02-96   8:10p
REQUESTR NLM        46,175 08-02-96   8:36p
NLMLIB   NLM        88,829 08-09-96   1:00p
NIT      NLM        48,151 08-02-96   8:56p
MATHLIB  NLM           417 10-06-95   3:22p
MATHLIBC NLM           426 10-06-95   3:21p

Directory of G:\4.X\DSAPI

DSAPI    NLM           620 07-01-96  11:15p
AUDNLM32 NLM         9,219 07-31-96   7:27a
CALNLM32 NLM        89,016 07-31-96   7:26a
CLNNLM32 NLM         5,248 07-31-96   7:22a
CLXNLM32 NLM         3,699 07-31-96   7:27a
LOCNLM32 NLM         4,128 07-31-96   7:22a
NCPNLM32 NLM       103,363 07-31-96   7:24a
NETNLM32 NLM       152,806 07-31-96   7:27a
DSEVENT  NLM         1,983 07-19-96  12:28p

Directory of G:\4.X\MSG

CLIB     MSG         4,275 07-24-96  11:33a
FPSM     MSG           543 07-24-96  12:27p
THREADS  MSG         8,821 07-24-96  11:28a
REQUESTR MSG           498 07-24-96  11:42a
NLMLIB   MSG         3,635 07-24-96  12:56p
NIT      MSG           957 07-24-96  11:54a

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

Date: Tue, 22 Oct 1996 20:47:05 -0700
From: "Robert S. Sfeir" <robert@BUYSIDE.COM>
Subject: Libup9... Attention!

I ran the install.exe that comes with Libup9 with the /n (no action)
parameter, and looked at the log file.  It only installs files for Netware
3.x NCP servers... It does not install anything for netware 4.1!... At
least it didn't pick up any candiate files for Netware 4.1 although I know
some of those files were reverted back to the LIBUP8 files.

As a matter of fact, if you click on the New files for the week button at
support.novell.com, the LIBUP9 only comes up under Netware 3.X...  You make
the call!

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

Date: Wed, 23 Oct 1996 16:37:05 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Patches for an old 3.11 setup

>We've got a small shop (16 users) w/ a few 3.11 and 3.12 servers
>running on 3/486s (16-32 meg) w/ generally no problems.  Our main app
>is run on unix which we use RS-232 terminal connections to get to, so
>Novell is truly just a file&print server. Up till now,
>our "not broke, don't fix" attitude has kept us from applying any
>patches to the original systems.  Well, recently I got a hold of
>the config.nlm program, which seems pretty nice, esp. w/ the win95
>viewer, seems like a reasonable way to go about patching etc but ...
>it only ran on our 3.12 server listing a number of outdated nlms,
>the 3.11 servers need to upgrade clib et alias.  However,
>I'm sort of afraid to go out and apply, say libup9 to my setup as
>it stands.  All the talk of what could/has gone wrong elsewhere
>w/ versions of clib etc. conflicts in makes me downright nervous.
>So, could anybody weigh in w/ what sort of risk we'd be taking or
>what'd be the safest path to get things back up to date?
------------
	We go through this about twice a year: should I patch or not.
	The bottom line, put first, is the problems will be yours to
sort out, whether a patch or lack of a patch causes trouble. If you call
Novell Tech Support their standard advice is get fully patched and call
them in the morning.
	Sharp managers lag behind a little and scan reports for indications
of trouble. Discount many reports as interaction between other components,
usually not detailed. Note the other reports if persistent. Eventually keep
up to date. Recall that it's your particular system which may or may not
react well to changes, and we can't predict how it will respond.
	Since I often make changes right away, to know if troubles will arise,
I can't put myself in the category of sharp managers; wounded and bandaged
managers is my group.
	Sharp managers always preserve the original environment in case they
need to retreat from a change. In some cases a full backup is wise before
adjusting things. Ah, I do fit in here.

	Libup9 has caused no trouble here. I don't know the kernel of the
rumors going round, but one guesses they involve interaction with third party
programs (say Arcserve and/or virus scanners) or particular hardware. But I
have no information to relay.
	In the end it's your call and your neck, whether you act or just
cross your fingers and hope. Gee, it could be worse where there are big
problems and no fixes (Windows, for example).
	Joe D.

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

Date: Wed, 30 Oct 1996 17:44:17 +1000
From: Rod Stemp <ucdelai@ULTRA.NET.AU>
Subject: FAQ as a Windows Help File

The latest version of the FAQ in Windows Help file format is available at

	ftp.ultra.net.au/pub/users/novell/nvfaqhlp.zip

It now has a completed search facility based on keywords from each topic
heading.   It still requires further massaging for example I have VLM showing
as VLM, VLMs and VLM's.   I will exorcise all these demons over the coming
weeks however if you find any please email me.

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

Date: Fri, 8 Nov 1996 13:56:22 GMT+0100
From: Chris Teuben <C.A.Teuben@RC.RUG.NL>
Subject: Memory allocator errors

After applying LIBUP6, 7, 8, or 9 memory errors appear:
"Cache memory allocator exceeded minimum cache buffer left limit." and
"Semi-permanent memory allocator is out of memory: 1 semi-permanent
 memory allocation request failed"

This is a cosmetic error that will exhibit itself when initially loading
message files for NLM's that require A3112.NLM and/or AFTER311.NLM. The
error will only be displayed when initially loading the module.
Novell advises to ignore the error for now. It will be fixed in future
updates to the file. It does not cause any server problems.

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

Date: Sun, 17 Nov 1996 17:13:32 +1100
From: Adrian Moore <C-Moore@MAIL.DEC.COM>
Subject: Re: 4.10 Patch Set (On SFT-III)

>As we ready to deploy our next 4.10 server (it will be our first
>SFTIII)
[snip]

Recommendation: Get a contractor in who has installed SFT-III if you
have any nerves at all. You run a 24 hour site, proud of your uptime?
Spend some dollars to ensure the machines are installed "like a bought
one" - i.e. vanilla configuration with no shortcuts. The bonus is that
someone with some experience is on hand to provide immediate
troubleshooting if things go "off the rails".

General recommendations: Apply the suggestions from TID 2905856. Also
ensure that the IOEngines have about 25% of the physical memory
allocated to them (The only place I've seen this documented is on
NSEPro / Support Connection in the SFT-III Lab, so I'll document it
here ;] )

Your issues:

>1)  The 410PT?.EXE has gone from 410PT3 to 410PT6 in 4 months.

My thought: 410PT6.EXE contains a considerable set of patches for SFT
III servers. The under-the-table information is that this patch was
basically released because of SFT-III. Apply 410PT6 to you SFT-III
server after installation.

>2)  The DSAPI.NLM (7/2/96) has changed, somehow, dramatically - going
>from 85,032 bytes to 620 bytes.  I assume it's been broken out as there
>are a few new NLMs that come with it - AUDNLM32.NLM, CALNLM32.NLM,
>CLNNLM32.NLM, CLXNLM32.NLM, DSEVENT.NLM, LOCNLM32.NLM, NCPNLM32.NLM, and
>NETNLM32.NLM.

NetWare 4.11 has prompted this "modular" architecture in NetWare
4.10.

>3)  While on LIBUP9 - CLIB has shrunk dramatically as well and now
>included are the new NLMs NIT.NLM, NLMLIB.NLM, REQUESTR.NLM & THREADS.NLM.

Modularity again - allows for snap in changes to part of the release.
Check the threads on this listserv regarding problems with LIBUP9.EXE
though. LIBUPA.EXE is available on
ftp://ftp.novell.com/pub/netwire/nsd/libupa.exe as a pre-release kit,
so steer clear of it too. One of the other recent postings suggested
sticking with LIBUP8.EXE until the dust settles... but LIBUP9.EXE has
been rolled out onto a critical SFT-III site by me with no apparent
side effects. Remember: These servers are only performing file & print
serving, so the relevance of CLIB should reduced greatly.

>4)  DSVIEW.NLM from DSVU41.EXE is no longer in a recommended patch.
>Was it's fix done elsewhere?  Did it come with 4.10 stock?

DSVU41.EXE went through a period of not working with DS 5.01. I think
it was updated, but the essential point is that it was never a patch,
it is a utility for looking at some of the nuts & bolts of your NDS
database. It shipped after NetWare 4.10. It is not required.

>5)  TCPN02.EXE's section for my 4.10 server is the same as the TCP41B
>used on the production 4.10 servers except TCPCFG.NLM has not been
included.  Is this functionality picked up elsewhere or dropped?

Over to someone else for this one. TCPCFG is called from INETCFG so it
is still required. I think I don't understand what issue you are
describing though. I think you mean that TCPN02 doesn't include
TCPCFG. TCPN02 was released to address the confusion over the various
different versions of TCPIP.NLM. Looking over the kit it seems as
though you would only use the version of TCPCFG in TCPN02 if you had
to use the verson 2.75 or 3.00F TCPIP.NLM. The way TCPN02 has been
positioned is that it only offers a subset of the IP kits, and so you
would use TCP41B unless you are using an affected product (according
to the table) which would then require applying those NLMs (and ONLY
those NLMs) from the relevant directory in TCPN02. I've said the same
thing a couple of times there, so maybe another posting will be
clearer.

>6)  41RTR3.EXE is now only listed as an NLSP protocol update (besides
>the fact that it is not recommended for my SFTII configuration).  It was
>recommended back when my now-production 4.10 servers were deployed.
>The question goes back to interoperability again.  Will an SFTIII server
>in the same tree with 4.10 servers patched with 41RTR3 interoperate
>successfully?

Yes, 41RTR2.EXE is still the SFT-III compatible kit. 41RTR2 includes
NLSP support. And NLSP is designed to interoperate with RIP servers
anyway.

>I know the knee-jerk reaction to most of these issues is to patch all
>my 4.10 servers to the same rev.  Folks, I run a 24-hour shop whose
>downtime is
[snip]

That's the usefulness of the listserv, isn't it? However, you can't
sue a listserv (at least I hope not) so you could check out the local
Novell office to determine whether their Novell Consulting Services
are available at a reasonable rate to install and optimally tune the
servers. There is always the danger that even though your server is
functioning, it may never really be performing well due to some
oversite at install time. Additionally - the last time you want to
find out that an SFT-III configuration parameter is set wrong is when
a department has been brought to its knees, so make certain you set
time aside to "break" the box using the inbuilt test parameters, or by
stressing the MSEngine before rollout.

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

Date: Wed, 27 Nov 1996 21:53:40 +1300
From: "Baird, John" <BAIRD2@WHIO.LINCOLN.AC.NZ>
Subject: JRButils V3.0 released

JRB300A.ZIP is now available at the following sites:

	ftp://netlab2.usu.edu/apps/jrb300a.zip

	ftp://ftp.let.rug.nl/jrbutils/jrb300a.zip

	ftp://tui.lincoln.ac.nz/jrbutils/jrb300a.zip

	ftp://risc.ua.edu/pub/network/misc/jrb300a.zip

V3.0 comprises 36 bindery based utils in Part A, 32 bindery based utils
in Part B and 55 NDS aware utils in Part C. The majority of the development
effort for V3.0 has gone into Part C, but there are a number of fixes and
minor enhancements in Part A plus four new programs. They are:

o Vol_info: displays volume information including those statistics available
  under servman.nlm on NW 4.x.

o Requests: Continuously monitors bytes read, bytes written and total NCP
  requests by workstation under NW 4.x, and displays values for the 20
  workstations generating the most requests since monitoring began.

o Cl_type: Detects whether NETX, VLMS or CLient32 are in use and sets an
  error level.

o Jberrmsg: Pass it a NetWare error code (e.g. 0xFDA6 or -634) and it will
  look it up in JRBERR.MSG (which is used by all of JRButils) and display
  a one line description.

Run JRBGUIDE for details of what is new and what has been fixed. Please
report any problems, and suggestions for new features are always welcome.

Updates have already been shipped to sites which purchased software only,
and there will be a delay of 2-3 weeks while I await mass production of
CDs before updates are shipped to sites which have bought software and
documentation.

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

Date: Tue, 10 Dec 1996 09:40:12 -0600
From: "Lindsay R. Johnson" <lrj5@IAONLINE.COM>
Subject: Re: Patch Order Installation

>This may be a no-brainer, but I'm new to installing new servers.
>After installing NetWare OS, is there any preferred method of
>installing the plethora of patches?  With MS, it is latest Service
>Pack and then the few post-SP patches in chronological order.  Of
>course Novell separates the patches into OS, client, and other
>categories which could complicate patch installing.

I LOGIN to the new server, copy in all my prepared patches, and run the
410PT? patch of the month.  When it reboots my patches are in place!  3.12
works about the same way.

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

Date: Tue, 24 Dec 1996 13:12:04 -0600
From: Bruce Sach <sach@MR.Net>
To: netw4-l@bgu.edu
Subject: Re: server patch info' needed -Reply

>All of the server patches i've done have been cake... There is a utility
>that will tell you what has been done to your server (two actually)...
>config.nlm and confgnut.nlm... they will produce a text file in the
>system directory called config.txt.  You can also get a program called
>config reader from the novell web site that will tell you what has been
>done and what drivers you need to update.  Also has general suggestions.

The latest version of config reader is Internet saavy.  It can download
files from a Novell controlled FTP site, but it will only run on Win95
machines

	http://support.novell.com/cgi-bin/search/download?/pub/updates/nwos/nw312/cfgrd3.exe

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

Date: Mon, 3 Feb 1997 15:36:44 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Joe, 4.11PT1 OK?

>Joe I know you posted a warning about the 411PT1 file, and it seems that
>Novell has corrected the read me file but the size is still the same.
>Anything new you'd like to add before I jump into it?
------------
	You'd think I live in Utah, in Provo to be precise, but that's not
correct. I live 140 miles north of those characters but still in Utah.
	Yes, Novell improved the docs on 411pt1. I have installed it without
grief.
	Please do notice what is happening with this material: patches are
now rolled into a single file, and most importantly they are applied by the
loader as server.exe itself starts (before startup.ncf, before autoexec.ncf).
The latter means we can't pick and choose or work around a patch which stops
the system upon inital boot. We can remove patches by name or by ensemble,
but only after the server is up.
	One may infer the Tech Support guys tearing their hair out with
callers asking if they can omit a patch here and a patch here, or maybe
even everywhere (see today's list), and still complain that the system does
bad things. In revenge, we might say lightly, it's do the whole thing or none.
We surely hope future patches are very solid affairs.
	Suppose there is a fatal patch one fine day. What to do? Easy:
fetch server.exe from the distribution media and boot it instead, or
go zap the patch file on C:.
	Joe D.

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

Date: Fri, 7 Feb 1997 14:03:16 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: OS/2 Name Space

>I did do an upgrade (Migrate from 3.11 to 4.1 and then upgraded to 4.11).
>How can I tell which files should be there and which should not in the
>SYS:SYSTEM and SYS:PUBLIC directories?
--------
	A person told me their extremely clever answer to that one. Before
the upgrade change ownership of files to a newly created username. Then
after the upgrade see which remain under that ownership.
	You should also do an NDIR /S > filename to have a listing of
files, datestamps, etc from the original 3.11 system.
	Now having said these words there is another aspect to consider.
That is disk allocation units. These days disks are large and it is
best to go to 64KB allocation units. You can do that with NW 3.1x and
tape restore files before unpacking the NW 4.11 CD-ROM. Naturally you
will have really good backups (plural) before commencing, and you will
know a restoration can be done via NW 4.11 (because you tested it on a
play machine).
	Joe D.

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

Date: Fri, 2 Jan 1998 09:07:08 -0800
From: Michael Trier <michael@SAFETYSTORAGE.COM>
Subject: Network Update System v2.01

The Network Update System is a utility that I wrote in order to help
me to maintain the 19+ modules that I have developed for in-house
use. These modules are updated on a daily to weekly basis.  The
Network Update System runs on the client machines and makes sure that
the end user is updated to the latest release of each module that the
user uses.  You can find out more information about the product in
the Readme.txt file.

In version 2.01 I have added quite a few features:

 * Separate 16/32 bit client side applications.  The 32 bit version
has full support of long filenames and a Windows 95 style interface.

 * Wildcard filemask ability and ability to copy whole directories
and/or subdirectories.

 * Ability to choose whether the destination file time / date stamp
is the same as the source file or the date and time of the file
update.

 * Can automatically create client side directory structures on the
fly if they do not already exist.

The Network Update System is provided for free.  It is available at:

http://www.pobox.com/~mtrier

Note:  I will not be posting notices of updates to this listserv in
the future; it is not the proper place for such postings.  If you
want to be notified about future updates, please sign up for the
Mailing List available at the website.

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

Date: Thu, 15 Jan 1998 19:10:11 +0200
From: Mike Glassman - Admin <admin@IAA.GOV.IL>
Subject: Old Netware Patches

TITLE: Old Novell Patches Available At...
PRODUCT: NetWare 3.11
NetWare 3.12
intraNetWare
NetWare 4.11
NetWare 4.0
DATE: 24SEP97
DOCUMENT ID: 2930303
REVISION: 3
DISTRIBUTION: Novell-Partners

ISSUE

Old Novell patch kits can be located at the following web address:

	http://www.apricot.co.uk/ftp/bbs/area37/index.htm

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

Date: Fri, 20 Feb 1998 09:46:11 -0700
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Patches

>(NW4.x) Do patches have to be sequentially applied in any case(s), or does
>the most recent patch kit supercede (or include) all previous patch versions?
>i.e. can I apply 410pt8 alone, or must I first apply 410pt7, etc.?
---------
	The general answer is patches are independent and can be applied
alone. But that is too simple in some situations. Thus I always unpack
the update file and look carefully at what it is about to change and
compare it to the current installation. Compendium patches, say 410pt8.exe,
typically are installed last because they include previous material.
	Novell's check is often matching file timestamps for older/newer/
same and a short log is produced listing what was replaced. That's fine,
but manual prechecking by us is still a wise idea.
	Finally, Novell has a habit of packaging ancient modules in recent
material, despite all, and we try to figure out if they really mean back
away from a recent change or if the guys making the package are clueless.
Often the latter case applies.
	Once patched I double check to see that the patch took. Changes to
server.exe are reported to fail in some cases and will need to be repeated
by hand. So look at the debris. Then review the list for comments on fixes
because some are real trouble makers.
	Joe D.

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

Date: Sat, 28 Feb 1998 22:58:25 -0700
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Those server updates

	The following is file warning.txt in brand new archive file
updates\nwos\nw410\410pt8.exe. It does seem to strike some servers and
the explanation might be of interest.
	Joe D.
--------------
We have seen a compatibility problem between the new Loader.exe and
some disk drivers.  This issue will manifest itself as an abend
"CPU Hog Detected by Timer" during the TimesyncMain process or a
"PageFault Processor exception" abend also during the TimesyncMain
Process.

The changes made to the loader are correct and necessary to correctly
provide year 2000 support, but have exposed some coding defects
involving the way some disk drivers deal with real mode access.

If you should experience this problem, contact your disk driver
vendor to see if they have an updated driver that will fix the problem.
A WORK AROUND that can alleviate the problem until the proper diskdriver
can be located is to roll back to the previous version of the loader.exe
or to another version with does not have the latest year 2000 fixes.
A different solution would be to have the customer change disk
controllers, thus eliminating the faulty driver.

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

