NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: Readme for VLMUP4.EXE
README FOR: VLMUP4.EXE
NOVELL PRODUCTS and VERSIONS:
NetWare 4.1
ABSTRACT:
Contains updated DOS client files. This file includes the v1.20B
NetWare DOS Requester
(VLMs), NetBIOS, DOS client files, and MLID drivers. This is an
update to the NetWare Client or DOS/MS Windows that ships with
NetWare v3.12 and v4.x, or is purchased separately. The entire
client kit can be downloaded - including these updates - from
NWOSFiles\NW Client DOS\WIN\vlmktx (x ranges from 1 to 6).
-----------------------------------------------------------------
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.
-----------------------------------------------------------------
ISSUE:
SYMPTOM:
For a detailed description of the problems the 1.20B VLMs
correct, read the VLMNEWS.WPD, VLMNEWS.WRI or VLMNEWS.TXT file
included in VLMUP4.EXE.
SOLUTION:
Apply VLMUP4.EXE.
This is an update to the NetWare Client for DOS/MS Windows
that ships with NetWare
v3.12 and v4.x, or is purchased separately. If you are using
3.11 or 2.x and do not have
the complete client kit, you can purchase a site license for
$99.00 (US dollars)by calling
1-800-UPDATE1 and ordering the "NetWare Client for DOS/MS
Windows v1.20" - part
number 00662644024943. The client kit that you purchase will
need to be updated with
the files in VLMUP4.EXE. Or you can download the entire client
kit, including the latest
updates from NWOSFiles\NW Client DOS\WIN\vlmktx (x ranges from 1
to 6).
Self-Extracting File Name: vlmup4.exe
Files Included Size Date Time
..\
VLMUP4.TXT (This file)
ODIINFO.DOC 24499 12-9-92 2:43:24 pm
VLMNEWS.TXT 9169 11-8-95 2:06:42 pm
VLMNEWS.WPD 101734 11-8-95 3:33:58 pm
VLMNEWS.WRI 11136 11-8-95 3:28:48 pm
VLMUP4.TXT 26245 11-8-95 4:42:34 pm
VLMUP4.WPD 29612 11-8-95 3:58:48 pm
VLMUP4.WRI 30080 11-8-95 3:59:06 pm
..\ODIDRV\
DOSNP.EXE 10757 9-1-94 10:49:16 am
INT2F.COM 640 7-28-88 11:48:58 am
LANSUP.COM 23339 4-6-95 10:29:02 am
LANSUP.INS 821 10-6-94 9:24:46 am
NE1000.COM 21790 4-6-95 10:21:46 am
NE1000.INS 515 10-6-94 8:52:20 am
NE1500T.COM 31205 4-6-95 10:24:14 am
NE1500T.INS 583 10-6-94 9:04:48 am
NE2.COM 22291 4-6-95 10:22:58 am
NE2.INS 330 10-6-94 9:32:08 am
NE2000.COM 23472 5-4-95 9:44:06 am
NE2000.INS 961 10-6-94 8:47:56 am
NE2100.COM 31203 4-6-95 10:24:08 am
NE2100.INS 577 10-6-94 9:06:16 am
NE2_32.COM 21980 4-6-95 10:23:46 am
NE2_32.INS 309 10-6-94 10:00:10 am
NE3200.COM 28566 4-6-95 10:26:18 am
NE3200.INS 538 10-6-94 10:03:12 am
NETBIOS.EXE 24482 4-10-95 12:15:26 pm
NTR2000.COM 26847 4-6-95 10:27:14 am
NTR2000.INS 616 10-7-94 3:17:56 pm
ODINSUP.COM 34298 4-6-95 10:29:48 am
ODINSUP.DOC 44764 10-4-94 2:24:34 pm
PCN2L.COM 21294 4-28-93 1:12:12 pm
ROUTE.COM 4919 2-23-95 12:50:14 pm
RPLFIX.COM 1838 6-30-93 10:56:12 pm
RPLFIX.TXT 2255 2-21-91 2:47:28 pm
RPLODI.COM 1652 3-21-91 2:24:30 pm
TOKEN.COM 27381 4-12-93 6:27:22 pm
TRXNET.COM 20979 4-6-95 10:28:56 am
TRXNET.INS 536 10-6-94 9:20:44 am
..\VLMS\
AUTO.VLM 4559 10-2-95 4:17:54 pm
BIND.VLM 4793 10-2-95 4:17:20 pm
CONN.VLM 10994 10-2-95 4:16:42 pm
DOSRQSTR.MSG 9624 6-16-95 12:37:24 pm
FIO.VLM 18378 10-2-95 4:18:22 pm
GENERAL.VLM 4958 10-2-95 4:18:38 pm
IPXNCP.VLM 10521 10-2-95 4:16:46 pm
IPXODI.COM 39748 8-8-95 2:27:48 pm
IPXODI.MSG 4334 2-1-95 1:23:06 pm
LSL.COM 18285 4-17-95 10:30:44 am
LSL.MSG 3551 4-17-95 10:29:50 am
NDS.VLM 8597 10-2-95 4:17:08 pm
NETCFG.TXT 14897 12-13-94 12:40:56 pm
NETX.VLM 17374 10-2-95 4:18:24 pm
NMR.MSG 620 6-5-95 1:19:28 pm
NMR.VLM 9874 10-2-95 4:17:30 pm
NWP.VLM 6661 10-2-95 4:17:24 pm
PACKET.SIG 3720 1-20-94 10:31:10 am
PNW.VLM 10140 10-2-95 4:18:10 pm
PRINT.VLM 8181 10-2-95 4:18:14 pm
REDIR.VLM 15258 10-2-95 4:18:18 pm
RSA.VLM 18961 10-2-95 4:29:08 pm
RXMONSTK.COM 11605 4-6-95 10:35:38 am
RXMONSTK.MSG 2548 4-6-95 10:31:20 am
SECURITY.VLM 8011 10-2-95 4:17:40 pm
TRAN.VLM 1562 10-2-95 4:16:54 pm
VLM.EXE 37763 10-2-95 4:15:54 pm
Installation Instructions:
INSTALLATION INSTRUCTIONS
The following is a matrix that identifies which files you need
to download to update your
workstation. When the VLMs are referenced - the assumption is
made that you have already installed the VLMS with the client kit
that is provided with the NetWare products 4.X and 3.12. If you
are using NetWare 3.11 or NetWare 2.x and do not have the
complete client kit, you can purchase a site license for $99.00
(US dollars) by calling 1-800-UPDATE1 and ordering the "NetWare
Client for DOS/MS Windows v1.20" - part number 00662644024943.
The client kit that you purchase will need to be updated with the
files in VLMUP4.EXE. Or you can download the entire client kit,
including the latest updates from NWOSFiles\NW Client
DOS\WIN\vlmktx (x ranges from 1 to 6).
Version of NetWare on file server
W/s configuration v2.x/v3.x/PNW @ v4.02
v4.10
________________________________________________________________-
____________
Netx with NET33x.EXE NET33X.EXE
NET33X.EXE
dedicated IPX VLMUP4.EXE VLMUP4.EXE
VLMUP4.EXE
(IPX.COM)
strictly DOS
Netx with NET33X.EXE NET33X.EXE
NET33X.EXE
dedicated IPX WINDR3.EXE WINDR3.EXE
WINDR3.EXE
with Windows VLMUP4.EXE VLMUP4.EXE
VLMUP4.EXE
Netx with NET33X.EXE NET33X.EXE
NET33X.EXE
ODI and VLMUP4.EXE VLMUP4.EXE
VLMUP4.EXE
strictly DOS
Netx with NET33X.EXE NET33X.EXE
NET33X.EXE
ODI and WINDR3.EXE WINDR3.EXE
WINDR3.EXE
Windows NWDLL2.EXE NWDLL2.EXE
NWDLL2.EXE
VLMUP4.EXE VLMUP4.EXE
VLMUP4.EXE
VLMs with VLMUP4.EXE VLMUP4.EXE
VLMUP4.EXE
ODI and
strictly DOS
VLMs with VLMUP4.EXE VLMUP4.EXE
VLMUP4.EXE
ODI and WINDR2.EXE WINDR2.EXE
WINDR3.EXE
Windows NWDLL2.EXE * **
* The dynamic link libraries (*.dll) that you need are
dependent upon the version of
NWADMIN.EXE that you run. If you are using the NWADMIN.EXE that
comes with 4.02
(NWADMIN.EXE 5-12-94 v4.06) you will need to use the client
files that come with
NetWare v4.02. That client kit contains the DLLs that
correspond to the 4.06 version of
NWADMIN.EXE. The v4.06 NWADMIN will not run if the workstation
has the DLLs from
this file loaded.
** The drivers contained in NWDLL2.EXE are the same as
the files that ship with NetWare v4.10.
@ Personal NetWare works only with VLMs (you cannot use
NETX).
UPDATING A WORK STATION WHICH HAS THE NETWARE DOS REQUESTER
ALREADY INSTALLED.
Make a backup of any files currently on your workstation that
appear in the list below.
FOR THE FILES IN THE SUB-DIRECTORY VLMS IN THE VLMUP4.EXE FILE:
Copy the following files to the workstation's NWCLIENT
directory:
LSL.COM
IPXODI.COM
AUTO.VLM
BIND.VLM
CONN.VLM
FIO.VLM
GENERAL.VLM
IPXNCP.VLM
NDS.VLM
NETX.VLM
NWP.VLM
PRINT.VLM
REDIR.VLM
RSA.VLM
SECURITY.VLM
TRAN.VLM
VLM.EXE
Copy the following files to the NWCLIENT\NLS\ENGLISH directory:
DOSRQSTR.MSG
IPXODI.MSG
LSL.MSG
NMR.MSG
Make sure you have LASTDRIVE=Z in the workstation's CONFIG.SYS
file.
FOR THE FILES IN THE SUB-DIRECTORY ODIDRV IN THE VLMUP4.EXE
FILE:
Copy the updated MLID and any other needed driver to the
workstation's NWCLIENT
directory and reboot to load the new drivers. If the MLID you
are using is not in this file, you
should contact the manufacturer of the card for an updated
driver. A listing of the Novell
certified DOS ODI drivers can be obtained by calling the Novell
Labs Faxback System at (800) 414-LABS. DOC# 10043 is a listing
of all the certified MLIDs, the Master Index Catalog contains a
listing and description of all documents on the system.
UPDATING THE ORIGINAL CLIENT DISKETTES OR THE
SYS:PUBLIC\CLIENT\DOSWIN DIRECTORY ON THE SERVER
Copy the updated files from this file to the corresponding
location on the diskettes or in the network directory. If the
original files are compressed (*.co_) - delete the compressed
file and put the updated files in its place. The client install
will use the files that are not compressed if the compressed
files are not present. The *.ins files in this file are used by
the client install to customize the NET.CFG for the corresponding
MLID.
Frame types
The following drivers included in this ZIP file now default
to the 802.2 frame type. When
using these drivers, it is necessary to either use the 802.2
frame type on your server tor change the frame type for the
workstation in your workstation's NET.CFG file.
NE1000 COM
NE1500T COM
NE2 COM
NE2000 COM
NE2100 COM
NE2_32 COM
NE3200 COM
If you wish to continue to use the 802.3 frame type, place the
following two lines in the
NET.CFG file:
Link Driver <drivername>
Frame Ethernet_802.3
If you were using the NE2000.COM driver, you would replace
<drivername> with NE2000. Be sure to indent the second line and
place a carriage return after the second line.
NTR2000.COM and TOKEN.COM
The NTR2000.COM driver can be used in place of TOKEN.COM.
RXMONSTK.COM
Due to an architecture change, programs like Lanalyzer and
the Intel LanDesk may not run with the new MLIDs (NE2000.COM) in
this file without loading a SHIM. RXMONSTK.COM is a shim that
will allow a program that uses the "Receive Monitor Stack" to
function (ie Lanalyzer). In the past the Receive Monitor Stack
was built into the MLID - but this was very inefficient and
caused high overhead. The decision was made to take it out of
the MLID and an increase in performance resulted. Because of this
change, applications like Lanalyzer need to be modified.
Lanalyzer for Windows has been modified to work with this new
architecture, the update can be downloaded from NOVLIB\08 - the
file
name is LZW002.COM. Applications such as LanDesk (and older
versions of Lanalyzer for Windows) that use the receive monitor
stack may not have been updated at this time and will require the
shim to be loaded.
Since modifications such as this takes time, Novell has
provided the RXMONSTK.COM as a migration tool until the Monitor
programs like LanDesk can be updated. This new architecture was
not released to developers until October 1994. If you have a
driver prior to that date, you should not need to load
RXMONSTK.COM. If you have a driver that is dated after August
1994 you may need to load the shim. The symptom that indicates
the need for RXMONSTK is the application (such as LanDesk) will
load, but does not appear to be receiving any packets.
The load order that should be used is as follows:
LSL
RXMONSTK
MLID
IPXODI
VLM
If you need to use this shim - copy RXMONSTK.COM from \VLMS
to the NWCLIENT directory and the RXMONSTK.MSG from \VLMS to the
NWCLIENT\NLS\ENGLISH directory.
The RXMONSTK.COM file has not been certified with any 32 bit
drivers - including the NE3200 and NE2_32. Workstations hanging
while running the application that uses the Receive Monitor Stack
is the most common symptom. Novell does not recommend using the
RXMONSTK.COM with a 32 bit driver. If you have a 32 bit driver
and need to run an application that uses the Receive Monitor
Stack (Lanalyzer for Windows), Novell recommends using the old
MLID which does not require RXMONSTK.COM. The older MLID can be
used in conjunction with the updated LSL.COM, IPXODI.COM, and the
updated VLMs in this file.
Brief Description of the files included in the kit:
ODIDRV
DOSNP.EXE: NetWare DOS NP Extender
INT2F.COM: Novell Network BIOS Interrupt 2Fh
Emulator
LANSUP.COM: IBM LAN Support MLID
LANSUP.INS: IBM LAN Support Instruction file
for Client Install
NE1000.COM: Novell NE1000 Ethernet MLID
NE1000.INS: Novell NE1000 Instruction file
for Client Install
NE1500T.COM: Novell NE1500T Ethernet MLID
NE1500T.INS Novell NE1500T Instruction file
for Client Install
NE2.COM: Novell NE2 Ethernet MLID
NE2.INS: Novell NE2 Instruction file for
Client Install
NE2_32.COM: Novell NE2-32 Ethernet MLID
NE2_32.INS: Novell NE2_32 Instruction file
for Client Install
NE2000.COM: Novell NE2000 Ethernet MLID
NE2000.INS: Novell NE2000 Instruction file
for Client Install
NE2100.COM: Novell NE2100 Ethernet MLID
NE2100.INS: Novell NE2100 Instruction file
for Client Install
NE3200.COM: Novell NE3200 Ethernet MLID
NE3200.INS: Novell NE3200 Instruction file
for Client Install
NETBIOS.EXE: Novell NetBIOS Emulation Package
NTR2000.COM: Novell NTR2000 Token-ring MLID
NTR2000.INS: Novell NTR2000 Instruction file
for Client Install
ODINSUP.COM: ODI Support Interface for NDIS
PCN2L.COM: IBM PC Network II & II/A MLID
ROUTE.COM: NetWare Source Routing Driver
RPLFIX.COM: NetWare Boot Disk Image Patch
Program
RPLODI.COM: Novell RPL ODI
TOKEN.COM: IBM Token-Ring MLID
TRXNET.COM: Novell Turbo RxNet & RxNet/2 MLID
TRXNET.INS: Novell TRXNET Instruction file for
Client Install
VLMs
AUTO.VLM: NetWare auto-reconnect module
BIND.VLM: NetWare bindery protocol module
CONN.VLM: NetWare connection table manager
DOSRQSTR.MSG: NetWare DOS Requester message file
(english)
FIO.VLM: NetWare file input-output module
GENERAL.VLM: NetWare general purpose function
module
IPXNCP.VLM: NetWare IPX transport module
IPXODI.COM: NetWare IPX/SPX Protocol
(No further development is being done on IPX.OBJ. Novell
recommends you
use the ODI client software. See ODIINFO.DOC for details.)
IPXODI.MSG: NetWare IPXODI Message file
(english)
LSL.COM: NetWare Link Support Layer
LSL.MSG: NetWare LSL Message file
(english)
NDS.VLM: NetWare directory services
protocol module
NETX.VLM: NetWare workstation shell module
NMR.VLM: NetWare Management Responder
module
NMR.MSG: NetWare NMR Message file (english)
NWP.VLM: NetWare protocol multiplexor module
PRINT.VLM: NetWare printer redirection module
PNW.VLM: Personal NetWare protocol module
REDIR.VLM: NetWare DOS redirecter module
RSA.VLM: NetWare RSA authentication module
RXMONSTK.COM Novell Receive Monitor Stack Shim
RXMONSTK.MSG NetWare RXMONSTK Message file (english)
SECURITY.VLM: NetWare security enhancement module
TRAN.VLM: NetWare transport multiplexor
module
VLM.EXE: NetWare virtual loadable module
manager
Brief Description of the document files included in the kit:
VLMUP3.TXT: This file in ASCII text format
VLMUP3.WRI: This file in Windows Write format
VLMUP3.WPD: This file in WordPerfect 5.1 format
VLMNEWS.TXT: Description of fixes and suggestions in
ASCII text format
VLMNEWS.WRI: Description of fixes and suggestions in
Write format
VLMNEWS.WPD: Description of fixes and suggestions in
WordPerfect 5.1 format
ODIINFO.DOC: Discussion on why Novell is promoting
ODI
ODINSUP.DOC: Info and configuration examples for
ODINSUP
PACKET.SIG: Info on Packet Signature and
parameters
RPLFIX.DOC: Information on how and when to run
RPLFIX
NETCFG.DOC: Information on net.cfg parameters
General Information
PACKET BURST:
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.20B VLMs have Packet Burst and Large
IInternet Packets enabled by default.
For v3.12 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
PBURST.NLM (for 3.11) and the patches for 3.12 and 4.x can be
downloaded in the file 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.
DOSNP.EXE:
This is the Named Pipes Extender for DOS. It allows
you to run Named Pipes applications under DOS.
Novell Named Pipe Route Enhancements
DOS Clients:
The default has been changed to not maintain a local Named
Pipe server router table. When a request for a DosOpen,
DosWaitNmPipe, or DosCallNmPipe is received the protocol will
query the network for the whereabouts of the Named Pipe server
specified. This means NCP services must be available i.e.
NETX.EXE or VLM's must be loaded before DOSNP.EXE
The following parameters can be used in the Net.cfg to
configure Dosnp.exe.
NP Max Machine Names = n where n is a number between
4 and 50. Replace n with how many named pipe servers you want in
the table. (This statement in the Net.cfg will make the client
maintain a local Named Pipe server router table.) (Not to be used
in conjunction with NP Max Sessions) Default is 10
NP Max Sessions = n where n is a number between 4 and 50.
Replace n with the number of Named Pipe servers you want to
communicate with at once from the remote router. (Not to be used
in conjunction with NP Max Machine Names) Default is 10
NP Max Open Named Pipes = n where n is a number between 4
and 128. Replace n with the maximum number of named pipes that
can be opened at once. Default is 4
RPLFIX.COM:
RPLFIX is used to allow workstations to remote program
load (RPL) properly with MS
DOS 5.x and above. This utility must be run after the boot
image file (usually NET$DOS.SYS) has been created using the
DOSGEN utility. RPLFIX will directly modify
the boot image file; the boot image file's size and last
modified date will be different after
RPLFIX has been run. RPLFIX only needs to be run against the
boot image file once.
Attempts to run RPLFIX against an already modified boot image
file are detected by the
utility, and no further modifications will be made to the boot
image file.
Follow the instructions for DOSGEN (setting up remote reset
workstations) in the Novell
reference manuals. For NetWare v2.x, this information can be
found in Chapter 9 of the
"Supervisor Guide", or Chapter 2 of the "Using the Network"
manual. For NetWare v3.x,
this information is found in Appendix D of the Installation
manual. After performing all steps
as outlined in the appropriate manual to create the boot image
file, run RPLFIX.COM. The
remote workstation will likely hang during the reset process if
you are resetting using DOS
5.x or above and the boot image file has not been modified by
RPLFIX.
After you have located RPLFIX.COM, map a drive to the
LOGIN subdirectory on the file server you wish to remote reset
from. The DOSGEN procedure instructed you to create a boot
image file in that subdirectory (usually named NET$DOS.SYS). If
the drive you
mapped to SYS:LOGIN was drive F, then you would enter the
following:
RPLFIX F:NET$DOS.SYS <ENTER>
RPLFIX only needs to be run if the version of DOS loaded on the
floppy disk used with
DOSGEN is 5.x or greater. Earlier versions of DOS do not
require that this utility be run.
NOTE: If you renamed your boot image file, then you must use
the new filename with RPLFIX:
RPLFIX [f:]<boot image file> <ENTER>
where [f:] is the drive letter where the image file is located,
and <boot image file> is the
name of the file created with the DOSGEN utility.
RPLODI.COM
How and When to Use RPLODI.COM
When a user has the traditional Novell Remote Boot
PROM that sends a Get-Nearest-Server packet to connect to the
server, the workstation will hang after the MLID (such as
NE2000.COM) loads. Use RPLODI.COM only with Novell Remote Boot
PROMS, and ensure it is loaded before the MLID.
Use RPLODI.COM only with the older Novell Remote Boot PROMS.
Do not use
RPLODI.COM with IBM RPL PROMS or the new Novell "Enhanced" Boot
PROMS. The
RPLODI.COM intelligence was built-into the following files:
TOKEN.RPL
ETHER.RPL
PCN2L.RPL
F1ETH.RPL
RBOOT.RPL
which are used by the IBM RPL and the Enhanced Novell Boot
PROMS. For Novell Remote Boot PROMS, RPLODI.COM is implemented as
shown in the following AUTOEXEC.BAT, and RPLODI.COM must load
before NE2000.COM (the MLID driver):
LSL
RPLODI
NE2000
IPXODI
VLM
To obtain the drivers necessary to run with NETX.EXE instead of
the VLMS you should
download NET33X.EXE from CompuServe.
To obtain the latest Windows drivers for workstations running
the VLMs you should download WINDRx.EXE and NWDLLx.EXE.
=================================================================
Any comments or suggestions on how we can improve the delivery
of these client update files are welcomed. Any enhancement
request to these drivers are welcomed at the same address. Please
send your responses to enhclient@novell.com via Internet Mail.
-----------------------------------------------------------------
Any trademarks referenced in this document are the property of
their respective owners. Consult your product manuals for
complete trademark information.
-----------------------------------------------------------------
-----------------------------------------------------------------
Any trademarks referenced in this document are the property of
their
respective owners. Consult your product manuals for complete
trademark
information.
-----------------------------------------------------------------