NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: NFS199.EXE; NFS2.1 Update README FOR: NFS199.EXE NOVELL PRODUCTS and VERSIONS: NetWare NFS Services - NetWare 4 Edition 2.1 ABSTRACT: NFS199.EXE contains a patch for NetWare NFS Services, version 2.1. NFS199.EXE is strongly recommended for all NetWare NFS Services, version 2.1. NFS199.EXE supersedes NFS197.EXE and NFS198.ZIP. NFS199.EXE is required for all NetWare 4.11 and IntranetWare users with NetWare NFS Services 2.1. ----------------------------------------------------------------- DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS 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. ----------------------------------------------------------------- ISSUE: TITLE: NFS199.EXE, Maintenance Patch for NetWare NFS Services - NetWare 4 Edition, version 2.1 DOCUMENT ID: DOCUMENT REVISION: A DATE: 14 October 1996 AUTHOR: Amitabh Sinha ALERT STATUS: Yellow DISTRIBUTION: Public INFORMATION TYPE: Symptoms, Solutions, and New Features README FOR: NFS199.EXE NOVELL PRODUCT CLASS: UNIX Connectivity NOVELL PRODUCT and VERSION: NetWare NFS Services - NetWare 4 Edition, version 2.1 CATEGORY: NA This TID has the following organization: SYMPTOMS: List of the bugs fixed and the enhancements SOLUTION: Recommended use of this patch and installation instructions NEW FEATURES: Configuring the FTP server for web clients Implementing a large block of memory for mounting Implementing lock compatibility between the NFS Gateway and Sun's PCNFS Implementing immediate file access to a NFS Gateway volume Printing to devices that emulate UNIX host LPR Using an alias to export a queue in a different context Tuning the NFS 2.1 server Configuring TCP/IP on a NetWare SFT III server ----------------------------------------------------------------- SYMPTOMS ----------------------------------------------------------------- When the NetWare server ran the NFS NLMs, the PACKET RECEIVE BUFFERS continued to increment up to the value set as MAXIMUM PACKET RECEIVE BUFFERS. The server appeared to hang, and MONITOR showed high CPU utilization with most, if not all, ECBs belonging to TCP/IP process. When reading files, the NetWare NFS server would occasionally abend due to a page fault. When accessing files on a NetWare NFS server, file ownership and access permissions randomly changed. During install, after all of the files were copied to the server and UNICON was loading, the installer tried to log in and received the error message that "Remote TCP/IP administration not running." The NetWare FTP server would not allow users to log in after the administrator had modified FTP access through the FTP Administration option in UNICON. The NetWare FTP server returned a generic return code of 200 upon successful completion of a directory change. Some clients expected a specific return code of 250. The NetWare FTP server did not allow multiple anonymous users to access the same file at the same time. When users were at the root level of a volume on a NetWare FTP server, they could not change to a subdirectory without using an absolute path name. When a user logged in as an anonymous user, the NetWare FTP server required a password (when a password had not been assigned). The NetWare FTP server did not support the STORE UNIQUE (STOU; SUNIQUE) command. The NetWare FTP server user could not log in if the NDS home directory was on a remote server that was down. The NetWare DNS server did not properly handle a primary domain name suffixed with anything other than .COM. UNICON failed to save the DNS database to text files. The following error message was displayed: "NIS and DNS services not configured to run on this machine." The NetWare DNS server did not properly resolve the MX (mail exchange) query. The NetWare DNS Server abended while doing a zone dump from a secondary server when the size of the reply was larger than the buffer allocated by the DNS server. SUN's NIS+ server, when running in YP emulation (NIS emulation) mode, did not support YPPROC_ORDER remote procedure call. This resulted in a situation where YPXFR.NLM could not get the NIS maps order numbers and would abort the transfer of maps. The NetWare NFS gateway failed to mount DEC VMS file systems. The NetWare NFS gateway did not support the SGID bit on remote directories. The NetWare NFS gateway server abended when it tried to mount more than 64 volumes. The OS/2 session hung while copying a file to a NFS Gateway volume. Even though the NetWare user was mapped, the NFS Gateway displayed the message: "Login user xxx does not have NFS UID and GID." From the UNICON menu, if the administrator selected the following options (Manage Services-> NFS Gateway->Configure Volumes) and then pressed the key, incorrect resource information was displayed. When the UNIX server had a hard disk larger than two Gigabytes, incorrect volume information was displayed and write-through was unnecessarily turned on. A NetWare client could not see changes made from UNIX to a NetWare NFS gateway directory until a file scan (DIR or other NetWare command that performs a scan) was done. When NetWare NFS print services was loaded while NDS was unloaded, the NetWare server abended with the following message: "NLM unloaded without deleting all its semaphore." The PLPD module would unload if the NETDB module did not successfully log in to NDS. The PLPD module used too much server memory when several jobs were sent from UNIX hosts. After applying the FORTRAN filter, FORTRAN print jobs would not print. When UNIX to NetWare printing was configured with UNICON, the NetWare server would occasionally abend. LPR clients were unable to submit print jobs to NetWare queues when the queue names were longer than eight characters. LPR gateway jobs were printed twice if the printer ran out of paper. When more paper was added, the printer finished the interrupted print job and then printed the job again. The PLPD module refused LPR requests from unauthorized port numbers (port numbers less than 1024). When using the LPR gateway, PSERVER showed "PRINTER MAY NEED ATTENTION" status and had to be restarted. When using the LPR Gateway, PSERVER showed the XRP printer state changing between "Ready for New Job" and "Error at remote Unix host." The PKERNEL module displayed the following error message: "No sequence numbers available for the remote host." When the LPR Gateway was unloaded and then loaded again, the LPR Gateway displayed the error message: "No configured UNIX printers." ---------------------------------------------------------------- SOLUTIONS ---------------------------------------------------------------- To resolve any of the problems described in the SYMPTOMS section, install the NFS199.EXE self-extracting file. NOTE: NFS199 replaces some of the NFS Services 2.1 files. It cannot run on its own, and it cannot be used to upgrade from NetWare NFS 1.x or NFS Gateway 1.x to NetWare NFS 2.1 NetWare 4 Edition. ----------------------------------------------------------------- NEW FEATURES ----------------------------------------------------------------- ----------------------------------------------------------- Configuring the Netware FTP Server for Web Clients ----------------------------------------------------------- 1. Verify that the Anonymous user is enabled and the home directory is set. a. Starting at the UNICON main menu, select the following options: Manage Services--> FTP Server--> Set Parameters. b. On the FTP Server Parameters form, check that the "Anonymous User's Home Directory" is configured and that "Anonymous User Access" is set to "Yes." 2. Verify that the Anonymous user is mapped. a. Starting at the UNICON main menu, select the following options: Manage Global Objects--> Manage Users. b. Select a method to view the mapping for the Anonymous user. By default the UID is set to 32000. 3.Verify that the volume where the Anonymous user's home directory resides supports the NFS name space. The console command, VOLUME, will display whether the volume supports the NFS name space. If not, enter the following console command: ADD NAME SPACE NFS TO Replace with the name of the volume that needs the NFS name space. 4.Verify that the Anonymous user owns its home directory and has file access rights to the directory. a. Starting at the UNICON main menu, select the following options: Perform File Operations--> View/Set File Permissions. b. Select the Anonymous user's home directory. c. Set the owner to Anonymous and give the owner NFS access rights. --------------------------------------------------------------- Implementing a Large Block of Memory for Mounting --------------------------------------------------------------- The NFS gateway module supports the allocation of a large block of memory when initially mounting an NFS gateway volume. The size of the initial block of memory is set with UNICON in the NFS Gateway Volume Information form. Select the volume that needs a larger block of memory and enter the block allocation number. The valid range is from 1 to 128 (each block contains 256KB of memory). To implement a large block of memory for mounting a volume, complete the following steps: 1. Install the NFS199.EXE patch. 2. Set error logging to INFORMATIONAL and clear the audit log. 3. At the server console, run the UNISTOP script. 4. At the server console, run the UNISTART script. 5. Load UNICON. 6. Configure each gateway volume to the number of blocks to be allocated. This is set in the NFS Gateway Volume Information form. To display the form, select the following options starting at the main menu: NFS Gateway Administration --> Configure Volumes --> volume. 7. Mount the NFS Gateway volumes. 8. Monitor the audit log to determine how many 256KB blocks are needed for each volume. ----------------------------------------------------------- Implementing Lock Compatibility between the NFS Gateway and Sun's PCNFS ----------------------------------------------------------- 1. Edit SYS:ETC\NWPARAMS file. 2. Set PCNFS_COMPATIBILITY to 1 in the [NFSGW] section. The PCNFS_COMPATIBILITY parameter makes NFS gateway locking compatible with Sun's PCNFS locking. ----------------------------------------------------------- Implementing Immediate File Access on NFS Gateway Volume ----------------------------------------------------------- To make files created from UNIX immediately visible to NetWare users accessing the NFS Gateway volume, complete the following steps: 1. Edit the SYS:ETC\NWPARAMS file. 2. Add the following parameters to the [NFSGW] section: DIR_COMP_TIME 0 GW_EXHAUSTIVE_SEARCH 1 The DIR_COMP_TIME parameter forces a frequent directory compare between the NetWare information and the UNIX information so that changes from UNIX are immediately visible from NetWare. The GW_EXHAUSTIVE_SEARCH parameter allows UNIX filenames with capital letters to be immediately visible. ----------------------------------------------------------- Printing to Devices That Emulate UNIX Host LPR ----------------------------------------------------------- The LPR Gateway was originally designed to interface only with actual UNIX hosts. Thus, the gateway's function was to transfer a print job to the host and optionally monitor the progress of the job at the host. However, with the advent of hardware that a llows printers to emulate the LPR protocol, many customers wanted to eliminate the UNIX host for printing purposes and transfer directly to the printer. The following devices have been tested and performed well with LPR gateway: HP JetDirect Card LANTRONICS MPS1 Other devices that emulate the LPR protocol may work with the LPR Gateway, but they have not been tested. This release of the LPR Gateway uses a set of parameters that are defined in the file "SYS:ETC/NWPARAMS" in the [PRINT_ADMIN] section. The file is case sensitive, so enter the parameter names in all capitals. The parameters are as follows: LPR_GWY_DIRECT_MODE ON Specifies when the job is sent to the printer by setting the LPR Gateway in direct or indirect mode. If the parameter is set to "on," the LPR Gateway is set to direct mode, and the next print job is immediately sent without waiting for the previous job to print. In this mode, once the print job has been spooled to the remote printer, the job cannot be ab orted or its status checked from the NetWare side. If the parameter is set to "off," the LPR Gateway is set to indirect mode, status checking is done until the job is printed, and the next job is not sent until the previous print job is finished. In this mode the NetWare user can check the status and abor t the job after it is spooled to the remote printer. For printers connected via the HP JetDirect Card, this parameter has no effect. The default mode is "ON." LPR_GWY_POLLING_TIME 2 Specifies, in seconds, how long the LPR Gateway waits after submitting a print job to interact with the remote printer. For direct mode, this is the time before sending the next print job, and for indirect mode, it is the time interval between status chec ks of the printer. The default value is 2 seconds. LPR_GWY_WRT_CHK_TIME 15 Specifies, in seconds, how long the LPR Gateway waits for a response after sending a write request while queuing a job. If the time expires, a check is made to see if the LPR Gateway is going down or the job is being aborted. If not, a secondary status is displayed of "BUSY/Printing." The default value is 15 seconds. LPR_GWY_CHK_PRT_TIME 90 Specifies, in seconds, how long the "BUSY/Printing" message is displayed before the message "May Need Attention" is displayed. The default value is 90 seconds. LPR_GWY_IR_TIME 60 Specifies, in seconds, how long the LPR Gateway waits to check on printers that are in an error condition state. The default value is 60 seconds. ----------------------------------------------------------- Using an Alias to Export a Queue in a Different Context ----------------------------------------------------------- 1. Use UNICON to create a print queue in the NDS context of the NetWare server that has the NFS/PRTS 2.1 product installed. The queue will be displayed as its common name if it resides in the server's NDS context (in this case ). Since servers running NetWare 4.1 and above can support multiple NDS contexts, the queue can be created in any context which the server is configured for. 2. Use UNICON to export this queue . 3. Use NWADMIN to create the queue in the desired context. 4. Use NWADMIN to delete queue from the context where NFS/PRTS 2.1 is installed. 5. Use NWADMIN to create an alias queue in the context where NFS/PRTS 2.1 is installed and point the alias to the new queue in the desired context. The alias queue is now set up to be used as one of the exported NetWare queues. -------------------------------------------------- Tuning the NFS 2.1 Server -------------------------------------------------- Many normal activities such as users logging into the server or backing up a server can cause NetWare 4.1 servers to reach 100% utilization. Peaking to 100% utilization is not bad, but if utilization is consistently high, some low priority threads may ca use your server to hang when they run. The server has normal tasks that are very CPU intensive, and these tasks are scheduled to run as low priority tasks when the server is not busy. Some of these tasks are related to the health of NetWare volumes, such as sub-block allocation and disk compre ssion. While these volume tasks are run, other threads that need to access the volume block on the volume semaphore. If your system is not properly tuned and NFS is consuming large time slices, then the low priority threads are not run. The server can then lock up when one of the sub-allocation pools runs out. The server then schedules the sub-allocation thread even tho ugh the server is busy, and all the server threads can end up blocked on the volume semaphore. The server requires a thread to restart the sub-allocation thread, but all available threads are in use. When this happens, MONITOR shows that the current number of server threads equals the maximum number of server threads. Follow the steps below to increase the performance and decrease the utilization of the server. 1. Make sure that the NetWare server and the drivers are at the current patch level. 2. Determine if the applications running on the server create a lot of temporary files. If this is the case, enable Immediate Purge of deleted files on the volumes that store the temporary files. The purging frees up directory entries and lowers CPU utili zation. 3.Tune the Number of Packet Receive Buffers to ensure that there are enough Packet Receive Buffers. Set the minimum number of packet receive buffers to two times the number of licensed connections and the maximum number of packet receive buffers to four times the number of licensed connections. 4. Disable File Compression and Packet Burst. Disabling File Compression and Packet Burst lowers CPU utilization. 5. After applying the NFS199 patch, monitor the performance of the NFS server to see if adjusting the number of NFS server threads is required. If performance is consistently high, increase the number of NFS server threads. a. Starting at the UNICON main menu, select the following options: Manage Services--> NFS Server--> Set Parameters. b. Increase the Number of NFS Threads from its current level to 10 more. You will need to monitor performance and gradually increase the threads by increments of 10 to find the right number for the server. The NFS patch changes the upper limit for threads from 20 to 150. The NFS server uses the threads to handle all the NFS server traffic. Increasing the number of threads allows more concurrent operations on the NetWare server. NOTE: After installing the patch and then loading PKERNEL, the initial TCP/IP Receive Buffers count may quickly climb but should drop off and remain low. ---------------------------------------------------- Configuring TCP/IP on a NetWare SFT III System ---------------------------------------------------- From a TCP/IP network perspective, a NetWare SFT III system consists of the following modules: two IO engines and a MS engine. NOTE: For NetWare 4.11 SFTIII and IntranetWare SFTIII users, there is a known issue if you are newly installing the NetWare NFS Services 2.1. You may not be able to complete the install time configration for the product because the UNICON login to the NetWare Server may time out at random. If you encounter this problem please contact Novell technical support for the fix. The two IO engines, IO Engine1 and IO Engine2, are connected to the physical network, and each has a unique IP address. The MS engine resides on a virtual LAN and is not directly connected to the physical network. The MS engine interfaces with the real network through the IO engines. The virtual LAN is a stub-subnet with the IO engines acting as routers between the real ne twork and the virtual LAN. (The IO engine on the Primary Server routes IP packets between the MS engine and the real/physical network.) The two IO engines share a common IO engine interface on the virtual LAN, and this interface resides on the virtual LAN along with the MS engine. In this document, this common interface is called the IO Engine-MS Engine Internal Interface. The two nodes on the virtual LAN, the MS Engine and the IO Engine-MS Engine Internal Interface, use a common stub-subnet Mask and each node has a unique IP address. Thus, an SFT III system requires four IP addresses: one for IO Engine 1 one for IO Engine 2 one for the MS Engine one for the IO Engine-MS Engine Internal Interface Figure 1. TCP/IP Configuration Example +-------------------------------+ | Mirrored Server - MS Engine | | 154.88.219.33 | +-------------------------------+ | | | Virtual LAN ---------------------------------------------- | | | (IO Engine-MS Engine Internal Interface) |------------154.88.219.34-----------| +-----------------+ +-----------------+ | IO Engine 1 | | IO Engine 2 | | 154.88.219.36 | | 154.88.219.37 | +-----------------+ +-----------------+ | | | Real Network 154.88.219.0 | -------------------------------------------------------------- In addition to the addresses illustrated in Figure 1, TCP/IP needs two other reserved addresses for IP network transactions. Also, the addresses in the stub-subnet mask address range cannot be allocated to any other node on the real/physical network. The refore, the actual range of IP addresses to be allocated or reserved for the NetWare SFT III system extends beyond the four addresses illustrated in Figure 1. To explain this, let's assume some example addresses. An SFT III system is to be set up on a class B subnetwork; the subnet IP address is 154.88.219.0. The Subnet Mask used by the IO Engines on the physical network will be 255.255.255.0 (FF.FF.FF.00), t he same as for any node on the network. Let us assume that the following range of IP addresses are available: 154.88.219.32 to 154.88.219.63. A stub-subnet mask is created by using any number other than 0 in the last slot of the mask address. We recommend the following configuration: Stub-Subnet Mask Number of IP addresses to be set aside exclusively for the Stub-Subnet 255.255.255.252 (FF.FF.FF.FC) 4 This configuration provides the stub-subnet with 4 addresses that the virtual LAN requires. Other masks can be used, for example FF.FF.FF.F8, but they reserve more IP addresses than the virtual LAN requires. (FF.FF.FF.F8 reserves 8 addresses.) The above subnet mask, 255.255.255.252, provides four addresses, of which two are assigned and two are reserved for IP network functions. You must pick four addresses which have a binary equivalent that ends in the following sequential values: 00 01 10 11 The addresses which have a binary equivalent of 00 or 11 must be reserved and not assigned. The addresses with a binary equivalent of 01 or 10 are assigned to the MS Engine and the IO Engine-MS Engine Internal Interface respectively. Using the range given above (154.88.219.32 to 154.88.219.63), the following numbers have a binary equivalent of 00 and can be used for a starting IP address of the virtual LAN: 32,36,40,44,48,52,56,60 For the following example, we will use the first four addresses in the range beginning with 154.88.219.32: The stub-subnet mask, 255.255.255.252, will use the following IP addresses: 154.88.219.32 = 0010 0000 (reserved) --> 154.88.219.33 = 0010 0001 (MS Engine) --> 154.88.219.34 = 0010 0010 (IO Engine-MS Engine Internal Interface) 154.88.219.35 = 0010 0011 (reserved) These four addresses cannot be used by any other node on the network, regardless of subnet mask. In addition to these addresses, the two IO engines need IP addresses. These addresses can be any other address in the above range, but for this example we wi ll assume the next two sequential addresses: Node IP Address Subnet Mask IO Engine1 154.88.219.36 255.255.255.0 IO Engine2 154.88.219.37 255.255.255.0 To set up the TCP/IP configuration on SFT III system, complete the following steps. These steps use the addresses described in the example above. 1. Configure IO Engine1. a. From the IO Engine1 console screen, load INETCFG. b. Select the following options: Bindings Option --> TCP/IP protocol. c. Press the key to configure the IP address and the subnet mask for IO Engine1. Use the following: IP Address for IO Engine1 154.88.219.36 Subnet Mask 255.255.255.0 d. Press the key to return to the main menu. e. Select the following options: Protocols Option --> TCP/IP protocol. f. Configure the IP address for the SFT III Network (the IP address for the IO Engine-MS Engine Internal Interface) and the subnet mask of SFT III network (the stub-subnet Mask). Use the following: IP address 154.88.219.34 Subnet Mask 255.255.255.252 2. From IO Engine2 console screen, load INETCFG and repeat the same steps as described above for IO Engine1. Use the following address for IO Engine2: IP Address for IO Engine2 154.88.219.37 Subnet Mask 255.255.255.0 The IP address for the IO Engine-MS Engine Internal Interface and its subnet mask are the same as the values assigned in the protocol form for IO Engine1. Use the following: IP Address 154.88.219.34 Subnet Mask 255.255.255.252 3. Configure the MS Engine. a. From the MS Engine console screen (accessed from either machine), load INETCFG. b. Select the following options: Protocols Option --> TCP/IP protocol c. Configure the following: "IP address for the SFT III Network" (the IP address for the MS Engine) and "Subnet Mask of SFT III Network" (the Stub-subnet Mask). Use the following: IP Address 154.88.219.33 Subnet Mask 255.255.255.252 Once the TCP/IP configuration for the SFT III system is complete (and TCP/IP has been loaded in both the IO Engines and the MS Engine), you can verify the configuration by doing a PING operation to the MS Engine IP address from another node (for example, a UNIX host) on the network. NOTE: To allow RIP broadcasts to function properly and reach the internetwork, the RIP = YES parameter is required. After successful configuration, the .NCF script files used by NetWare SFT III system contain the TCP/IP network configuration. Using the addresses and masks from the example above, the script files would contain the following configuration. DO NOT MODIFY THESE FILES WITH ANY TEXT EDITOR. Use the view option in INETCFG. I/O Engine 1--- The SYS:ETC/IO1/NETINFO.CFG file LOAD TCPIP RIP=YES FORWARD=YES BIND IP NE2000 ADDR=154.88.219.36 MASK=255.255.255.0 BIND IP MSENGINE ADDR=154.88.219.34 MASK=255.255.255.252 I/O Engine 2---The SYS:ETC/IO2/NETINFO.CFG file LOAD TCPIP RIP=YES FORWARD=YES BIND IP NE2000 ADDR=154.88.219.37 MASK=255.255.255.0 BIND IP MSENGINE ADDR=154.88.219.34 MASK=255.255.255.252 MS Engine ---The SYS:ETC/NETINFO.CFG file LOAD TCPIP RIP=YES FORWARD=NO BIND IP MSENGINE ADDR=154.88.219.33 Self-Extracting File Name: NFS199.EXE Files Included Size Date Time ..\ NFS199.TXT (This file) NFS199.TXT 63519 10-15-96 10:30:22 pm ..\DISK1\ NFSICMD.NLM 16524 7-2-96 4:36:08 pm PINSTALL.IPS 550 10-14-96 11:23:16 pm PINSTALL.NLM 163665 9-28-96 10:37:46 pm README.TXT 30263 10-14-96 11:20:10 pm SPACE.DAT 13 9-30-96 6:53:46 pm ..\DISK1\ETC\ NFS20.MIB 25591 12-1-94 3:06:48 am ..\DISK1\SYSTEM\ NFSUNINS.NLM 95799 9-28-96 10:38:16 pm PCONFIG.NLM 21394 9-28-96 10:38:00 pm PKERNEL.NLM 172804 9-30-96 6:53:56 pm UNISTART.NCF 4 8-6-96 9:18:06 pm ..\DISK1\SYSTEM\NLS\ ..\DISK1\SYSTEM\NLS\19\ NFSUNINS.HLP 898 3-3-95 8:01:18 pm NFSUNINS.MSG 12243 9-28-96 10:38:12 pm PCONFIG.DAT 15077 9-30-96 6:01:34 pm PCONFIG.HLP 2183 7-29-92 8:27:20 pm PCONFIG.MSG 1142 9-28-96 10:37:58 pm PFILES.DAT 42060 9-30-96 6:53:46 pm PINSTALL.HLP 7839 6-20-95 4:20:58 pm PINSTALL.MSG 12243 9-28-96 10:37:42 pm PKERNEL.MSG 3924 9-27-96 10:37:42 pm ..\DISK1\SYSTEM\NLS\4\ NFSUNINS.HLP 898 3-3-95 8:01:18 pm NFSUNINS.MSG 12243 9-28-96 10:38:12 pm PCONFIG.DAT 15077 9-30-96 6:01:34 pm PCONFIG.HLP 2183 7-29-92 8:27:20 pm PCONFIG.MSG 1142 9-28-96 10:37:58 pm PFILES.DAT 42060 9-30-96 6:53:46 pm PINSTALL.HLP 7839 6-20-95 4:20:58 pm PINSTALL.MSG 12243 9-28-96 10:37:42 pm PKERNEL.MSG 3924 9-27-96 10:37:42 pm ..\DISK1\SYSTEM\NLS\6\ NFSUNINS.HLP 898 3-3-95 8:01:18 pm NFSUNINS.MSG 12243 9-28-96 10:38:12 pm PCONFIG.DAT 15077 9-30-96 6:01:34 pm PCONFIG.HLP 2183 7-29-92 8:27:20 pm PCONFIG.MSG 1142 9-28-96 10:37:58 pm PFILES.DAT 42060 9-30-96 6:53:46 pm PINSTALL.HLP 7839 6-20-95 4:20:58 pm PINSTALL.MSG 12243 9-28-96 10:37:42 pm PKERNEL.MSG 3924 9-27-96 10:37:42 pm ..\DISK1\SYSTEM\NLS\7\ NFSUNINS.HLP 898 3-3-95 8:01:18 pm NFSUNINS.MSG 12243 9-28-96 10:38:12 pm PCONFIG.DAT 15077 9-30-96 6:01:34 pm PCONFIG.HLP 2183 7-29-92 8:27:20 pm PCONFIG.MSG 1142 9-28-96 10:37:58 pm PFILES.DAT 42060 9-30-96 6:53:46 pm PINSTALL.HLP 7839 6-20-95 4:20:58 pm PINSTALL.MSG 12243 9-28-96 10:37:42 pm PKERNEL.MSG 3924 9-27-96 10:37:42 pm ..\DISK1\SYSTEM\NLS\8\ NFSUNINS.HLP 898 3-3-95 8:01:18 pm NFSUNINS.MSG 12243 9-28-96 10:38:12 pm PCONFIG.DAT 15077 9-30-96 6:01:34 pm PCONFIG.HLP 2183 7-29-92 8:27:20 pm PCONFIG.MSG 1142 9-28-96 10:37:58 pm PFILES.DAT 42060 9-30-96 6:53:46 pm PINSTALL.HLP 7839 6-20-95 4:20:58 pm PINSTALL.MSG 12243 9-28-96 10:37:42 pm PKERNEL.MSG 3924 9-27-96 10:37:42 pm ..\DISK2\ ..\DISK2\ETC\ RPCNET.CFG 156 8-4-94 7:37:36 pm ..\DISK2\ETC\NET\ ..\DISK2\ETC\NET\NETWARE\ SERVICES 140 7-31-92 10:39:50 pm ..\DISK2\SYSTEM\ CONFADDR.NLM 27576 9-19-96 10:00:06 pm DISPATCH.NLM 18236 9-27-96 10:38:34 pm DNSADMIN.NLM 43827 9-19-96 10:18:12 pm DNSAGENT.NLM 32828 9-19-96 10:13:54 pm DNSCONV.NLM 3674 9-19-96 10:11:08 pm DNSDBGEN.NLM 12992 9-19-96 10:18:42 pm DNSUTIL.NLM 2459 9-19-96 10:18:56 pm HOSTG.NLM 10726 9-19-96 9:56:22 pm HOSTGADM.NLM 7073 9-19-96 9:56:46 pm HOSTGAGT.NLM 3764 9-19-96 9:57:02 pm INETD.NLM 6390 9-19-96 10:21:08 pm LOCAL_ND.NLM 4930 7-11-94 12:48:04 am NAMED.NLM 34693 9-19-96 9:54:22 pm NETDB.NLM 48596 9-19-96 9:49:52 pm NETDIR.NLM 7155 9-22-94 9:11:02 pm NFSUSER.NLM 45092 9-27-96 10:39:26 pm NFS_41X.NAM 15007 9-27-96 7:24:28 pm NFS_GR.NAM 15541 9-27-96 7:24:50 pm NWNFS.NLM 12760 9-27-96 10:38:46 pm SPX_ND.NLM 5378 7-11-94 12:47:44 am SRVAGT.NLM 22596 9-27-96 10:39:36 pm TCP_ND.NLM 7232 7-11-94 12:38:14 am TIRPC.NLM 52636 3-3-95 1:16:24 am UNICON.NLM 92346 9-27-96 10:39:08 pm USRAGT.NLM 15695 9-27-96 10:39:46 pm ..\DISK2\SYSTEM\NLS\ ..\DISK2\SYSTEM\NLS\19\ CONFADDR.MSG 2201 9-19-96 10:00:02 pm DISPATCH.MSG 1882 9-27-96 10:38:32 pm DNSADMIN.HLP 6167 5-31-95 11:25:56 pm DNSADMIN.MSG 5213 9-19-96 10:18:08 pm DNSAGENT.MSG 2028 9-19-96 10:13:52 pm DNSCONV.MSG 474 9-19-96 10:11:08 pm HOSTG.MSG 474 9-19-96 9:56:20 pm HOSTGADM.HLP 1170 1-8-95 12:04:08 am HOSTGADM.MSG 968 9-19-96 9:56:44 pm HOSTGAGT.MSG 225 9-19-96 9:57:02 pm INETD.MSG 763 9-19-96 10:21:06 pm IPADDR.HLP 2823 1-9-95 4:45:06 pm NAMED.MSG 4803 9-19-96 9:54:18 pm NETDB.MSG 2013 9-19-96 9:49:48 pm NFSUSER.MSG 4963 9-27-96 10:39:22 pm NFS_41X.MSG 2159 9-27-96 7:24:24 pm NFS_GR.MSG 2216 9-27-96 7:24:48 pm NIS.MSG 7937 9-27-96 10:42:40 pm NWNFS.HLP 142 1-31-95 7:01:04 pm NWNFS.MSG 2677 9-27-96 10:38:42 pm SRVAGT.MSG 1354 9-27-96 10:39:32 pm UNICON.HLP 15185 5-31-95 3:12:20 pm UNICON.MSG 10329 9-27-96 10:39:00 pm USER.HLP 13367 8-4-95 5:17:44 pm USRAGT.MSG 705 9-27-96 10:39:44 pm ..\DISK2\SYSTEM\NLS\4\ CONFADDR.MSG 2201 9-19-96 10:00:02 pm DISPATCH.MSG 1882 9-27-96 10:38:32 pm DNSADMIN.HLP 6167 5-31-95 11:25:56 pm DNSADMIN.MSG 5213 9-19-96 10:18:08 pm DNSAGENT.MSG 2028 9-19-96 10:13:52 pm DNSCONV.MSG 474 9-19-96 10:11:08 pm HOSTG.MSG 474 9-19-96 9:56:20 pm HOSTGADM.HLP 1170 1-8-95 12:04:08 am HOSTGADM.MSG 968 9-19-96 9:56:44 pm HOSTGAGT.MSG 225 9-19-96 9:57:02 pm INETD.MSG 763 9-19-96 10:21:06 pm IPADDR.HLP 2823 1-9-95 4:45:06 pm NAMED.MSG 4803 9-19-96 9:54:18 pm NETDB.MSG 2013 9-19-96 9:49:48 pm NFSUSER.MSG 4963 9-27-96 10:39:22 pm NFS_41X.MSG 2159 9-27-96 7:24:24 pm NFS_GR.MSG 2216 9-27-96 7:24:48 pm NIS.MSG 7937 9-27-96 10:42:40 pm NWNFS.HLP 142 1-31-95 7:01:04 pm NWNFS.MSG 2677 9-27-96 10:38:42 pm SRVAGT.MSG 1354 9-27-96 10:39:32 pm UNICON.HLP 15185 5-31-95 3:12:20 pm UNICON.MSG 10329 9-27-96 10:39:00 pm USER.HLP 13367 8-4-95 5:17:44 pm USRAGT.MSG 705 9-27-96 10:39:44 pm ..\DISK2\SYSTEM\NLS\6\ CONFADDR.MSG 2201 9-19-96 10:00:02 pm DISPATCH.MSG 1882 9-27-96 10:38:32 pm DNSADMIN.HLP 6167 5-31-95 11:25:56 pm DNSADMIN.MSG 5213 9-19-96 10:18:08 pm DNSAGENT.MSG 2028 9-19-96 10:13:52 pm DNSCONV.MSG 474 9-19-96 10:11:08 pm HOSTG.MSG 474 9-19-96 9:56:20 pm HOSTGADM.HLP 1170 1-8-95 12:04:08 am HOSTGADM.MSG 968 9-19-96 9:56:44 pm HOSTGAGT.MSG 225 9-19-96 9:57:02 pm INETD.MSG 763 9-19-96 10:21:06 pm IPADDR.HLP 2823 1-9-95 4:45:06 pm NAMED.MSG 4803 9-19-96 9:54:18 pm NETDB.MSG 2013 9-19-96 9:49:48 pm NFSUSER.MSG 4963 9-27-96 10:39:22 pm NFS_41X.MSG 2159 9-27-96 7:24:24 pm NFS_GR.MSG 2216 9-27-96 7:24:48 pm NIS.MSG 7937 9-27-96 10:42:40 pm NWNFS.HLP 142 1-31-95 7:01:04 pm NWNFS.MSG 2677 9-27-96 10:38:42 pm SRVAGT.MSG 1354 9-27-96 10:39:32 pm UNICON.HLP 15185 5-31-95 3:12:20 pm UNICON.MSG 10329 9-27-96 10:39:00 pm USER.HLP 13367 8-4-95 5:17:44 pm USRAGT.MSG 705 9-27-96 10:39:44 pm ..\DISK2\SYSTEM\NLS\7\ CONFADDR.MSG 2201 9-19-96 10:00:02 pm DISPATCH.MSG 1882 9-27-96 10:38:32 pm DNSADMIN.HLP 6167 5-31-95 11:25:56 pm DNSADMIN.MSG 5213 9-19-96 10:18:08 pm DNSAGENT.MSG 2028 9-19-96 10:13:52 pm DNSCONV.MSG 474 9-19-96 10:11:08 pm HOSTG.MSG 474 9-19-96 9:56:20 pm HOSTGADM.HLP 1170 1-8-95 12:04:08 am HOSTGADM.MSG 968 9-19-96 9:56:44 pm HOSTGAGT.MSG 225 9-19-96 9:57:02 pm INETD.MSG 763 9-19-96 10:21:06 pm IPADDR.HLP 2823 1-9-95 4:45:06 pm NAMED.MSG 4803 9-19-96 9:54:18 pm NETDB.MSG 2013 9-19-96 9:49:48 pm NFSUSER.MSG 4963 9-27-96 10:39:22 pm NFS_41X.MSG 2159 9-27-96 7:24:24 pm NFS_GR.MSG 2216 9-27-96 7:24:48 pm NIS.MSG 7937 9-27-96 10:42:40 pm NWNFS.HLP 142 1-31-95 7:01:04 pm NWNFS.MSG 2677 9-27-96 10:38:42 pm SRVAGT.MSG 1354 9-27-96 10:39:32 pm UNICON.HLP 15185 5-31-95 3:12:20 pm UNICON.MSG 10329 9-27-96 10:39:00 pm USER.HLP 13367 8-4-95 5:17:44 pm USRAGT.MSG 705 9-27-96 10:39:44 pm ..\DISK2\SYSTEM\NLS\8\ CONFADDR.MSG 2201 9-19-96 10:00:02 pm DISPATCH.MSG 1882 9-27-96 10:38:32 pm DNSADMIN.HLP 6167 5-31-95 11:25:56 pm DNSADMIN.MSG 5213 9-19-96 10:18:08 pm DNSAGENT.MSG 2028 9-19-96 10:13:52 pm DNSCONV.MSG 474 9-19-96 10:11:08 pm HOSTG.MSG 474 9-19-96 9:56:20 pm HOSTGADM.HLP 1170 1-8-95 12:04:08 am HOSTGADM.MSG 968 9-19-96 9:56:44 pm HOSTGAGT.MSG 225 9-19-96 9:57:02 pm INETD.MSG 763 9-19-96 10:21:06 pm IPADDR.HLP 2823 1-9-95 4:45:06 pm NAMED.MSG 4803 9-19-96 9:54:18 pm NETDB.MSG 2013 9-19-96 9:49:48 pm NFSUSER.MSG 4963 9-27-96 10:39:22 pm NFS_41X.MSG 2159 9-27-96 7:24:24 pm NFS_GR.MSG 2216 9-27-96 7:24:48 pm NIS.MSG 7937 9-27-96 10:42:40 pm NWNFS.HLP 142 1-31-95 7:01:04 pm NWNFS.MSG 2677 9-27-96 10:38:42 pm SRVAGT.MSG 1354 9-27-96 10:39:32 pm UNICON.HLP 15185 5-31-95 3:12:20 pm UNICON.MSG 10329 9-27-96 10:39:00 pm USER.HLP 13367 8-4-95 5:17:44 pm USRAGT.MSG 705 9-27-96 10:39:44 pm ..\DISK3\ ..\DISK3\ETC\ DOMAIN.IDX 25 6-14-94 8:57:56 pm DOS2UNIX.C 1440 8-1-96 5:50:42 pm HOSTS 28 6-24-92 10:22:56 pm INETD.CFG 245 7-11-94 5:31:46 pm NFSGROUP 35 6-16-94 6:04:12 pm NFSUSERS 33 6-16-94 6:04:08 pm NISMAKE 226 8-9-94 5:18:10 pm NWPARAMS 734 9-27-96 5:51:40 pm ROOT.DB 821 12-9-94 5:16:20 pm SERVICES 988 8-1-96 9:32:00 pm UNIX2DOS.C 1362 8-1-96 5:50:46 pm ..\DISK3\PUBLIC\ CHGRP.EXE 25508 9-27-96 10:27:50 pm CHMOD.EXE 25902 9-27-96 10:27:36 pm CHOWN.EXE 25530 9-27-96 10:27:26 pm DOS2UNIX.EXE 7242 6-23-92 1:25:28 am LS.EXE 30454 9-30-96 6:49:00 pm UNIX2DOS.EXE 7172 6-26-92 12:42:32 am VAXCRC.DAT 440 9-30-96 6:49:14 pm ..\DISK3\PUBLIC\NLS\ ..\DISK3\PUBLIC\NLS\ENGLISH\ CHGRP.MSG 724 9-27-96 10:36:08 pm CHMOD.MSG 714 9-27-96 10:36:04 pm CHOWN.MSG 724 9-27-96 10:36:06 pm LS.MSG 1402 9-27-96 10:36:04 pm ..\DISK3\SYSTEM\ FTPSERV.NLM 55642 9-27-96 10:47:26 pm GWADMIN.NLM 22286 9-27-96 10:46:40 pm GWAGENT.NLM 14138 9-27-96 10:46:52 pm GWREPAIR.NLM 27603 9-27-96 10:46:30 pm LOCKD.NLM 37493 9-27-96 10:43:30 pm NFSCA.NLM 31725 9-27-96 10:44:26 pm NFSDISP.NLM 2508 9-27-96 10:44:34 pm NFSGWSA.NLM 7194 9-27-96 10:46:18 pm NFSGWVS.NLM 226293 9-27-96 10:46:04 pm NFSSERV.NLM 40231 9-27-96 10:43:14 pm NISADMM.NLM 19809 9-27-96 10:42:56 pm NISBIND.NLM 21609 9-27-96 10:40:28 pm NISDMAG.NLM 32994 9-27-96 10:40:12 pm NISGO.NLM 16435 9-27-96 10:40:46 pm NISSERV.NLM 23947 9-27-96 10:41:02 pm NISSWDD.NLM 12264 9-27-96 10:42:42 pm SA_ADMN.NLM 11467 9-27-96 10:44:14 pm SA_LOCK.NLM 6294 9-27-96 10:43:54 pm SA_STAT.NLM 9476 9-27-96 10:44:04 pm STATD.NLM 10461 9-27-96 10:43:40 pm YPCAT.NLM 11174 9-27-96 10:41:52 pm YPMATCH.NLM 11039 9-27-96 10:42:08 pm YPPUSH.NLM 14771 9-27-96 10:41:36 pm YPSET.NLM 10405 9-27-96 10:42:24 pm YPXFR.NLM 21827 9-27-96 10:41:20 pm ..\DISK3\SYSTEM\NLS\ ..\DISK3\SYSTEM\NLS\19\ FTPADMIN.HLP 3334 1-9-95 4:38:30 pm FTPSERV.MSG 6222 9-27-96 10:47:22 pm GWADMIN.HLP 9252 8-9-95 12:56:12 am GWADMIN.MSG 4812 9-27-96 10:46:50 pm GWREPAIR.MSG 5842 9-27-96 10:46:26 pm LOCKD.MSG 6207 9-27-96 10:43:26 pm NFSCA.MSG 5010 9-27-96 10:44:24 pm NFSCAHLP.HLP 13190 1-20-95 5:27:20 pm NFSGWSA.MSG 631 9-27-96 10:46:14 pm NFSGWVS.MSG 26767 9-27-96 10:45:34 pm NFSSERV.MSG 4574 9-27-96 10:43:10 pm NIS.MSG 7937 9-27-96 10:42:40 pm NISADMM.HLP 3250 10-20-94 8:17:20 pm NISADMM.MSG 2980 9-27-96 10:42:54 pm SAADMN.MSG 1707 9-27-96 10:44:12 pm SALOCK.MSG 781 9-27-96 10:43:50 pm SASTAT.MSG 1544 9-27-96 10:44:02 pm STATD.MSG 2208 9-27-96 10:43:38 pm ..\DISK3\SYSTEM\NLS\4\ FTPADMIN.HLP 3334 1-9-95 4:38:30 pm FTPSERV.MSG 6222 9-27-96 10:47:22 pm GWADMIN.HLP 9252 8-9-95 12:56:12 am GWADMIN.MSG 4812 9-27-96 10:46:50 pm GWREPAIR.MSG 5842 9-27-96 10:46:26 pm LOCKD.MSG 6207 9-27-96 10:43:26 pm NFSCA.MSG 5010 9-27-96 10:44:24 pm NFSCAHLP.HLP 13190 1-20-95 5:27:20 pm NFSGWSA.MSG 631 9-27-96 10:46:14 pm NFSGWVS.MSG 26767 9-27-96 10:45:34 pm NFSSERV.MSG 4574 9-27-96 10:43:10 pm NISADMM.HLP 3250 10-20-94 8:17:20 pm NISADMM.MSG 2980 9-27-96 10:42:54 pm SAADMN.MSG 1707 9-27-96 10:44:12 pm SALOCK.MSG 781 9-27-96 10:43:50 pm SASTAT.MSG 1544 9-27-96 10:44:02 pm STATD.MSG 2208 9-27-96 10:43:38 pm ..\DISK3\SYSTEM\NLS\6\ FTPADMIN.HLP 3334 1-9-95 4:38:30 pm FTPSERV.MSG 6222 9-27-96 10:47:22 pm GWADMIN.HLP 9252 8-9-95 12:56:12 am GWADMIN.MSG 4812 9-27-96 10:46:50 pm GWREPAIR.MSG 5842 9-27-96 10:46:26 pm LOCKD.MSG 6207 9-27-96 10:43:26 pm NFSCA.MSG 5010 9-27-96 10:44:24 pm NFSCAHLP.HLP 13190 1-20-95 5:27:20 pm NFSGWSA.MSG 631 9-27-96 10:46:14 pm NFSGWVS.MSG 26767 9-27-96 10:45:34 pm NFSSERV.MSG 4574 9-27-96 10:43:10 pm NISADMM.HLP 3250 10-20-94 8:17:20 pm NISADMM.MSG 2980 9-27-96 10:42:54 pm SAADMN.MSG 1707 9-27-96 10:44:12 pm SALOCK.MSG 781 9-27-96 10:43:50 pm SASTAT.MSG 1544 9-27-96 10:44:02 pm STATD.MSG 2208 9-27-96 10:43:38 pm ..\DISK3\SYSTEM\NLS\7\ FTPADMIN.HLP 3334 1-9-95 4:38:30 pm FTPSERV.MSG 6222 9-27-96 10:47:22 pm GWADMIN.HLP 9252 8-9-95 12:56:12 am GWADMIN.MSG 4812 9-27-96 10:46:50 pm GWREPAIR.MSG 5842 9-27-96 10:46:26 pm LOCKD.MSG 6207 9-27-96 10:43:26 pm NFSCA.MSG 5010 9-27-96 10:44:24 pm NFSCAHLP.HLP 13190 1-20-95 5:27:20 pm NFSGWSA.MSG 631 9-27-96 10:46:14 pm NFSGWVS.MSG 26767 9-27-96 10:45:34 pm NFSSERV.MSG 4574 9-27-96 10:43:10 pm NISADMM.HLP 3250 10-20-94 8:17:20 pm NISADMM.MSG 2980 9-27-96 10:42:54 pm SAADMN.MSG 1707 9-27-96 10:44:12 pm SALOCK.MSG 781 9-27-96 10:43:50 pm SASTAT.MSG 1544 9-27-96 10:44:02 pm STATD.MSG 2208 9-27-96 10:43:38 pm ..\DISK3\SYSTEM\NLS\8\ FTPADMIN.HLP 3334 1-9-95 4:38:30 pm FTPSERV.MSG 6222 9-27-96 10:47:22 pm GWADMIN.HLP 9252 8-9-95 12:56:12 am GWADMIN.MSG 4812 9-27-96 10:46:50 pm GWREPAIR.MSG 5842 9-27-96 10:46:26 pm LOCKD.MSG 6207 9-27-96 10:43:26 pm NFSCA.MSG 5010 9-27-96 10:44:24 pm NFSCAHLP.HLP 13190 1-20-95 5:27:20 pm NFSGWSA.MSG 631 9-27-96 10:46:14 pm NFSGWVS.MSG 26767 9-27-96 10:45:34 pm NFSSERV.MSG 4574 9-27-96 10:43:10 pm NISADMM.HLP 3250 10-20-94 8:17:20 pm NISADMM.MSG 2980 9-27-96 10:42:54 pm SAADMN.MSG 1707 9-27-96 10:44:12 pm SALOCK.MSG 781 9-27-96 10:43:50 pm SASTAT.MSG 1544 9-27-96 10:44:02 pm STATD.MSG 2208 9-27-96 10:43:38 pm ..\DISK4\ ..\DISK4\ETC\ ENSCRIPT.PRO 497 6-25-92 8:23:50 pm FILTERS 147 11-24-93 9:58:42 pm FILTTYPE 163 12-16-93 11:35:52 pm POSTSCPT.PRO 998 6-25-92 8:24:04 pm RESTRICT.FTP 944 12-22-94 1:43:30 am XFONTEUR 90 2-4-95 12:38:58 am ..\DISK4\SYSTEM\ DLLINFO.NLM 3200 9-27-96 10:49:46 pm FTPADMIN.NLM 16019 9-28-96 10:41:40 pm FTPAGT.NLM 7843 9-28-96 10:41:50 pm IOTADJST.NLM 4294 9-27-96 10:50:04 pm IOXCSTUB.NLM 4771 9-19-96 10:10:54 pm LPRLOAD.NLM 2277 9-27-96 10:48:52 pm LPR_GWY.NLM 19373 9-27-96 10:48:44 pm MSTADJST.NLM 3507 9-27-96 10:50:12 pm MSXCSTUB.NLM 3558 9-19-96 10:10:28 pm NWCCSS.NLM 3676 9-19-96 10:20:00 pm NWPCNFSD.NLM 24279 9-27-96 10:49:14 pm PLPD.NLM 35228 9-27-96 10:48:10 pm PRADM.NLM 36498 9-27-96 10:48:22 pm PRADM_SA.NLM 8276 9-27-96 10:48:32 pm PRLIB.NLM 22034 9-27-96 10:47:56 pm RARPSERV.NLM 8176 9-19-96 10:21:40 pm TADJST.NLM 2299 9-27-96 10:49:54 pm TELNETD.NLM 10937 9-19-96 10:19:48 pm TFTPSERV.NLM 5824 9-19-96 10:20:40 pm TIMCHK.NLM 2243 9-27-96 10:49:34 pm TUI.NLM 24212 10-19-94 7:13:56 pm UNICRYPT.NLM 2484 9-27-96 10:37:56 pm UNIDLL.NLM 4446 9-27-96 10:49:40 pm UNIXLIB.NLM 32780 9-27-96 10:49:24 pm V_NFS.NLM 4936 9-27-96 10:49:00 pm XCONSOLE.NLM 4078 9-19-96 10:20:20 pm XCONSSRV.NLM 67576 9-19-96 10:10:02 pm ..\DISK4\SYSTEM\NLS\ ..\DISK4\SYSTEM\NLS\19\ FTPADMIN.MSG 2420 9-28-96 10:41:38 pm FTPAGT.MSG 393 9-28-96 10:41:48 pm IOTADJST.MSG 655 9-27-96 10:50:02 pm IOXCSTUB.MSG 747 9-19-96 10:10:54 pm LPRLOAD.MSG 323 9-27-96 10:48:50 pm LPR_GWY.MSG 3831 9-27-96 10:48:40 pm MSTADJST.MSG 533 9-27-96 10:50:10 pm MSXCSTUB.MSG 527 9-19-96 10:10:28 pm NWPCNFSD.MSG 3848 9-27-96 10:49:10 pm PLPD.MSG 6916 9-27-96 10:48:06 pm PRADM.HLP 6728 3-2-95 11:45:48 pm PRADM.MSG 3676 9-27-96 10:48:18 pm PRLIB.MSG 1586 9-27-96 10:47:52 pm TADJST.MSG 197 9-27-96 10:49:52 pm TELNETD.MSG 1822 9-19-96 10:19:46 pm TFTPSERV.MSG 992 9-19-96 10:20:40 pm TIMCHK.MSG 318 9-27-96 10:49:32 pm TUI.MSG 1356 11-16-93 4:57:40 am UNIXLIB.MSG 2333 9-27-96 10:49:22 pm V_NFS.MSG 986 9-27-96 10:48:58 pm XCONSOLE.MSG 799 9-19-96 10:20:20 pm XCONSSRV.MSG 4454 9-19-96 10:09:58 pm ..\DISK4\SYSTEM\NLS\4\ FTPADMIN.MSG 2420 9-28-96 10:41:38 pm FTPAGT.MSG 393 9-28-96 10:41:48 pm IOTADJST.MSG 655 9-27-96 10:50:02 pm IOXCSTUB.MSG 747 9-19-96 10:10:54 pm LPRLOAD.MSG 323 9-27-96 10:48:50 pm LPR_GWY.MSG 3831 9-27-96 10:48:40 pm MSTADJST.MSG 533 9-27-96 10:50:10 pm MSXCSTUB.MSG 527 9-19-96 10:10:28 pm NWPCNFSD.MSG 3848 9-27-96 10:49:10 pm PLPD.MSG 6916 9-27-96 10:48:06 pm PRADM.HLP 6728 3-2-95 11:45:48 pm PRADM.MSG 3676 9-27-96 10:48:18 pm PRLIB.MSG 1586 9-27-96 10:47:52 pm TADJST.MSG 197 9-27-96 10:49:52 pm TELNETD.MSG 1822 9-19-96 10:19:46 pm TFTPSERV.MSG 992 9-19-96 10:20:40 pm TIMCHK.MSG 318 9-27-96 10:49:32 pm TUI.MSG 1356 11-16-93 4:57:40 am UNIXLIB.MSG 2333 9-27-96 10:49:22 pm V_NFS.MSG 986 9-27-96 10:48:58 pm XCONSOLE.MSG 799 9-19-96 10:20:20 pm XCONSSRV.MSG 4454 9-19-96 10:09:58 pm ..\DISK4\SYSTEM\NLS\6\ FTPADMIN.MSG 2420 9-28-96 10:41:38 pm FTPAGT.MSG 393 9-28-96 10:41:48 pm IOTADJST.MSG 655 9-27-96 10:50:02 pm IOXCSTUB.MSG 747 9-19-96 10:10:54 pm LPRLOAD.MSG 323 9-27-96 10:48:50 pm LPR_GWY.MSG 3831 9-27-96 10:48:40 pm MSTADJST.MSG 533 9-27-96 10:50:10 pm MSXCSTUB.MSG 527 9-19-96 10:10:28 pm NWPCNFSD.MSG 3848 9-27-96 10:49:10 pm PLPD.MSG 6916 9-27-96 10:48:06 pm PRADM.HLP 6728 3-2-95 11:45:48 pm PRADM.MSG 3676 9-27-96 10:48:18 pm PRLIB.MSG 1586 9-27-96 10:47:52 pm TADJST.MSG 197 9-27-96 10:49:52 pm TELNETD.MSG 1822 9-19-96 10:19:46 pm TFTPSERV.MSG 992 9-19-96 10:20:40 pm TIMCHK.MSG 318 9-27-96 10:49:32 pm TUI.MSG 1356 11-16-93 4:57:40 am UNIXLIB.MSG 2333 9-27-96 10:49:22 pm V_NFS.MSG 986 9-27-96 10:48:58 pm XCONSOLE.MSG 799 9-19-96 10:20:20 pm XCONSSRV.MSG 4454 9-19-96 10:09:58 pm ..\DISK4\SYSTEM\NLS\7\ FTPADMIN.MSG 2420 9-28-96 10:41:38 pm FTPAGT.MSG 393 9-28-96 10:41:48 pm IOTADJST.MSG 655 9-27-96 10:50:02 pm IOXCSTUB.MSG 747 9-19-96 10:10:54 pm LPRLOAD.MSG 323 9-27-96 10:48:50 pm LPR_GWY.MSG 3831 9-27-96 10:48:40 pm MSTADJST.MSG 533 9-27-96 10:50:10 pm MSXCSTUB.MSG 527 9-19-96 10:10:28 pm NWPCNFSD.MSG 3848 9-27-96 10:49:10 pm PLPD.MSG 6916 9-27-96 10:48:06 pm PRADM.HLP 6728 3-2-95 11:45:48 pm PRADM.MSG 3676 9-27-96 10:48:18 pm PRLIB.MSG 1586 9-27-96 10:47:52 pm TADJST.MSG 197 9-27-96 10:49:52 pm TELNETD.MSG 1822 9-19-96 10:19:46 pm TFTPSERV.MSG 992 9-19-96 10:20:40 pm TIMCHK.MSG 318 9-27-96 10:49:32 pm TUI.MSG 1356 11-16-93 4:57:40 am UNIXLIB.MSG 2333 9-27-96 10:49:22 pm V_NFS.MSG 986 9-27-96 10:48:58 pm XCONSOLE.MSG 799 9-19-96 10:20:20 pm XCONSSRV.MSG 4454 9-19-96 10:09:58 pm ..\DISK4\SYSTEM\NLS\8\ FTPADMIN.MSG 2420 9-28-96 10:41:38 pm FTPAGT.MSG 393 9-28-96 10:41:48 pm IOTADJST.MSG 655 9-27-96 10:50:02 pm IOXCSTUB.MSG 747 9-19-96 10:10:54 pm LPRLOAD.MSG 323 9-27-96 10:48:50 pm LPR_GWY.MSG 3831 9-27-96 10:48:40 pm MSTADJST.MSG 533 9-27-96 10:50:10 pm MSXCSTUB.MSG 527 9-19-96 10:10:28 pm NWPCNFSD.MSG 3848 9-27-96 10:49:10 pm PLPD.MSG 6916 9-27-96 10:48:06 pm PRADM.HLP 6728 3-2-95 11:45:48 pm PRADM.MSG 3676 9-27-96 10:48:18 pm PRLIB.MSG 1586 9-27-96 10:47:52 pm TADJST.MSG 197 9-27-96 10:49:52 pm TELNETD.MSG 1822 9-19-96 10:19:46 pm TFTPSERV.MSG 992 9-19-96 10:20:40 pm TIMCHK.MSG 318 9-27-96 10:49:32 pm TUI.MSG 1356 11-16-93 4:57:40 am UNIXLIB.MSG 2333 9-27-96 10:49:22 pm V_NFS.MSG 986 9-27-96 10:48:58 pm XCONSOLE.MSG 799 9-19-96 10:20:20 pm XCONSSRV.MSG 4454 9-19-96 10:09:58 pm Installation Instructions: Some steps must be done from a workstation and others at the server console. You can do all the steps from a workstation if you use RCONSOLE to access the server console. You need to log in as the server's administrator and have supervisory rights to the SYS volume. 1. Backup your current SYS:SYSTEM and SYS:ETC subdirectories as a precaution. 2. From a workstation logged in to the NetWare 4.1 server, create the following directory at the root of the SYS volume: MD NFS199 3. Copy NFS199.EXE into the new directory. Enter the following: COPY NFS199.EXE NFS199 4. Change to the patch directory and extract the files. Enter the following: CD NFS199 NFS199 A DISK1 subdirectory will be created, and the files will be extracted to that directory. 5. From the server console, run UNISTOP.NCF as a general precaution. Enter the following: UNISTOP 6. From the server console, load the installation program. Enter the following: LOAD INSTALL 7. Select "Product options." 8. Select the "View/Configure/Remove Installed Product" option from the "Other Installation Actions" menu. The "Currently Installed Products" menu appears and should include the following item: NFS 2.1 NFS 2.1 If this entry is not present, you have not installed NFS 2.1. This is not a problem since the patch can be installed before the product itself. 9. If you have installed the NFS197.EXE or the NFS198.ZIP patch, remove it before installing the NFS199 patch. Select the NFS197.EXE or the NFS198.ZIP patch and press the key. 10. Press the key to install a new product. 11. Press the key to install the NFS199 patch. The "Specify Directory Path" dialogue box appears. 11. Enter the path to the directory where the NFS199 files were extracted. Enter the following: SYS:\NFS199\DISK1 After the installation program installs the files, the "Currently Installed Products" menu should list the following: NFS 2.1 NFS 2.1 NFSPAT 2.1b Upadate for NetWare NFS Services 2.1 12. Exit the INSTALL program or press + to return to the system console prompt. 13. From the server console, run UNISTART.NCF to restart NFS Services 2.1 (and other products if installed). Enter the following: UNISTART ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------