NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:              NetWare Client for OS/2 v2.01
DOCUMENT ID:        TID013939
DOCUMENT REVISION:  A
DATE:               05NOV93
ALERT STATUS:       Yellow
INFORMATION TYPE:   Symptom Solution
README FOR:         R201FX.EXE

NOVELL PRODUCT and VERSION:
NetWare Client for OS/2 2.01

ABSTRACT:

DOS Global Session fixes for NetWare Client for OS/2 2.01

_________________________________________________________________

DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL.  NOVELL
MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION.  HOWEVER, THE
INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY.  NOVELL
MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
_________________________________________________________________

SYMPTOM

Current Novell issues in WinOS2 sessions:

When running WinOS2 standard mode sessions with NETWARE RESOURCES
set to GLOBAL the following errors may be encountered:

General Protection Fault in NETWARE.DRV

Sys3176 ,Sys3171, Sys3175 errors in WinOS2

When in FILE - RUN - BROWSE it would return IGNORE RETRY messages

General Protection Fault in NWIPXSPX.DLL

The Drive list from within FileManager was incorrect.

LanServer Drives Didn't show up in the File Manager List of
Drives.

R201FX.EXE will address all of the above issues.

Note: If you are executing multiple seamless window applications,
and  still experience  problems, try setting up each session as a
separate window session.  If an ipx/spx application seems to be
losing connection to the Network check the following Dos
settings:
            DOS_BACKGROUND_EXECUTION =ON
            IDLE_SENSITIVITY=100
These may be a temporary workarounds. Novell is currently
determining if these are Requester issues.


Current Novell issues in Dos sessions:

Running Dos sessions with NETWARE RESOURCES set to GLOBAL 
can result in occasional TRAP D or Sys3176 messages if the
application is using Queue Managment Services (the application
can print directly to a NetWare queue).
201FX1.EXE will address these issues.


CAUSE



SOLUTION

Apply R201FX.EXE


Self-Extracting File Name:  R201FX.EXE      Revision:  A

Files Included     Size     Date      Time

\
  R201FX.TXT             (This File)
    VIPX.SYS      53248   04-16-93    4:23p
  VSHELL.SYS      81920   09-08-93    4:23p
 WIPXSPX.DLL      37968   05-18-93    1:00p
NWNETAPI.DLL     106047   01-23-92    4:36p


Installation Instructions:

1.) Copy vipx.sys and vshell.sys to the Netware directory.

2.) Copy nwipxspx.dll to the os2\mdos\winos2\system directory.

3.) Copy nwnetapi.dll to the os2\mdos\winos2\system directory.

For windows applications also do the following:

4.) Load TBMI2.COM from the os2\mdos\winos2\system directory.  (Can be
executed from Autoexec.bat for all sessions)

5.) Run winos2 session in Standard Mode for applications using IPX/SPX API's.


To speed up login process if no v4.0x NetWare Servers are present on your
network use the following net.cfg option.

NETWARE REQUESTER
     DIRECTORY SERVICES OFF


Solution Specifics:

DOS and WinOS2 Session support

WinOS2 support clarification:

Currently IBM does not support VxDs (Virtual Device Driver) in WinOS2. As a
result applications that MUST run in enhanced mode and MUST make IPX/SPX calls
do not work at this time.  Novell is currently working with IBM to address
this issue.  The above scenario will return a General Protection fault in
NWIPXSPX.DLL.

Following is a suggested work around for the above issue:

Many applications that are typically run in enhanced mode can be run in
standard mode.  (Standard mode can be achieved by running WINOS2 from the
command line or choosing standard mode from the WINOS2 notebook settings.) 
The NWIPXSPX.DLL issue can be addressed by loading TBMI2.COM and running the
application in standard mode.  This will allow applications to run in standard
mode and make IPX\SPX calls.

DOS support clarification:

Currently IBM does not provide support for redirectors in a DOS Session. This
means that the VLMs will not function in a DOS Session.  Novell is currently
working with IBM to address this issue.  As a work around a DRDOS kernel, or a
DOS kernel other than the emulation kernel shipping with OS/2, can be loaded
from a DOS partition configured under partition manager or a VMBOOT session.
 
This work around will provide redirector support and allow the VLMs to be
loaded in a DOS session or WinOS2 session with NETWARE RESOURCES set to
PRIVATE.
ÿ