Notes on Novell's client software: (Doc. Revision 2.2 - 12/31/94) Novell Client file updates: GO NOVFILES File Notes ==== ===== NET33X.EXE Latest NETX & NETWARE.DRV Files (DOS & Windows!) NOT required for VLM users Only change to previous NET33X is PC-DOS 7 support. VLMUP2.EXE * Latest DOS ODI drivers & VLM's Required for ALL NETX & VLM users except NW4.1 users. NWDLL2.EXE Latest Windows DLL's for VLM's & NETX Required for ALL Windows/WFWG users except NW4.1 users. WINDR2.EXE * Latest Windows drivers (No NETX Netware.drv - see NET33X) Required for ALL Windows/WFWG users except NW4.1 users. * NOTE: VLMUPx & WINDRx are upgrades to VLM clients as supplied with NW3.12 and higher. NW 3.11 and prior users must order the VLM Client Kit ($99 for a corporate license). Call 1-800-UPDATE1 or GO NOVFILES or contact your local Authorised Reseller to place your order. After installing the kit, apply the appropriate updates. The VLM updates are NOT needed for NW4.1 users or if you have the client kit version 1.21, as both these products include all these files. Also, International (non-US) users who use NDS (but do NOT have NW4.1) are also required to order the client kit as the updates on CompuServe do not contain updated international support (UNICODE) files. Further Notes: * PLEASE BE SURE TO READ THE TXT & DOC FILES CONTAINED IN THESE UPDATES! * * IT IS VITALLY IMPORTANT THAT OLDER COPIES OF THE CLIENT FILES DO NOT REMAIN IN YOUR WINDOWS DIRECTORY STRUCTURE! REMOVE ALL COPIES OF OLDER CLIENT FILES FROM BOTH WINDOWS DIRECTORIES (\WINDOWS AND \WINDOWS\SYSTEM) AND YOUR PATH BEFORE APPLYING THE NEW UPDATES! * NETWARE 4.0x users - ALL NW4.0x users must also get NWADM1.EXE from NOVLIB 14. This contains an updated NWADMIN program (v4.10). No other version of NWADMIN will work with NWDLL2.EXE. Selection of MS patches: If using WFWG, Novell, MS-Networking and 3COM's 3C509 get WG1004.EXE from MSL - GO MSL. This is a must! Microsoft Files / KB articles - GO MSL / GO MSKB KB NO. FILE MSL NO. 3.1 3.11 WFWG Notes: ====== ==== ======= === ==== ==== ====== Q104551 WW0863.EXE S14296 X Q Q VTDA.386. Fix FEW timer problems Q106511 NA NA X Application Note on SETUP (inc /A) Q109562 WG0973.EXE S14508 X NE2000 & start-up delay with apps Q111712 WG1004.EXE X 3C509 & Novell only (see above) Q112025 WW1000.EXE S14590 X X Q VSHARE.386 - upgrade to SHARE.EXE X means needed Q means that the patch is already implemented, so not needed, but KB article (text file) might prove useful Note: None of the above applies to WFWG3.1 - you should upgrade to WFWG3.11 if using Novell NetWare and WFWG3.1 Suggestions for improvements to the Novell Client: Novell has a new e-mail address to allow you to make suggestions for improvements to their DOS/Windows client software. Please use this address for any enhancement requests you have. DO NOT USE IT FOR BUG REPORTS! Requests that are technically possible are implemented based on demand for them, so the more people that request a new feature, the more likely it is to appear. A good example would be a Windows login script capability. Upon submitting a request, you will be added to a mailing list and offered to beta your enhancement when it is available. The address is (use private e-mail) INTERNET:enhclient@novell.com from CompuServe or enhclient@novell.com from the Internet directly. DOS version numbers. If you are using the %OS_VERSION variable in the login script to set a DOS drive, do not use MS's SETVER program (or at least remove table entries for NETX.COM, NETX.EXE and VLM.EXE). The one exception to this when using MS DOS 6.21 which incorrectly reports itself as v6.20. In this case add NETX.EXE or VLM.EXE to the SETVER table, indicating version 6.21. There is a free upgrade to MS DOS 6.22 available for 6.21 users. MS DOS 6.22 correctly reports it's version number. This is available on the MS TECHNET supplemental CD. "NWDRV-3.00-30: There was a problem loading the UNICODE table. All NetWare Directory Services functions are now disabled." If not using NW4.x this can readily be solved by not loading NDS.VLM. The easiest way to stop loading NDS.VLM is to rename the VLM extension. Alternatively you can add the line "NetWare Protocol = BIND" to the NET.CFG NetWare DOS Requester section. If NDS is present on this line already you can remove it to save memory and resources. Also remove PNW if it is not in use. If you are using NW4.x and PNW the line should read "NetWare Protocol = NDS BIND PNW". This line controls which VLM's will load by default. If you are using 4.x's NDS features, copy the NLS sub-directory structure to the directory that contains your Windows shell program, as specified in WIN.INI, shell= line. By default this is progman.exe and the \Windows directory. Windows drivers and NETX or VLM IMPORTANT! There is a different version of NETWARE.DRV and NETWARE.HLP for use with NETX shell. This is available in NET33X.EXE. You can not use the VLM version of NETWARE.DRV from WINDRx.EXE with the NETX shell. Also note that NWUSER.EXE will not work with the NETX version of NETWARE.DRV. See NET33X.TXT (in NET33X.EXE) on how to configure the hotkey for the NETX NETWARE.DRV. Windows and the VLM client Currently, with Windows 3.x the only way to install the VLM client is to run the VLM install program. There is no OEMSETUP.INF file available for the VLM client. You should run the VLM install program and then apply the updates as appropriate. Windows for Workgroups version 3.11 - all configurations. WFWG will set up the VLM client if you select "Novell NetWare (Workstation Shell 4.0 and above)" option. It will NOT prompt for all the required DLL files from Novell. You must manually copy these from NWDLLx.EXE. Alternatively, if installing only NetWare support (no MS Networking) use the VLM Install program. If using NETX - select Workstation Shell 3.x Windows for Workgroups - 32 bit File Access Many ODI Network card drivers have a bug in them whereby they leave a file (often NET.CFG) open. This prevents 32 bit FA from loading. In particular, 3COM drivers as shipped with NW3.12 and NW 4.0x exhibit this problem. GO ASKFORUM for updated 3COM drivers or contact your NIC vendor. Windows for Workgroups with MS-Networking and Novell Read all directions below BEFORE beginning to implement! Versions of the VLM install program (1.02, 1.1 and 1.11) as shipped with NW3.12 and 4.0x and the client kit, will disable MS-NETWORKING if run with the "Install support for Windows" option. The versions of INSTALL.EXE in NW4.1 and the v1.21 client kit resolve this problem. This is because MS-NET is always configured on Network= in system.ini. If Novell Networking is also installed as an additional network, WFWG installs it on SecondNet= line. The VLM install.exe program always installs Novell Networking on Network= line, removing the MS-NET network. Below are some details on resolving this problem or installing WFWG with MS-networking for the first time. This is also a good troubleshooting step for any networking problem. Ensure you have a line to load IFSHLP.SYS in CONFIG.SYS file. If not add DEVICE=C:\WINDOWS\IFSHLP.SYS to config.sys and re-boot. Get the Novell Client software installed and working. Ensure that you can login from DOS, and that all the latest Windows driver files are in the correct Windows directories. (If you have a lot of machines to install or upgrade this is probably most readily accomplished by creating a directory corresponding to the Windows directories with a System sub-directory, and if appropriate the NLS sub-directories, placing all the files in their correct locations, and then simply XCOPYing it to your Windows directory with the /s/v/e options). Follow the installation instructions in the client update archives for locations of the client files. Make absolutely certain that you have deleted all previous copies of the client files before you copy the new ones over. This is necessary because many files that originally were placed in the Windows directory are now in the Windows\System directory, and so will not be overwritten. Make sure you are logged into Novell! Do this from DOS by running LOGIN.EXE from your login drive. This is vital! Then run WFWG with WIN/N - Go to WFWG's network setup (network group or Windows Setup -> network setup option) and remove all network support. (Select No support for Networking) Exit Network Setup. Vital! WFWG will tell you it has updated some files and ask you to restart - choose continue instead. Re-run WFWG's network setup and re-install network support. MS-Networking should be installed with Novell as an additional network. Try to select a network card that matches the one you have installed. If none is available then select a generic ODI driver for Token Ring, Ethernet or Arcnet as appropriate (see notes on Error 58 below). The driver type should be ODI/NDIS3. It should default to this. There will be no IRQ/Base IO settings to configure, as these are set in the Novell NET.CFG file. You must ensure that you have only one NET.CFG file on your drive and that it is located in your NWCLIENT directory. WFWG can scan for this file or you can tell WFWG where it is. Also ensure that you use Shell V4.0 for the VLM client and Shell V3.x for the NETX shell, irrespective of what version of NetWare you have. IMPORTANT: If your Novell ODI client or routers uses a frame type other than 802.3 you will need to configure the IPX/SPX compat. protocol to reflect this. Highlight this protocol (click on Drivers, then click on the IPX/SPX compat. protocol) and then click on Setup. Add the frame type setting by selecting the correct frame type from the pull down list box. On clicking OK when you have made all the choices, WFWG will ask whether you want to keep several sets of files. You should opt to keep all existing files. (i.e. Say NO to Do you wish to replace these files). When WFWG asks you to restart - this time click OK. The above procedure forces WFWG to re-write your .ini files and install the Novell client correctly. If it fails to solve the problem, rename PROTOCOL.INI and repeat the whole procedure. Error 58 with WFWG This is caused when there is a mismatch between your ODI MLID name (as used in the Link Driver section of NET.CFG and usually the name of the NIC driver file) and the name used in PROTOCOL.INI. WFWG will often use XXXX in PROTOCOL.INI and add a Link Driver XXXX line to net.cfg when it does not know the MLID name. To correct this edit PROTOCOL.INI to reflect the correct ODI MLID name. Look for Bindings= lines. Problems with MS's IPX/SPX compatible protocol MS's IPX/SPX protocol (NWLINK and NWNBLINK.386) work by replacing Novell's VIPX.386 driver which virtualises IPX and SPX services. There are known compatibility problems with NETWARE.DRV v3.0x and these protocols. These typically affect SPX based applications such as RCONSOLE. The IPX/SPX compat. protocol is NOT needed for Novell support. It was included in WFWG 3.11 to provide a routable protocol (IPX) for use by WFWG's peer to peer networking functions. If you do not have IPX routers, or have no requirement to use MS Networking across IPX routers, then you can safely remove this protocol. Incidentally this will make MS browsing very much faster. Simply remove it with WFWG's network setup, which will then re-install VIPX for you. An alternative if a routable protocol is needed, is to use MS's 32 bit TCP/IP protocol available free of charge from MSL. IMPORTANT: This information is provided without any guarantee of accuracy. YOU USE IT AT YOUR OWN RISK! Copyright (c) 1994, C Data Services Ltd., UK. Authored by Mike Crabtree of C Data Services Ltd. and distributed with permission of C Data Services Ltd. Distribution: The content herein may be distributed freely, provided the entire text is distributed as is, including copyright and this distribution information. Mike Crabtree is employed by neither Microsoft or Novell, and as such, the content herein is presented independently of both organisations. With compliments, Mike - ECNE, MS Product Specialist (WFWG, NT, DOS, Windows)