<==========================================================================>
| Ositech Trumpcard |
| NetWare Client Kit |
| Version 2.12 |
| Copyright (c) 1994-1996, Ositech Communications Inc. |
<==========================================================================>
This document supplements the Ethernet User's Guide and the accompanying
software provided with your Ositech Trumpcard. This document contains
information specific to this "Trumpcard Network Client DOS / Windows 3.x
Diskette". Please read this document in its entirety before installing this
software.
Contents
========
1. General Information
1.1 Avoiding Loss of Fake Root Mapping
1.2 Resolving the NDIR Error in COMPAQ DOS 5.0 and DR DOS 6.0
1.3 Supporting Current NetWare Client File Versions
1.4 Logging In to a Personal NetWare Server
1.4.1 Using MS Windows
1.4.2 Using DOS
1.5 Using the Receive Monitor Utility (RXMONSTK.COM) with Monitor
Type Applications (Such as Lanalyzer)
2. Information Specific to Using the NetWare DOS Requester
2.1 Mapping Roots Within Paths Over 64 Characters in Length
2.2 Search Mode Now Uses the DOS ENVIRONMENT Variable
2.3 Difference in Diagnostic Information Reported in the NETX.VLM
File Compared to the NETX.COM and Related Files
3. Information Specific to Using MS Windows
3.1 Using the NETWARE.DRV Version 3.03 with MS Windows
3.2 Using the Correct Version of the Dynamic Link Libraries
(*.DLL) Files of the NetWare Administrator Utility in NetWare
4
3.3 Fixing the Situation in which MS Windows Hangs and Displays a
Blinking Cursor in the Upper-Lefthand Corner of the Screen
(Black Screen of Death)
3.4 VIPX Configuration Parameters for VIPX
3.4.1 [VIPX] Section Parameters
3.5 [386h] Section Parameters
4. Information Specific to Using MS Windows for Workgroups
4.1 Using LSL.COM, 3C5X9.COM, IPXODI.COM, and the NetWare DOS
Requester with MS Windows for Workgroup NWLINK.386 and
MSODISUP.386 files
5. Information Specific to Documentation
5.1 Typographical Error
6. Disclaimer
7. Technical Support
==========================================================================
1. General Information
1.1 Avoiding Loss of Fake Root Mapping
Do not use the DR DOS MOVE command. The MOVE.EXE file in DOS causes the loss
of the fake root mapping, because MOVE obtains the current path and attempts
to perform a CD command on that path.
1.2 Resolving the NDIR Error in COMPAQ DOS 5.0 and DR DOS 6.0
In COMPAQ DOS 5.0 and DR DOS 6.0, the following commands produce an error:
NDIR servername/volume
DIR servername/volume
CD servername/volume
This is because DOS treats a slash (/) as an option specifier when it does
its preprocessing. You can map a drive and use drive letters instead of the
servername/volume syntax.
1.3 Supporting Current NetWare Client File Versions
To support the Packet Burst ODI functionality, the SFT III checksums, and the
NetWare management responder, the IPXNCP.VLM file requires the IPXODI.COM
file version 2.0 or later to be loaded.
Support for checksums and GNMA must also be enabled (the version and the API
support level are treated separately in IPXODI).
1.4 Logging In to a Personal NetWare Server
The PNW.VLM file needs to be loaded before connecting to a Personal NetWare
server. Use the "NETWARE PROTOCOL" line in your NET.CFG file to load the PNW
software. For example:
NetWare DOS Requester
NETWARE PROTOCOL = NDS BIND PNW
1.4.1 Using MS Windows
Use the NetWare User Tools for Windows to log in to a Personal NetWare
server.
Ensure that the "Personal" checkbox is marked in the "Resource Display
Option" box under "NetWare Settings" in the NetWare User Tools. If the
"Personal" checkbox is not marked, Personal NetWare resources are not
accessible.
Ensure that the PNW.DLL file is copied to the MS Windows SYSTEM directory.
1.4.2 Using DOS
Use the NET.EXE utility provided with Personal NetWare to log in and access
Personal NetWare resources in DOS.
Ensure that the NET.EXE, NETU.OVL, and NETA.OVL files are copied to your
NetWare client directory (default is C:\NWCLIENT) and the NETC.MSG file is
copied to the NLS\ENGLISH directory under the NetWare client directory.
NOTE: Currently, support for simultaneous login to a Personal NetWare and
NetWare Directory Services network is not available on 80286-based
workstations.
1.5 Using the Receive Monitor Utility (RXMONSTK.COM) with Monitor Type
Applications (Such as Lanalyzer)
If the monitor type applications you are using seems to stop receiving
network packets when you install a new LAN driver on your workstation, load
the RXMONSTK.COM file.
The application you are using probably requires the network card to operate
in promiscuous mode, and the LAN driver you are using was developed to a new
specification that does not support this mode (Oct. 1994 or later).
Load the RXMONSTK.COM file after the LSL.COM driver but before the LAN
driver. The RXMONSTK.COM operates as a TSR and requires 2684 bytes of
memory. You can load only one LAN driver when using the RxMonStk.
==========================================================================
2. Information Specific to Using the NetWare DOS Requester
2.1 Mapping Roots Within Paths Over 64 Characters in Length
DOS limits the number of characters that the NetWare DOS Requester software
can support in a path name. To use longer paths, map a root within the path
at a point where fewer than 64 characters remain in the path.
DR DOS 6 and Novell DOS 7 allow paths longer than 64 characters on local
drives only. To use paths longer than 64 characters on network drives,
follow the root mapping instructions in the previous paragraph.
2.2 Search Mode Now Uses the DOS ENVIRONMENT Variable
The "SEARCH MODE" function uses the "PATH" DOS ENVIRONMENT variable rather
than the public search mode table provided in the NETX.VLM file. You should
experience no change unless users corrupt their workstation environment.
If you exceed the PATH limitation, your search drive mappings are not
included in the PATH.
2.3 Difference in Diagnostic Information Reported in the
NETX.VLM File Compared to the NETX.COM and Related Files
Some of the current diagnostic information supported in the NETX.COM file
appear to be invalid in the NETX.VLM file. This is because the NetWare DOS
Requester is responsible for much of the diagnostics information previously
maintained in the NetWare Shell for DOS.
Some of the information maintained in the diagnostics responder is not
provided in the current client software. Such information includes the
following:
Bad reply header (InvalidReplyHeaderCount)
Bad slot (InvalidSlotCount)
Bad sequence number (InvalidSequenceNumberCount)
No router found (NoRouterFoundCount)
Request in process (BeingProcessedCount)
Bad server slot (InvalidSlotFromServerCount)
Bad net address (NetworkGoneCount)
Bad local address (BadLocalAddressCount)
Allocate slot errors (AllocateSlotCannotFindRoute,
AllocateNoSlotsAvailable, AllocateServerIsDown)
The NetWare Management Responder (NMR.VLM) file now provides diagnostic
information similar to the information provided in the NetWare Shell
software.
==========================================================================
3. Information Specific to Using MS Windows
*****************************************************************
** **
** NOTE: If you are using the Ositech ODI Driver OTCETH.com **
** (v4.05) with Windows for Workgroups, you MUST have the **
** following parameter in your Link Driver OTCETH section **
** (found in the NET.cfg file): **
** ERX 0 **
** i.e. **
** Link Driver OTCETH **
** ERX 0 **
** {your other parameters} **
** **
** REMEMBER: ALL parameters following the Link Driver OTCETH **
** heading MUST be indented AT LEAST 1 space in!! **
** **
*****************************************************************
3.1 Using the NETWARE.DRV Version 3.03 with MS Windows
The current version of NETWARE.DRV (version 3.03) requires the NWGDI.DLL file
to be loaded when running MS Windows 3.1 or later.
If you receive the following message when loading MS Windows with the NetWare
for MS Windows client software, you should ensure that a copy of the
NWGDI.DLL file exists in your MS Windows SYSTEM directory:
Application Error: Call to Undefined Dynalink
3.2 Using the Correct Version of the Dynamic Link Libraries (*.DLL) Files
of the NetWare Administrator Utility in NetWare 4
The dynamic link library (*.DLL) files provided with the current version of
the NetWare Client software do not support the NWADMIN.EXE file version 4.05
or earlier (NetWare 4.0 and 4.01).
To support the NWADMIN.EXE file version 4.05 or earlier, download the
WINDR1.EXE from NetWare or FTP.NOVELL.COM.
3.3 Fixing the Situation in which MS Windows Hangs and Displays a Blinking
Cursor in the Upper-Lefthand Corner of the Screen (Black Screen of
Death)
If you are experiencing the situation in which MS Windows hangs and then
displays a blinking underline cursor in the upper-lefthand corner of the
screen, you should perform any or all of the following:
1) If you are using a third-party memory manager, do not load any IPX
interface software (such as LSL.COM or IPXODI.COM) into high memory.
2) Add the TimerCriticalSection=10000 command line in the [386Enh]
section of the SYSTEM.INI file.
3) Download and implement the VTDA.386 driver from Microsoft.
You can obtain a copy by downloading the appropriate file from
Microsoft Download Services or FTP.MICROSOFT.COM SOFTLIB Area.
4) If using the IBM LAN Support system, virtualize the network board's
IRQ in the [VIPX] section of the SYSTEM.INI.
See the documentation if the next section for specific information
about the available parameters.
3.4 VIPX Configuration Parameters for VIPX
Under most circumstances, VIPX will work fine under the default configuration.
However, some applications might require custom configuration of the driver.
The following sections list and discuss the SYSTEM.INI parameters that can be
used to configure VIPX:
3.4.1 [VIPX] Section Parameters
VipxMappingPages=[number of 4K pages]
(Default=16)
This is the number of pages that VIPX can use to globalize requests to
the global IPXODI.COM driver.
VIPX is not absolutely guaranteed to have all of these pages available
at any one point, because this is the requested number of pages for
shared global mapping that VIPX makes to the Windows VMM at
initialization time.
VipxFailOverSizedPackets=[ON|OFF|TRUE|FALSE]
(Default=OFF)
This parameter directs VIPX to fail any requests that require more than
the maximum allowed globalization size. The actual maximum varies
according to the media the user is using.
The absolute maximum is 8000 (decimal) bytes. With media that have
smaller packets than 8000 bytes, the maximum allowed size is the maximum
packet size that can be put onto the media.
VirtualizeIrq[0-F]=[ON|OFF|TRUE|FALSE]
(Default=OFF)
VIPX version 1.15 or later avoids a deadlock between the machine and
network board by virtualizing the network board's IRQ. With ODI and
dedicated IPX (IPX.OBJ) drivers, VIPX automatically reads the
configuration of the network board from the driver and virtualizes the
selected IRQs.
However, when using the IBM LAN Support Program with SLANSUP.OBJ or
LANSUP.COM, the LAN IRQ is not readable from the driver. Therefore, you
must set the IRQ for the network board in the [VIPX] section of the
SYSTEM.INI.
For example, to virtualize both IRQ 2 and IRQ 3, you would add the
following lines in your SYSTEM.INI file:
[VIPX]
VirtualizeIrq2=TRUE
VirtualizeIrq3=TRUE
VIPX can virtualize up to four different LAN
IRQs.
3.5 [386h] Section Parameters
TimerCriticalSection=number
As of version 1.15 of VIPX, the TimerCriticalSection must be activated. The
recommended setting is as follows:
[386Enh]
TimerCriticalSection=10000
Set this parameter to avoid a deadlock with the LAN IRQ Virtualization code.
See the "VirtualizeIrq[0-F]" parameter in the "[VIPX] Section Parameter"
documentation.
==========================================================================
4. Information Specific to Using MS Windows for Workgroups
4.1 Using LSL.COM, 3C5X9.COM, IPXODI.COM, and the NetWare DOS
Requester with MS Windows for Workgroup NWLINK.386 and
MSODISUP.386 files
When copying files from a local to a network drive from MS Windows for
Workgroups 3.11, the file might become corrupted or the client workstation
might hang or lose its network connection.
You should update your version of Microsoft's MSODISUP.386 file. You can
obtain a copy by downloading the WG1004.EXE from Microsoft Download Services
or FTP.MICROSOFT.COM SOFTLIB Area.
4.2 Supporting DOS Named Pipes
Novell's DOSNP.EXE file is not compatible with MS Windows for Workgroup
(WFWG) version 3.11. WFWG does not allow the use of INT 21 Named Pipes
requests used by the DOSNP.EXE file.
Currently, there is no fix available.
==========================================================================
5. Information Specific to Documentation
5.1 Typographical Error
The following example in the "NetWare Client for DOS and MS Windows User
Guide" on page 148:
[port]
lp1:=
lp2:=
lp3:=
lp4:=
net1:=
record.prn=
should appear as follows:
[port]
lpt1:=
lpt2:=
lpt3:=
lpt4:=
com1:=
record.prn=
==========================================================================
6. Disclaimer
Novell, Inc., makes no representations or warranties with respect to any
NetWare software, and specifically disclaims any express or implied
warranties of merchantability, title, or fitness for a particular purpose.
Distribution of any NetWare software is forbidden without the express written
consent of Novell, Inc. Further, Novell reserves the right to discontinue
distribution of any NetWare software.
Novell is not responsible for lost profits or revenue, loss of use of the
software, loss of data, costs of recreating lost data, the cost of any
substitute equipment or program, or claims by any party other than you.
Novell strongly recommends a backup be made before any software is installed.
Technical support for this software may be provided at the discretion of
Novell.
==========================================================================
7. Technical Support
If you have any problems with your Ositech Trumpcard adapter, please
call our technical support staff toll free in Canada and the United States
at 1-800-563-2365, FAX at 1-519-836-6156, Internet e-mail at
support@ositech.com, CompuServe (GO OSITECH), or mail to the following
address:
Ositech Communications, Inc.
679 Southgate Drive,
Guelph, Ontario N1G 4S2
CANADA
Tel: 1 (519) 836-8063
FAX: 1 (519) 836-6156
BBS: 1 (519) 836-1196
WWW: http://www.ositech.com/
FTP: ftp.ositech.com
==========================================================================
Trademarks
Novell, NetWare, and DRDOS are registered trademarks of Novell, Inc.
NetWare Client, NetWare DOS Requester, Novell DOS, Packet Burst, Personal
NetWare, ODI, and SFT III are trademarks of Novell, Inc.
Compaq is a registered trademark of Compaq Computer Corporation.
IBM is a registered trademark of International Business Machines Corporation.
Microsoft is a registered trademark of Microsoft Corporation.
PostScript is a registered trademark of Adobe Systems Incorporated.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.