{ "disks": { "1": { "dirs": [ { "path": "/", "files": [ { "name": "PCNFS SYS", "size": 60432, "date": "1993-07-20", "time": "8:01" }, { "name": "README TXT", "size": 20427, "date": "1992-02-19", "time": "4:00" }, { "name": "INSTALL EXE", "size": 155266, "date": "1992-02-19", "time": "4:00" }, { "name": "INSTALL TXT", "size": 20256, "date": "1992-02-19", "time": "4:00" }, { "name": "INSTALL NDX", "size": 1199, "date": "1992-02-19", "time": "4:00" }, { "name": "PC-NFS PCX", "size": 57407, "date": "1992-02-19", "time": "4:00" }, { "name": "BASICNFS ZOO", "size": 324817, "date": "1992-02-19", "time": "4:00" }, { "name": "DRIVERS ZOO", "size": 73085, "date": "1992-02-19", "time": "4:00" }, { "name": "DBFILES ZOO", "size": 1872, "date": "1992-02-19", "time": "4:00" }, { "name": "NDIS ZOO", "size": 26222, "date": "1992-02-19", "time": "4:00" }, { "name": "WINNFS ZOO", "size": 205509, "date": "1992-02-19", "time": "4:00" }, { "name": "WINWIN ZOO", "size": 31891, "date": "1992-02-19", "time": "4:00" }, { "name": "PCNFSD TAR", "size": 61015, "date": "1992-02-19", "time": "4:00" }, { "name": "DOPCNFSD SH", "size": 1818, "date": "1992-02-19", "time": "4:00" }, { "name": "RFCMSG TAR", "size": 30290, "date": "1992-02-19", "time": "4:00" }, { "name": "DORFCMSG SH", "size": 1779, "date": "1992-02-19", "time": "4:00" }, { "name": "SLIPD40 TAR", "size": 24541, "date": "1992-02-19", "time": "4:00" }, { "name": "ADDSLIP CSH", "size": 11716, "date": "1992-02-19", "time": "4:00" }, { "name": "MAKEFILE", "size": 732, "date": "1992-02-19", "time": "4:00" } ] } ] }, "2": { "dirs": [ { "path": "/", "files": [ { "name": "LOCKD4 TAR", "size": 91743, "date": "1992-02-19", "time": "4:00" }, { "name": "LOCKD3X TAR", "size": 67519, "date": "1992-02-19", "time": "4:00" }, { "name": "DOLOCKD SH", "size": 6072, "date": "1992-02-19", "time": "4:00" }, { "name": "FULL1NFS ZOO", "size": 308151, "date": "1992-02-19", "time": "4:00" }, { "name": "FULL2NFS ZOO", "size": 185461, "date": "1992-02-19", "time": "4:00" }, { "name": "FULL3NFS ZOO", "size": 306415, "date": "1992-02-19", "time": "4:00" }, { "name": "FULL4NFS ZOO", "size": 199043, "date": "1992-02-19", "time": "4:00" } ] } ] }, "3": { "dirs": [ { "path": "/", "files": [ { "name": "QUIKNDIS EXE", "size": 35680, "date": "1992-02-19", "time": "0:48" }, { "name": "README", "size": 17088, "date": "1992-02-19", "time": "0:10" }, { "name": "ELNK16", "dir": true, "date": "1993-12-28", "time": "16:08" }, { "name": "ELNKD", "dir": true, "date": "1993-12-28", "time": "16:09" }, { "name": "ELNKIID", "dir": true, "date": "1993-12-28", "time": "16:09" }, { "name": "ELNKMCD", "dir": true, "date": "1993-12-28", "time": "16:09" }, { "name": "ELNKPLD", "dir": true, "date": "1993-12-28", "time": "16:09" }, { "name": "NE1000D", "dir": true, "date": "1993-12-28", "time": "16:09" }, { "name": "NE2000D", "dir": true, "date": "1993-12-28", "time": "16:09" }, { "name": "MACWDD", "dir": true, "date": "1993-12-28", "time": "16:09" }, { "name": "MADGE", "dir": true, "date": "1993-12-28", "time": "16:09" }, { "name": "TOKWDD", "dir": true, "date": "1993-12-28", "time": "16:09" }, { "name": "XEETHER", "dir": true, "date": "1993-12-28", "time": "16:09" }, { "name": "XPETHER", "dir": true, "date": "1993-12-28", "time": "16:09" }, { "name": "XPETHER2", "dir": true, "date": "1993-12-28", "time": "16:09" }, { "name": "XPTOKEN", "dir": true, "date": "1993-12-28", "time": "16:09" }, { "name": "TLNKD", "dir": true, "date": "1993-12-28", "time": "16:09" } ] }, { "path": "/ELNK16", "files": [ { "name": "ELNK16 DOS", "size": 9790, "date": "1991-03-04", "time": "16:35" }, { "name": "ELNK16 NIF", "size": 132, "date": "1991-02-26", "time": "14:48" }, { "name": "ELNK16D ZIP", "size": 7401, "date": "1991-09-05", "time": "13:02" }, { "name": "LIBRARY TXT", "size": 139, "date": "1991-07-08", "time": "13:15" }, { "name": "NDISCRT BAT", "size": 410, "date": "1991-09-05", "time": "13:02" }, { "name": "PROTOCOL DIS", "size": 110, "date": "1991-02-27", "time": "14:12" }, { "name": "PROTOCOL INI", "size": 202, "date": "1992-01-09", "time": "23:00" } ] }, { "path": "/ELNKD", "files": [ { "name": "ELNK DOS", "size": 7218, "date": "1990-06-28", "time": "0:00" }, { "name": "ELNK NIF", "size": 118, "date": "1990-06-28", "time": "0:00" }, { "name": "PROTOCOL INI", "size": 2354, "date": "1992-01-09", "time": "23:22" }, { "name": "README TXT", "size": 3477, "date": "1990-06-28", "time": "0:00" } ] }, { "path": "/ELNKIID", "files": [ { "name": "ELNKII DOS", "size": 10150, "date": "1990-06-28", "time": "0:00" }, { "name": "ELNKII NIF", "size": 125, "date": "1990-06-28", "time": "0:00" }, { "name": "PROTOCOL INI", "size": 2184, "date": "1992-01-09", "time": "23:29" }, { "name": "README TXT", "size": 4144, "date": "1990-06-28", "time": "0:00" } ] }, { "path": "/ELNKMCD", "files": [ { "name": "ELNKMC DOS", "size": 8048, "date": "1990-06-28", "time": "0:00" }, { "name": "ELNKMC NIF", "size": 125, "date": "1990-06-28", "time": "0:00" }, { "name": "PROTOCOL INI", "size": 716, "date": "1992-01-09", "time": "23:31" }, { "name": "README TXT", "size": 2408, "date": "1990-06-28", "time": "0:00" } ] }, { "path": "/ELNKPLD", "files": [ { "name": "ELNKPL DOS", "size": 17048, "date": "1990-06-28", "time": "0:00" }, { "name": "ELNKPL NIF", "size": 127, "date": "1990-06-28", "time": "0:00" }, { "name": "PROTOCOL INI", "size": 1843, "date": "1992-01-09", "time": "23:35" }, { "name": "README TXT", "size": 3340, "date": "1990-06-28", "time": "0:00" } ] }, { "path": "/NE1000D", "files": [ { "name": "LIBRARY TXT", "size": 142, "date": "1991-09-16", "time": "14:36" }, { "name": "NDISCRT BAT", "size": 398, "date": "1991-09-05", "time": "12:37" }, { "name": "NE1000 DOS", "size": 17228, "date": "1991-08-29", "time": "15:50" }, { "name": "NE1000 NIF", "size": 140, "date": "1991-05-16", "time": "9:02" }, { "name": "PROTOCOL DIS", "size": 121, "date": "1990-08-02", "time": "9:31" }, { "name": "PROTOCOL INI", "size": 733, "date": "1992-01-09", "time": "22:56" }, { "name": "README TXT", "size": 1769, "date": "1990-08-03", "time": "0:00" } ] }, { "path": "/NE2000D", "files": [ { "name": "NE2000 DOS", "size": 16720, "date": "1990-11-28", "time": "16:22" }, { "name": "NE2000 NIF", "size": 159, "date": "1992-01-10", "time": "0:13" }, { "name": "PROTOCOL INI", "size": 732, "date": "1992-01-10", "time": "0:12" }, { "name": "README TXT", "size": 1769, "date": "1990-08-03", "time": "0:00" } ] }, { "path": "/MACWDD", "files": [ { "name": "MACWD DOS", "size": 13392, "date": "1990-06-28", "time": "0:00" }, { "name": "MACWD NIF", "size": 149, "date": "1990-06-28", "time": "0:00" }, { "name": "README TXT", "size": 2665, "date": "1990-06-28", "time": "0:00" }, { "name": "PROTOCOL INI", "size": 1582, "date": "1992-01-24", "time": "11:41" } ] }, { "path": "/MADGE", "files": [ { "name": "MADGE NIF", "size": 150, "date": "1992-02-17", "time": "16:44" }, { "name": "PROTOCOL INI", "size": 81, "date": "1992-02-17", "time": "16:44" }, { "name": "SMARTND DOS", "size": 80361, "date": "1991-10-03", "time": "15:05" } ] }, { "path": "/TOKWDD", "files": [ { "name": "PROTOCOL INI", "size": 2515, "date": "1992-01-10", "time": "0:28" }, { "name": "README TXT", "size": 3424, "date": "1990-06-28", "time": "0:00" }, { "name": "TOKWD DOS", "size": 16432, "date": "1990-06-28", "time": "0:00" }, { "name": "TOKWD NIF", "size": 145, "date": "1990-06-28", "time": "0:00" } ] }, { "path": "/XEETHER", "files": [ { "name": "EE_NDIS DOS", "size": 22742, "date": "1991-08-13", "time": "23:25" }, { "name": "PROTOCOL INI", "size": 520, "date": "1992-01-09", "time": "23:06" }, { "name": "XIRCDOS NIF", "size": 148, "date": "1991-08-26", "time": "12:00" } ] }, { "path": "/XPETHER", "files": [ { "name": "PE_NDIS DOS", "size": 18432, "date": "1991-04-17", "time": "8:41" }, { "name": "PROTOCOL INI", "size": 520, "date": "1992-01-09", "time": "23:05" }, { "name": "XIRCDOS NIF", "size": 127, "date": "1992-01-02", "time": "10:35" } ] }, { "path": "/XPETHER2", "files": [ { "name": "PE2_NDIS EXE", "size": 14174, "date": "1991-09-02", "time": "11:07" }, { "name": "PROTOCOL INI", "size": 520, "date": "1992-01-09", "time": "23:10" }, { "name": "XIRCDOS NIF", "size": 151, "date": "1991-08-21", "time": "12:00" } ] }, { "path": "/XPTOKEN", "files": [ { "name": "PROTOCOL INI", "size": 522, "date": "1992-01-09", "time": "23:07" }, { "name": "SMARTND DOS", "size": 82617, "date": "1991-05-08", "time": "15:29" }, { "name": "XIRCDOS NIF", "size": 127, "date": "1992-01-02", "time": "10:32" } ] }, { "path": "/TLNKD", "files": [ { "name": "PROTOCOL INI", "size": 2946, "date": "1992-01-10", "time": "0:46" }, { "name": "README TXT", "size": 4500, "date": "1990-06-28", "time": "0:00" }, { "name": "TLNK DOS", "size": 12138, "date": "1990-06-28", "time": "0:00" }, { "name": "TLNK NIF", "size": 116, "date": "1990-06-28", "time": "0:00" } ] } ] } }, "desc_file": "README.TXT", "desc_text": "\r\n PC-NFS(R) RELEASE NOTES \t\t\t \r\n \r\n\r\n(C)1992 by Sun Microsystems, Inc. - Printed in the United \r\nStates of America.\r\n\r\nAll rights reserved. No part of this work may be reproduced\r\nin any form or by any means - graphic, electronic or mechanical,\r\nincluding photocopying, recording, taping, or storage in an \r\ninformation retrieval system - without prior written permission\r\nof the copyright owner. \r\n\r\nRESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by\r\nthe government is subject to restrictions as set forth in \r\nsubparagraph (c)(1)(ii) of the Rights in Technical Data and\r\nComputer Software clause at DFARS 252.277-7013 (October 1988)\r\nand FAR 52.277-19 (June 1987).\r\n\r\nThe product described in these Release Notes may be protected \r\nby one or more U.S. patents, foreign patents, and/or pending\r\napplications.\r\n\r\nPC-NFS and NFS are registered trademarks of Sun Microsystems,\r\nInc. in the United States and other countries. All other \r\nproducts and services mentioned in these Release Notes are \r\nidentified by the trademarks as designated by the companies\r\nthat market those products or services. Inquiries concerning\r\nsuch trademarks should be made directly to those companies.\r\n\r\n\r\n\r\n**OVERVIEW**\r\n\r\nPlease read these Release Notes before installing PC-NFS 4.0\r\nsoftware. These notes describe:\r\n\r\n o Installation\r\n o Configuration\r\n o Locking Services and PCNFSD\r\n o General Notes\r\n o Microsoft(R) Windows(TM) Support\r\n o Printing\r\n o Applications Compatibility\r\n\r\n\r\n\r\n**INSTALLATION**\r\n\r\n\r\nBEFORE A \"BASIC\" UPGRADE REMOVE CERTAIN PC-NFS FILES\r\n\r\nThe \"basic\" upgrade installation procedure does not remove \r\nthe following files installed by earlier versions of PC-NFS \r\nsoftware. To avoid any conflicts with PC-NFS 4.0 software, \r\ndelete these files before upgrading PC-NFS software. \r\n\r\n(Consult the \"PC-NFS Installation Guide\" for a definition of \r\n\"basic\" installation.)\r\n\r\n ARP.EXE FTP.EXE NFSPING.EXE RCP.EXE\r\n CHMOD.EXE HANGUP.EXE NFSRUN.EXE RDATE.EXE\r\n CONNECT.EXE LPD.EXE NFSSTAT.EXE RPCINFO.EXE\r\n DOS2UNIX.EXE LPT.EXE NISCAT.EXE RSH.EXE\r\n EM.COM LS.EXE NISMATCH.EXE SHOWMNT.EXE\r\n EM.SES MV.EXE PCNFSCFG.EXE SNMP.EXE\r\n EMTELNET.EXE MYEADDR.EXE PCNFSLPD.EXE TELNET.EXE\r\n EM_MSG.TXT NETSTAT.EXE PING.EXE UNIX2DOS.EXE\r\n\r\nAfter you have deleted the files listed above, follow the basic \r\nupgrade installation procedure described in Chapter 4 of the \r\n\"PC-NFS Installation Guide.\"\r\n\r\n\r\nREMOVE /Y OPTION IN CONFIG.SYS WHEN UPGRADING PC-NFS SOFTWARE\r\n\r\nIf you are running MS-Windows, and you plan to upgrade from PC-NFS \r\nVersion 3.5, you must remove the /y option from the PCNFS.SYS\r\nline in the CONFIG.SYS file before upgrading. Refer to the \"PC-NFS \r\nReference Manual\" for details about the /y option.\r\n\r\n\r\nINSTALLING PC-NFS SOFTWARE WITH AN NDIS DRIVER\r\n\r\nQUIKNDIS is a utility supplied with PC-NFS software which assists \r\nyou in configuring an NDIS driver for use with PC-NFS software. If \r\nyou plan to use an NDIS driver, you may use the QUIKNDIS utility \r\non the QUIKNDIS diskette. If your system administrator has installed \r\nQUIKNDIS on the network, you may run it from the network instead.\r\n\r\nRead the QUIKNDIS README file before you install PC-NFS software for\r\nimportant information about installing PC-NFS software for use with\r\nan NDIS driver.\r\n\r\n\r\nEXIT MS-WINDOWS BEFORE REBOOTING PC\r\n\r\nWhen prompted to reboot after installing or configuring PC-NFS \r\nsoftware within MS-Windows, exit MS-Windows before rebooting \r\nyour PC.\r\n\r\n\r\nTHIRD-PARTY MEMORY MANAGER LOAD-HIGH LINES OVERWRITTEN \r\n\r\nIf you are using a third-party memory manager with PC-NFS software, \r\ne.g., QEMM (TM), any lines in AUTOEXEC.BAT or CONFIG.SYS that load \r\nPC-NFS device drivers or TSRs into high memory will be overwritten \r\nwhen you upgrade PC-NFS software. After upgrading, manually edit the \r\nlines in AUTOEXEC.BAT or CONFIG.SYS so that these programs will be \r\nloaded into high memory.\r\n\r\n\r\n\r\n**CONFIGURATION**\r\n\r\n\r\nDO NOT LOAD PROTMAN.SYS INTO HIGH MEMORY\r\n\r\nIf you reconfigure any of the PC-NFS drivers to load high using \r\nMS-DOS(R) 5.0, DR DOS(TM), or a third-party memory manager, make \r\nsure that PROTMAN.SYS is not loaded high.\r\n\r\n\r\nSOME SERVER NAMES IN NFSCONF CANNOT EXCEED 15 CHARACTERS\r\n\r\nWhen defining a PCNFSD server, NIS server, or gateway in the \r\nNFSCONF Advanced Questions screen, you cannot enter a server name\r\nthat exceeds 15 characters. PC-NFS software will accept server names \r\nup to 64 characters, but not in the NFSCONF program. You must enter \r\nany server name exceeding 15 characters in the appropriate line in \r\nthe NETWORK.BAT file, as described below.\r\n\r\nIf you are configuring PC-NFS software for the first time, follow \r\nthese steps:\r\n\r\n1. Proceed according to the configuration instructions in the \"PC-NFS\r\n Installation Guide\" with the following exception: in the Advanced\r\n Questions screen, leave the server name field blank if you intend \r\n to use a server name that exceeds 15 characters.\r\n\r\n2. When prompted, press N to defer a reboot and exit to DOS. \r\n\r\n3. Using a text editor, modify the NETWORK.BAT file as necessary to \r\n contain lines similar to the following:\r\n\r\n NET ROUTE shishkebob.East.Sun.COM\r\n NET NISSET baklava.East.Sun.COM\r\n NET PCNFSD souvlaki.East.Sun.COM\r\n \r\n4. Reboot the PC for your changes to take effect.\r\n \r\nIf you are reconfiguring PC-NFS software, modify NETWORK.BAT as\r\ndescribed in the previous instructions, and do not use the Advanced\r\nQuestions screen to change your configuration.\r\n\r\n\r\nGATEWAY AND PCNFSD SERVER NAME FIELDS SHOULD NOT BE BLANK IN NFSCONF\r\n\r\nIf your network uses a gateway, enter the gateway name in the Advanced \r\nQuestions screen of the installation program, or edit the name manually \r\nin the NETWORK.BAT file as described in the preceding note. If you do \r\nnot, an incorrect gateway name may be used (with NIS), or your PC will \r\nnot be able to reach machines outside of the local network (without NIS).\r\n\r\n\r\nUSE DEFAULT SETTINGS FOR IBM(R) TOKEN RING(TM) ADAPTER ON MICROCHANNEL PC \r\n\r\nIf you are using an IBM PS/2(R) or other Microchannel PC and an IBM Token \r\nRing adapter with the PC-NFS (non-NDIS) driver TRDRIVEM.SYS, the Token \r\nRing adapter must be configured with the default ROM and RAM settings. \r\nTo do this, reboot your PC with the system reference diskette supplied\r\nwith the PC, choose the menu options to view the current configuration,\r\nand verify that the ROM address is CC000H and that the RAM is configured\r\nwith 16 Kbytes of RAM based at D8000H. If the adapter settings are \r\ndifferent from this, use the menu options to change them. Consult your \r\nPC and adapter documentation for more information.\r\n\r\nIf you cannot reconfigure your Token Ring adapter for any reason, you\r\ncan still run PC-NFS software using the NDIS driver. Consult the \r\n\"PC-NFS Installation Guide\" for instructions.\r\n\r\n\r\n\r\n**LOCKING SERVICES AND PCNFSD**\r\n\r\n\r\nINSTALLING THE LOCK DAEMON\r\n\r\nRead this note if you are a system administrator who wants to install\r\nPC-NFS locking services on an NFS(R) server. The dolockd.sh script \r\nshould only be run on a server with SunOS(TM) 4.1 or 4.1.1, and a \r\nSun-3x, Sun-4(TM), or Sun-4c architecture. \r\n\r\nThe dolockd.sh script does not install a lock daemon for the Sun-3(TM)\r\narchitecture. If you are using a server with the Sun-3 architecture, \r\nyou can run the lock daemon from PC-NFS 3.5 software. If you do not \r\nhave PC-NFS Version 3.5 software, you can obtain a patch from your \r\nlocal support representative.\r\n\r\nTo determine the server's architecture, run the following command:\r\n\r\n arch -k\r\n\r\nPC-NFS 4.0 ships a lockd and kernel patch (release 100075-06) on the\r\ndistribution diskette. If a later patch has been installed \r\n(e.g., release 100075-07), do not run the dolockd.sh script.\r\n\r\nThe dolockd.sh script does not support the Sun-4m architecture. Servers\r\nwith this architecture should be running SunOS 4.1.2 or greater, which \r\nsupplies an appropriate lock daemon.\r\n\r\n\r\nCOMPILING PCNFSD ON AN IBM RS6000\r\n\r\nTo compile PCNFSD Version 2 on an IBM RS6000, modify the PCNFSD \r\nMakefile by adding the -D_BSD option to the CFLAGS line below:\r\n\r\nCFLAGS= -g -DUSER_CACHE -DWTMP -DUSE_YP -D_BSD\r\n\r\nFor more information about installing PCNFSD, refer to the \"PC-NFS \r\nAdministration Guide.\"\r\n\r\n\r\n \r\n**GENERAL NOTES**\r\n\r\n\r\nRUNNING PC-NFS UTILITIES WITH LIMITED MEMORY\r\n\r\nMany PC-NFS utilities require the resident transport module (RTM) \r\nand the resident naming module (RNMFILE or RNMNIS) to be installed \r\nin order to operate. These utilities automatically load RTM and the\r\nresident naming module if they are not already loaded. When these\r\nmodules are automatically loaded, the utilities reserve more than\r\nthe required amount of memory. When you load them from the command \r\nline, they do not require as much memory.\r\n\r\nIf a PC-NFS application fails unexpectedly, e.g., you cannot mount \r\na printer by using NFSCONF, exit the application. Load RTM and then \r\nload either RNMFILE or RNMNIS from the DOS command line and rerun \r\nthe application. Refer to the \"PC-NFS Reference Manual\" for\r\ninformation about RTM, RNMFILE, and RNMNIS. \r\n\r\n\r\nMV COMMAND WITH LOCAL FILES MAY GENERATE INCORRECT ERROR MESSAGE\r\n\r\nWhen renaming local files and directories, the MV command sometimes\r\ndisplays the following message even though the file or directory was\r\nrenamed correctly:\r\n\r\n NFS081F : File not found, or access violation.\r\n\r\n\r\nPROBLEMS WITH LONG ICMP PACKETS \r\n\r\nPC-NFS software does not correctly handle ICMP packets (e.g., PING)\r\nwith 256 bytes or more of data. Two problems can occur: (1) any \r\nPING reply will be incorrectly formatted, and (2) if using a 3Com \r\nadapter with a non-NDIS driver, the PC may ignore all subsequent ICMP \r\npackets. \r\n\r\nUsing an NDIS driver prevents the second problem from occurring, but\r\nnot the first. For details about configuring PC-NFS software for use \r\nwith an NDIS driver, refer to the \"PC-NFS Installation Guide\" or the \r\nREADME file on the QUIKNDIS diskette supplied with PC-NFS software.\r\n\r\n\r\nPC MAY HANG IF CTRL-BREAK IS USED TO ABORT PROGRAM WHILE LOADING \r\n\r\nYour PC may hang if you use CTRL-BREAK to stop a large executable file\r\nfrom loading. This is true with any application - not just those \r\nsupplied with PC-NFS software. \r\n\r\n\r\nMYEADDR UTILITY HANGS PC WITH 3COM(R) 3C505 BOARD \r\n\r\nDo not use the MYEADDR command if your PC has a 3Com 3c505 board. \r\nTo determine the board's Ethernet(R) address, use the diagnostic \r\nprogram supplied with the board.\r\n\r\n\r\nSHOWMNT -L COMMAND MAY CAUSE PC TO HANG\r\n\r\nDo not use the SHOWMNT -L command. Doing so may cause your PC to hang.\r\n\r\n\r\nUSE LATEST RTM AND RNM MODULES \r\n\r\nIf you install both PC-NFS 4.0 and the PC-NFS Programmer's Toolkit 2.0\r\non the same PC, or if you use an application which is distributed\r\nwith the resident modules (RTM and either RNMFILE or RNMNIS), verify \r\nthat you are using the most recent resident modules. \r\n\r\nYou can check the version of each module using the -v option: the files \r\ndistributed with the Toolkit are identified as 2.0, while those shipped \r\nwith PC-NFS Release 4.0 are identified as version 3.0. \r\n\r\nIf you install the PC-NFS Programmer's Toolkit 2.0 after you have \r\ninstalled PC-NFS software, make sure that the resident modules supplied\r\nwith PC-NFS 4.0 are not overwritten.\r\n\r\n\r\n\r\n**MICROSOFT WINDOWS SUPPORT**\r\n\r\n\r\nUSE PRINT MANAGER TO CONTROL PRINTING \r\n\r\nWhen configuring Printers to be used with PC-NFS software, it is\r\nrecommended that you use the Print Manager. You can do so by selecting \r\n\"Use Print Manager\" in Control Panel. Print Manager correctly handles \r\noutput redirection to a local or remote printer. If you have problems \r\nprinting to a local printer (i.e., one attached to your machine), go \r\nto Print Manager and verify that \"Print Net Jobs Direct\" is disabled. \r\nIn Windows 3.1, select \"Options\" and then select \"Network Settings.\" \r\nIn Windows 3.0, select \"Options\" and then select \"Network.\"\r\n\r\n\r\nMANUALLY UPDATE NETWORK QUEUE STATUS WHEN USING PRINT MANAGER\r\n\r\nIf you are viewing a network print queue using Print Manager, the \r\nstatus of the print job will not be automatically updated by Print \r\nManager. To update the status of the print queue manually, follow \r\none of these procedures:\r\n\r\n o If using MS-Windows 3.0, choose Update Net Queues from the View \r\n menu.\r\n\r\n o If using MS-Windows 3.1, choose Refresh from the View menu.\r\n\r\n\r\nTELNET IN MS-WINDOWS DOES NOT SCROLL PROPERLY\r\n\r\nIf you are running TELNET within MS-Windows, scrolling may work \r\nincorrectly and the bottom half of the screen may appear blank. \r\nThis problem appears to be associated with particular MS-Windows \r\nvideo drivers.\r\n\r\nIf this occurs, you can iconize TELNET and reopen the window, or \r\nmaximize the window. If you are running an application in your \r\nTELNET session, enter the appropriate keystrokes for your \r\napplication to refresh the screen. For example, to refresh the \r\nscreen when you are using vi, enter command mode and type CTRL-L. \r\n\r\n\r\nFILE MANAGER DRIVE ICON INCORRECTLY APPEARS TO BE A LOCAL DRIVE\r\n\r\nIf the network path of the file system you are mounting exceeds \r\n64 characters, MS-Windows File Manager will incorrectly display \r\nthe Disk-drive icon in the Directory Tree window as a local drive, \r\nrather than as a network drive. This has no effect on operation.\r\n\r\n\r\nINCORRECT DATE AND TIME DISPLAYED WHEN VIEWING PRINT QUEUE\r\n\r\nWhen you view a print queue using MS-Windows Print Manager, the date\r\nand time are incorrectly displayed. You may turn off the date and\r\ntime display by using the View submenu in Print Manager.\r\n\r\n\r\nCANCELLING PRINTING FROM MS-WINDOWS APPLICATIONS LEAVES PART OF JOB \r\nIN QUEUE\r\n\r\nThis applies if you decide not to use Print Manager and instead, \r\nyou print network jobs directly. If you print from an MS-Windows \r\napplication, a dialog box is displayed while the job is being spooled, \r\nenabling you to cancel the print job. If you select \"Cancel,\" the job \r\nstops spooling; however, the portion of the file that is already \r\nspooled to the print queue will be printed.\r\n\r\n\r\nPING COMMAND DOES NOT WORK WITHIN MS-WINDOWS WITH 3C501 BOARD \r\n\r\nIf your PC has a 3Com 3c501 board and you are running MS-Windows,\r\nyou cannot use the PING command to reach a machine on your network.\r\nTo avoid this problem use an NDIS driver with this board.\r\n\r\n\r\n\r\n**PRINTING**\r\n\r\n\r\nUSING INCORRECT SYNTAX FOR TIME-OUT OPTION CAUSES PC TO HANG \r\n\r\nAny time you change the time-out option -Tnnn for the PRT.COM program,\r\nmake sure that you do not enter a space between the -T option and the\r\n variable. Doing so causes your PC to hang.\r\n\r\nUse the syntax: \r\n\r\n PRT -Tnnn *\r\n\r\nwhere is the number of seconds that PC-NFS software waits before\r\nspooling the print job.\r\n\r\n\r\nDIRECTIONS FOR INSTALLING AN HP LASERJET(TM) PRINTER ON A SUN SERVER\r\n\r\nTo set up an HP LaserJet printer on a Sun server and make the printer\r\navailable for printing from PC applications configured for HP LaserJet\r\nprinters, follow this procedure:\r\n\r\n 1. Make the following entry in the /etc/printcap file on the Sun\r\n server and save the file:\r\n \r\n hplaser|hplaser|HP LaserJet in PGL mode:\\\r\n :lp=/dev/ttya:br#9600:\r\n :ms=pass8,ixon,raw:\\\r\n :sh:\\\r\n :sd=/var/spool/hplaser:\\\r\n :lf=/var/spool/lpd/log:\r\n \r\n 2. Make this printer available to PC-NFS software users by creating\r\n the spool directory /var/spool/hplaser. \r\n\r\n 3. Export the spool directory by adding the directory name to the\r\n /etc/exports file. \r\n\r\nWhen you mount the LaserJet printer from a PC, use the print filter\r\noption, Raw (unfiltered).\r\n\r\n\r\nSPECIFYING TRAILER OPTION WHEN USING PC PRINT SERVER\r\n\r\nWhen the PC print server sends a print job to the local printer, it \r\nuses the CTRL-L (form feed) character as the default end-of-job \r\ncharacter. If you do not want to send this character to the printer\r\n(because you do not want a page eject, because you want to send \r\ndifferent end-of-job characters, or because CTRL-L hangs the printer), \r\nyou can use the trailer option when starting the print server. \r\n\r\nTo start the print server from the command line with the trailer \r\noption, use the following syntax:\r\n\r\npcnfslpd -P -t[] { or NUL}\r\n\r\nwhere: \r\n\r\n is the name of the printer to which the trailer option\r\napplies. If is not specified, the trailer option applies\r\nto all printers. \r\n\r\n is the name of the file residing in the \\NFS directory which\r\ncontains the end-of-job characters that you want to send to the printer.\r\nIf you do not specify a filename, the default end-of-job character \r\nCTRL-L (form feed) will be sent to the printer. If you do not want the\r\ndefault to be sent to the printer, specify NUL. \r\n\r\nTo start the print server using a PCNFSLPD.INI file with the trailer\r\noption, add the following line to the file:\r\n\r\nTRAILER [] { or NUL}\r\n\r\nFor example, to start the print server and send CTRL-L to printer lp1, \r\nand prevent CTRL-L from being sent to printer ps2, enter the following \r\ncommand:\r\n\r\npcnfslpd -PLPT1: lp1 -PCOM1: ps2 -tCOM1: NUL \r\n\r\nTo start the print server using the PCNFSLPD.INI file, and to send\r\nthe end-of-job characters contained in the file named TRAIL.LP to\r\nthe printers lp1 and lp2, add the following lines to PCNFSLPD.INI:\r\n\r\nPRINTER LPT1: lp1\r\nPRINTER LPT2: lp2\r\nTRAILER TRAIL.LP \r\n \r\nFor more information about the print server start-up options, \r\nrefer to Chapter 4 of the \"PC-NFS User's Guide.\"\r\n\r\n\r\nPRINT JOBS SENT TO SERIAL PORT MAY BE LOST WHEN USING PRINT SERVER\r\n \r\nYour print jobs may be lost if you use the print server on a printer\r\nattached to a serial port and the following conditions apply: \r\n\r\n o The printer has generated an error condition (e.g., \"out of\r\n paper\"), and\r\n\r\n o There are other print jobs in the queue. \r\n\r\nAs a workaround, re-send the print job.\r\n\r\n\r\nUSE LPT D COMMAND ONLY TO DELETE JOBS SENT TO PC PRINT SERVER\r\n\r\nThe LPT D command can only be used to delete jobs that are sent to\r\na PC print server. To delete other jobs, use the NET CANCEL command.\r\nRefer to the \"PC-NFS Reference Manual\" for information about the \r\nNET CANCEL command.\r\n\r\n\r\n\r\n**APPLICATIONS COMPATIBILITY**\r\n\r\n\r\nMS-DOS 5.0 DOSSHELL PROGRAM COPIES FILE TO INCORRECT LOCATION \r\n\r\nWhen you use the MS-DOS 5.0 DOSSHELL program to copy a file to \r\na subdirectory on a network drive, the file is copied to the root of\r\nthat network drive, instead of the subdirectory. \r\n\r\n\r\nMS-DOS 5.0 BACKUP COMMAND WORKS INCORRECTLY ON NETWORK DRIVES\r\n\r\nThe MS-DOS 5.0 BACKUP command does not work correctly when you attempt\r\nto back up files to a network drive.\r\n\r\n\r\nHARVARD GRAPHICS(TM) DOES NOT RETRIEVE FILES WITH SHORT NAMES \r\n\r\nWhen using Harvard Graphics with certain versions of DOS, you \r\ncannot retrieve a previously created file if the file name consists \r\nof fewer than eight characters before the extension or fewer than \r\nthree characters after the extension. This is due to the way some \r\nversions of DOS treat short file names. To access these files, \r\nchange the file name or use the /s option in the PCNFS.SYS line \r\nin CONFIG.SYS. (See the \"PC-NFS Reference Manual\" for information \r\nabout using the /s option in the CONFIG.SYS file.)\r\n\r\n\r\nDO NOT USE PC-NFS UTILITIES AFTER ISSUING DOS ASSIGN COMMAND \r\n\r\nIf you use the ASSIGN command after PC-NFS software has been started,\r\nyou will be unable to use PC-NFS applications or utilities that require\r\nRTM to be loaded. There are two ways to avoid this problem if you need \r\nto use the ASSIGN command: (1) Use the ASSIGN command before you start \r\nPC-NFS software, or (2) Load RTM after you start PC-NFS software but \r\nbefore you use the ASSIGN command. Note that PC-NFS software does not \r\nsupport the use of the ASSIGN command to map network drives.\r\n\r\n\r\nPC-NFS SOFTWARE MAY NOT DETECT FILES LOCKED WITH DBASE(R) IV VERSION 1.1\r\n\r\nAlthough a file has been locked with dBase IV Version 1.1, PC-NFS\r\nsoftware may not detect that the file has been locked. Users\r\nexperiencing this problem should use a later version of dBase IV.\r\n\r\n\r\n\r\n\r\nPart No. 800-6928-10\r\nRevision A, March 1992" }