{ "disks": { "1": { "dirs": [ { "path": "/", "files": [ { "name": "INSTALL EXE", "size": 80622, "date": "1991-11-04", "time": "12:00" }, { "name": "WP S01", "size": 1087606, "date": "1991-11-04", "time": "12:00" }, { "name": "WP SPN", "size": 496, "date": "1991-11-04", "time": "12:00" } ] } ] }, "2": { "dirs": [ { "path": "/", "files": [ { "name": "README NET", "size": 34358, "date": "1991-11-04", "time": "12:00" }, { "name": "DLL SPN", "size": 397, "date": "1991-11-04", "time": "12:00" }, { "name": "DLL S01", "size": 1139591, "date": "1991-11-04", "time": "12:00" } ] } ], "volume": "Y" }, "3": { "dirs": [ { "path": "/", "files": [ { "name": "UTIL SPN", "size": 1108, "date": "1991-11-04", "time": "12:00" }, { "name": "UTIL S01", "size": 1065587, "date": "1991-11-04", "time": "12:00" } ] } ] }, "4": { "dirs": [ { "path": "/", "files": [ { "name": "LEARN SPN", "size": 3529, "date": "1991-11-04", "time": "12:00" }, { "name": "LEARN S01", "size": 1153632, "date": "1991-11-04", "time": "12:00" } ] } ] }, "5": { "dirs": [ { "path": "/", "files": [ { "name": "LMI SPN", "size": 310, "date": "1991-11-04", "time": "12:00" }, { "name": "LMI S01", "size": 813277, "date": "1991-11-04", "time": "12:00" } ] } ] }, "6": { "dirs": [ { "path": "/", "files": [ { "name": "UNIXNEWS", "size": 30096, "date": "1991-01-21", "time": "14:17" }, { "name": "TRANSLAT", "size": 16602, "date": "1991-01-21", "time": "15:29" }, { "name": "INSTALL LST", "size": 20446, "date": "1991-11-05", "time": "12:00" }, { "name": "WPR1 SPN", "size": 1075, "date": "1991-11-05", "time": "12:00" }, { "name": "WPR1 S01", "size": 987953, "date": "1991-11-05", "time": "12:00" } ] } ] } }, "desc_file": "README.NET", "desc_text": "=================================================================\r\nREADME.NET 11/04/91\r\n=================================================================\r\nThis README file contains information that was not available when\r\nthe WordPerfect Reference Manual was printed. This file is\r\nintended to complement Appendix M: Networking WordPerfect by\r\ncovering the following topics:\r\n\r\n* What to do if WordPerfect 5.1 for Windows is NOT supported on\r\n your network\r\n\r\n* What you should know generally before you install WordPerfect,\r\n including information about:\r\n\r\n - sharing resources\r\n - which directories are created during installation\r\n - which startup options are placed in environment files (for\r\n example, WP{WP}.ENV) during installation\r\n - why the PATH statement is optional\r\n - why the WordPerfect Group File (WPW51US.GRP) is necessary\r\n - startup options \r\n - .INI files\r\n \r\n* Network specific helps and hints\r\n \r\nYou can find additional information about running Windows on a\r\nnetwork in the NETWORK.TXT file included with your copy of\r\nWindows.\r\n\r\nMost network software companies that support Windows also include\r\ninformation on how to configure Windows to run with their\r\noperating systems. This information may prove helpful in\r\ntroubleshooting problems related to the operating system and\r\nWindows.\r\n\r\n=================================================================\r\nIS WORDPERFECT 5.1 FOR WINDOWS SUPPORTED ON YOUR NETWORK?\r\n=================================================================\r\nThough WordPerfect 5.1 for Windows is supported on a wide variety\r\nof network operating systems, there is the chance that it is not\r\nsupported on your network.\r\n\r\nWordPerfect 5.1 for Windows is considered \"supported\" on a\r\nnetwork if the network: 1) has file locking and allows\r\nworkstations to attach to shared resources and use them through\r\nWindows, and 2) is available to developers and testers at the\r\nWPCorp Lab.\r\n\r\nThe following networks meet these criteria:\r\n\r\n0-Other\r\n1-Novell Netware\r\n2-Banyan Vines\r\n3-TOPS Network\r\n4-IBM LAN Network\r\n4-IBM OS/2 LAN Server\r\n4-Microsoft LAN Manager\r\n4-Ungerman Bass LAN Manager \r\n4-LANsmart\r\n4-PC NOS\r\n4-DNA\r\n4-Invisible NET\r\n5-Nokia PC-Net\r\n6-3COM 3+\r\n7-10NET\r\n8-LANtastic\r\n9-AT&T StarGROUP\r\nA-DEC PCSA (Pathworks)\r\nB-3COM 3+ OPEN\r\nC-Banyan Streetalk\r\n\r\nThe numbers or letters next to the network names identify the /NT\r\nstartup option that you choose during installation.\r\n\r\nIf your network is not listed above, it may be able to emulate a\r\nnetwork that WPCorp does support. Listed below are those\r\nnetworks for which an emulation exists, followed by the supported\r\nnetwork and /NT startup option:\r\n\r\nNETWORK EMULATION /NT STARTUP OPTION\r\nNetware Lite IBM LAN Network 4\r\nCBIS IBM LAN Network 4\r\nHP Office Share OS/2 LAN Manager 4\r\nPCNFS Other 0\r\nPowerLAN IBM LAN Network 4\r\nMainLAN IBM LAN Network 4\r\n\r\nIf your network does not appear in any list above, but the\r\nWindows File Manager and Print Manager let users see and use\r\nnetwork shared resources (drives and printers), call Network\r\nCustomer Support at 1-800-228-6066. WPCorp is eager to help you\r\nrun WordPerfect 5.1 for Windows on your network.\r\n\r\nNOTE: WPCorp does not support workstations running OS/2\r\n(versions 1.0 - 1.3) because the OS/2 DOS compatibility box\r\ncannot run Windows in Standard or Enhanced mode.\r\n\r\n=================================================================\r\nBEFORE YOU INSTALL WORDPERFECT\r\n=================================================================\r\nThis section explains generally what you should do or know before\r\nyou begin installing WordPerfect on the network. The next major\r\nsection, NETWORK SPECIFIC HELPS AND HINTS, elaborates on many of\r\nthe concepts in this section.\r\n\r\nSHARING RESOURCES\r\nBefore installing WordPerfect, we suggest that you create a\r\nshared resource or a destination drive. The Installation Program\r\ncreates, at your request, default program directories (see\r\nSHARING RESOURCES under NETWORK SPECIFIC HELPS AND HINTS below). \r\n\r\nDIRECTORIES\r\nIf you choose to do a network installation in the Installation\r\nProgram, three directories are created on the destination drive:\r\nWPWIN, WPCINI, and WPC.\r\n\r\nThe WPWIN and WPC directories are where the Installation Program\r\ninstalls executable and .DLL files. The WPCINI directory stores\r\nuser specific .INI and .SET files. See GRANTING RIGHTS TO THE\r\nWPWIN, WPC, AND WPCINI DIRECTORIES under NETWORK SPECIFIC HELPS\r\nAND HINTS below to learn which rights these directories should\r\nhave.\r\n\r\nENVIRONMENT FILES\r\nDuring installation, an environment file is created for each\r\nWPCorp product (for example, WP{WP}.ENV for WordPerfect,\r\nFM{FM}.ENV for WordPerfect File Manager, SP{SP}.ENV for\r\nWordPerfect Speller, and TH{TH}.ENV for WordPerfect Thesaurus). \r\nThese files allow WordPerfect products to operate in a networked\r\nenvironment. At your request, the Installation Program checks\r\nthese files (or creates them if they do not exist) to make sure\r\nthe following startup options are included:\r\n\r\nENVIRONMENT FILE STARTUP OPTIONS INCLUDED\r\nWP{WP}.ENV /nt, /ps, /ni, and /wpc\r\nFM{FM}.ENV /nt and /ni\r\nSP{SP}.ENV /nt and /ni\r\nTH{TH}.ENV /nt and /ni\r\n\r\nFor more information about these startup options, see STARTUP\r\nOPTIONS below. The following is an example of how the WP{WP}.ENV\r\nfile might look after network installation:\r\n\r\n /NT=1\r\n /PS=J:\\WPCINI\r\n /NI=J:\\WPC\r\n /WPC=J:\\WPC\r\n\r\nThe exact network number and pathnames depend on the network you\r\nchoose and the pathnames you specify for the Shared .INI and .SET\r\nfiles and the WPCorp Shared Products.\r\n\r\nTHE PATH\r\nIf the WP{WP}.ENV file contains the /WPC startup option and a\r\npathname, the path statement (normally located in each user's\r\nAUTOEXEC.BAT file) is NOT necessary to run WordPerfect 5.1 for\r\nWindows. The Installation Program does not add directories or\r\ndrive letters to the path. If you decide to have a path\r\nstatement, the WPCorp Shared Products pathname specified in the\r\n/WPC startup option overrides any pathnames you establish for the\r\nsame purpose in the path statement. See NETWORK SPECIFIC HELPS\r\nAND HINTS below for more information about the path.\r\n\r\nWPW51US.GRP\r\nThe WPCorp Group file contains the WordPerfect 5.1 for Windows\r\nand WordPerfect File Manager icons. Each network user must have\r\na group in order to set up the icons. The Installation Program\r\ncreates the Group file and adds it to the PROGMAN.INI file. If\r\nyou want all users on the network to use this group file, it must\r\nbe copied to users' Windows directory. In addition, their\r\nPROGMAN.INI file must be edited to include this group.\r\n\r\nSTARTUP OPTIONS\r\nThe /NT, /NI, /PS, and /WPC startup options are necessary for\r\nsuccessfully running WordPerfect 5.1 for Windows from your file\r\nserver. During installation, the Installation Program places all\r\nfour of these startup options (at your request) in the WP{WP}.ENV\r\nfile, while only the /ni and /nt options are placed in the\r\nenvironment files for other WPCorp products (see ENVIRONMENT\r\nFILES above). The /D and /PI startup options are also useful for\r\nrunning WordPerfect on the network. The following information\r\ndefines these six startup options in alphabetical order.\r\n\r\nNOTE: THE ONLY PLACE YOU MAY USE THE /WPC STARTUP OPTION IS IN\r\nTHE WP{WP}.ENV FILE (SEE BELOW).\r\n\r\n /D\r\n The /D startup option redirects the creation of the user\r\n work directory and temporary files to a specified location. \r\n Use the following syntax when using this option: WPWIN.EXE\r\n /D-DRIVE:\\DIRECTORY (for example, WPWIN.EXE /D-C:\\TEMP). \r\n This startup sequence will force the work directory to be\r\n created and subsequent temporary files to be created in the\r\n specified directory. You can include this startup option,\r\n using the same syntax, in the DOS environment via a SET\r\n command. You can also use the /D startup option in the file\r\n properties of the WordPerfect 5.1 for Windows icon itself,\r\n for example: W:\\WPWIN\\WPWIN.EXE /D-C:\\TEMP.\r\n\r\n /NI\r\n The /NI startup option lets you specify the path to the\r\n WPC_NET.INI file. The syntax of this startup option is\r\n /NI-PATH and is processed when the first WPCorp application\r\n starts. You can put the startup option on the command line,\r\n in the application specific DOS environment variable (for\r\n example, \"WPWIN\" for WP 5.1 for Windows), in the DOS\r\n environment variable \"WPC,\" or in the application specific\r\n .ENV file (for example \"WP{WP}.ENV\" for WordPerfect 5.1 for\r\n Windows). \r\n\r\n If you don't specify the /NI startup option, but the /PI\r\n startup option is specified, the application searches for\r\n the WPC_NET.INI file in the location given in the /PI\r\n startup option. If the WPC_NET.INI file is not found in\r\n either location, the application will look in the following\r\n directories in the listed order:\r\n\r\n 1. The directory in which the application .EXE file\r\n resides.\r\n 2. The Windows directory (containing WIN.COM).\r\n 3. The directories listed in the DOS PATH environment\r\n variable.\r\n 4. The directories mapped in a network.\r\n\r\n If WordPerfect cannot find the WPC_NET.INI file, it will\r\n still run but will not be able to access this file.\r\n\r\n /NT\r\n The /NT startup option tells WordPerfect which network you\r\n are using (for example, /NT=1 for Novell, /NT=2 for Banyan).\r\n Unless you use the /NT startup option, and the corresponding\r\n network number or letter, WordPerfect will NOT run as a\r\n network version for your network. \r\n\r\n NOTE: Appendix M: Networking WordPerfect in your copy of\r\n the WordPerfect for Windows Reference Manual may say that\r\n the existence of the WP{WP}.ENV file is sufficient for\r\n WordPerfect 5.1 for Windows to run as a network version. \r\n However, THIS IS NO LONGER THE CASE. You MUST use a /NT\r\n startup option in the WordPerfect Environment file for\r\n WordPerfect to run as a network version. See IS WORDPERFECT\r\n 5.1 FOR WINDOWS SUPPORTED ON YOUR NETWORK above for a\r\n listing of the networks that currently support WordPerfect\r\n 5.1 for Windows and the corresponding numbers and letters. \r\n This list is subject to change. To find out about any\r\n changes, call WordPerfect Information Services at 801-225-\r\n 4777.\r\n\r\n /PI\r\n This startup option lets you specify the path to the WPC.INI\r\n file, and is OPTIONAL. Use it only if you choose NOT to\r\n place the WPC.INI file in users' Windows directory, or if\r\n you want to use a different language version of WordPerfect\r\n 5.1 for Windows (see below). The syntax for this startup\r\n option is /PI-PATH. \r\n\r\n NOTE: Before establishing a directory pathname in the /PI\r\n startup option, you should make sure that directory exists\r\n and that it contains the WPC.INI file.\r\n\r\n The /pi and /ni startup options let you install and use\r\n multiple languages of the same WPCorp product on one\r\n computer. For example, let's suppose that you already have\r\n a U.S. English copy of WordPerfect 5.1 for Windows installed\r\n on your computer, but you would also like to install the\r\n French version of WordPerfect 5.1 for Windows.\r\n\r\n Because the U.S. English and French versions are considered\r\n separate applications, you would put them in different\r\n locations on the file server, each with its own WPC.INI and\r\n WPC_NET.INI files. If users ask to use the French version\r\n of WordPerfect 5.1 for Windows, you can change the directory\r\n pathname in the /pi and /ni startup options, and thereby\r\n redirect the program to the \"French product\" WPC.INI and\r\n WPC_NET.INI files containing the locations of the\r\n appropriate .INI files and other executable files.\r\n\r\n You can easily add the /pi startup option to the WordPerfect\r\n environment file using a text editor.\r\n\r\n /PS\r\n This startup option provides the directory path where\r\n individual personal setup files will be located. The /PS\r\n option identifies a common directory that is accessible by\r\n each network user to store his or her personal WPXXX}.SET\r\n file, where XXX represents the individual user's initials. \r\n WordPerfect .SET files are used to define the initial\r\n settings that the WordPerfect program will use, such as\r\n WordPerfect (non-Windows) printer selections, display\r\n attributes, and backup options. See /PS under Startup\r\n Options in Appendix M: Networking WordPerfect for more\r\n information.\r\n\r\n /WPC\r\n The /WPC startup option provides the directory path where\r\n the WPCorp Shared Products code is stored. Using this\r\n startup option frees you from having to include the Shared\r\n Products directory in the path. During installation, the\r\n Installation Program places this startup option in the\r\n WP{WP}.ENV file. THIS STARTUP OPTION SHOULD NOT BE ANYWHERE\r\n ELSE EXCEPT IN THE WP{WP}.ENV FILE. You may still include\r\n the Shared Code directory in the path, but the /WPC startup\r\n option will override it.\r\n\r\n.INI FILES\r\nA .INI file is an ASCII text file that an application uses during\r\ninitialization. In other words, .INI files tell applications\r\nwhich customized settings to use upon startup. Applications\r\nwrite to .INI files (usually upon closure), recording the changes\r\na user makes in Preferences and elsewhere. Regardless of whether\r\na user makes changes, however, these files always exist.\r\n\r\nNOTE: You may need to modify global .INI files. For example, if\r\nyou want all users to have a default QuickList or Short Menus\r\nturned on or standard macros on their menus, you will need to\r\nedit the WPC_NET.INI and WPWP_NET.INI files. Since .INI files\r\nare ASCII text files, you can easily do so using any text editor.\r\n\r\nThis section defines each type of .INI file and illustrates the\r\ninformation it contains (for more information, see .INI Files\r\nunder Appendix M: Networking WordPerfect).\r\n\r\n WPC.INI and WPC_NET.INI Files\r\n The user-specific, product-global .INI file (WPC.INI) is\r\n created for each user and stores information common to each\r\n WPCorp product. The shared-network, product-global .INI\r\n file (WPC_NET.INI) is a shared file which means it can be\r\n used by any number of network users. It is \"product-global\"\r\n because it stores information common to all of the WPCorp\r\n products. \r\n\r\n Both files may contain the same information. Here are some\r\n examples of the settings:\r\n\r\n [Settings] \r\n SuppDictionaryPath=j:\\users\\kelli\\docs\r\n MainDictionaryPath=j:\\wpc\\DE\r\n\r\n [Quicklist]\r\n Backup Files=j:\\users\\kelli\r\n Documents=j:\\users\\kelli\\docs\\*.doc\r\n\r\n [App Server]\r\n WPWP=w:\\wpc\\wpwin\\wpwin.exe;00600000;WordPerfect\r\n\r\n [FileOpen Options] \r\n Show QuickList=Yes\r\n\r\n [WPDB] \r\n SculpturedDialogs=Off\r\n\r\n [Launch-Open]\r\n Ami Pro 1.0=WPWIN \r\n etc.\r\n \r\n WP??_NET.INI and WP??XXX.INI Files\r\n The settings for each product are stored in either a shared-\r\n network, product-specific .INI file (WP??_NET.INI), or a\r\n user/product specific .INI file (WP??XXX.INI), where ??\r\n identifies the two letter product code (for example,\r\n WP=WPWIN, SP=SPWIN, TH=THWIN, MX=MXWIN), and XXX stands for\r\n the user's initials.\r\n\r\n The two files differ in that the WP??_NET.INI contains\r\n default settings for all users, whereas the WP??XXX.INI file\r\n contains unique settings for individual users. You can\r\n manually place settings in the \"master\" .INI file\r\n (WP??_NET.INI) to establish default settings for each user\r\n on the network. These files are stored where the\r\n WPC_NET.INI [Ini Paths] specifies. Some examples of\r\n settings found in these files are:\r\n\r\n WPWPXXX.INI or WPWP_NET.INI\r\n [Settings]\r\n Keyboard=* (for CUA keyboard) or\r\n Keyboard=x:\\wpwin\\macros\\wpdos51.wwk (for DOS 5.1)\r\n\r\n [Button Bar]\r\n ATTRIBS=112 (text and left side)\r\n BARNAME=w:\\wpwin\\macros\\wp{wp}.wwb\r\n\r\n [LastOpened] (four last opened files)\r\n labels.tst=j:\\users\\kelli\\labels.tst\r\n bottle.pri=j:\\users\\kelli\\bottle.pri\r\n bottle.sec=j:\\users\\kelli\\bottle.sec\r\n test.doc=j:\\users\\kelli\\test.doc\r\n\r\n WPSPXXX.INI or WPSP_NET.INI\r\n [Settings]\r\n Language=US\r\n Pos=124,348,552,254\r\n\r\n=================================================================\r\nNETWORK SPECIFIC HELPS AND HINTS\r\n=================================================================\r\nThis section contains network-specific information for the\r\nfollowing networks:\r\n\r\nNovell Netware 286 & 386\r\nBanyan\r\nIBM PC LAN\r\nIBM OS/2 LAN Server\r\nMicroSoft LAN Manager\r\n3 Com\r\n10 NET\r\nLANtastic\r\nAT & T StarGROUP\r\nDEC Pathworks\r\n3 Com 3+ Open\r\n\r\nIn this section, you will learn about:\r\n\r\n- Sharing resources\r\n- Optionally placing the WordPerfect directory in the path\r\n- Which rights are necessary for the WPWIN and WPCINI directories\r\n- Which rights are necessary for WordPerfect subdirectories \r\n- Additional rights you can give users to printer files\r\ndirectories\r\n- Network printing\r\n\r\nIt is assumed that during installation you chose option 3 for\r\nnetwork installation and that you used Install's default\r\ndirectories. \r\n\r\nSHARING RESOURCES\r\nBefore installing WordPerfect 5.1 for Windows on your network\r\noperating system, you should create a shared resource. This may\r\nmean creating a new directory structure on the file server and\r\nsharing it or simply sharing an existing resource. You would\r\nthen make this resource available to users following the\r\ninstallation and configuration of WordPerfect. The Installation\r\nProgram creates the necessary directories for you.\r\n\r\nIf you have a Novell, AT&T StarGroup, or DEC PSCA/Pathworks\r\nnetwork, read below for additional information:\r\n\r\n Novell\r\n On Novell Netware, you can share resources by mapping a\r\n search drive. You can do this by creating a new directory\r\n structure and mapping a new drive on the file server or by\r\n simply mapping a new drive letter to an existing structure. \r\n Allow users access to this search drive following the\r\n installation and configuration of WordPerfect.\r\n\r\n AT&T StarGroup\r\n If you are using the AT&T StarGroup network operating\r\n system, we recommend that you update workstations to use\r\n AT&T 3.4.1 requesters.\r\n\r\n DEC PSCA/Pathworks\r\n For the DEC PCSA/Pathworks operating system, we recommend\r\n that you create a disk service area or use a subdirectory of\r\n an existing disk service to hold the WPWIN directory. This\r\n disk service area should be created according to DEC PCSA\r\n network instructions. The disk service area must be mounted\r\n as read/write before the WPWIN files are installed. The\r\n installation process will create a file called WP{WP}.ENV\r\n (see General Concepts above). Make sure the user .SET files\r\n are directed to a file service. \r\n\r\nPLACING THE WORDPERFECT DIRECTORY IN THE PATH (OPTIONAL)\r\nIf the /WPC startup option and appropriate pathname have been\r\nspecified in the WP{WP}.ENV file, it is not necessary to place\r\nthe WordPerfect 5.1 for Windows directory (WPWIN) in the path;\r\nhowever, you can still place the WordPerfect directory in the\r\npath.\r\n\r\nIf you have a Novell, Banyan, or DEC PCSA Pathworks network, read\r\nbelow for additional information:\r\n\r\n Novell\r\n On Novell networks, we suggest that you map a drive to the\r\n shared resource where WordPerfect 5.1 for Windows has been\r\n installed. This drive letter MUST be used when setting up\r\n the file properties. For example, when setting the file\r\n properties for the WordPerfect 5.1 for Windows icon, the\r\n path might read W:\\WPWIN\\WPWIN.EXE.\r\n\r\n Banyan\r\n When setting up the WordPerfect 5.1 for Windows icon on\r\n Banyan networks, you should include the WordPerfect 5.1 for\r\n Windows executable program filename, plus any startup\r\n options you deem necessary. You can edit user or group\r\n profiles using the MANAGE utility.\r\n\r\n DEC PCSA/Pathworks\r\n If you're using a DEC PCSA/Pathworks network, invoke\r\n WordPerfect 5.1 for Windows to create the .LCN file before\r\n remounting the disk service as read-only. This file\r\n contains the WordPerfect License Number. Remount the disk\r\n service area as read-only before individual users access\r\n WordPerfect 5.1 for Windows.\r\n\r\nGRANTING RIGHTS TO THE WPWIN, WPCINI, AND WPC DIRECTORIES\r\nThe table below lists the rights that users should have to the\r\nWPWIN, WPC, and WPCINI directories. The utility that you will\r\nneed to grant these rights is listed in the third column.\r\n\r\nNETWORK WPWIN and WPCINI UTILITY\r\nOPERATING SYSTEM WPC\r\n\r\nNovell Netware Read, Open, All rights SYSCON\r\n286 Search but\r\n Parental\r\n\r\nNovell Netware Read, All but SYSCON\r\n386 Filescan Supervisor\r\n and Access\r\n Control\r\n\r\nBanyan VINES Read or R Modify or M SETARL\r\n\r\nIBM PC LAN Read, Read, NET\r\n Execute Write,\r\n Create,\r\n Execute\r\n\r\nIBM OS/2 LAN Read, Read, NETADMIN\r\n Execute Write,\r\n Create,\r\n Execute\r\n\r\nMS LAN MAN 2.0 Read, Read, NETADMIN\r\n Execute Write,\r\n Create,\r\n Execute\r\n\r\n3 COM 3+ Read Read, 3F Share\r\n Write,\r\n Create\r\n\r\n10 NET Read Read, NET SHARE\r\n Write,\r\n Create\r\n\r\nLANTastic Read, File All rights NET_MGR\r\n Lookup, but\r\n Execute Physical\r\n access to\r\n devices\r\n\r\nAT&T Read, Read, NET\r\n Execute Write,\r\n Create,\r\n Delete\r\n\r\nDEC Disk Service File ---\r\nPCSA/Pathworks Service\r\n\r\n3 COM 3+ OPEN Read, Read, NETADMIN\r\n Execute Write,\r\n Create,\r\n Delete\r\n\r\nYou should limit users' rights or privileges to the WPWIN\r\ndirectory. For example, users should not be able to create\r\ntemporary work directories or temporary files in this directory. \r\nIn handling temporary files and temporary work directories,\r\nWordPerfect looks for the following, in the listed order:\r\n\r\n1. SET WPWIN=/D-DRIVE:\\DIRECTORY NAME\r\n2. SET TEMP environment variable\r\n\r\nIf the SET WPWIN=/D-DRIVE:\\DIRECTORY NAME option exists,\r\nWordPerfect creates the temporary files directory and places the\r\ntemporary files in that directory. If this doesn't exist, then\r\nWordPerfect uses the SET TEMP environment variable. If the TEMP\r\ndirectory is not specified, then temporary files are created in\r\nthe TMP directory. If none of these are specified, then\r\ntemporary files are created in the current WordPerfect default\r\ndirectory (that is, where WPWIN.EXE is located).\r\n\r\nIf WordPerfect cannot find one of these two variables and cannot\r\ncreate the temporary work directories and temporary files, it\r\ndisplays a message box that reads: \"Unable to create work\r\ndirectory for work files.\" Choosing OK on this message box\r\ndisplays another message box which reads: \"Cannot initialize -\r\nThe most probable reason is insufficient memory.\" If you choose\r\nOK on this message box, you will return to the Program Manager. \r\n\r\nOn Novell networks, you can also put the /D startup option in the\r\nusers' login script. For example: \r\nDOS SET WPWIN=\"/D-U:\\USERS\\%LOGIN_NAME\" Use SYSCON to edit login\r\nscripts.\r\n\r\nOn Banyan networks, you can put the /D startup option in the\r\ngroup profile. For example: SET WPWIN=/D-C:\\TEMP. Use the\r\nMANAGE utility to edit group or user profiles.\r\n\r\nGRANTING RIGHTS TO WORDPERFECT SUBDIRECTORIES\r\nYou should make sure that you give users sufficient access to the\r\ndirectories they need while they work with WordPerfect. The\r\ntable below lists the rights users may have in these directories.\r\n\r\nNOTE: You may want to give users more rights to the printer\r\nfiles directory so they can change Paper Size/Types and Soft Font\r\nand Cartridges. If this is the case, see GRANTING ADDITIONAL\r\nRIGHTS TO PRINTER FILES DIRECTORY below.\r\n\r\nNETWORK Backup Document Graphic Printer Spread-\r\nOPERATING Files Files Files Files Sheets\r\nSYSTEM\r\n\r\nNovell All All Read, Read, All\r\nNetware 286 except except Open, Open, except\r\n Parental Parental Search Search Parental\r\n\r\nNovell All All Read, Read, All\r\nNetware 386 except except Filescan Filescan except\r\n Supervisor Supervisor \r\nSupervisor\r\n and and and\r\n Access Access Access \r\n Control Control Control \r\n \r\nBanyan Modify Modify or Read Read Modify\r\nVINES or M M or R or R or M\r\n\r\nIBM PC LAN Read, Read, Read Read Read,\r\n Write, Write, Write,\r\n Execute, Execute, Execute,\r\n Delete Delete Delete\r\n\r\nIBM OS/2 Read, Read, Read Read Read,\r\nLAN Write, Write, Write,\r\n Execute, Execute, Execute,\r\n Delete Delete Delete\r\n\r\nMS LAN MAN Read, Read, Read Read, Read,\r\n Write, Write, Execute Write,\r\n Delete Delete Delete\r\n\r\n3 COM 3+ Read, Read, Read Read Read,\r\n Write Write Write\r\n\r\n10 NET Read, Read, Read Read Read,\r\n Write, Write, Write,\r\n Create Create Create\r\n\r\nLANTastic All but All but Read and Read All but\r\n Physical Physical File and Physical\r\n access access to Lookup File access\r\nto\r\n to devices Lookup devices\r\n devices\r\n\r\nAT&T Read, Read, Read Read Read,\r\n Write, Write, Write,\r\n Execute, Execute, Execute,\r\n Delete Delete Delete\r\n\r\nDEC File File Disk File File\r\nPCSA/ Service Service Service Service Service\r\nPathworks\r\n\r\n3 COM 3+ Read, Read, Read Read Read,\r\nOPEN Write, Write, Write,\r\n Execute, Execute, Execute,\r\n Delete Delete Delete\r\n\r\n\r\nNETWORK Macros*/ Styles Thesaurus/ Thesaurus/\r\nOPERATING Keyboards/ Speller/ Speller/\r\nSYSTEM Button Hyphenation Hyphenation\r\n Bars (Main) (SUPP)\r\n\r\nNovell All except All except Read, Open, All except\r\nNetware 286 Parental Parental Search Parental\r\n\r\nNovell All except All except Read, All except\r\nNetware 386 Supervisor Supervisor Filescan Supervisor\r\n and Access and Access and Access\r\n Control Control Control\r\n\r\nBanyan VINES Modify or Modify or Read or R Modify or M\r\n M M\r\n\r\nIBM PC LAN Read, Read, Read Read,\r\n Write, Write, Write,\r\n Execute, Execute, Execute,\r\n Delete Delete Delete\r\n\r\nIBM OS/2 LAN Read, Read, Read Read,\r\n Write, Write, Write,\r\n Execute, Execute, Execute,\r\n Delete Delete Delete\r\n\r\nMS LAN MAN Read, Read, Read, Read,\r\n Write, Write, Execute Write,\r\n Delete Delete Delete\r\n\r\n3 COM 3+ Read, Read, Read Read, Write\r\n Write Write\r\n\r\n10 NET Read, Read, Read Read,\r\n Write, Write, Write,\r\n Create Create Create\r\n\r\nLANTastic All but All but Read and All but\r\n Physical Physical File Lookup Physical\r\n access to access to access to\r\n devices devices devices\r\n\r\nAT&T Read, Read, Read Read,\r\n Write, Write, Write,\r\n Execute, Execute, Execute,\r\n Delete Delete Delete\r\n\r\nDEC File File Disk File\r\nPCSA/Pathwork Service Service Service Service\r\ns\r\n\r\n3 COM 3+ OPEN Read, Read, Read Read,\r\n Write, Write, Write,\r\n Execute, Execute, Execute,\r\n Delete Delete Delete\r\n\r\n* You should compile all macros that users are going to use\r\nbefore restricting access to the macro directory. If you\r\nrestrict access before compiling macros, users won't be able to\r\nrun them.\r\n\r\nGRANTING ADDITIONAL RIGHTS TO PRINTER FILES DIRECTORY\r\nLimiting users' access to the printer files directory to READ\r\nwill not permit them to make permanent changes to Printer\r\nResource (.PRS) Files. These files include Paper/Size/Type and\r\nSoft Font/Cartridge information. \r\n\r\nTo give users access to these files, you need to grant at least\r\nthe rights listed in the table below. We suggest that you grant\r\nthese rights on a temporary basis only.\r\n\r\n\r\nNETWORK RIGHTS/PRIVILEGES\r\nOPERATING REQUIRED FOR USER ACCESS\r\nSYSTEM TO PRINTER FILES\r\n\r\nNovell Netware Parental\r\n286\r\n\r\nNovell Netware All but Supervisory\r\n386 and Access Control \r\n\r\nBanyan VINES Modify or M\r\n\r\nIBM PC LAN Read, Write, Execute,\r\n Delete\r\n\r\nIBM OS/2 LAN Read, Write, Delete\r\n\r\nMS LAN MAN Read, Write, Delete\r\n\r\n3 COM 3+ Read, Write\r\n\r\n10 NET Read, Write, Create\r\n\r\nLANTastic All rights but Change\r\n File Attributes and\r\n Physical Access to\r\n Devices\r\n\r\nAT&T Read, Write, Create,\r\n Delete\r\n\r\nDEC File Service\r\nPCSA/Pathworks\r\n\r\n3 COM 3+ OPEN Read, Write, Delete\r\n\r\nNETWORK PRINTING\r\nThis section provides network specific information for printing\r\nwith WordPerfect on your network.\r\n\r\nIn general, you need to use a printer redirection command so that\r\nthe workstation's local device attaches to the shared printer\r\nresource. You can place this command in each user's AUTOEXEC.BAT\r\nfile; however, other locations are listed in the table below. \r\n\r\nThe local device must be connected in the Windows Printer Control\r\nbefore WordPerfect will print correctly. You can manage\r\nredirection commands from the file server using your network's\r\nutility. For a complete listing of redirection commands, see\r\nNetwork Printing under Appendix M: Networking WordPerfect.\r\n\r\nNETWORK OPERATING WHERE TO PUT PRINTER\r\nSYSTEM REDIRECTION COMMANDS\r\n\r\nNovell Netware 286 AUTOEXEC.BAT\r\n Login Script\r\n\r\nNovell Netware 386 AUTOEXEC.BAT\r\n Login Script\r\n\r\nBanyan VINES Group or User\r\n Profile\r\n\r\nIBM PC LAN AUTOEXEC.BAT\r\n\r\nIBM OS/2 LAN AUTOEXEC.BAT\r\n\r\nMS LAN MAN AUTOEXEC.BAT\r\n\r\n3 COM 3+ AUTOEXEC.BAT\r\n *See below\r\n\r\n10 NET AUTOEXEC.BAT\r\n\r\nLANTastic **See below\r\n\r\nAT&T AUTOEXEC.BAT\r\n\r\nDEC PCSA/Pathworks NET USE Command\r\n\r\n3 COM 3+ OPEN AUTOEXEC.BAT\r\n\r\n*You can manage redirection commands using the 3P Share utility\r\n(from the server) and 3P Link (from the workstation).\r\n\r\n**On LANTastic networks, all printing must be sent to LPT2 or\r\nLPT3; only local printing should be sent to LPT1. \r\n\r\nTo print with WordPerfect 5.1 for Windows through LANTastic,\r\n\r\n1 Share the server's printer resource with the NET USE command\r\n(such as net use lpt2: \\\\servername\\@printer).\r\n\r\n2 Invoke Windows.\r\n\r\n3 Select the Control Panel from the MAIN group.\r\n\r\n4 Select the Printers option.\r\n\r\n5 Bypass the Windows spooler by clearing the Use Printer\r\nManager check box. \r\n\r\n6 From the Printer menu, select your printer driver from the\r\nInstalled Printers list and select the Configure button. \r\n\r\n7 Highlight the redirected port from your choices (LPT2 or\r\nLPT3). \r\n\r\n8 From the Printer Configuration window, set the timeouts of\r\nDevice Not Selected to 900 and Transmission Retry Timeout to 950." }