NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:	NETX,EMSNETX,XMSNETX, and NETWARE.DRV

DOCUMENT ID:	TID014005

DOCUMENT REVISION:	D

DATE:	13DEC94

ALERT STATUS:	Yellow

INFORMATION TYPE:	Symptom Solution

README FOR:	NET33X.EXE

NOVELL PRODUCT and VERSION:

NetWare Client for DOS/MS Windows Pre 1.1

ABSTRACT:

This file includes the NetWare driver set v2.02 for workstations using NETX and Windows 3.0,3.1 or 3.11. Netx has been updated to run with all version of DOS 7.x. and below. Note: DO NOT USE THESE FILES ON WORKSTATIONS USING THE NETWARE DOS REQUESTER (VLMs). (No further development is being done on IPX.OBJ, NETX.EXE, EMSNETX.EXE and EMSNETX.EXE. Novell recommends you use the ODI/VLM client requester software. To get the latest info on the client requester download VLMUPx.EXE ,where x stands for the latest rev.)

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

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.

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

Self-Extracting File Name: NET33X.EXE Revision: D

Files Included	Size	Date	Time

=============================================================

\

NET33X.TXT (This File)

IPX.OBJ	20340	11-21-91 12:50p

NETX.EXE	78749	11-22-94 9:50a

EMSNETX.EXE	90605	11-22-94 9:52a

XMSNETX.EXE	87273	11-22-94 9:54a

\NETXWIN\

NETWARE.DRV	126256 12-14-94 9:53a

NETWARE.HLP	34348	02-12-92 3:12p

=============================================================

Installation Instructions:

If you have DOS Client without MS Windows copy the following files to your client directory:

NETX.EXE

XMSNETX.EXE

EMSNETX.EXE

=============================================================

CLIENT KIT NOTE:

If you are running MS Windows on the client and have installed the client kit, you will need to update your files with the files in WINDRx.EXE and NWDLLx.EXE, (were x is the current rev), If you have NOT installed the client kit, you can get a site license of it from a 3.12 or 4.x Novell server. If you do not have a copy of the previously listed server version you can purchase a site license for $99.00 (US) by going into the NOVFILES forum \ Client Kits \ Order DOS/Windows client, or you can call 1-800-update1 and order the "NetWare for DOS/MS Windows". After you have install the client kit, then copy the following files to the from NET33X.EXE to the WINDOWS\SYSTEM directory:

NETXWIN\NETWARE.DRV

NETXWIN\NETWARE.HLP

=============================================================

SHARED WINDOWS NOTE:

If NETX clients and VLMS clients are accessing the same shared windows files, then complete the following

a. Create a subdirectory under the network WINDOWS directory called NETXDRVS

b. Copy the following files from the NETXWIN directory, located below the root of the expanded NET33X.EXE file, to the network WINDOWS\NETXDRVS directory:

NETWARE.DRV

NETWARE.HLP

c. Edit the SYSTEM.INI of every user that will be using the NETX.EXE shell. Under the [boot] section of the SYSTEM.INI file, there is currently a "network.drv=NETWARE.DRV" line. Edit this line to contain the following:

network.drv=*<Shared NetWork DriveLetter>:\windows\netxdrvs\NETWARE.DRV

=============================================================

NWUSER NOTE:

NetWare Pop-Up Menu - The Windows 3.0/3.1 NetWare driver v2.02 provides an optional pop-up menu that allows you to perform common NetWare-related operations. To enable the pop-up menu, add a section to the NETWARE.INI file in the Windows directory (you might need to create this file) with the following lines:

[Options]

HotKeyEnabled=1

NetWareHotKey=117

This maps the pop-up menu to the F6 key. The menu has a button that allows you to change the hot-key to any of the twelve Function-keys.

ERROR NOTE:

If you installed the client kit a User Tools Icon is maded. If you

double click on the User Tools Icon you will get an error "NetWare

Driver not loaded. Load NETWARE.DRV to run". The User Tools	Icon does not work with the NETWARE.DRV 2.x. In order to be	able to map drives within windows you will have follow the above	Note on NWUSER.

=============================================================

PACKET BURST SERVER NOTE:

If you are using packet burst over a wide area link with NetWare 3.X, download PBURST.EXE from Novlib\05, for packet burst over a WAN link.

=============================================================

PACKET BURST CLIENT NOTE:

BNETX.EXE has been deleted from the client update due to a rare problem which can result in data corruption.

For Packet Burst support at the client, the workstation will need to be upgraded to the NetWare DOS Requester (VLM) technology. v1.20 VLMs have Packet Burst and Large Internet Packets enabled by default.

For v3.12, SFTIII and v4.x NetWare, Packet Burst and Large Internet Packets are enabled by default in the O/S, and do not require or use PBURST.NLM. v3.11 servers need PBURST.NLM loaded to support Packet Burst and LIP NCP calls. To turn Large Internet Packets off at a 3.11 server with PBURST.NLM loaded, or at a 3.12 or 4.x server, at the server console type: Allow LIP=OFF

If you are using PBURST over a WAN (Wide Area Link), download PBURST.EXE from Novlib\05.

November 1993 NetWare Application Notes has an article comparing packet burst under BNETX vs VLMs.

December 1993 NetWare Application Notes has an article with a sample packet burst configuration for VSAT satellite links.

=============================================================

BINDFIX NOTE:

BINDFIX FOR OLDER VERSIONS OF NETWARE

If you are running a version of BINDFIX shipped with NetWare version 2.11 or below, you need to update it with the BINDFIX.EXE in BINDFIX.EXE on Compuserv. For further information, see Novell Technical Bulletin 255 and 256, dated October 26,1989 and November 3, 1989, respectively.

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

Any trademarks referenced in this document are the property of their respective owners. Consult our product manuals for complete trademark information.

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

_