Previous | Next

Technical Notes for Windows 98 on NetWare Networks

This section contains information about obtaining current Novell-supplied files and technical notes on the IPX/SPX-compatible protocol.

Obtaining Current Novell-Supplied Files

If your computer is not configured with the necessary NetWare software, or if you do not have the support files that Windows 98 Setup requires to configure your computer, several sources are available for these files.

Important

Use the latest available version of Novell-supplied driver files. If the latest version of VLM does not work, use version 120.

To obtain current NetWare software files

Required Support Files for Novell-supplied Clients

In addition to the base Novell-supplied NetWare client software required to communicate with a NetWare server, some additional NetWare support files are necessary for the Novell-supplied components to work properly in the Windows 98 environment. When Windows 98 is configured to support a Novell NetWare client, Setup checks to see if the required supporting files for Windows are in the \Windows directory. If the files are not in the \Windows directory, Setup asks for a disk or network drive location for these files.

The required Novell-supplied supporting files for NetWare connectivity under Windows are shown in Table 17.3.

Table 17.3 Novell-supplied files for Windows support

File Description
Netware.drv,
Netware.hlp		 Windows-compatible network driver and associated help file to provide access to network redirector functionality from 16-bit applications. Notice that this must be the version 2.x WinNet16 driver for the NETX client. Also, the Novell-supplied version of Netware.drv for NETX is approximately 124 KB in size; for VLM, the size is approximately 144 KB or 162 KB, depending on the version.
Nwpopup.exe NetWare messaging utility. Used to receive messages and alerts from a NetWare server.
Vnetware.386 Virtual device driver providing virtualization services for the NetWare redirector in the Windows environment and across virtual machines (VMs).
Vipx.386 Virtual device driver providing virtualization services for the NetWare IPX protocol for the Windows environment and across VMs.
Nw16.dll1 A thunk layer for passing 32-bit calls to 16-bit NETX APIs.
1 Required for VLM, but not for NETX.

Required Support Files for ODI Drivers

A computer using Novell-supplied ODI and the IPX/SPX protocol requires certain files, depending on whether you choose to keep the Novell-supplied client when installing Windows 98 on a NetWare network. Table 17.4 lists the required files.

Table 17.4 Required support files for ODI drivers with Novell-supplied client

Type of driver Support files
Windows 98 drivers Vnetbios.386
Novell-supplied NETX drivers Ipxodi.com
Lsl.com
Netware.drv
Netware.hlp
Netx.exe		 Nwpopup.exe
Vipx.386
Vnetware.386

A network adapter driver, such as Ne2000.com.
Novell-supplied VLM drivers Netx.vlm version 4.0 or later.

VLM client supporting files, version 1.02 or later.
Windows 98 driver Msodisup.vxd1
Ndis.vxd
Nwlink.vxd
Nwnblink.vxd
Nwnet32.dll		 Nwnp32.dll
Nwredir.vxd
Odihlp.exe
Vnetbios.386
Novell-supplied drivers Lsl.com

A network adapter driver, such as Ne2000.com.
1 Msodisup.vxd is the ODI support layer that maps NDIS 3.1 and later protocols to an ODI driver, and Odihlp.exe is the real-mode stub that allows LSL to complete its binding process in real mode.

Search Mode with Windows 98 on NetWare Networks

Many applications, when started, also open a number of other files (such as overlay files and data files) that are used as application resources. To find these files, older NetWare-aware applications, such as the FILER version 3.x NetWare utility look for files in NetWare search drives in two ways:

Under Windows 98, the search mode defines how files are found, depending on the network client you use, as described in Table 17.5.

Table 17.5 Search mode for NetWare networks

Client Search mode
Client for NetWare Networks Search from a drive mapped to the server where the utility is stored.
Novell-supplied Novell Client for Windows 95/98 Configured in the client’s properties.
Novell-supplied NETX Search from any local drive or any network drive.
Novell-supplied VLM Search from any network drive. Cannot search from a local drive.

Technical Notes on Client for NetWare Networks

This section presents some technical issues you should be aware of when using Client for NetWare Networks, including a summary of configuration settings and required support files, and configuration notes, as well as notes about NetWare API support and running NetWare utilities with Client for NetWare Networks.

Summary of Settings for Client for NetWare Networks

Client for NetWare Networks does not require you to change any settings in Autoexec.bat, Startnet.bat, or Config.sys. However, it does modify some configuration files automatically. For information about configuration files that are modified automatically, see "Required Support Files for Client for NetWare Networks," later in this chapter.

Login.exe is not loaded from any configuration file. Windows 98 Setup removes this entry automatically. If you install Client for NetWare Networks over a real-mode client, Setup does not always remove references to the real-mode client from Autoexec.bat or another batch file. If either NETX or VLM is initialized from Autoexec.bat or another batch file, Client for NetWare Networks will not be loaded, and your computer might lock up. Therefore, you should remove real-mode clients before installing Client for NetWare Networks.

No real-mode drivers are needed if a network adapter driver appears in the list of installed components in the Network option in Control Panel.

Table 17.6 summarizes the minimum settings that you should see in the Network option in Control Panel after you install Client for NetWare Networks.

Table 17.6 Required network settings for Client for NetWare Networks

Network component Configuration options
Client for NetWare Networks If the computer will be downloading system policies or user profiles from NetWare servers, Client for NetWare Networks should be selected in the Primary Network Logon box.

In the General properties for Client for NetWare Networks, Preferred Server should show the name of the NetWare server to be used for initial logon. If login scripts are used, the option that enables login scripts should be checked.
Network adapter In the properties for the adapter, the driver type should be Enhanced mode (32 bit and 16 bit) NDIS. 1
IPX/SPX-compatible protocol In its Advanced properties, the Frame Type should be Auto, or 802.2 if you have problems connecting to a NetWare server. If any network applications at your site require support for NetBIOS over IPX, that option should be checked in the NetBIOS properties.
1 You can also specify 16-bit ODI drivers. You do not need to load such drivers from Config.sys or another configuration file.

Required Support Files for Client for NetWare Networks

Table 17.7 summarizes the support files required for Client for NetWare Networks. All of these files are found in the \Windows\System directory and are provided with Windows 98; no Novell-supplied components are required. For more information about these components, see Chapter 29, "Windows 98 Network Architecture."

Table 17.7 Required files for Client for NetWare Networks1

File Description
Netware.drv1 Emulates a WinNet driver required by some NetWare-aware applications that check for this file, such as Lotus Notes. Notice that this file is supplied with Windows 98, and is not the same as the similarly-named Novell-supplied file and, therefore, does not support applications that make direct function calls to Novell’s Netware.drv. (The Windows 98 version is approximately 2 KB in size.)
Nwlink.vxd Provides the IPX/SPX-compatible protocol.
Nwlsproc.exe, Nwlscon.exe Optionally, provides the 32-bit login script processor and console used by Client for NetWare Networks.
Nwnet32.dll Provides common NetWare networking functions for the 32-bit network provider and print provider.
Nwnp32.dll Provides access to NetWare network resources using Windows Explorer, Network Neighborhood, and so on. This 32-bit network provider for NetWare networks is the service provider interface to the Multiple Provider Router.
Nwpp32.dll Provides the print provider interface to the print router in Spoolss.dll. This 32-bit print provider supports the ability to print to NetWare printing resources.
Nwredir.vxd Provides a 32-bit file system driver (redirector) to support applications that use the NCP file sharing protocol.
1 These files are all supplied on the Windows 98 product disks. Netware.drv in this configuration replaces an identically named Novell-supplied file.

Tables 17.8 and 17.9 summarize entries that are changed automatically in configuration files when Client for NetWare Networks is installed with Windows 98.

Table 17.8 Configuration file deletions for Client for NetWare Networks

File Deletions
Autoexec.bat bnetx
brequest
emsnetx
emsnet5
emsnet4
emsnet3
int2f
ipxodi		 ipx
lsl
msipx
netbios
net3
net4
net5
netx		 odihlp
odinsup
startnet
vlm
xmsnet3
xmsnet4
xmsnet5
xmsnetxp
System.ini [386enh]
network=
uniquedospsp=
pspincrements=
timercriticalsection=
reflectdosint2a=		 [Boot]
network.drv=		 [boot.description]
network.drv=
Net.cfg msipx
Protocol.ini [nwlink$]

DriverName=nwlink$
Frame_Type=4
cachesize=0
bindings=device driver(s) ; for adapters that support
NDIS 2

The following list shows files that are renamed in the Windows and System directories when Client for NetWare Networks is installed. Files are renamed to file name.??~. (For example, the file Nwuser.exe is renamed to Nwuser.ex~.)

Client for NetWare Networks Configuration Notes

This section presents some configuration notes for Client for NetWare Networks.

Additional Settings for Client for NetWare Networks

This section describes some additional settings that can be added to the registry for Client for NetWare Networks or for File and Printer Sharing for NetWare Networks. For information about how to add registry values, see Chapter 31, "Windows 98 Registry."

Setting maximum IPX packet size for the LIP protocol.

You can set a global value for the maximum IPX packet size for the LIP protocol. To do this, add a registry entry named MaxLIP and specify a binary or DWORD value that is the greatest value allowed on any one network segment. The value should be a binary value entered in hexadecimal in reverse order. This global setting is also used on the local network. For example, if a client on a token-ring segment (which allows 4 KB packet sizes) communicates over an Ethernet segment (which allows 1.5 KB packets) to a server on another token-ring segment, the size specified for MaxLIP should be limited to the lowest packet size allowed.

Add MaxLIP as an entry under the following registry key:

Hkey_Local_Machine\System\CurrentControlSet\Services\VxD\Nwredir

To continue the earlier example, you would specify a value for 1.5 KB (0x000005DC in hexadecimal). The actual optimal value depends on the frame-header size, which is the IPX portion of the packet. You might want to experiment to get the right size, but in general, specifying a size that is too small is better than too large, because you want to make sure that the echo packet goes through on the first try.

Turning off support for packet-burst protocol.

If you want to turn off support for the packet-burst protocol (which is enabled by default for File and Printer Sharing for NetWare Networks), set SupportBurst=0 in the following registry key:

Hkey_Local_Machine\System\CurrentControlSet\Services\VxD\Nwredir

Setting the shell version for OVL files.

The versions of NetWare available for the United States that run on x86-based computers use Novell-supplied Ibm*.ovl (overlay) files to present the NetWare shell. This is the default assumed by Windows 98. However, other locales use other versions of OVL files to account for different architecture. For example, Table 17.10 shows the overlay files that NetWare 3.x J (for Japan) uses for various computer types.

Table 17.10 Overlay Files

Overlay file Computer architecture
Pc98$run.ovl NEC PC9800
Dosv$run.ovl IBM PC-compatible
J31$run.ovl Toshiba J3100
Fmr$run.ovl Fujitsu FMR
Ps55$run.ovl IBM Japan

For real-mode clients, alternate OVL files are specified in Net.cfg as the SHORT MACHINE TYPE. For Microsoft Client for NetWare Networks, you can specify alternate OVL files as the ShellVersion value in the following registry key:

Hkey_Local_Machine\System\CurrentControlSet\Services\VxD\Nwredir

The default value is MDOS\0V7.00\0IBM_PC\0IBM\0, where \0 indicates a binary zero (null value). This value represents the four concatenated strings returned by the INT 21 function 0xEA. You must replace the last string (0IBM) with the one used to generate the *$Run.ovl name. The value in the registry must have a binary type; however, you can enter the required combination of raw ASCII and binary data in the Enter Binary Data dialog box.

NetWare API Support in Client for NetWare Networks

Client for NetWare Networks includes built-in support for MS-DOS -based APIs defined by Novell for NetWare 3.x, as summarized in Table 17.11.

Table 17.11 APIs for MS-DOS

API for MS-DOS Description
INT21H Used by applications for NetWare information, bindery services, and so on.
INT64 and INT7A Used by applications to submit IPX/SPX requests.

Client for NetWare Networks supports MS-DOS-based API calls documented in the Novell NetWare Client SDK. If problems occur with applications that make proprietary or undocumented API calls, then you should use a real-mode Novell-supplied client. Also, please report this problem to both Microsoft and the application vendor.

The Windows 3.x APIs for NetWare consist of a series of DLLs provided by Novell with the version 3.x WinNet16 driver for the VLM client. The 16-bit Novell-supplied DLLs for Windows can run with Client for NetWare Networks. This ensures that Windows-based applications and utilities that are NetWare-aware will run with Microsoft Client for NetWare Networks.

If any of your applications requires one or more of these DLLs when running on a real-mode Novell-supplied client (NETX or VLM), you must also run the same DLLs when using that application under Client for NetWare Networks. For example, you need the DLLs listed in Table 17.12 to run Novell’s NWAdmin utility. You also need access to these files if you want to change passwords for a bindery server by using the Passwords option in Control Panel.

Table 17.12 NetWare dynamic-link libraries (DLLs)

API for Windows Description
Nwcalls.dll APIs for NCP communication between the file server and the client computer.
Nwgdi.dll NetWare Graphical Device Interface.
Nwipxspx.dll APIs for IPX/SPX communication.
Nwlocale.dll APIs for localization of applications.
Nwnetapi.dll Network API support for NDS.
Nwpsrv.dll Print server services APIs.

Microsoft Service for NetWare Directory Services searches for these files in locations in the user’s search path statement. If you put these files in a directory on a server, make sure the directory is in each of your users’ search path statements. Microsoft recommends that you place these files in the SYS:PUBLIC directory of your users’ preferred servers.

These Novell-supplied DLLs are not provided with Windows 98. They are provided by Novell with NetWare versions 3.12 and 4.x, and are updated on http://support.novell.com/. To install these files, you must follow the directions provided in your Novell documentation. For information about obtaining the most recent files, see "Obtaining Current Novell-Supplied Files" earlier in this chapter.

Technical Notes on Novell Client for Windows 95/98

This section provides technical information about Novell Client for Windows 95/98. It describes the files Novell’s Setup program copies to your computer and the changes the Setup program makes to system files. It also briefly discusses changes the Setup program makes to your registry.

File Locations

Setup.exe copies or creates the listed Client files into the folders shown in Table 17.13.

Table 17.13 Files copied during Novell Client installation

Folder Files copied
\Novell\Client32 Client32.nlm
Cmsm.nlm
Cne2000.lan
Cne3200.lan
Ethertsm.nlm
Fdditsm.nlm
Ipx.nlm
Loginw95.exe
Lslc32.nlm
Nios.log
Nmr.nlm (if NMR is installed)
NWIP95.NLM (if NetWare/IP is installed)		 Nwpopup.exe
Nwsipx32.nlm
Pc32mlid.lan phasers.wav
Readme.txt
Setupnw.cnt
Setupnw.hlp
Spx_skts.nlm
Sroute.nlm
Tokentsm.nlm
Vmlid.nlm
\Novell\Client32\Install Admin.cfg
Net2reg.log (created during install)		 Nwlinks.exe
Nwsetup.ini
\Windows\NLS\language1 Login.dat
Login.msg
\Novell\Nwclient2 Driver.com
Lsl.com
N16odi.com
Nesl.com		 Net.cfg
Route.com (if a token-ring driver)
\Windows\Help3 Loginw95.hlp
Nwcfg95.hlp
Nwover95.hlp
Nwtips95.hlp
Nwtsg95.hlp
Nwuse95.hlp
\Windows\Inf Ne1000.inf
Ne15_21.inf
Ne2.inf
Ne2_32.inf
Ne2000.inf
Ne3200.inf
Netdef.inf 		Ntr2000.inf Nwclient.inf
Nwip.inf
Nwlayout.inf Nwserv.inf
Nwtrans.inf
Odinsup.inf
\Windows\NLS\language4 Novelnpr.dll
\Windows\System Calwin16.dll
Calwin32.dll
Clnwin16.dll
Clnwin32.dll
Clnwinth.dll
Clxwin16.dll
Clxwin32.dll
Lgnw9532.dll
Locwin16.dll
Locwin32.dll
Ncpwin16.dll
Ncpwin32.dll
Netware.drv
Netwin16.dll
Netwin32.dll
Nios.vxd
Nioslib.dll
Novellnp.dll
Novpp32.dll
Nwcalls.dll		 Nwdrvlgo.bmp
Nwgdi.dll
Nwipxspx.dll
Nwlink2.vxd
Nwlocale.dll
Nwnet.dll
Nwpasswd.dll
Nwpsrv.dll
Nwrrnsp.dll
Nwsetup.dll
Nwshellx.dll
Nwsipx32.dll
Odiload.vxd
Odinsup.sys
Odipage.dll
Prtwin16.dll
Prtwin32.dll
Tli_spx.dll
Tli_win.dll
1 The name of this folder varies depending on the language being used. For example, for English, the folder name is ENGLISH.

2 Setup adds the following files to the NWCLIENT folder on workstations that use 16-bit ODI LAN drivers.

3 Each of these help files might also have files with the following file types associated with them:

*.cnt ,*.fts*.gid.

4 The name of this folder varies depending on the language being used. For example, for English, the folder name is ENGLISH.

Changes to System Files

Table 17.14 shows the changes Novell Client installation makes to Windows 98 system files.

Table 17.14 Changes to Windows 98 system files

System file Changes
Autoexec.bat Removes lines that reference the following:

IP

NETX

SERVER

STARTNET

VLM

Removes the NWCLIENT folder from the SET PATH statement.
Config.sys Removes LASTDRIVE=drive letter
System.ini Adds the following lines to the [386Enh] section:

NWHOMEDIR=[drive]\NOVELL\CLIENT32

FileSysChange=Off

NWEnableLogging is a feature that logs status messages from the Novell Client. You can set the path and file name for the log from the Log File parameter in the Network Control Panel Advanced Settings page.
Netdef.inf Sets the NetClient= line to NOVELL32.

Changes to the Windows Registry

Novell Client makes several changes to the registry. You can reverse these changes by removing the Novell Client software. The INF files document all changes Setup makes to the registry.

Technical Notes on Novell’s NETX

This section provides technical information about using the Novell-supplied NetWare 3.x client software (NETX) with Windows 98.

When running NETX with Windows 98, you keep all the same functionality that you had when running NETX with MS-DOS, Windows 3.x, and Windows 95.

Using NETX with Client for Microsoft Networks

If you are using NETX as the network client, you might also choose to install the 32-bit, protected-mode Client for Microsoft Networks if you want to connect to other Microsoft network computers, such as computers running Windows for Workgroups 3.x, LAN Manager, or Windows NT.

When you run the NetWare NETX client with Windows 98 in this configuration, you should continue to load the necessary Novell-supplied client components and MS-DOS- based TSR programs (LSL, ODI driver, IPXODI, and NETX) in Autoexec.bat or Startnet.bat, just as you did with MS-DOS, Windows 3.1, or Windows 95. Windows 98 Setup automatically adds the configuration settings if they are not present. For information about required configuration settings, see your Novell documentation.

You will need a Microsoft Windows NT Client Access license if the computer will be connecting to servers running Windows NT Server. For information, see Chapter 16, "Windows 98 on Microsoft Networks."

Figure 17.3 shows the architecture for this configuration. Novell-supplied components appear in bold.

Figure 17.3 Architecture for Novell-supplied NETX with Client for Microsoft Networks

In this configuration, the Novell-supplied version of Netware.drv is installed and loaded only for applications that call it directly. Because this driver is not used by Windows 98, all access to NetWare resources occurs by using the Windows 98 user interface, not the Netware.drv dialog boxes provided by Novell. The Nw16.dll component translates 32-bit network calls to 16-bit network calls that can be passed to Vnetware.386.

Using NETX as the Sole Client

You might want to use NETX as the sole client if you do not need to connect to other computers running Windows for Workgroups 3.x, LAN Manager, or Windows NT.

If you use NETX as the sole client, you can still connect to computers running Microsoft File and Printer Sharing Services for NetWare.

To use only NETX client support, use the Network option in Control Panel to remove Client for NetWare Networks and Client for Microsoft Networks, if either of these clients is installed. Then add the Novell NetWare (Workstation Shell 3.x [NETX]) client, as described in "Installing or Upgrading a Real-Mode NetWare Client" earlier in this chapter.

Figure 17.4 shows the architecture for this configuration. Novell-supplied components appear in bold.

Figure 17.4 Architecture for Novell-supplied NETX as the sole client

Table 17.15 lists the required settings for Config.sys and Autoexec.bat files if you use NETX as the sole network client.

Table 17.15 Configuration file settings for NETX as the sole network client

Filename Required settings
Config.sys lastdrive=drive letter
Autoexec.bat1 lsl.com
odi_driver
ipxodi.com
netx.exe
q:; that is, lastdrive+1
login
c:
1 Or this could be the name of a batch file called from Autoexec.bat.

Table 17.16 summarizes the minimum settings that you should see in the Network option in Control Panel if you use NETX as the sole network client.

Table 17.16 Network settings for NETX as the sole network client

Component Options
NetWare (Workstation Shell 3.x [NETX]) Novell NetWare (Workstation Shell 3.x [NETX]) appears in the list of installed components. All other settings are configured in Net.cfg.
Network adapter In the properties for the adapter, the Real mode (16 bit) ODI Driver option should be selected.
Novell IPXODI Settings are configured in Net.cfg.

Setting the LastDrive Parameter for NETX

Windows 98 uses the value of the LastDrive= entry in the registry (or in Config.sys) to allocate enough storage space in the internal memory structures to recognize drive letters for devices. For example, a setting of LastDrive=Z tells Windows 98 to recognize drive letters from A to Z. Windows 98 uses all drive letters up to the letter assigned as the last drive.

In contrast, NETX clients can use only the drive letters following the last drive. For example, if you specify LastDrive=P, you will be able to map NetWare volumes only to drives Q-Z. This can cause problems if you have a setting of LastDrive=Z, because you will then have no drives available for mapping to NetWare servers.

NETX clients always use the drive letters following the drive specified in the LastDrive= entry, even if they are local drives. Also, when you install NETX, Windows 98 adds LastDrive=E to the registry. This can cause problems: for example, if you have a local drive F: and a network drive is mapped to F:, you will no longer be able to access the local drive. If this happens, you will need to modify the LastDrive= entry in Config.sys.

Setting Show Dots and File Access Limits

A NetWare file server does not include the directory entries dot (.) and double dot (..) as MS-DOS and Windows 98 do. However, the NetWare Workstation Shell client version 3.01 or later can emulate these entries when applications attempt to list the files in a directory.

To turn on the Show Dots feature

By default, NetWare client software allows you access to only 40 files at a time. When you are running many applications under Windows 98, it is possible to exceed this limit, so you will want to increase the settings for file limits.

To increase the file access limit

  1. Add the following line to the beginning of Net.cfg:
    file handles=60
  2. Add the following line to Config.sys for the local computer:
    files=60

Technical Notes on Novell’s VLM

VLM, the network client provided with Novell NetWare version 4.x, provides the same support and behavior under Windows 98 as it does under MS-DOS or Windows 3.1.

If the computer is using VLM, you should still load the Novell-supplied client components and TSR programs and log on from either Autoexec.bat or Startnet.bat. Logon scripts also work in the same way they do with MS-DOS, Windows 95, and Windows 3.x. After Windows 98 starts, you can use the Windows 98 user interface to make drive and printer connections, or you can run NetWare utilities by running NWUSER or other commands at the command prompt. Notice, however, that you cannot use NDS names in Windows 98 dialog boxes.

This section presents specific notes related to using the Novell-supplied NetWare 4.x client software with Windows 98.

Using VLM with Client for Microsoft Networks

If you are using VLM as the network client, you might also choose to install the 32-bit, protected-mode Client for Microsoft Networks if you want to connect to other Microsoft networking computers, such as computers running Windows for Workgroups 3.x, LAN Manager, or Windows NT. Figure 17.5 shows the architecture for this configuration. Novell-supplied components appear in bold.

Figure 17.5 Architecture for Novell-supplied VLM with Client for NetWare Networks

In this configuration, the Novell-supplied version of Netware.drv is not used by Windows 98. It is installed and loaded only for applications that call it directly. All access to NetWare resources is through the Windows 98 user interface, not the Netware.drv dialog boxes. The NWUSER utility calls Netware.drv directly to bring up the central NetWare Version 3.0 WinNet16 dialog box.

Notice that this configuration requires a Microsoft Windows NT Client Access License if this computer will be connecting to servers running Windows NT Server. For more information, see Chapter 16, "Windows 98 on Microsoft Networks."

Using VLM as the Sole Client

You can use VLM as the sole client if you do not need to connect to other computers that are running Windows for Workgroups 3.x, LAN Manager, or Windows NT. (If you use VLM as the sole client, you can still connect to a Windows 98 computer running Microsoft File and Printer Sharing for NetWare.)

Figure 17.6 shows the architecture for this configuration. Novell-supplied components appear in bold.

Figure 17.6 Architecture for Novell-supplied VLM as the sole client

Table 17.17 lists the required settings for Config.sys and Autoexec.bat files if you use VLM as the sole network client.

Table 17.17 Configuration file settings for VLM as the sole network client

File name Required settings
Config.sys lastdrive=drive_letter
Autoexec.bat startnet.bat
Startnet.bat lsl.com
odi driver
ipxodi.com
vlm.exe
f:; that is, first network drive in net.cfg
login
c:

Table 17.18 summarizes the minimum settings that you should see in the Network option in Control Panel if you install Windows 98 with VLM as the sole network client.

Table 17.18 Network settings for VLM as the sole network client

Component Options
NetWare (Workstation Shell 4.x [VLM]) Novell NetWare (Workstation Shell 4.x [VLM]) appears in the list of installed components. All other settings are configured in Net.cfg.
Network adapter In the properties for the adapter, the Real mode (16 bit) ODI Driver option should be checked.
Novell IPXODI Settings are configured in Net.cfg.

Setting the LastDrive Parameter for VLM

Windows 98 uses the value of the LastDrive= entry in the registry to allocate enough storage space in the internal memory structures to recognize drive letters for devices. For example, a setting of LastDrive=Z tells Windows 98 to recognize drive letters from A to Z.

The Novell-supplied NetWare 4.x redirector handles the LastDrive= entry the same way that Windows 98 does. That is, both the NetWare 4.x redirector and Windows 98 allow drive letters to be used to connect to redirected network drives up through the drive letter specified by the LastDrive= entry. For example, a setting of LastDrive=Z tells the NetWare 4.x redirector to recognize drive letters up through Z.

The NetWare 4.x redirector uses the First Network Drive= entry in the Net.cfg file to identify the first network drive that can be mapped. For more information about this setting, consult your Novell documentation.