HDTenEightyP/NetNews huggingface dataset:
Newsgroups: bit.listserv.novell
Date:         Fri, 8 Jan 1993 17:21:35 MET
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         weber@RHRK.UNI-KL.DE
Subject:      Re: IBM Token Ring 16/4 Adapter II

In bit.listserv.novell you write:

>Has anyone setup an IBM Token Ring 16/4 Adapter II card running TCP/IP and IPX
>via packet drivers and CUTCP?  We have set up the IBM Token Ring 16/4 Adapter c
>ard (without the II) like this:

>     Config.sys
>         device=c:\cutcp\dxma0mod.sys 001
>         device=c:\cutcp\dxmc0mod.sys
>         device=c:\cutcp\dxmt0mod.sys

That one you don't need for ipx ore tcp/ip

>     Autoexec.bat
>         ibmtoken 0x60 0

This is ok, but it works only for ip and frieds.
Therfore you can't use...

>         pdipx (Intel's) (ver. 3.10)

Replace it with a linked ipx for the IBM LAN Support Program.
Link it with the LANSUP driver FROM THE ORIGINAL Netware box!
Then put it into the batch BEFORE the IBMTOKEN.

>         netx  (ver. 3.26)

>When we try this with the IBM Token Ring 16/4 Adapter II it says that there is
>no adapter present.  Also the documentation that came with the card says that t
>he card works with Lan Support Program ver. 1.3 or above.  Our IBM rep says tha
>t the latest version of Lan Support is ver. 1.26.

Nonsense. (What the documentation says...)

Regards

Christoph Weber-Fahr



--
  Christoph Weber-Fahr                  |  E-Mail:  weber@rhrk.uni-kl.de
  Universitaet Kaiserslautern,  KIT     |  S-Mail:  Postfach 3049
  Tel. 0631/205-3391                    |           D-6750 Kaiserslautern
--------------------------  My personal opinion only    ---------------------
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Mon, 4 Jan 1993 01:15:16 -0500
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         "Scott A. Jenkins" <sjenkins@INFO.UMD.EDU>
Subject:      Offweek FAQ Reminder

    The FAQ (Frequently Asked Question) list for this mailing list is
automatically mailed every second Monday (this reminder is mailed on
the alternate Mondays).  The FAQ contains basic information such as how
to subscribe and unsubscribe, as well as questions and answers about
commonly used programs such as Pegasus Mail, Charon, as well as information
about ODI issues, and more.
    If you don't want to wait for the biweekly FAQ mailing, you may get
it via anonymous ftp:

FAQ Access Information:
    To get the NOVELL@SUVM FAQ via ftp, ftp to info.umd.edu (128.8.10.29).
Get either faq.txt (straight ASCII) or faq.wp (WordPerfect 5.1) from the
info/Computers/Novell/Information directory.
    The FAQ contains information on subscribing to the mailing list as well
as other general list-related administrative information, pointers to
Novell related FTP sites, information on how to access the info.umd.edu
system via a user-friendly telnet front-end, as well as general Novell
related information.
    You may also want to explore the rest of the info heirarchy.  The
Novell/Utilities and PC/Utilities in particular contain many useful
programs.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Fri, 8 Jan 1993 10:11:59 CST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         "Mark D. McKamey" <mark@RIA-EMH2.ARMY.MIL>
Subject:      Thank you

Please forgive this message, but I am unable to e-mail Mr. Dunn directly.

Stephen,

     Thank you very much for your reply to my posting requesting directions
on installing NetWare from an existing operational NetWare system.  I'll
give the steps a try next week.  Once again, thank you.

Mark D. McKamey
INTERNET:  mark@ria-emh2.army.mil                     ROCK ISLAND ARSENAL
BITNET:    mark%ria-emh2.army.mil@vm1.nodak.edu       SMCRI-IMC-S
UUCP:      uunet.uu.net!ria-emh2.army.mil!mark        ATTN: Mark D. McKamey
DSN PHONE #:   793-0540                               Rock Island, IL
COMMERCIAL PHONE #: (309) 782-0540                    61299-5000
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Via:         UK.AC.SALF.GANY; 11 JAN 93 15:55:28 GMT
X-Mailer:    ELM [version 2.3 PL11]
Newsgroups: bit.listserv.novell
Date:         Mon, 11 Jan 1993 15:55:05 GMT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Richard Letts <R.J.Letts@SALFORD.AC.UK>
Subject:      Re: LWP/Kermit to do Tek Emulation... HELP PLEASE

Joe Doupnik writes....
>
>
..... lots of good stuff deleted ....
>
>         In the end you can override all of these things by setting the
> Unix environment to hold the terminal type you want right now. In Kshell and
> Bourne shell-speak:
>         TERM=terminal-type-string
>         export TERM
> Csh users are on their own (setenv); I can't abide that shambles.

set term=vt100

is all you need to type on most unix systems, it works on SUNos and HP-UX
anyway

--
Richard Letts
Network Manager
University of Salford               Email: R.J.Letts@salford.ac.uk
United Kingdom                      Phone : +44 61 745 5252
United States of Europe
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Thu, 7 Jan 1993 03:04:02 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Brett Warthen <BRETT@INFINITE.MHS.COMPUSERVE.COM>
Subject: Re: Pegasus and Global messaging

FORWARDED MESSAGE from David Harris (MAIL@CSERVE
DH> {INTERNET:DLH@PMAIL.GEN.NZ}) at 1/07/93 12:22 AM
DH> From: David Harris <DLH@PMAIL.GEN.NZ>
DH> Subject:      Re: Pegasus and Global messaging
DH>
> I was wondering if Pegasus mail would work with Netware's Global
> messaging system with the MHS and SMTP modules running.
DH>
DH> Absolutely. PMail is completely SMF-71 conformant (may be the only
DH> mailer available at present which is, I think). Make sure you get
DH> PMail/DOS v2.35 and PMail/Mac v2.0.2.
DH>
DH> Cheers!
DH>
DH> -- David --
***** NOTES from Brett Warthen (BRETT @ INFINITE) at 1/07/93 2:49 AM
Well...not the only one. <g>  One other mailer came out with SMF-71
compliance at the time of NGM's first shipment.

Of course, here we are 5 months later, and it's still only you and me...<g>

------------------------+-------------------------------------------------
 Brett Warthen          |        MHS:  Brett @ Infinite (via NHUB/CSERVE)
 Infinite Technologies  | CompuServe:  >MHS:Brett@Infinite
 11433 Cronridge Drive  |   Internet:  Brett@Infinite.mhs.compuserve.com
 Suite H                |       Phax:  +1-410-363-3779
 Owings Mills, MD 21117 |      Phone:  +1-410-363-1097
------------------------+-------------------------------------------------
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Mon, 11 Jan 1993 14:37:58 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Brett Warthen <BRETT@INFINITE.MHS.COMPUSERVE.COM>
Subject:      RE: What is status of the Novell security patches?

FORWARDED MESSAGE from Joe Rosenfeld (MAIL@CSERVE
JR> {INTERNET:cowboy@TRANS.CSUOHIO.EDU}) at 1/11/93 11:19 AM
JR> Subject:      What is status of the Novell security patches?
JR>
JR> Does anyone know the status of the Novell NetWare security patches?  I
JR> have been told
JR> that the patches have been pulled, but I would like to make certain
JR> that this is, in fact, correct.
JR>
JR> Gee, anyone from Novell want to answer this one?  We would appreciate
JR> it.
JR>
JR> Joe
***** NOTES from Brett Warthen (BRETT @ INFINITE) at 1/11/93 2:14 PM
The security updates were, in fact, pulled.  From what they told us on
CompuServe, the new CLIB.NLM is the culprit, and can cause problems with
some name space modules.  A new CLIB.NLM is expected, in a couple of weeks,
at which time the security updates will be made available.

- Brett
Xref: sparky bit.listserv.novell:19931 comp.sys.novell:11132
From: brian@SJF.Novell.COM (Brian Meek)
Newsgroups: bit.listserv.novell,comp.sys.novell
Subject: Re: Novell/ODI & Memory For PC Gopher
Date: 5 Jan 93 21:46:53 GMT
Organization: Novell, Inc.

rtravsky@news.uwyo.edu (Rich Travsky) writes:
>Subject: Novell/ODI & Memory For PC Gopher
>Date: 5 Jan 93 09:28:51 MST
>Distribution: world
>Organization: Banzai Institute
>Lines: 38
>
>I recently picked up the latest version of PC Gopher (version 1.05r3).
>With some consternation, I discovered it'll no longer Telnet out 
>properly. Why? Not enough memory.
>
>Here's the deal. Our site (a university) maintains a Novell (3.11) lan for 
>our faculty, staff and students. We use the ODI software. They use a lot
>of memory. After all the network stuff and my tsrs (about 12K worth) are 
>loaded (this includes putting as much as possible into high memory - on 
>a Zenith 386 with 4 mb), I have about 555K of free base memory.

Typical ODI drivers plus a basic LSL the are about the same combined size as 
the older "dedicated IPX" drivers.  The big difference with respect to ODI 
is that the Link Support Layer LSL.COM can be configured to provide receive 
buffers and a send mempool.  I've seen some example NET.CFG files for using 
ODIPKT where the Link Driver section is ridiculously bloated with buffers 
and mempool.  Not all protocol stacks for ODI even use these buffers 
(IPXODI.COM does not, TCPIP.EXE does).  

The example NET.CFG in hsdndev.harvard.edu: ~/pub/odipkt shows an LSL 
with 10 buffers of 2048 bytes each.  This seems quite large.  Can anyone 
tell me to what extent ODIPKT requires or uses receive buffers?  Dan?

Anyway, how big is your resident LSL.COM?  It could range anywhere from 
4.4KB to as much as 64KB.  If you're using the ODIPKT example, I'll bet it's 
about 25KB.  Probably too big to be beneficial.  

Novell's TCPIP.EXE, for example, requires that LSL.COM be configured with at 
least one receive buffer equal to the maximum data segment size of your 
network media (1500 bytes for Ethernet), and a mempool of twice that size 
(mempool must be large enough to stage the data of at least two full-sized 
packets).  Therefore, a minimum resident LSL size on an Ethernet node would 
be about 9K, containing one 1500 byte receive buffer and a 3000 byte mempool.
Adding more receive buffers of the same size and a larger mempool will
improve performance up to a point, although the minimum is probably
adequate for casual Telnet usage.

-- brian
___________________________________________________________________________
Brian Meek                            Novell, Inc. -- Desktop Systems Group
                                      Internet mail:  brian@Novell.COM
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Via: uk.ac.manchester.computer-science; Wed, 6 Jan 1993 11:02:14 +0000
X-Disclaimer: Any opinions expressed herein do not necessarily reflect
X-Disclaimer: those of Barclays Bank Plc.
Priority: normal
X-Mailer: Pegasus Mail v2.3 (R4).
Newsgroups: bit.listserv.novell
Date:         Wed, 6 Jan 1993 10:51:45 GMT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Rod Wilson <Rod.Wilson@BARCLAYS.CO.UK>
Subject:      Re: Novell signs letter of intent with AT&T to acquire USL

> Quite so.  Another reason that Novell is trying to aquire UNIX is that they
> are deathly afraid of Windows NT.  If Microsoft's networking technology
> becomes as widespread as Windows 3.x is it would be a death blow to Novell.

Not quite so. Microsoft's so called "networking technology" has been
trying to deal a "death blow" to Novell for years now with second
rate products such as Lan Manager. The only effect these have had is
to convince people that Novell have the best product. Let the market
share speak for itself.

> Hence they will position UNIX as a competetor to Windows NT hoping
> that users will opt for it instead.

Surely Windows NT will be a competitor to Unix, not the other way
round. I am sure that Novell will not change Unix, but add to it, in
order to improve the connectivity between Unix based systems and PC
based systems. I am looking forward to it.






Rod.Wilson@barclays.co.uk      "My opinions are my own
Barclays Bank Plc               and do not reflect those
England                         of my company".
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Wed, 6 Jan 1993 12:17:00 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Don Kazem <DKAZEM@NAS.BITNET>
Subject:      Re: Routing Bug - cisco or Novell or 3com ?

The latest version of the CISCO  firmware is 9.1. Maybe worth asking for it now
so you won't have to upgrade again.

dkazem@nas.edu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Posted-Date: Wed, 06 Jan 93 17:12 EST
X-Vers: CCMail to SMTP translator by Alan Marshall vers 2.71 12/16/92
Organization: Proteon, Inc., Westborough, MA  01581  [(508)898-2800]
X-*To: #Novell-CTC@relay.proteon.com
Newsgroups: bit.listserv.novell
Date:         Wed, 6 Jan 1993 15:07:00 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Novell-Administrator_at_CTC@RELAY.PROTEON.COM
Subject: Re: Adaptec 1740 driving disks and an exabyte

Message-Id: <9211220407.AA25422@monk.proteon.com>
Reply-To: bokonon!stephen@eddie.mit.edu
From: BOKONON!stephen@eddie.mit.edu
X-To:         itcyyz!NOVELL@uunet.ca
SMTP-CCMail translator Ver: acm 2.70 10/30/92
--------------------------------------------------------------------------------
$I have an Adaptec 1740 driving 2X1GB of disk (there are actually 2X this
$whole configuration acting as a duplex pair).  I am trying to add an
$Exabyte tape drive into this and Cheyenne Arcserve 4.  As soon as I start
$writing to the tape the disk channel which it's attached to goes down
$and I get all kinds of volume dismounted due to drive failure messages.
$It doesn't matter which controler of the duplex pair I attach it to  or
$even if I demirror the disks.  As a result of this crash the disks may
$or may not be seriously messed up.  In the duplexed case it's OK cos
$it just disrupts the mirror, in the single ended case it took
$1.5 hours to vrepair the disks (3 times before they would mount).


Sorry for taking so long in replying to this but we have the same
configuration you talk about above and we're running okay.  All I
can think of is make sure you are using the APSI driver when
configuring the ArcServe.  This allows your card to talk to both a
tape drive and disk drives off the same card.

          /Susan_Whetzel_at_CTC@relay.proteon.com
Xref: sparky bit.listserv.novell:20305 comp.sys.novell:11403
From: keith@novell.com (Keith Brown)
Newsgroups: bit.listserv.novell,comp.sys.novell
Subject: Re: Novell MPR
Date: 12 Jan 93 22:15:29 GMT
Organization: Connectivity Products Division, Novell Inc.

In article <NOVELL%93011211555465@SUVM.SYR.EDU> Rob Hudson <SSROB@ECUVM.CIS.ECU.EDU> writes:
>
>Does anyone know where I can find a very detailed description of what
>Novell's Multi-protocol router supports?  Thanks in advance.

You'll have to come to your own opinion about the level of detail but I just 
took a few minutes to hunt down the latest (October '92) edition of the 
electronic NetWare Buyers Guide and place it on sjf-lwp.novell.com 
(130.57.11.140) in the 'buyguide' directory. It contains a section on MPR 
version 2.0. Read and enjoy...

I know, I know... My apologies for not updating the buyers guide on sjf-lwp 
sooner. I did at least have the April '92 edition on there up until yesterday 
and Novell have been keeping me just a tad busy with the job they pay me to do 
over the past few months. Pretty unreasonable of them I know but c'est la
vie! :-)

Keith
-
Keith Brown                                        Phone: 408-473-8308
Novell San Jose Development Center                   Fax: 408-473-8990
2180 Fortune Drive, San Jose, CA 95131               Net: keith@sjf.novell.COM
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Via:         UK.AC.SALF.EUROPA;  6 JAN 93 13:46:33 GMT
X-Mailer:    ELM [version 2.3 PL11]
Newsgroups: bit.listserv.novell
Date:         Wed, 6 Jan 1993 13:46:40 GMT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Richard Letts <R.J.Letts@SALFORD.AC.UK>
Subject:      Re: Remote NFS Access

SSJACK@ECUVM1.EARN writes....
>
>
> Can Netware 3.11 (with NFS NLM) provide its Netware users with access to a
> Unix host (also running NFS) via an additional logical drive mapping?
>

No.

You need the LanWorkplace NFS client Kit to be able to do this.

Novell servers with NFS can only export their volumes as NFS volumes -
they cannot mount remote NFS filesystems, and make them visible to the user.

Richard
--
Richard Letts
Network Manager
University of Salford               Email: R.J.Letts@salford.ac.uk
United Kingdom                      Phone : +44 61 745 5252
United States of Europe
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Fri, 8 Jan 1993 16:24:39 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         SAD.JB@VHLAWSIS.LAW.NYU.EDU
Subject:      shared memory cards and windows

I have some Cabletron E2119 cards with 16K of shared memory.  I want to
be able to keep two non-Windows, non-local applications (Accessing our
minicomputer and our university Student Information System on an IBM
mainframe) open in Windows at the same time.  When I used the non-shared
memory Cabletron cards I can get this to work even though it is unstable
by setting up PIF files.  If I try to do the same thing with the shared
memory cards it crashes.  Has anyone else had this sort of problem or
attempted to do this?  If you have a solution or know of another kind of
ethernet card that would let me do this, please let me know.
Julie
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Vmsmail-To: SMTP%"NOVELL@SUVM.SYR.EDU"
Newsgroups: bit.listserv.novell
Date:         Mon, 4 Jan 1993 05:32:17 GMT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         KETCHUM@ASA.ORG
Subject:      Re: SystemPro questions...

I would concur with Glenn's solution, however, be warned of using 3rd party
memory on any SystemPro.  We have tried various brands of 8Mb modules on 14
servers and had nothing but problems with 3rd party memory.  The quality of
Compaq memory correlates directly to their stringent quality control.  As
memory prices have fallen (Compaq's too), I would stick with Compaq memory.

Respectfully,

Chris Ketchum, Systems Coordinator              ketchum@asa.org
Antarctic Support Associates                    Voice (303)790-8606
Englewood, Colorado
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Mailer: Pegasus Mail v2.2 (R4).
Newsgroups: bit.listserv.novell
Date:         Mon, 11 Jan 1993 16:09:35 MDT
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         RODGER_FRAASE@DSU1.DSU.NODAK.EDU
Subject:      TCP-IP problems with Proteon boards

I am using 134x Proteon Token Ring network boards in Gateway 2000
386sx computers on my Token Ring network.  After TCP-IP was
installed, the computer will hang at indiscriminate times in any
application.  A Proteon technical support person told me that if I
dropped back to version 2.41 of IBM Lan Support program, the problem
would go away.  Others have told me it would not be wise to drop back
to version 2.41, and I couldn't find a version of 2.41 Lan Support
anyway.  A Novell rep said I should try version 2.63 of the IBM Lan
Support program.  However, I discovered that this version does not
seem to work with the packet driver IBMTOKEN.COM (Iniatialization
error 02).  This seemed to be confirmed by an earlier posting in this
listserv.

A local Novell dealer thought the best solution would be to switch to
ODI drivers.  However with ODI the workstation will not boot up at
all (Packet Class is neither Ethernet nor Slip, Not supported class).
I was then told there is no packet driver to support the Proteon
network board.

Does anyone have any experience with this or is able to shed any
light on this problem?  Am I in a Catch-22?  Thanks in advance for
any help offered.
Newsgroups: bit.listserv.novell
From: kpeckyin@trantor.dso.gov.sg (Kee Peck Yin)
Subject: Local News Reader on LWP
Organization: DSO
X-Newsreader: TIN [version 1.1 PL6]
Date: Fri, 8 Jan 1993 02:28:04 GMT

Anyone know whether there is any local news reader that can run on LAN WorkPlace
for DOS? We had tried Winqvtnet with ODIPKT to run with LWP but it is not too
stable in our environment.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-NUPop-Charset: English
Return-Receipt-To: shathaway@[192.33.12.1]
X-Envelope-to: novell@suvm.acs.syr.EDU
Newsgroups: bit.listserv.novell
Date:         Wed, 6 Jan 1993 10:17:35 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         "Stephen B. Hathaway" <shathaway@[192.33.12.1]>
Subject:      NW 2.2 errors again

Hi,
    Something occured to me. The problem I mentioned in my last message
surfaced after upgrading from a 12mhz 286 to a 33 mhz 486 with an Intel
Etherexpress 16 NIC. Many of the clients are XT clones with 3C501s or
equivalent cards. Could these be getting swamped with too many packets too
fast? Is there a comm buffers setting I should be adjusting(shell.cfg or
whatever?).  I left my red books in my other office...

Thanks again...
Stephen B. Hathaway, Laboratory Manager, School of Natural Science
Hampshire College, Amherst, MA  01001
shathaway@hamp.hampshire.edu
(413) 549-4600 x774
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: novell@suvm.bitnet
X-VMS-To: IN%"novell@suvm.bitnet"
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Newsgroups: bit.listserv.novell
Date:         Fri, 8 Jan 1993 13:18:55 -0500
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Gary Flynn <ACS_GARY@JMUVAX.BITNET>
Subject:      HLP..NWMAC VAP printers offline after AT2 NLM router install

I need help. We just installed a NW for MAC 3.011 server and configured
it and our campus Cisco router for Appletalk routing. The 3.011 server
is configured to get its zone information from the Cisco. There is
only one zone being advertised at this time from the Cisco. The
internel network of the 3.011 server is advertising three zones.

The problem is with our NW for MAC 2.2 VAP machines. Some of them
have the Appletalk servers disconnecting from the queues. Users
can spool to the queues but they just sit there. Pconsole shows
no attached queues. The printers can be printed to directly. The
console shows the printers as being offline. I've used reconfig
to assign and deassign zone names to no avail. The confusing part
is that some servers are working fine. Same drivers, same cards,
same Netware....just some work and some don't . The printers are
attached via Dayna boxes. These are switched to AT2 and have been
reset as have been the printers and servers.

I'm walking over with a protocol analyzer now but after 16 hours
I'd sure like a quick fix. Any suggestions? Many thanks.

Gary Flynn
James Madison University
acs_gary@vax1.acs.jmu.edu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.novell
Date:         Mon, 11 Jan 1993 10:22:09 MET
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         kirchner@INFORMATIK.UNI-KL.DE
Subject:      Upgrade for everybody

Hello,

after getting mail from two people who got that update I simply phoned
Novell Germany and asked what is going on. The woman was quite astonished
that I did not get anything, because ALL registered customers should have
got the update directly from Novell. If you did not get it, phone your
nearest Novell office and ask. Do it soon, the woman said she had to look
if she still can get one. I now wait for her to call back.

I'll keep you informed.

Reinhard Kirchner
Univ. of Kaiserslautern, Germany
kirchner@informatik.uni-kl.de