A few REQUIRED notes and patches for Novell Netware 386 Advanced
        version 3.1 Revision A.....



     First off, the ARCNET driver, TRXNET.LAN, is bad...  it just does NOT
     work properly with 8 bit cards.  You will get error such as this:

                Packet receive buffers not being released
                Abort, Retry, Ignore  at your workstations
                Workstations unable to login
                System halt/exit to debugger at 00000001 (INT 13)


     Delete Novell's TRXNET.LAN from SYS:SYSTEM, and copy the one included
     with this file to that directory.  It seems to take care of most of the
     problems.


     The new version of MENUPARZ.EXE has a severe bug -  it no longer
     recognizes the !logout function from menus.  If you are getting a
     "Bad Command or Filename" with your menus, this is the problem.  Logon
     as the supervisor, and change the access rights of

                        SYS:PUBLIC\MENUPARZ.EXE

     so that you can delete it off.  Make note of the original flags, as you
     will want to reflag the MENUPARZ.EXE included here the same way.  Just
     copy the new MENUPARZ.EXE to SYS:PUBLIC, and that problem will disappear.



     IMPORTANT NOTE:

       Some hacker at Novell seems to have made a small typo in the install
       program.  If you take their default maximum packet recieve buffers of
       100, you will find that TWO users can lockout your system due to
       buffers full errors.  I suggest increasing it to at LEAST 1000, by
       including the following line in your AUTOEXEC.NCF file:

              SET MAXIMUM PACKET RECEIVE BUFFERS = 1000

       This solves all the "Block Remap" ,"Write Error on F:", and
       "Bottleneck" errors that will occur otherwise.  I had 3 users in
       WordPerfect 5.1 actually lockup my server due to this one......


     If you are NOT running a dedicated Print server, and decide to use
     your fileserver as a print server as well, there are two points to
     remember:

          1>  DON'T name the print server the same name as the fileserver.
              It behaves rather flaky, and seems to hold print jobs for
              a minute or so before sending the queue to the printer.

          2>  Make sure that the PSERVER.NLM is loaded BEFORE MONITOR.NLM.
              The system loses the MONITOR.NLM if you don't load it last.

     Hey!  Read This!

       Thanks for all the help from The Red Phone BBS, specializing in
       Novell Support.  Without them, I'd still be kicking the fileserver.



    Roy Wilson
    Telegard Alpha Site III
    FidoNet 1:107/200, /201, /207
    MORDOR BBS  (516) 957-1465


    The Red Phone BBS
    SysOp Chris Welber
    (212) 924-1138