Microsoft KB Archive/117918

INF: Updating, Troubleshooting Novell NetWare VLM Installation

PSS ID Number: Q117918 Article last modified on 03-13-1995

2.00

WINDOWS

= SUMMARY =

This article describes how to update specific Novell NetWare drivers on your system to the latest Novell virtual loadable module (VLM) drivers, so that Microsoft Access will run correctly on your Novell network.

= MORE INFORMATION =

Steps to Update Novell Network Drivers
Microsoft Access requires specific versions (or later) of certain Novell network files to run correctly. The following steps describe how to be sure that the correct versions of these files are installed on your system:


 * 1) Obtain the following files:


 * WINUP9.EXE and DOSUP9.EXE (from Novell). These files are available on Novell’s CompuServe NOVLIB forum. To obtain them, log on to CompuServe and type GO NOVFILES, or contact Novell technical support at (800) 638-9273. These files are also available through NetWire and authorized Novell resellers.
 * WW0863.EXE (from Microsoft). This file is available on the Microsoft Software Library (MSL). You can download it from the MSL on the following services:
 * Microsoft Download Service (MSDL) Dial (206) 936-6735 to connect to MSDL Download WW0863.EXE from WINDOWS\31
 * Internet (anonymous FTP) ftp ftp.microsoft.com Change to the SOFTLIB/MSLFILES subdirectory Get WW0863.EXE
 * CompuServe GO MSL Search for WW0863.EXE Display results and download

  Run WW0863.EXE, which is a self-extracting file. When you run this file, it will expand into the following three files: VIPX.386, VTDA.386, and README.TXT. Follow these steps to install the new files:   Rename or back up your original VIPX.386 file. To rename the file, type the following line at the command prompt: ren vipx.386 vipx.bak   Copy the VTDA.386 file to your WINDOWSsubdirectory. To copy the file, type the following line at the command prompt: copy : .386 c:   Using any text editor (such as Windows Notepad), open the SYSTEM.INI file in your Windows directory. Add the following lines to the [386Enh] section of the file, or change them to match these lines if they already exist: InDOSPolling=FALSE TimerCriticalSection=10000 ;device=*vtd device=vtda.386   Save and then close the SYSTEM.INI file.    DOSUP9.EXE and WINUP9.EXE are self-extracting files. Run both of these files to produce the following files: LSL.COM v2.05 9-10-93 17805 IPXODI.COM v2.12 10-7-93 30247 VLM.EXE v1.10 12-9-93 36525 VIPX.386 v1.17 10-11-93 23855 NETWARE.DRV v3.02 11-24-93 146736 Copy the first three files, LSL.COM, IPXODI.COM, and VLM.EXE, to your NWCLIENT directory. (NOTE: C:is the default directory. Your directory location may differ, depending on your installation.) Copy the other two files, VIPX.386 and NETWARE.DRV, to your WINDOWSsubdirectory. NOTE: There is one version of the NETWARE.DRV file for VLM, and another version for NETX. You must be sure to use the version for VLM. If you use the wrong version, network problems can occur. These files add to or replace your existing network files. To see which version of each .EXE or .COM file you are currently running, type the name of the file and press ENTER. If the file is already loaded, you will get a message that states that the file is already loaded, and displays the version number of the currently loaded file.   Modify the NET.CFG file (or the SHELL.CFG file, depending on your network setup) by adding the following entry: READ ONLY COMPATIBILITY = OFF If your .CFG file has the heading “Netware DOS Requestor,” then the preceding line should follow this heading. Otherwise you can place this line anywhere in the .CFG file. </li>  Quit and then restart Microsoft Windows. </li>  Make sure that every workstation on the network has the correct versions of the files listed in this article and has the .INI file entries listed in this article. </li></ol>

Troubleshooting Tips
If, after following the above steps, you still encounter network problems, try the following tips:

<ul>  Make sure that everyone on the network who uses Microsoft Access has the necessary network rights. All Microsoft Access users must have File Scan and Read rights for the WINDOWS and ACCESS directories on the network. Also, users must have File Scan, Read, Write, Create, Erase, and Modify rights for the ACCESSsubdirectory. </li>  Use the network Supervisor or Admin account to run the Microsoft Access network Setup (SETUP /A) and the first workstation Setup. </li>  If the ACCESS directory on the server is marked as Read-Only, make sure that the ACCESSsubdirectory is marked as Create/Erase/ FileScan/Modify/Read/Write for all users. </li>  Load NETX.EXE instead of VLM.EXE when you start the network. If you do this, make sure to change the NETWARE.DRV driver from the VLM version to the NETX version before you start Windows. To do this, make sure the following files are present in the WINDOWSsubdirectory: NETX.EXE v3.32 11-17-93 78654 NETWARE.DRV v2.02 10-27-92 126144 </li></ul>

Multiuser Database Corruption or Locking Issues
If you experience multiuser database corruption or locking issues, perform the following steps:

  On the NetWare server, create the following setting: SET MAXIMUM RECORD LOCKS PER CONNECTION = 10000 </li>  On each workstation, add the following line to the [ISAM] section of the MSACC20.INI file in the Windows directory: PageTimeout=300 </li>  If you are running Novell NetWare version 3.11, obtain the TTSFIX patch file described in the following article (and in the ACREADME.HLP file): ARTICLE-ID: Q102522 TITLE : PRB: “Record Lock Threshold Exceeded” with Large Action Query </li></ol>

NetWare is manufactured by Novell Inc., a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product’s performance or reliability.

Additional reference words: 2.00 networking KBCategory: kbnetwork KBSubcategory: EvnNtw

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

Copyright Microsoft Corporation 1995.