PC-NFS(R) VERSION 5.1a RELEASE NOTES (C)1994 by Sun Microsystems, Inc. All rights reserved. No part of this work may be reproduced in any form or by any means - graphic, electronic or mechanical, including photocopying, recording, taping, or storage in an information retrieval system - without prior written permission of the copyright owner. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the United States Government is subject to the restrictions set forth in DFARS 252.277-7013(c)(1)(ii) and FAR 52.277-19. The product described in these Release Notes may be protected by one or more U.S. patents, foreign patents, and/or pending applications. PC-NFS and NFS are registered trademarks of Sun Microsystems, Inc. in the United States and other countries. All other products and services mentioned in these Release Notes are identified by the trademarks as designated by the companies that market those products or services. Inquiries concerning such trademarks should be made directly to those companies. _________________________________________________________________ Please read these Release Notes before installing PC-NFS Version 5.1a software. **CONTENTS** --NEW FEATURES IN PC-NFS 5.1 --NEW FEATURES IN PC-NFS 5.1a --THINGS TO KNOW ABOUT 1. INSTALLATION 2. DEVICE DRIVERS 3. SLIP 4. DOMAIN NAME SERVICE 5. PRINTING 6. FILE MOUNTING 7. TELNET 8. NEW NETBIOS BROADCAST FILE OPTION 9. WINDOWS FOR WORKGROUPS 10. RTM AND RNM WITH TOOLKIT APPLICATIONS 11. GENERAL NOTES ================================================================= NEW FEATURES IN PC-NFS 5.1 o Improved TCP Performance o New Fully Integrated Installation Program o New and Easier Configuration Program o Easy-to-Use Mount Program under DOS o New Version of Telnet for Windows o LPR Printing for DOS and Windows o Print Spooling on Any Drive o Support for Int14 APIs o Support for Dynamic Host Configuration Protocol and BOOTP o Support for Domain Name Service o SLIP Support for the Annex(R) Terminal Server o Compiled Server Daemons for All Solaris and SunOS Platforms o Windows-based On-Line Documentation Available on CD-ROM (Must be ordered separately) o Utility for dumping the PLUM database file to an ASCII file (convert) NEW FEATURES IN PC-NFS 5.1a o NET.CFG automatically modified to enable PC-NFS to use your ODI driver o Improved WinSock performance o Improved network performance when PCNFS is run over ODI o Enhancement to PLUM to allow license deletions o Incorporation of a few bug fixes not included in 5.1. ================================================================= THINGS TO KNOW ABOUT 1. INSTALLATION --------------- MEMORY MANAGER LOAD-HIGH LINES OVERWRITTEN If you are using a memory manager with PC-NFS software, e.g., MEMMAKER (TM), QEMM (TM), or 386MAX (TM) any lines in AUTOEXEC.BAT or CONFIG.SYS that load PC-NFS device drivers or TSRs into high memory will be overwritten when you upgrade your PC-NFS software. After upgrading, manually edit the lines in AUTOEXEC.BAT and CONFIG.SYS so that these programs will be loaded into high memory, or re-run the memory manager's setup program. The original files are saved as AUTOEXEC.mmm and CONFIG.nnn, where mmm and nnn are three-digit numbers. INCORRECT CHANGE MADE TO CONFIG.SYS Under unusual conditions, the installation program may incorrectly modify the line in your CONFIG.SYS file that loads the SOCKDRV.SYS device driver. Instead of updating the path and driver name, the installation program appends the path and driver name. In such instances, PC-NFS will fail to load when you reboot, and it will report that PC-NFS was not installed correctly. If this occurs on your system, edit the CONFIG.SYS file and correct the line that loads SOCKDRV.SYS device driver. If you see a line similar to this one, DEVICE=C:\NFS\SOCKDRV.SYS =C:\NFS51\SOCKDRV.SYS edit it so that it looks like this: DEVICE=C:\NFS51\SOCKDRV.SYS OLD .DLL FILES AFTER AN UPGRADE PC-NFS Windows applications may not work if they find .DLL files from a previous version of PC-NFS. If you get an error message indicating that an inconsistency has been detected between .DLL files that support PC-NFS networking, remove the old .DLL files. Reinstalling the PC-NFS software will not solve this problem. Messages that indicate that a "dynalink" error has occurred also mean that old .DLL files are present and accessible to PC-NFS. The PC-NFS installation program detects duplicate versions of .DLL files and displays the file names. You can note them and delete them before running the PC-NFS Windows applications. INSTALLATION PROGRAM CAN UNDER ESTIMATE REQUIRED MEMORY In certain configurations, the installation program may present an error message indicating that there is not enough memory to run the installation program and that it needs at least 370K. The installation program actually needs 380K. Unload any unnecessary TSR's and/or device drivers until your system has 380K of available memory. After you complete the installation, you may reload the TSR's and device drivers that you removed. If your system has between 370K and 380K of available memory, the installation program will not warn you of the memory shortage. Before installing PC-NFS you should confirm that you have at least 380K, otherwise the PC may produce unexpected results during installation. 2. DEVICE DRIVERS ----------------- USING AN ODI DRIVER The nfsconf program now determines if you have ODI by checking whether the Link Support Layer (LSL) is loaded and asks if you want to use ODI for PC-NFS. If NET.CFG needs to be modified to specify the frame type required for PC-NFS, nfsconf does it for you. In addition, nfsconf adds a line for specifying buffer size to NET.CFG to improve the performance of applications like FTP, if the buffer size was not previously set. You can remove the entry or reduce the size if you have memory restrictions. As a result of changes in the ODI shim, NFSODI.SYS, the protocol lines for IPX, IP, and ARP are no longer needed in NET.CFG. Also, NFSODI.SYS can be loaded without using the /B switch, in which case it uses the first logical board with an acceptable frame type (for example, Ethernet_II) for PC-NFS. Chapter 4 of the PC-NFS Installation and Configuration Guide does not reflect the above changes in ODI configuration. The chapter describes how to set up NET.CFG, AUTOEXEC.BAT, and CONFIG.SYS by hand to enable PC-NFS to use ODI, which was required in PC-NFS 5.1. Much of the other information in Chapter 4 is still relevant, though. If you do not already have LSL running, when you select ODI, nfsconf does not add the Link Support lines to NET.CFG, though it tells you the file is OK. You should add the Link Support lines to NET.CFG, because ODI performance is likely to be poor without them. The ODI shim can now handle back-to-back received packets properly. In order to take advantage of this functionality, ECB buffers must be available from LSL. To set up LSL so that these buffers will be reserved, add the following Link Support lines to your NET.CFG: Link Support Buffers 4 1580 The '4' specifies the number of buffers available for back-to-back packet reception. The '1580' specifies the size of the buffers. The number of buffers may be tuned upward or downward to provide the most appropriate memory-performance tradeoff. For most applications, four should be nearly optimal. The size of the buffers should not be changed from 1580. If the size of the buffers is smaller than 1580, NFSODI.SYS will not use them. If the size of the buffers is larger, PC-NFS will not take advantage of the excess. It is no longer necessary to specify the 'Protocol IP 800 ...' lines in NET.CFG. The ODI shim will attempt to bind protocol id values automatically if none have been specified. If protocol ids are specified in the NET.CFG file, they will override the automatic values. When NFSODI.SYS is run with the /Bn switch, it will attempt to bind to logical board n explicitly, as in previous releases. If the /Bn switch is not included on the command line though, the shim will scan all the logical boards defined and will bind to the first one that provides a frame type usable by PC-NFS. CONFIGURING PC-NFS AND NETWARE TO USE AN ODI DRIVER The instructions in "How to Configure PC-NFS and NetWare to Use an ODI Driver" on page 136 of the "PC-NFS Installation and Configuration Guide" indicate that IPXODI driver and NETX redirector must be loaded after the NET INIT command is executed in the AUTOEXEC.BAT file. This is not absolutely necessary, newer versions of NETX permit users to load them before NET INIT. REMOVING AN ODI CONFIGURATION If you change your adapter configuration from ODI to NDIS or LLDK, you must remove any ODI components you have loaded, such as LSL, IPXODI, BNETX, NETX, from your AUTOEXEC.BAT and reboot. This must be done after you change the configuration with the nfsconf program. REPLACING UNSUPPORTED DEVICE DRIVERS When you switch to an unsupported device driver, the PC-NFS configuration program (nfsconf) does not remove it from the CONFIG.SYS file. You must manually edit CONFIG.SYS so the driver is no longer started. LLDK DRIVER FOR 3C501 The note on page 57 of the "PC-NFS Installation and Configuration Guide" should say that PC-NFS no longer supplies an LLKD driver for the 3C501 adapter. An NDIS driver is provided, however, and can be used if the PC has a 3C501 adapter card. NDIS DRIVER FILES When you select "Other" to configure a network adapter and then install an NDIS driver from the driver manufacturer's diskette, nfsconf may not install files marked "ancillary" in the .NIF file. These files may be needed to operate the driver. A message is displayed if the files are not copied. Refer to the manufacturer's documentation for installation of these files. LLDK DRIVER FOR 3C505 ETHERLINK PLUS ADAPTER If you are installing PC-NFS for the first time on the machine with the 3C505 Etherlink Plus adapter, then you must move the LDR.CFG file after you finish the installation, before you reboot the system. The LDR.CFG file must be moved from the PC-NFS directory to the root directory (C:\). The PC-NFS directory is C:\NFS unless you have specified that the PC-NFS software be installed elsewhere. If you are upgrading PC-NFS and have previously configured with the LLDK driver for the 3C505 Etherlink Plus adapter, you should continue to use LDR.CFG file that is already in the C:\ directory. If you have installed the PC-NFS software in a directory other than C:\NFS directory, you must edit the LDR.CFG file to change the name of the PC-NFS directory. The LDR.CFG file contains the following lines. You can create this file in the C:\ directory if necessary. DRIVER=C:\NFS\PROA.SYS 32 1 50 DRIVER=C:\NFS\VECIE3.SYS DRIVER=C:\NFS\3C505DX.SYS If the PC-NFS directory is installed in a directory other than C:\NFS, that directory must be reflected in the above LDR.CFG entries. SMC8000 DRIVER WITH WINDOWS FOR WORKGROUPS The SMC8000 driver is designed to replace the SMCMAC driver for all SMC network adapters. When you choose to use SMC with PC-NFS, the new SMC8000 driver will be put in the nfs directory and CONFIG.SYS will be modified to use the SMC8000 driver. However, Windows for Workgroups still uses the older SMCMAC driver. Whenever Windows for Workgroups Network Setup is run, it will change entries in SYSTEM.INI and PROTOCOL.INI to revert to the SMCMAC driver. If you are running PC-NFS as an additional network with Windows for Workgroups, you can continue to use the SMCMAC driver. Or, if you wish to use the new driver, you can copy it to your Windows directory, and change any references from SMCMAC to SMC8000 in SYSTEM.INI and PROTOCOL.INI. This would need to be done each time you run Windows for Workgroups Network Setup. When you are completing the configuration of the SMC8000 driver, check your PROTOCOL.INI file to see if it has a board-setting entry for iobase. If it does, then you must change that setting to 0x format. For example: "iobase=300" would be changed to "iobase0x300". If you are running PC-NFS as the only network (the primary network), you will be configured to use the new SMC8000 driver. Refer to Chapter 7 of the PC-NFS Installation and Configuration Guide for complete instructions on editing your system files to configure PC-NFS with Windows for Workgroups. For older SMC network adapters, you may need to continue using the SMCMAC driver. If you have problems after configuring to use the SMC8000, you can revert to the SMCMAC driver by going through all of the changed files and substituting SMCMAC for SMC8000. 3. SLIP ------- DHCP AND SLIP SLIP connections cannot get their configuration from a Dynamic Host Configuration Protocol (DHCP) server. However, during configuration of a serial direct connection, you are asked if you are using DHCP. You must answer N. CHECK THE SUBNET MASK AFTER INSTALLING SLIP You should always check the subnet mask using the /etc/ifconfig command after installing the SLIP daemon when you plan to use SLIP with a direct connection. 4. DOMAIN NAME SERVICE ---------------------- TURNING OFF DOMAIN NAME SERVICE (DNS) If you use nfsconf to switch from DNS to FILES or NIS for name services, you must manually rename the RESOLVE.CNF file, or delete it, in order to turn off DNS. BROWSING IN WINDOWS NOT SUPPORTED The Get Servers (Browsing feature in Windows File Manager, Control Panel, and FTP) is not available when you are using DNS. 5. PRINTING ----------- MISLEADING INSTALLATION MESSAGE If you do not include the PRT * statement in the AUTOEXEC.BAT file, you will get the error message: PC-NFS was not installed correctly No print redirector You can ignore this message if you do not intend to use PC-NFS print services. You do not need the PRT * statement if you are not using PC-NFS print services. ASTERISK MANDATORY WITH PRT When you include the PRT statement in the AUTOEXEC.BAT file, it must contain an asterisk, as follows: PRT * If the asterisk is missing, the PC will hang when you attempt to print. UNMOUNT A PRINTER WITH PRINT JOBS PENDING If you mount a printer with the /end=m option, do not unmount the printer until you have entered a net print to print all spooled print jobs. If you attempt to unmount while there are spooled jobs, you get an error message indicating that the printer cannot be unmounted because of the pending print jobs. If you enter net print at that point, or wait for the timeout, and then unmount, you are told that the printer has already been unmounted. If you try to remount it, you are told that the device is already in use. STOPPING PRINT JOBS WITH LPR You can use the LPR client to stop a print job submitted with LPR if you own the print job and you send the stop request from the same machine used to enter the print job. You cannot use the LPR client to stop a print job sent to an NFS-mounted printer. If you attempt to stop such a print job with LPR, the attempt will fail, but you will not receive a message indicating it failed. MOUNTING PRINTERS When mounting printers with the NET USE command, you cannot use the MUSTSHARE, READONLY, NOSHARE, or OS2 parameter options. The on-line description of the NET command syntax is misleading in this regard. 6. FILE MOUNTING ---------------- DISMOUNTING THE CURRENT DRIVE When you dismount a drive you are currently using (i.e., you are in a directory on that drive) and then try to remount it, you get the error message "Invalid drive specification." However, the drive is actually mounted again. You can ignore the error message in this case. MOUNTING NETWORK DRIVES WITH THE ALLIED TELESIS ADAPTER In order to successfully access mounted network file systems when your PC has an Allied Telesis 1500 adapter, you must use a write size of 2048. 7. TELNET --------- TELNET FOR DOS HOT KEY IN MULTIPLE SESSIONS When you have two or more Telnet for DOS connections and you use the Hot key to move between the sessions, the PC may hang after several moves between sessions. TELNET GUIDE FOR DOS ERROR The PC-NFS Telnet Guide for DOS says that the @ character is used from the command line to start a Telnet command file. This is wrong and will produce an error. The correct syntax is -c. For example, the following command will work correctly: telnet -c demofile TELNET FOR DOS LEAVES CODE IN MEMORY If the Telnet for DOS program fails to load when you start it, it leaves code in memory. It fails to unload RNMNIS. Under these circumstances, you must unload RNMNIS manually with the following command: rnmnis -u 8. NEW NETBIOS BROADCAST FILE OPTION ------------------------------------ When loading NetBIOS, you can now use the "-c bcast-file" option with NB.EXE to define the name and path of a file that contains one or more NetBIOS names and their Internet addresses. The bcast-file uses the format of the PC-NFS hosts file. It stores the names and addresses of NetBIOS nodes that reside outside of the broadcast range of local nodes. All broadcast packets are sent to the nodes specified in bcast-file and the hosts file. 9. WINDOWS FOR WORKGROUPS ------------------------- RUNNING PC-NFS AND LANMANAGER You can configure PC-NFS as an additional network within Windows or Workgroups (WFW), but WFW does not have an option to configure LanManager as an additional network. Only one additional network can be selected at a time within WFW. With PC-NFS as the additional network, you can connect and disconnect remote drives and printers from within Windows using the PC-NFS network driver. However, drives and printers you connect from DOS using the LanManager network driver are still available in Windows, and appear to be local drives. They cannot be disconnected, nor can you connect additional drives and printers using the LanManager network driver from within WFW. If you want to use both PC-NFS and LanManager with Windows for Workgroups: 1. Set up PC-NFS and LanManager as you normally would. 2. Connect drives and printers using LanManager that you want available from within WFW. 3. Go into WFW and under Network Setup configure PC-NFS as the additional network. 4. Go to a DOS shell and mount drives and printers using LanManager, if desired. When you first install PC-NFS with WFW, you must run the WFW Network Setup before rebooting. RUNNING PC-NFS AND NETWARE With Microsoft Windows Network as the primary network, you have concurrent access to remote drives and printers over multiple network drivers (for example, PC-NFS, NetWare, LanManager), but you can only make and break remote connections to drives or printers from Windows File Manager on the stack for the network you chose as the network additional to Microsoft Windows Network. If you set up PC-NFS and NetWare to coexist over ODI, you can select PC-NFS or NetWare as the additional network under Windows for Workgroups 3.11. If you select PC-NFS, Windows File Manager maintains the drives and printers already connected by PC-NFS and permits you to connect and disconnect remote drives and printers using the PC-NFS network driver. Even though you select PC-NFS as the additional network under Windows, drives and printers connected from DOS using NetWare are still available in Windows. The following instructions describe how to switch between PC-NFS and NetWare as the additional network in Windows. NOTE: On page 18 of the PC-NFS Installation and Configuration Guide, a note says you may be able to set up both PC-NFS and NetWare as networks, one primary and the other secondary (additional). This statement is misleading. You can configure PC-NFS or NetWare as the primary network instead of Microsoft Windows Network. Or, you can configure either PC-NFS or NetWare as a network in addition to Microsoft Windows network. But, you cannot configure PC-NFS or NetWare as the primary network and the other as the additional network. To set up WFW 3.11 to run with Netware or PC-NFS as the addtional network: 1. If PC-NFS is already configured as the additional network using an NDIS driver, start WFW and remove the additional network. >open : Network group in Program Manager >open : Network Setup >select : Networks >select : "No additional Network" >select : OK From Network Setup dialog box >select : OK >select : Continue 2. Set up PC-NFS and Netware to Co-exist using ODI. Refer to the information in Section 2 of this Release Note, under "Using an ODI Driver," first, and then Chapter 4 in the PC-NFS Installation and Configuration Guide. Make sure PC-NFS and NetWare are working and their drives are accessible. Note: Check CONFIG.SYS file for the LASTDRIVE= statement, which WFW may have changed. If you are using NETX.COM, your LASTDRIVE should be lower than Z. This is to allow NetWare to map all letters after the lastdrive. If you are using VLM, LASTDRIVE should be Z. Check also that PCNFS.SYS and SOCKDRV.SYS are being loaded; WFW may have commented out the lines for these drivers. 3. Start Windows for Workgroups. 4. Bring up the Networks dialog box. >open : Network group in Program Manager >open : Network Setup >select : Networks 5. Install either PC-NFS or NetWare as the additional network. From "Install Windows Support for an additional network:" >select : Other >Choose either: - SunSelect PC-NFS 5.1 (The first time use "Unlisted or Updated Network") - Novell NetWare [Workstation Shell 3.X or 4.0] Note: The network you choose here will be the only network supported while you are in WFW. The unsupported network's drives and printers will have to be mounted/unmounted from a DOS window. >select : OK 4. Configure ODI as the driver to use for your network adapter. >select : Drivers >select : Add Adapter >choose your Network Adapter Card if not already there >select : OK >select : Setup From "Driver Type" >select : ODI Driver >select : OK >select : Add Protocol >choose : PC-NFS/ODI >select : OK >select : Close >select : OK 5. To install/upgrade files, >select : Yes to All Required files will be in: c:\nfs - for NFS files WFW installation disks - for WFW files Netware Directory - for NetWare files NOTE: The NetWare files you need are contained in WINUP9.ZIP. To Modifying configuration files, >select : YES 6. >select : Continue NOTE: Check CONFIG.SYS file for the LASTDRIVE= statement, which WFW may have changed. If you are using NETX.COM, your LASTDRIVE should be lower than Z (but not lower than S if a SolarNet client). This is to allow NetWare to map all letters after the lastdrive. If you are using VLM, LASTDRIVE should be Z. After switching to NetWare as the additional network, check also that PCNFS.SYS and SOCKDRV.SYS are being loaded; WFW may have commented out the lines for these drivers. 7. Reboot the PC. NOTE: If you see conflicts between PC-NFS and NetWare drives check your WIN.INI file. CONFIGURING PC-NFS WITH WINDOWS FOR WORKGROUPS 3.1 The nfsconf program sets up your PROTOCOL.INI for the correct driver if your PROTOCOL.INI contains a MS$NETBEUI section. If you don't have a MS$NETBEUI section, edit your PROTOCOL.INI using the example PROTOCOL.INI files found in Chapter 7 of the PC-NFS Installation and Configuration Guide. 10. RTM AND RNM WITH TOOLKIT APPLICATIONS ----------------------------------------- USE LATEST RTM AND RNM MODULES WITH TOOLKIT APPLICATIONS PC-NFS 5.1a includes new versions of the resident modules (RTM and either RNMFILE or RNMNIS). If you install an application that was built with the PC-NFS Programmer's Toolkit after you install PC-NFS software, it is important to make sure that the resident modules supplied with PC-NFS 5.1a are not overwritten. You can check the version of the resident modules by entering: RTM -V RNMFILE -V or RNMNIS -V If the version is not 5.1a, restore the resident modules by reinstalling PC-NFS software from the PC-NFS distribution disks. 11. GENERAL NOTES ----------------- NETWORK INFORMATION QUERY When you run the Network Information Query application under Windows, the hourglass disappears before the query is complete. Because the PC will not respond to input, it appears that the system is hung. Wait until the query is complete before attempting to enter any input. If you attempt to use the mouse or keyboard while Network Information Query is still running, the input is held in a buffer and then executed when Network Information Query stops. Depending on the type of input, it could produce unpredictable results. NEW HAYES S REGISTER INT14 PC-NFS int14 support also includes a new Hayes S register. The register is s13. It is used to toggle between seven- and eight-bit data modes. When s13 is 0, transmitted data will be seven bits, and eight-bit data will have the most significant bit cleared. When s13 is 1, transmitted data will be sent unfiltered. This feature is not covered in the int14 documentation in the PC-NFS Reference Manual. USING RARP REQUIRES HOST FILE To use RARP, you must have a HOSTS file in the directory from which you run the PC-NFS software. A HOST file containing a single blank line is sufficient. NFSHUSH ENVIRONMENT VARIABLE NOT SUPPORTED The NFSHUSH environment variable in PC-NFS Version 5.0 is not supported in Version 5.1. NAME CHANGE The Sun Microsystems business unit that makes PC-NFS has changed its name from SunSelect to SunSoft. The change has not been made in all parts of the software and documentation, so you may still see some references to SunSelect.