NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: Novell Client v3.02 for Win95 TID #: 2944870 README FOR: W95302.EXE NOVELL PRODUCTS and VERSIONS: Server 3.12 NetWare 4.11 Utilities 3.12 TCP/IP - DW 2.11 Capture IW 4.11 Provider IW Win95 2.11 Protocols - C3295212 GENERAL - NBM IP/IP Gateway - NBM Novell Distributed Printing Services 1.0 intraNetWare Client 2.20 for WIN 95 - IWCD897 Remote Control Policy - ZEN1DMUP Workstation Import Policy - ZEN1DMUP Remote Control Policy - ZEN1DMWP NetWare Client 2.50 for WIN 95 Policies and Profiles - NWC25W95 Requestor/Redirector - NWC25W95 TCP/IP - NWC25W95CC Setup.exe - NWC25W95I NetWare 5 Client - GW55 GUI Login - NWCL3 Policies and Profiles - NWCL3 Setup.exe - NWCL3IN 95 Desktop References - ZEN101DM95UP intraNetWare Client for WIN95 NetWare Client 3.02 for WIN 95 Setup.exe - NWCL302W95 ABSTRACT: Novell Client v3.02 for Windows 95/98. You are not required to update to this version of the client. This client is provided on the Support Connection for customers that are using Border Manager v3.0 and need the Novell IPX/IP Gateway support. ----------------------------------------------------------------- DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES ALL REASONABLE EFFORTS 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. ----------------------------------------------------------------- INSTALLATION INSTRUCTIONS: Run the SETUP.EXE. ISSUE: Novell Client For Windows 95/98 Release Notes 10/30/98 These notes describe new features and some issues that have not been resolved for this release of the Novell* Client* for Windows** 95/98 software. Most of these issues will be resolved in future releases. This release supports workstations running the following versions of Windows: * Windows 95a * Windows 95b * Windows 95c * Windows 98 This release does not support the original release of Windows 95. To install Novell Client for Windows 95/98, you must have access to the Windows 95/98 CD or be able to access Windows 95/98 installation files over the network. ---------------------------------------------------------------- Contents ---------------------------------------------------------------- 1.0 Installing 2.0 Logging In 3.0 General 4.0 Printing 5.0 IP/IPX Gateway 6.0 Primary Documentation Is HTML ---------------------------------------------------------------- 1.0 Installing ---------------------------------------------------------------- ---------------------------------------------------------------- 1.1 Installing from Diskettes ---------------------------------------------------------------- An option to install from diskettes is not available for this release. ---------------------------------------------------------------- 1.2 ODI Drivers Not Installed ---------------------------------------------------------------- ODI drivers are not installed in the latest version of the Client. If you are upgrading an older version of the Client and you have ODI drivers currently installed, these ODI drivers are still supported. If you are installing the Client for the first time, NDIS drivers will be installed. If you do not already have the necessary NDIS driver, you might need to obtain it from the Windows CD-ROM or from the network card manufacturer. ---------------------------------------------------------------- 1.3 "The DeviceIDDeleteOrder section in NWSETUP.INI is either incomplete, or incorrect." ---------------------------------------------------------------- During installation on Windows 95a, an error occurs if the network interface card is not configured properly (the IRQ and Port Numbers are not correct or they conflict with another device). To solve this problem, configure the network adapter manually or apply the OSR2 patch from the Microsoft Web site. ---------------------------------------------------------------- 1.4 MFC42.DLL Error ---------------------------------------------------------------- The Novell Client runs with mfc42.dll version 4.21.7022 or later. Mfc42.dll version 4.21.7303 is installed when you install Novell Client. If an older version is installed over the version installed by Novell Client, the client login fails with an error message similar to the following: "The ordinal 6453 could not be located in the dynamic link library MFC42.DLL." The actual message might vary, depending on the version of mfc42.dll you are using. To recover from this error, reinstall the correct version of mfc42.dll. You can find the correct file on the Z.E.N.works CD at: d:\products\win95\ibm_enu\mfc42.dll Copy the DLL to the following directory on your workstation: c:\windows\system ---------------------------------------------------------------- 1.5 Drag-and-Drop Might Not Work Immediately ---------------------------------------------------------------- Drag-and-drop operations between applications or the desktop might not work immediately after the client is installed and the workstation is rebooted. To solve this problem, reboot again to ensure proper registration of the ActiveX controls included in the client. ---------------------------------------------------------------- 1.6 Using ACU to Upgrade from the Microsoft Client for NetWare ---------------------------------------------------------------- If you are upgrading from the Microsoft client for Netware to any version of the Novell Client for Windows 95/98 using the setup.exe /acu method in a login script, you must use the # sign in the login script and the user must manually restart the workstation after the Novell client installation has finished. ---------------------------------------------------------------- 1.7 Incompatibility with Built-in Audio and Video Drivers on Hewlett-Packard Vectra and Compaq Presario Computers ---------------------------------------------------------------- Some Hewlett-Packard Vectra and Compaq Presario computers use drivers for their built-in audio and video features that are incompatible with Novell Client for Windows 95. This incompatibility can cause a General Protection Fault on the workstation. If you use a Hewlett-Packard Vectra or a Compaq Presario and experience a GPF after installing Novell Client for Windows 95/98, use one of the following methods to avoid a GPF: 1. Update your audio and video drivers. Current drivers can be obtained from your workstation's manufacturer. 2. Install generic audio and video drivers. 3. After installing the client, do not restart the workstation. Return to Windows and shut down the workstation using the Start > Shut Down option. Finally, restart the workstation. ---------------------------------------------------------------- 1.8 MSBATCH Installation Not Supported in This Release ---------------------------------------------------------------- This release of Novell Client for Windows 95/98 does not support MSBATCH installation. Please disregard the MSBATCH instructions in the documentation. However, a patch to support the MSBATCH process on Windows 98 will be made available on the Novell web site at a later date. ---------------------------------------------------------------- 1.9 "IP with IPX Compatibility" Dependancy ---------------------------------------------------------------- When using the client configuration "IP with IPX Compatibility" make sure the TCP/IP stack has been configured with a TCP/IP Gateway. This can be configured through DHCP or locally defined. The IPX Compatibility driver and IP routing will not work properly without a TCP/IP Gateway configured. Under Windows 95/98 the Gateway can be configured by opening the TCP/IP Properties page, from the Network Properties page. If your network is configured to use DHCP you do not need to configure the Gateway locally. ---------------------------------------------------------------- 1.10 "IP with IPX Compatibility" needs Migration Agent ---------------------------------------------------------------- If you are using "IP with IPX Compatibility" on the client and are trying to see IPX only servers, you need to make sure that you've configured a Migration Agent (MA) on the network. See the NetWare 5 documentation for more information on setting up a Migration Agent on the network. To troubleshoot a NetWare client's MA visibility or configuration, run the CMDINFO command from an MS-DOS Prompt. The command should list all configured or discovered MAs, depending on the IPX Compatibility configuration. ---------------------------------------------------------------- 1.10 Installing Multiple Clients from a Login Script ---------------------------------------------------------------- If you plan to install the Novell Client software on multiple workstations, you can install from the network by copying files to the server and modifying the login script. Even if your network has workstations on multiple platforms, you can install and upgrade the client software on all platforms when users log in. Complete instructions including a sample login script are included in the inst_log.txt file located at the root of the CD-ROM. ---------------------------------------------------------------- 1.11 Fix for ManageWise 2.6 Console Running on Windows 98 ---------------------------------------------------------------- At the time ManageWise(R) 2.6 released (August 18, 1998), users were required to update the Novell Client for Windows 95/98 on the ManageWise Console workstation with one file located on the ManageWise 2.6 CDROM. If the client file, NIOS.VXD, was not updated from the patches provided under the \misc\w98clt\ folder the ManageWise Console becomes unstable. The Novell Client for Windows 95/98 included on the Z.E.N.works 1.1 CD-ROM incorporates changes required to the NIOS.VXD file for the ManageWise 2.6 Console running on Windows 98. ---------------------------------------------------------------- 2.0 Logging In ---------------------------------------------------------------- ---------------------------------------------------------------- 2.1 No Login with 3Com 3C589C PCMCIA Adapter ---------------------------------------------------------------- After installing Novell Client for Windows 95/98, if you are using a 3Com 3C589C PCMCIA Ethernet board, you might not receive the NetWare login screen during startup. To solve this problem: 1. Go to DOS. 2. Change to the client folder (for example: novell\client32). 3. Enter LOAD 3C589.LAN. 4. Execute the NetWare login by clicking Start > Programs > Novell > NetWare Login. ---------------------------------------------------------------- 2.2 Loginw32.exe is the Preferred Login Program ---------------------------------------------------------------- Login.exe does not work in some situations. In those cases, use loginw32.exe. ---------------------------------------------------------------- 2.3 Online help for Username and Password Contains Windows NT Information ---------------------------------------------------------------- The Novell Clients for Windows 95/98 and Windows NT share some help files. In the help for the Username and Password fields, some information was not marked as being NT-specific. The help text for Username and Password in Windows 95/98 says that the username and password can be used for logging in to a workstation, but a workstation can only be logged in to in Windows NT. Windows 95/98 has Windows login, but this is a separate dialog box from Novell Login. The username and password from Novell Login can't be used for Windows login in Windows 95/98. Also, the help text says that a workstation can be locked and unlocked in Windows 95/98, but this is an NT-specific feature. ---------------------------------------------------------------- 2.4 Login Restrictions Set for IPX/SPX Prevent User From Logging In ---------------------------------------------------------------- Symptom: Login restrictions are set for IPX/SPX and the node address. When the administrative workstation is reset, the new Client files are automatically updated and the reboot prompt is displayed. After restarting, the workstation and all of the other workstations that are placed in the restriction list as being able to login as admin and which now have the new client cannot log in and no administration of the server can be done. Cause: This is a problem with preferring IP. The allowed addresses assigned in NDS are IPX. If the server is bound to IP, the clients are designed to prefer this protocol by default. The result is that the client is attempting to log in to the server using IP and so the address is restricted to only allow IPX addresses, causing an authentication failure. This is due ultimately to the IP address not being store in NDS. Solution: Do not bind IP to the server until static IP addresses have been assigned. Or, change your protocol preference to IPX. ---------------------------------------------------------------- 2.5 DOS Utilities Supported Only When Used with IPX or IP Compatibility Mode ---------------------------------------------------------------- The DOS Utilities (CX, MAP, CAPTURE, etc.) are supported only when used with IPX or IP Compatibility Mode. Use the equivalent GUI-based utilities when accessing resources that are only available from IP servers. ---------------------------------------------------------------- 2.6 Associating Login Restrictions with Workstation Objects ---------------------------------------------------------------- SYMPTOM: Workstation policy doesn't work correctly. CAUSE: Login restrictions can be associated with Workstation objects and OUs, but not to groups of Workstation objects. If a policy is associated with a group of Workstation objects, it is not effective. SOLUTION: Do not associate login restrictions with a group of Workstation objects. Associate login restrictions only with a single Workstation object or OU. ---------------------------------------------------------------- 3.0 General ---------------------------------------------------------------- ---------------------------------------------------------------- 3.1 Dial-Up Networking With LAN Connections ---------------------------------------------------------------- Using Dial-Up Networking concurrently with a LAN connection might cause name resolution problems. Servers on the LAN or the Dial-Up connection might not be found. To solve this problem, disable the LAN adapter by doing the following: 1. Click Start > Settings > Control Panel. 2. Double-click System, and then click the Device Manager tab. 3. Double-click the network adapter you want to disable. 4. In the Device Usage filed, check Disable in this Configuration, and then click OK. ---------------------------------------------------------------- 3.2 SLP Configuration Over IP ---------------------------------------------------------------- In order to use SLP name resolution with Dial-Up Networking, you must add the directory agent's IP address to the directory agent list on the Novell NetWare Client Properties Service Location tab. To do this: 1. Click Start > Settings > Control Panel. 2. Double-click Network, and then double-click the Novell NetWare Client. 3. Click the Service Location tab. 4. Add the directory agent IP address to the directory agent list, and then click OK. ---------------------------------------------------------------- 3.3 Dial-Up Networking over IP, Unable to see Network ---------------------------------------------------------------- If you are trying to use Dial-Up Networking on the client and are unable to login or browse the Network, try the following troubleshooting suggestions. 1. Make sure that you can resolve NetWare 5 IP server names. a. For dynamic discovery of server make sure that your client can see an SLP Directory Agent. The agent can be statically configured, (see previous section), or if your Dial-Up host supports DHCP and is configured with the proper DA, then that should also work. Note: By default, the client uses DHCP to discover a DA. (This assumes that there is a DA configued on the Dial-Up host network.) b. The client will use an NWHOST file, if present, which contains server names and their addresses. This might be a preferred way to run your client. (The file is created in the "\NOVELL\CLIENT32" directory on the workstation.) c. The client also supports DNS names. After connecting to the Dial-Up host make sure your DNS server is working properly by trying to PING your server using its DNS name. If the ping was successful, then use that same DNS name as your server name in the login dialog. d. Isolate the problem down to name resolution by using an IP address instead of the server name. If the login works, the problem is in name resolution. 2. Make sure that the IP stack is still functioning properly by pinging known active IP nodes that are on the Dial-Up host network. 3. If you are using IP with Compatibility mode on the client and cannot see any IPX servers, make sure that the client has an MA conigured properly. See section 3.4. ---------------------------------------------------------------- 3.4 Dial-Up Networking with Compatibility Mode ---------------------------------------------------------------- In order to use Compatibility mode to see IPX services over a Dial-Up connection, you should statically configure the Migration Agent on the Compatibility Mode Driver property page. Note: If your Dial-Up host supports DHCP Inform requests, and it's configured to hand out Migration Agents, you shouldn't need to statically set the MA. To statically set the MA address: 1. Click Start > Settings > Control Panel. 2. Double-click Network > Compatibility Mode Driver (CMD) 3. Uncheck Use DHCP and then add a Migration Agent, using an IP address in dotted format (for example: 137.65.1.5). You can also use a DNS name, keeping in mind the dial-up environment you are trying to use. 4. Press OK to save the changes. ---------------------------------------------------------------- 3.5 Online Help Shows Wrong Default for Several Properties ---------------------------------------------------------------- The defaults for several client parameters were changed after the online help was finalized. The following list shows the corrected information. * Contextless Login The correct default is OFF. * Enable Banner The correct default is OFF. * Form Feed The correct default is OFF. * Max Cache Size The correct range is 0 to 49152. * Name Cache Level The correct default is 1. * Notify The correct default is ON. * Retries to DSS During Startup The correct range is 0 to 10. * Show Novell System Tray Icon The Correct default is ON. * Show Scheduler System Tray Icon The correct default is ON. * Shrink Path To Dot The correct default is ON. ---------------------------------------------------------------- 3.6 Advanced Settings Not Documented in Help File ---------------------------------------------------------------- Two Novell Client for Windows 95/98 advanced settings are not documented in the online help file: * File Write Through * Use Extended File Handles ---------------------------------------------------------------- 3.6.1 File Write Through ---------------------------------------------------------------- File Write Through controls whether or not all files are opened in write-through mode. If a file is opened in write-through mode, the writes to that file will not be cached on the client. In effect, File Write Through = ON disables file write caching, which reduces overall client performance but ensures data integrity in the event of catastrophic failure of the client workstation. The default setting (File Write Though = OFF) is recommended. ---------------------------------------------------------------- 3.6.2 Use Extended File Handles ---------------------------------------------------------------- Use Extended File Handles controls whether the client uses extended file handles. If Use Extended File Handles = OFF then the number of files the client can open is limited by the space available in the JFT to 170 files. If Use Extended File Handles = ON the number of files that can be opened is limited only by the value of the server's Maximum Locks Per Connection setting. Except in special cases, the default of Use Extended File Handles = OFF is recommended. ---------------------------------------------------------------- 3.7 Winsock2 not Set Up Correctly on Windows 95 with Early Versions of DCOM'95 ---------------------------------------------------------------- Winsock2 is not set up correctly if the client workstation has DCOM'95 installed and the version is not 812 or later. WS2Setup.exe closes but there is no feedback given to the user about the problem. The following is from the Microsoft Web page: http://www.microsoft.com/windows/downloads/contents/updates/ w95sockets2/releasenotes.asp WS2SETUP.EXE AND DCOM'95 WS2SETUP.EXE will only install on machines that have DCOM'95 build 812 or higher, or no version of DCOM'95 at all. If a version of DCOM'95 prior to build 812 is detected, WS2SETUP.EXE will abort without installing Winsock2 for Windows 95 and an error message will be written to WS2SETUP.LOG. ---------------------------------------------------------------- 3.8 Map.exe Might Fail When Mapping a Drive to an NDS Object ---------------------------------------------------------------- Map.exe is not IP-aware for NDS objects. As a result, map.exe might fail if you try to use it to map a drive to an NDS object, for example with a command like the following: map n .mydir.organization.company The failure will result in a message such as: MAP-4.13-195: Directory [N .mydir.organization.company] cannot be located This error can be avoided by using one of the following solutions: * Use "map n server\vol:\directory" instead of "map n .mydir.organization.company". * Unbind IP from the server that the NDS object points to. * Configure the Protocol Preferences of Novell Client property page to use IPX only. ---------------------------------------------------------------- 3.9 Unable to Autodetect NetWare/IP Under Some Conditions ---------------------------------------------------------------- When using NWIP with an IP & IPX Client configuration, under some configurations, NWIP will fail to get its DHCP information. The problem will be fixed in the first maintenance release of NetWare 5. Some ways to work around this problem are: * Configure the Client as IPX Only when using NWIP. * Statically configure the NWIP information during setup. ---------------------------------------------------------------- 4.0 Printing ---------------------------------------------------------------- ---------------------------------------------------------------- 4.1 Printing to a Volume with Insufficient Space ---------------------------------------------------------------- When you print a large file to a volume with insufficient space, the Novell Client returns an error which might hang the computer. This occurs because the Novell Client cannot retry printing because the volume is out of disk space, and it cannot delete the print job because it thinks that important data will be lost. To resolve this problem, make sure that you have sufficient disk space before you start printing a large file. ---------------------------------------------------------------- 4.2 Do Not Configure a Local NPRINTER with Interrupts ---------------------------------------------------------------- You should not configure a local NPRINTER with interrupts. Use the default "polled mode" instead. ---------------------------------------------------------------- 4.3 Printer Driver Setup ---------------------------------------------------------------- Associating a printer driver with a printer or queue in the printer policy packages requires driver files to be copied to a server. The path that these files are copied to is displayed in the Path box in the Setup Printer Driver dialog box (which is displayed when you select New Driver in the Printer Policy dialog box). Users or workstations must have read file/scan rights to this path (sys:public on the server where the queue resides) if the workstation or user package is to be able to download these drivers to the workstation. The printers associated with a package will not be installed if the drivers are not downloaded. When you select a driver to be associated with a printer, you might be asked to enter a path where an .inf file or driver is located. If you are setting up drivers for an NT package while running Windows 95/98, you are asked to enter the path where the ntprint.inf is located. This file is located in the windows\inf directory, the windows directory being the directory where NT 4.0 is installed. The easiest thing to do is to copy all of the files from the i386 directory of your NT installation CD to an area on a server or the workstation and then copy the ntprint file to that same directory. Once you have given the path to the .inf file, a list of drivers displays. Select the driver you want. You might then be asked where the driver files are located. (If you have put the drivers and the .inf file in the same directory, you might not be prompted for the location.) If the drivers are somewhere else (usually on the NT install CD if you have not copied them to a different path), then browse to the path or type it in. The files are then copied to the path on the server. If you are setting up drivers for Windows 95/98 while running Windows NT, you are prompted to enter the path to the msprint.inf file location. This file is located in the windows\inf directory, the windows directory being the directory where Windows 95/98 is installed. The easiest thing to do is to copy all of the .cab files from the win95 or win98 directory of your Windows installation CD to an area on a server or the workstation, and then copy the msprint.inf, msprint2.inf, and layout.inf files to that same directory. If you are installing drivers for a Windows NT package on Windows NT or a Windows 95/98 package on Windows 95/98, you will not be asked for the .inf files. However, you must still point the install to where the drivers are located, usually the Windows installation CD. If you attempt to copy drivers that are set as READ ONLY, then the Microsoft API will copy the files as .TMP files. This will cause problems when users go to download the driver because the driver will not be found. Make sure the files in the area you copy from are not read only. This usually will not be a problem if you follow the above directions. ---------------------------------------------------------------- 5.0 IPX/IP Gateway ---------------------------------------------------------------- ---------------------------------------------------------------- 5.1 The Novell IPX/IP Gateway is Included with this Release ---------------------------------------------------------------- The Novell IPX/IP Gateway is included with this release of Novell Client for Windows 95/98. ---------------------------------------------------------------- 6.0 Primary Administrative Documentation is HTML ---------------------------------------------------------------- The HTML documentation for Novell Client for Windows 95/98 contains information on installing, configuring, using, understanding, and troubleshooting this Client. The HTML documentation is available on the Novell Client CD-ROM in the Novdoc directory. The search and print functionality are available on 32-bit operating systems such as Windows 95/98 and Windows NT. In addition to the HTML documentation, interface and end-user documentation can be found in the Client help. To access the help, open the setupnw.hlp file. For example, on a Windows 95/98 workstation, click Start > Run, and then enter c:\novell\client32\setupnw.hlp. Self-Extracting File Name: W95302.EXE Files Included Size Date Time ..\ W95302.TXT (This file) ..\W95302\ 1250_UNI.001 727 3-20-1998 6:02:26 am 1251_UNI.001 727 3-20-1998 6:02:26 am 1252_UNI.001 727 3-23-1998 3:12:50 am 1253_UNI.001 727 3-20-1998 6:02:28 am 1254_UNI.001 727 3-20-1998 6:02:30 am 1255_UNI.001 727 3-20-1998 6:02:32 am 1256_UNI.001 727 3-23-1998 3:27:50 am 1257_UNI.001 727 3-20-1998 6:02:34 am 1258_UNI.001 727 3-20-1998 6:02:36 am 3C589MGR.EXE 8537 1-24-1996 10:23:58 am 874_UNI.001 727 3-20-1998 5:59:38 am 932_UNI.001 27139 5-20-1998 11:26:18 am 936_UNI.001 20090 3-20-1998 7:34:10 am 949_UNI.001 20090 3-20-1998 6:01:34 am 950_UNI.001 32946 3-20-1998 6:02:24 am ADMAPI32.DLL 69120 5-8-1997 1:02:20 pm ADMIN.CFG 49 9-26-1995 4:36:38 am ADMINRAP.EXE 173568 5-15-1997 6:48:44 am ADSNNDS.DLL 162304 2-20-1998 2:19:14 am ADSNNDS.INF 3935 6-24-1998 4:38:18 am ATMLEC.DLL 14192 6-23-1997 5:11:02 am ATMTSM.NLM 28342 6-2-1997 7:28:10 am AUDWIN16.DLL 14720 8-19-1998 1:24:20 pm AUDWIN32.DLL 37888 8-19-1998 1:45:20 pm AXBNDRY.HLP 11609 6-9-1998 4:41:58 pm AXBNDRY.OCX 53760 8-4-1998 7:22:50 am AXBNDRY.RLL 19456 8-23-1998 8:03:32 pm AXCRED.HLP 12836 10-27-1998 2:35:04 am AXCRED.OCX 27648 8-23-1998 8:04:34 pm AXCRED.RLL 9728 8-23-1998 8:04:42 pm AXDIALUP.HLP 14777 6-9-1998 4:47:00 pm AXDIALUP.OCX 60416 8-4-1998 7:25:24 am AXDIALUP.RLL 15872 8-23-1998 8:05:22 pm AXDIST.EXE 803680 10-24-1996 9:41:48 am AXLOC.HLP 9698 6-9-1998 4:48:38 pm AXNDS.HLP 16538 6-9-1998 5:08:26 pm AXNDS.OCX 91136 8-4-1998 7:26:50 am AXNDS.RLL 30208 8-23-1998 8:06:22 pm AXPRF.HLP 9788 6-9-1998 5:11:04 pm AXPRF.OCX 25088 8-4-1998 7:27:28 am AXPRF.RLL 8192 8-23-1998 8:06:54 pm AXSCRIPT.HLP 17078 10-27-1998 2:36:40 am AXSCRIPT.OCX 41472 8-4-1998 7:28:26 am AXSCRIPT.RLL 10752 8-23-1998 8:07:32 pm BC450RTL.DLL 220672 8-28-1995 11:52:00 pm BIVBX11.DLL 81920 8-5-1996 8:26:34 am CALWIN16.DLL 108272 8-19-1998 1:15:06 pm CALWIN32.DLL 132608 8-19-1998 1:35:24 pm CFGMGR32.DLL 22528 5-7-1998 7:00:00 pm CFW95NLM.NLM 42324 11-5-1998 8:47:32 am CFWNTDLL.DLL 106496 11-5-1998 8:47:18 am CLIENT32.MSG 4434 5-11-1998 9:39:36 am CLIENT32.NLM 517615 10-28-1998 2:47:34 am CLNWIN16.DLL 67696 8-19-1998 12:43:02 pm CLNWIN32.DLL 61440 8-19-1998 1:08:42 pm CLNWINTH.DLL 6701 8-19-1998 1:01:30 pm CLXWIN16.DLL 11264 8-19-1998 1:23:10 pm CLXWIN32.DLL 24064 8-19-1998 1:44:06 pm CMD.MSG 3547 4-29-1998 11:00:12 am CMD.NLM 54536 9-14-1998 11:34:42 am CMDINFO.BAT 24 6-5-1998 12:23:46 pm COEXIST.DLL 11776 10-15-1998 6:14:04 am COMCTL32.DLL 379152 5-19-1997 7:38:02 am CONNSVC.DLL 58880 8-19-1998 9:16:26 am CONNSVCR.DLL 21504 8-19-1998 9:55:58 am COUNTRY.INI 56264 5-22-1998 10:04:12 am CPQCFG.EXE 29440 7-10-1996 6:18:32 am CPROXY95.NLM 28537 11-5-1998 8:48:04 am CTL3D.DLL 20976 10-15-1998 6:12:50 am CTL3D32.DLL 26624 9-15-1995 7:30:18 pm CTL3DV2.DLL 27632 12-18-1996 2:17:38 pm CW3215.DLL 176128 8-28-1995 11:52:00 pm CW3215MT.DLL 176128 8-28-1995 11:52:00 pm CW3230MT.DLL 319488 3-24-1997 10:02:00 pm CXCFG.EXE 29632 7-10-1996 6:17:48 am DE660.INS 459 4-10-1996 11:27:56 am DIALOUT.CNT 970 6-10-1998 4:35:18 pm DIALOUT.HLP 154632 6-9-1998 5:23:44 pm DISK2 12349 1-26-1997 5:09:50 pm DISK3 4704 1-26-1997 5:09:50 pm DISK4 13428 1-26-1997 5:09:48 pm DISK5 2408 1-26-1997 5:09:50 pm DPAWIN32.DLL 57344 8-19-1998 11:56:50 am DPLMRW32.DLL 12719 8-5-1998 12:52:52 pm DPLMW32.DLL 54272 8-25-1998 2:21:26 am DPLWIN32.DLL 131072 8-19-1998 11:56:48 am DPMW32.EXE 28672 8-25-1998 2:24:40 am DPPWIN32.DLL 106496 8-19-1998 11:56:50 am DPRPCW32.DLL 45056 8-26-1998 10:45:36 am DPSWIN32.DLL 77824 8-19-1998 11:56:52 am DSCQRY32.DLL 404992 6-25-1998 2:43:36 am EDCREGC.EXE 16896 5-6-1997 12:04:16 pm GWINST.EXE 23552 8-14-1998 12:14:08 pm GWSPDLL.DLL 97792 11-5-1998 8:49:48 am HOSTMIB.MSG 1252 6-11-1996 3:52:42 am HOSTMIB.NLM 24330 7-2-1996 10:20:22 am IDISP16.DLL 123904 10-28-1998 12:13:14 pm IMP16.DLL 35840 10-15-1998 6:14:26 am IN95MOB.CNT 5570 6-10-1998 4:28:16 pm IN95MOB.HLP 76296 6-9-1998 5:13:40 pm IPHLPR.NLM 22220 7-24-1998 11:34:28 am IPMAP.NLM 24418 11-5-1998 8:47:40 am IPX.MSG 6028 1-20-1998 7:56:50 am IPX.NLM 114903 2-12-1998 4:18:16 am IPXMAP.NLM 24742 11-5-1998 8:47:50 am LANDRV16 14159 1-26-1997 5:09:50 pm LANDRV32 14948 1-26-1997 5:09:50 pm LGNCNR32.DLL 5120 8-20-1998 6:27:54 am LGNCON32.DLL 50688 8-20-1998 6:27:52 am LGNW3116.DLL 175824 8-25-1998 1:01:50 pm LGNW9532.DLL 246272 8-25-1998 1:01:04 pm LOC16VC.DLL 70056 10-15-1998 6:13:40 am LOC32VC.DLL 60928 10-15-1998 7:31:00 am LOCWIN16.DLL 75728 8-19-1998 12:35:40 pm LOCWIN32.DLL 105984 8-19-1998 12:41:24 pm LOGIN.DAT 60928 3-12-1998 9:44:34 am LOGIN.MSG 11962 7-22-1998 11:06:32 am LOGINS31.CNT 2461 6-10-1998 4:39:58 pm LOGINS31.HLP 225006 6-9-1998 5:37:14 pm LOGINSVC.DLL 28160 8-19-1998 9:16:36 am LOGINSVR.DLL 17920 8-19-1998 9:58:16 am LOGINW31.DLL 458240 3-12-1998 8:51:08 am LOGINW31.EXE 4512 3-12-1998 8:51:20 am LOGINW31.HLP 45864 6-9-1998 5:42:30 pm LOGINW32.DLL 125952 8-23-1998 8:08:58 pm LOGINW32.EXE 25088 8-23-1998 8:07:46 pm LOGINW32.HLP 13098 10-27-1998 2:37:58 am LOGINW32.RLL 52224 8-23-1998 8:09:14 pm LOGINW95.DLL 31744 8-23-1998 8:09:06 pm LOGINW95.EXE 16896 12-17-1997 6:11:18 am LSLC32.MOL 2048 2-27-1996 3:31:02 am LSLC32.MSG 1947 1-7-1998 8:37:00 am LSLC32.NLM 20043 1-7-1998 8:37:30 am LSLC32.NOL 18615 7-1-1996 11:09:18 pm M16ACFG.EXE 29408 1-8-1997 7:33:02 am MAPBASE.DLL 265728 7-17-1998 10:32:16 am MAPBASER.DLL 93696 7-17-1998 10:40:02 am MDGDOS30.BIN 57068 11-14-1996 10:07:00 pm MFC40.DLL 921872 5-13-1996 5:39:04 am MFC42.DLL 954640 11-3-1997 7:12:42 pm MONOID.IDX 131016 8-13-1998 1:12:20 pm MSVCIRT.DLL 70656 1-22-1997 3:27:46 pm MSVCIRTD.DLL 81408 1-22-1997 2:46:12 pm MSVCRT.DLL 277776 11-3-1997 3:10:32 pm MSVCRT40.DLL 326656 2-19-1996 6:03:16 pm MULTPROT.DLL 48640 10-15-1998 7:34:22 am NBIC32.NLM 47953 5-12-1998 11:44:48 am NCPWIN16.DLL 142640 8-19-1998 12:59:44 pm NCPWIN32.DLL 141824 8-19-1998 1:11:20 pm NDPP95.DLL 43520 8-5-1998 5:43:08 pm NDPP95R.DLL 4608 4-29-1998 12:44:34 pm NDSPUR32.EXE 21504 4-28-1997 10:27:36 am NDSSRCH.DLL 31232 5-8-1997 12:56:30 pm NESL.MSG 1134 1-10-1996 6:50:58 am NETWARE.DRV 267328 9-25-1998 10:53:14 am NETWARER.DRV 33296 4-22-1998 11:48:28 am NETWIN16.DLL 237712 8-19-1998 1:22:06 pm NETWIN32.DLL 207872 8-19-1998 1:42:58 pm NEWLINKS.EXE 25600 6-24-1997 4:17:22 am NIOS.VXD 149787 7-10-1998 10:20:40 am NIOSLIB.DLL 89092 11-17-1997 4:05:36 pm NIOSRPL.VXD 9327 6-16-1998 11:54:46 am NIOSWIN4.MSG 12423 2-12-1998 1:45:36 am NLLAYOUT.INF 4788 6-24-1998 4:39:10 am NMR.NLM 11464 7-2-1996 11:20:36 am NOVELLNP.DLL 512000 10-26-1998 5:10:14 am NOVELNPR.DLL 194560 7-17-1998 11:07:40 am NOVPP32.DLL 135168 7-22-1998 12:43:46 pm NOVPP32R.DLL 10240 4-29-1998 12:46:04 pm NRDWIN32.DLL 126976 8-19-1998 9:14:44 am NWAPP32.DLL 323584 10-31-1998 5:40:12 pm NWCALLS.DLL 147824 9-20-1996 11:01:14 am NWCAP.VXD 37845 11-27-1997 2:35:42 am NWCCFG16.DLL 3904 5-17-1998 4:21:48 pm NWCCFG32.DLL 5120 5-27-1998 2:57:56 pm NWCLIENT.INF 32071 10-26-1998 10:31:00 am NWCMD.INF 2812 6-24-1998 4:41:12 am NWDIAL.INF 5547 8-3-1998 4:17:16 pm NWDLKPCI.INF 9610 7-17-1996 7:55:56 am NWDRVLGO.BMP 48112 7-15-1998 7:06:08 am NWGDI.DLL 40464 4-22-1998 10:33:20 am NWGROUP.DLL 6656 7-17-1998 11:22:32 am NWHOST 561 7-13-1998 4:24:18 am NWIP.INF 3062 7-12-1998 3:07:36 pm NWIP.MSG 4528 5-10-1996 5:42:38 am NWIP95.NLM 65020 8-5-1997 11:20:38 am NWIPSVC.DLL 100864 5-8-1997 1:09:50 pm NWIPXIP.INF 4709 10-29-1998 7:34:32 am NWIPXSPX.DLL 41088 1-9-1996 7:17:58 am NWLAYOUT.INF 13892 8-2-1998 5:28:28 pm NWLINK2.VXD 17753 5-8-1998 5:50:34 am NWLOCALE.DLL 43408 9-20-1996 8:15:54 am NWMADMIN.HLP 31445 4-30-1997 11:59:18 am NWMSG95.CNT 11772 1-16-1996 5:37:32 am NWMSG95.HLP 140655 6-10-1998 4:29:52 pm NWNDPS.INF 4223 7-22-1998 10:52:48 am NWNET.DLL 225328 8-28-1997 4:19:02 am NWNETAPI.DLL 106884 12-17-1997 7:07:14 am NWPASSWD.DLL 22016 7-17-1998 11:09:42 am NWPASSWR.DLL 19456 7-17-1998 11:13:20 am NWPOPUP.EXE 19712 9-16-1998 8:24:04 am NWPSRV.DLL 279770 1-26-1996 3:55:30 am NWRCA.INF 4398 11-2-1998 8:45:40 am NWREGSVR.EXE 5632 3-24-1998 7:03:00 pm NWRRNSP.DLL 12288 8-26-1996 8:33:46 am NWSERV.INF 11546 7-14-1998 9:14:42 am NWSETUP.DLL 274672 10-29-1998 6:17:14 am NWSETUP.INI 9017 10-29-1998 1:52:06 am NWSHELLR.DLL 58880 7-17-1998 11:14:48 am NWSHELLX.DLL 156160 7-17-1998 11:13:52 am NWSIPX32.DLL 25088 3-19-1998 6:36:34 am NWSIPX32.NLM 27338 6-24-1998 3:15:26 am NWSRVLOC.DLL 8704 4-1-1998 6:30:22 am NWTRANS.INF 5514 10-16-1998 4:41:24 am NWTSAW95.CNT 334 6-10-1998 4:31:08 pm NWTSAW95.HLP 29287 6-9-1998 5:15:50 pm NWUNC32.DLL 16176 6-24-1998 7:04:18 am NWUSE.CNT 36 2-4-1998 9:48:34 am NWUSE.HLP 146775 10-27-1998 2:42:44 am NWWS2GW.DLL 23040 11-5-1998 8:46:04 am NWWS2NDS.DLL 27952 11-5-1998 8:29:40 am NWWS2SAP.DLL 24544 8-19-1998 9:35:16 am NWWS2SLP.DLL 36656 8-19-1998 9:35:46 am NWWSINST.DLL 4608 6-22-1998 2:49:44 pm NWWSMGR.INF 6033 10-29-1998 6:52:00 am ODINSUP.INF 4110 1-7-1998 9:28:02 am ODINSUP.SYS 17312 1-9-1998 8:56:18 am OEM.CNT 821 1-8-1996 8:06:44 am OIDMSG.IDX 55196 8-13-1998 11:04:38 am OIDNAME.MSG 53378 8-13-1998 1:12:14 pm OLEAUT32.DLL 492304 5-19-1997 3:08:12 am OLEPRO32.DLL 32528 11-5-1996 7:27:16 pm PARSER.NLM 6128 6-2-1997 7:58:08 am PCISETUP.EXE 18481 6-3-1996 8:42:48 am PHASERS.WAV 11114 12-1-1994 8:14:12 am PHBK1.DLL 103936 5-8-1997 1:11:12 pm PHBKSYNC.EXE 46080 5-8-1997 12:57:24 pm PROP.HLP 236067 10-27-1998 2:44:52 am PRTWIN16.DLL 279260 4-30-1996 6:09:38 am PRTWIN32.DLL 192512 5-1-1997 9:15:08 am QUEUEBUF.DLL 153088 10-15-1998 7:48:08 am RAPADM32.DLL 60416 5-8-1997 1:06:38 pm RCAGENT.HLP 82062 10-15-1998 8:31:54 am READ95.TXT 30790 10-30-1998 7:48:58 am RNAEX.DLL 43008 5-8-1997 1:14:06 pm RNAPH.DLL 9728 8-16-1996 8:44:32 am ROLLBACK.EXE 98256 6-24-1998 7:05:14 am SETUP.EXE 207808 11-6-1998 10:58:36 am SETUP1 17550 1-26-1997 5:09:48 pm SETUPAPI.DLL 342288 5-7-1998 7:00:00 pm SETUPNW.CNT 133 6-10-1998 4:31:58 pm SETUPNW.HLP 23248 6-24-1998 5:14:12 pm SLPINFO.BAT 109 6-22-1998 10:53:32 am SNMP.MSG 3816 7-20-1995 12:46:54 pm SNMP.NLM 26547 1-7-1996 7:32:50 am SNMPDLL.DLL 18432 1-23-1996 8:26:28 am SNMPIPX.EXE 18944 1-23-1996 8:34:58 am SNMPUDP.EXE 18944 1-23-1996 8:35:56 am SPX_SKTS.NLM 41902 8-4-1998 6:14:22 am SROUTE.NLM 10259 1-27-1998 3:24:08 am SRVLOC.NLM 74510 7-23-1998 5:20:22 am STDOLE2.TLB 16896 5-19-1997 3:08:12 am TCPIP.MSG 4206 6-17-1998 6:16:14 am TCPIP.NLM 233662 10-26-1998 10:51:36 am TLI_SPX.DLL 52853 1-14-1997 5:22:28 am TLI_WIN.DLL 15713 8-7-1995 11:56:42 am TRANNTA.MSG 170 9-10-1997 1:24:58 pm TRANNTA.NLM 37044 9-14-1998 5:14:36 am UNC32.INF 6127 6-24-1998 6:06:52 am UNINSTAL.HLP 22210 6-9-1998 5:19:30 pm UNINSTAP.EXE 20480 6-24-1997 4:28:42 am UNI_1250.001 1081 3-20-1998 6:06:02 am UNI_1250.W32 17408 6-26-1998 12:03:00 pm UNI_1251.001 874 3-20-1998 6:06:04 am UNI_1251.W32 17408 6-26-1998 12:04:20 pm UNI_1252.001 1049 3-23-1998 3:13:04 am UNI_1252.W16 10408 10-3-1997 5:35:28 am UNI_1252.W32 16896 6-26-1998 12:05:58 pm UNI_1253.001 980 3-20-1998 6:06:10 am UNI_1253.W32 16896 6-26-1998 12:07:04 pm UNI_1254.001 1108 3-20-1998 6:06:14 am UNI_1254.W32 17408 6-26-1998 12:08:54 pm UNI_1255.001 1076 3-20-1998 6:06:16 am UNI_1255.W32 17408 6-26-1998 12:10:32 pm UNI_1256.001 1273 3-23-1998 3:28:32 am UNI_1256.W32 17408 6-26-1998 12:12:12 pm UNI_1257.001 1076 3-20-1998 6:06:24 am UNI_1257.W32 17408 6-26-1998 12:13:30 pm UNI_1258.001 1204 3-20-1998 6:06:26 am UNI_1258.W32 17408 6-26-1998 12:14:48 pm UNI_437.W16 11140 10-3-1997 8:29:46 am UNI_437.W32 17920 6-26-1998 11:32:04 am UNI_737.W32 17408 6-26-1998 11:33:50 am UNI_775.W32 17920 6-26-1998 11:35:22 am UNI_850.W32 17408 6-26-1998 11:36:34 am UNI_852.W32 17920 6-26-1998 11:37:52 am UNI_855.W32 17920 6-26-1998 11:39:18 am UNI_857.W32 17408 6-26-1998 11:40:48 am UNI_860.W32 17920 6-26-1998 11:42:36 am UNI_861.W32 17920 6-26-1998 11:44:08 am UNI_862.W32 17920 6-26-1998 11:45:50 am UNI_863.W32 17920 6-26-1998 11:47:34 am UNI_864.W32 17408 6-26-1998 11:49:10 am UNI_865.W32 17920 6-26-1998 11:50:28 am UNI_866.W32 17920 6-26-1998 11:51:56 am UNI_874.001 731 3-20-1998 6:03:20 am UNI_874.W32 16896 6-26-1998 11:53:40 am UNI_932.001 46475 5-20-1998 11:26:40 am UNI_932.W32 78336 6-26-1998 12:40:28 pm UNI_936.001 31028 3-20-1998 7:37:18 am UNI_936.W32 72704 6-26-1998 12:42:26 pm UNI_949.001 34400 3-20-1998 6:05:10 am UNI_949.W32 90624 6-26-1998 12:43:48 pm UNI_950.001 47106 3-20-1998 6:05:58 am UNI_950.W32 91648 6-26-1998 12:45:18 pm UNI_COL.001 665 3-20-1998 6:06:28 am UNI_MON.001 2361 3-20-1998 6:06:32 am UNI_MON.W16 11832 10-3-1997 8:34:02 am UNI_MON.W32 23040 6-26-1998 12:16:10 pm UNI_UPR.W16 12176 10-3-1997 8:35:50 am UNI_UPR.W32 23552 6-26-1998 12:17:32 pm UNREG32.EXE 8192 7-16-1998 5:50:46 am UPPSMLID.EXE 75661 3-17-1996 7:01:00 pm VMLID.MSG 505 12-15-1995 3:45:18 am VMLID.NLM 30375 6-8-1998 1:48:46 am VUSER.386 9285 10-15-1998 6:29:24 am VXDLIST.VXD 4662 10-17-1997 12:00:28 pm W95TSA.DLL 99840 8-14-1998 7:38:42 am W95TSA.EXE 162304 8-14-1998 7:45:00 am W95TSARC.DLL 34304 7-21-1998 12:42:30 pm W95TSARP.DLL 63488 8-14-1998 7:42:20 am WCHAT32.EXE 49664 10-15-1998 6:48:42 am WHMOBILE.HLP 22440 6-10-1998 4:33:30 pm WINPING.EXE 42496 10-28-1998 1:01:02 am WM95.EXE 139776 10-30-1998 10:24:38 am WM95API.DLL 30720 9-23-1998 7:17:10 am WM95CSP.DLL 120320 8-28-1998 5:51:32 am WM95ENDS.NLM 826 1-20-1998 4:25:36 am WM95INV.DLL 114688 6-11-1998 9:53:46 am WM95PM.DLL 37888 8-16-1998 11:37:54 am WM95R.DLL 12288 6-18-1998 4:02:06 am WM95ROAM.DLL 8192 10-20-1998 7:49:40 am WM95SASR.DLL 5632 5-18-1998 4:01:08 am WM95SAST.EXE 35328 9-23-1998 7:33:04 am WM95USP.DLL 134656 6-11-1998 9:55:54 am WMCCHLPR.DLL 391680 10-29-1998 9:54:34 am WMPRT95.DLL 35840 4-29-1998 12:43:36 pm WMRASM.DLL 28672 7-15-1998 10:51:10 am WMREG.DLL 24064 8-19-1998 9:15:40 am WMREG16.DLL 11336 2-12-1998 1:31:48 pm WMSCHAPI.DLL 136704 1-29-1998 9:36:48 am WMSCHED.CNT 744 6-10-1998 4:49:26 pm WMSCHED.DLL 134656 8-19-1998 9:21:16 am WMSCHED.EXE 23040 7-17-1998 5:57:44 am WMSCHED.HLP 72339 10-6-1998 4:58:56 am WMSCHEDR.DLL 33792 8-19-1998 10:14:12 am WMUTIL.DLL 27408 10-20-1998 8:01:16 am WOUDAT16.DLL 15360 10-15-1998 6:24:58 am WS2NSINS.EXE 167424 8-19-1998 6:53:26 am WS2SETUP.EXE 986400 3-23-1998 8:13:38 am WSLAVE32.EXE 75264 10-15-1998 6:49:24 am WSREG.DLL 199168 10-27-1998 5:01:34 pm WSREG32.EXE 132608 10-27-1998 5:01:40 pm WSREG32R.DLL 47104 10-27-1998 5:01:44 pm WUSER.EXE 113152 10-15-1998 2:19:02 pm WUSERMSG.DLL 17408 10-15-1998 7:53:52 am ZENPOL32.DLL 67072 10-14-1998 9:42:44 am ZENRC32.EXE 148992 10-28-1998 12:20:50 pm ..\W95302\ADMIN\ NCIMAN.CNT 293 6-10-1998 4:42:20 pm NCIMAN.EXE 454656 10-29-1998 8:58:20 am NCIMAN.HLP 20966 6-9-1998 5:46:20 pm NCIMANR.DLL 206848 10-20-1998 9:04:26 am UNC32.EXE 107632 6-24-1998 7:03:26 am UNC32.INF 6127 6-24-1998 6:06:52 am UNINSTAL.HLP 22210 6-9-1998 5:19:30 pm ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------