PATHWORKS for DOS Version 4.1A Release Notes August 1992 Software Version: PATHWORKS for DOS Version 4.1A Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ First Published, September 1991 Revised, August 1992 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1992. All rights reserved. _________________________________________________________________ Contents 1 Introduction 1.1 What Is Included in This Release................. 1-1 1.2 How to Use These Release Notes................... 1-3 2 Installing the PATHWORKS for DOS Version 4.1A Update 2.1 Installation Procedure........................... 2-2 2.2 Next Steps....................................... 2-5 3 Procedures for Token Ring Configuration 3.1 Required Software and Hardware................... 3-5 3.2 Network Configuration Guidelines................. 3-5 3.3 Using Routers.................................... 3-6 3.3.1 Choosing Bilingual or Phase IV Prime Routing ............................................... 3-6 3.3.2 Setting the MS-NET Flag ....................... 3-7 3.4 Configuring Users' PCs........................... 3-7 3.4.1 Basic PC Configuration ....................... 3-8 3.4.2 Additional Configuration for Microsoft Windows and Memory Managers ........................... 3-10 3.5 Configuring the PC for DLC Driver Support ....... 3-11 3.5.1 Prerequisites: Installing the DLC Drivers ..... 3-11 3.5.2 Setting Up DLC Driver Support ................. 3-13 3.5.3 Additional Configuration for DLC Driver Support with NetWare Coexistence ...................... 3-16 3.6 Setting Up Concurrent Support for DECnet and IBM NetBEUI.......................................... 3-17 3.7 Setting the MAC Address.......................... 3-18 3.7.1 Determining the DECnet Phase IV MAC Address ... 3-19 iii 3.7.2 Configuring the PC for MAC Addresses .......... 3-19 3.7.2.1 Configuring the PC for MAC Addresses with NDIS Drivers................................ 3-20 3.7.2.2 Configuring the PC for MAC Addresses with DLC Drivers................................. 3-20 3.8 Alternate Configurations......................... 3-20 3.8.1 Configuring the PC for Phase IV ............... 3-21 3.8.2 Configuring for Source Routing Environments ... 3-22 3.9 Troubleshooting Tips............................. 3-22 3.9.1 Using the PERMIT Command With NetBEUI ......... 3-22 3.9.2 Eliminating Address Conflicts ................. 3-23 3.9.3 System Reboots or Hangs During Heavy Network Activity....................................... 3-24 3.9.4 Failure when Booting a PC ..................... 3-25 3.9.5 Error When Booting a PC ....................... 3-25 3.9.6 Failure with Third-Party Applications ......... 3-25 3.9.7 Problems Using PC DECwindows .................. 3-26 4 Changes in PATHWORKS for DOS Version 4.1A Update 4.1 New Procedures................................... 4-1 4.1.1 Changing an Expired Password .................. 4-1 4.1.2 Using File Names Starting with "-" ............ 4-2 4.1.3 Using File Names Starting with "DIR" .......... 4-2 4.1.4 Using PATHWORKS Mail .......................... 4-2 4.1.5 Setting Up a Local Area Transport (LAT) Print Service on a PATHWORKS for ULTRIX Server....... 4-5 4.1.5.1 Step 1: Use LATCP to Share a Print Service.. 4-5 4.1.5.2 Step 2: Verify the Print Service............ 4-8 4.1.5.3 Step 3: Set Up an ULTRIX Print Queue........ 4-8 4.1.5.4 Step 3a: Check LAT Ports.................... 4-9 4.1.5.5 Step 3b: Create LAT Ports................... 4-9 4.1.5.6 Configure LAT Ports......................... 4-10 4.1.5.7 Autostart the LAT........................... 4-10 4.1.5.8 Run the lprsetup Utility.................... 4-10 4.1.5.9 Verify the LAT Printer Setup................ 4-12 4.1.5.10 Step 4: Add a Print Service with the Manager Menu........................................ 4-12 4.1.5.11 Step 5: Connecting to a Shared Printer...... 4-13 4.2 Problems Using PATHWORKS for DOS Version 4.1A Update........................................... 4-13 4.2.1 Creating Files in Another User's Account ...... 4-13 iv 4.2.2 Copying Short Files Using the Enhanced Redirector..................................... 4-14 4.2.3 Problems Using the VT320 Terminal Emulator with LAT............................................ 4-14 4.2.4 Problems Running PATHWORKS MAIL ............... 4-14 4.2.5 Creating a Root Directory on a Network Drive .. 4-15 4.3 Documentation Changes............................ 4-15 4.3.1 Choosing Between Basic Redirector and Full or Enhanced LAN Manager Redirector................ 4-15 4.3.2 Printing with the LAN Manager Full Redirector ............................................... 4-16 4.3.3 Correction to NET PRINT Command ............... 4-16 4.3.4 Getting Help for Network Services ............. 4-16 4.3.5 InfoServer (CD-ROM) Support ................... 4-17 A Trademarks Tables 2-1 Steps in Installing PATHWORKS for DOS Version 4.1A Update.................................... 2-1 3-1 Procedures for Token Ring Configuration ....... 3-2 3-2 Required Hardware and Associated Software ..... 3-5 3-3 Controller Files .............................. 3-12 3-4 Commands to Enter in the CONFIG.SYS File ...... 3-14 3-5 Parameters and Default Addresses ............. 3-24 4-1 Length Limitations in Enhanced and Full Redirectors.................................... 4-16 v 1 _________________________________________________________________ Introduction 1.1 What Is Included in This Release The PATHWORKS for DOS Version 4.1A Update includes: o Support for source routing over Token Ring networks. With source routing, clients and servers can communicate in configurations spanning multiple rings connected by source routing bridges. o Support for arbitrary MAC addresses for end nodes, which are required by some applications running in an IBM environment. To use MAC addresses, you need the changes to DECnet called DECnet Phase IV Prime included in this release. o A datalink interface for DECnet communications over DLC drivers, which are supplied by the IBM PC LAN Support Program in a Token Ring environment. DLC device drivers are required for some IBM applications, such as 3270 terminal emulators, and communications over IBM NetBEUI on a Token Ring network. For example, a PATHWORKS for DOS client can use DECnet to access PATHWORKS for VMS services, while also using the PC LAN Support Program over IBM NetBEUI on Token Ring to access an IBM LAN server. ________________________ Note ________________________ Token Ring networks do not support the Local Area Transport (LAT), Local Area System Transport (LAST), and Local Area Disk (LAD) or disk services. Token Ring networks are not supported with a PATHWORKS for ULTRIX server. ______________________________________________________ o Fixes to known problems in PATHWORKS for DOS Version 4.0. Introduction 1-1 1.2 How to Use These Release Notes This section summarizes the steps you must take to install and configure the PATHWORKS for DOS Version 4.1A Update software: ________________________ Note ________________________ To ensure that the components are correctly installed, you must read and follow all the steps in the release notes. ______________________________________________________ 1. Read the release notes before installing any components. 2. Install PATHWORKS for DOS Version 4.1A Update. See Chapter 2. 3. Configure for Token Ring support (see Chapter 3) for any of the following features: o Source routing o DECnet Phase IV Prime o DLC drivers 1-2 Introduction 2 _________________________________________________________________ Installing the PATHWORKS for DOS Version 4.1A Update Table 2-1 describes the steps you must follow to install PATHWORKS for DOS Version 4.1A Update: Table 2-1 Steps in Installing PATHWORKS for DOS Version 4.1A Update Follow these steps: And read: 1. Install PATHWORKS for DOS The appropriate client Version 4.1 if not already installation and configuration installed. guide for your server. 2. Make an initial PC-server The appropriate client connection. installation and configuration guide for your server. 3. Install the PATHWORKS for Section 2.1 DOS Version 4.1A Update. Installing the PATHWORKS for DOS Version 4.1A Update 2-1 2.1 Installation Procedure This section describes the installation procedure for PATHWORKS for DOS Version 4.1A Update. The installation procedure updates the system file service and each of the diskettes you received with PATHWORKS for DOS Version 4.1. The installation procedure copies the following files to the system file service: o \R_NOTES.TXT o \DECNET\NCPLOOP.EXE o \DECNET\NCPSHOW.EXE o \DECNET\DNNETH.EXE o \DECNET\DNETWIK.V41 o \DECNET\DNETOMO.V41 o \DECNET\DNETHLP.V41 o \DEBUG\DDNETH.EXE o \DEBUG\DTP.EXE o \LMDOS\DRIVERS\PCSA\DLLNDIS.EXE o \LMDOS\DRIVERS\PCSA\DLLNDIST.EXE o \LMDOS\DRIVERS\PCSA\DLLDLC.EXE o \LMDOS\DRIVERS\PCSA\EMSLOAD.EXE o \LMDOS\DRIVERS\PCSA\LAST.EXE o \LMDOS\DRIVERS\PCSA\SRM.EXE o \PCAPP\LDU.EXE o \PCAPP\NETSHLP.V41 o \PCAPP\NETSETUP.EXE o \TCPIP\TCPIPOMO.V41 2-2 Installing the PATHWORKS for DOS Version 4.1A Update To install PATHWORKS for DOS Version 4.1A Update: 1. If you are configuring a PC on the network for the first time, you need to make an initial connection between the PC and the server. Read the appropriate client installation and configuration guide for your server. 2. Install PATHWORKS for DOS Version 4.1 if not already installed as described in the appropriate client installation and configuration guide for your server. 3. Make a copy of each of the original diskettes. 4. Connect to the system file service using a privileged account by entering: C:\> USE ?: \\SRVR1\PCSAV41%SYSTEM * The following display indicates which drive (for example, L) is connected to the system service called PCSAV41: Status Dev Type Connection Name Mode Size ------ --- ---- ------------------------------- ------ ---- L: FILE \\SRVR1\PCSAV41%SYSTEM 5. Insert the PWRKS for DOS V4.1A UPDATE 1/x diskette into the diskette drive. 6. Set the default drive to the diskette drive, for example A: A:\> 7. Run the install program by entering: A:\> INSTALL 8. Answer the prompts. 9. Insert each diskette when prompted for it. 10.Remove the PWRKS for DOS V4.1A diskette from the diskette drive. Since the correct files are installed, ignore the following warning, if present: Warning B:\DDNETH.EXE not present copying M:\DEBUG\DDNETH.EXE to B:\DDNETH.EXE Installing the PATHWORKS for DOS Version 4.1A Update 2-3 11.If you install PATHWORKS for DOS (TCP/IP) V2.0 after having installed PATHWORKS for DOS Version 4.1A: a. Find the TCPIPOMO.V41 file on one of the PWRKS FOR DOS 4.1A UPDATE diskettes and insert that diskette in the drive. b. Copy the file to the PATHWORKS for DOS Version 4.1A system service, substituting "x" for the system service drive: C:\>COPY A:\TCPIPOMO.V41 x:\TCPIP\TCPIPOMO.V41 2.2 Next Steps You are ready to do the following: o If you are using the Token Ring features included in this release, read Chapter 3. o Otherwise, run Netsetup as described in the appropriate client installation and configuration guide for your server. Installing the PATHWORKS for DOS Version 4.1A Update 2-4 3 _________________________________________________________________ Procedures for Token Ring Configuration The DECnet Phase IV Prime architecture, designed for use in a Token Ring environment only, is a modification to the standard DECnet Phase IV architecture. It enables a DECnet node to use an arbitrary Media Access Control (MAC) address format instead of a Phase IV DECnet station address. A DECnet station address starts with AA-00-04-00; the full address has the format AA-00-04-00-XX-YY. An arbitrary MAC address can be either: - The hardware address, also known as the universally administered address - A MAC address determined by the user, also known as a locally administered address MAC addresses are often addresses that start with 40-00, in the format 40-00-XX-XX-XX-XX. Section 3.7 describes this feature in more detail. Procedures for Token Ring Configuration 3-1 Table 3-1 describes the steps you must follow to configure a PC for source routing and DECnet Phase IV Prime in a Token Ring network. Table_3-1_Procedures_for_Token_Ring_Configuration__________ Follow these steps: And read: 1. Check for required software and Section 3.1 in hardware. this chapter. 2. Follow the network configuration Section 3.2 in guidelines, including all this chapter. restrictions. 3. If you are using a router other than Section 3.3.2 a Proteon router, set the MS-NET in this chapter. flag. 4. If you are using a Proteon router: a. Choose bilingual or Phase IV Prime Section 3.3.1 routing. in this chapter. b. Set the MS-NET flag. Section 3.3.2 in this chapter. (continued on next page) 3-2 Procedures for Token Ring Configuration Table_3-1_(Cont.)_Procedures_for_Token_Ring_Configuration__ Follow these steps: And read: c. Set up the Proteon router. Proteon Bridging Router Configuration Guide and Proteon Bridging Router Reference Guide. 5. Configure the PC for use in Token Section 3.4 and Ring networks. Section 3.4.1 in this chapter. 6. Configure the PC for Microsoft Section 3.4.2 Windows and memory managers, if in this chapter. desired. 7. Configure the PC for DLC driver Section 3.5, support: Section 3.5.1, and Section 3.5.2 in this chapter. o With NetWare Coexistence Section 3.5.3 in this chapter. o With concurrent access to IBM Section 3.6 in NetBEUI this chapter. (continued on next page) Procedures for Token Ring Configuration 3-3 Table_3-1_(Cont.)_Procedures_for_Token_Ring_Configuration__ Follow these steps: And read: 8. Set the MAC address if desired: Section 3.7, Section 3.7.1, and Section 3.7.2 in this chapter. o With NDIS drivers Section 3.7.2.1 in this chapter. o With DLC drivers Section 3.7.2.2 in this chapter. ___________________________________________________________ Alternate configurations are discussed in Section 3.8. Troubleshooting tips are discussed in Section 3.9. 3-4 Procedures for Token Ring Configuration 3.1 Required Software and Hardware Before configuring the PC for a Token Ring network, you must install the following software: o VMS Version 5.5, installed on the server o DECnet Token Ring Network Device Driver for VMS Version 1.1, and DECnet-VAX Phase IV Prime o PATHWORKS for VMS Version 4.1-1, installed on the server o PATHWORKS for DOS Version 4.1, installed on the server o Upgrades for any other PATHWORKS products you are running, such as PATHWORKS for OS/2 Version 2.0A In addition, if you purchase this release with the hardware components, make sure to install the corresponding software, listed in Table 3-2. Table_3-2_Required_Hardware_and_Associated_Software________ Hardware Software Proteon 4100+ Multi R12.1 Protocol Bridging Router Proteon CNX500 Multi R12.1 Protocol Bridging Router DEC TRNcontroller 100 DEC Token Ring Network Device Driver for VMS Version 1.1 (TRDRIVER.EXE) 3.2 Network Configuration Guidelines You need to observe the following restrictions when you configure a Token Ring network. o In the absence of a bilingual DECnet router on the Token Ring network, DECnet Phase IV and Phase IV Prime systems cannot communicate. o By default, Proteon controllers (Network Integration Controllers (NICs) use DMA channel 5. DECpc's with a SCSI hard disk controller also use DMA channel 5. If you are using a Proteon controller in a DECpc with a Procedures for Token Ring Configuration 3-5 SCSI controller, you must select a different Proteon DMA channel for the Proteon NIC. o If the network has a bridge that transmits data between a Token Ring network and an Ethernet network and a VMS system is running on the Ethernet, you also need to use a router that handles DECnet traffic. If a bridge is also used in parallel, it must filter out the DECnet protocol messages that the routers are routing. For example, if you use an IBM 8209 bridge, you also need a Proteon router. If DECnet Token Ring Phase IV Prime packets are not blocked in such a bridge, then DECnet may fail on that portion of the network. To avoid these problems, you need to upgrade all the VMS systems on the Ethernet to VMS Version 5.5 and higher, regardless of whether they use the Token Ring network. Next Steps If using a router, proceed to Section 3.3. If not using a router, proceed to Section 3.4. 3.3 Using Routers If using a Proteon router, read Section 3.3.1 and Section 3.3.2. For all routers, read Section 3.3.2. 3.3.1 Choosing Bilingual or Phase IV Prime Routing When you set up a router to be used on the Token Ring network, you can select bilingual or Phase IV Prime architecture: o Choose bilingual routing if some nodes use Phase IV and others use Phase IV Prime on the Token Ring. The Proteon router, for example, converts arbitrary MAC addresses (Phase IV Prime) to Phase IV DECnet station addresses. 3-6 Procedures for Token Ring Configuration ________________________ Note ________________________ A configuration with Phase IV nodes is supported as a migration path only until all nodes are configured to run Phase IV Prime. ______________________________________________________ o Choose Phase IV Prime if all nodes on the Token Ring network use Phase IV Prime. 3.3.2 Setting the MS-NET Flag If you are using a router to connect a client on the Token Ring to a server on the Ethernet, you need to define that server on the client with the MS-NET flag. At the client, enter the following command to define the server: M:\> NCP DEF NODE nodenumber NAME server MS-NET For more information, see the DECnet Network Management Guide. Next Steps You are ready to configure users' PCs. Proceed to Section 3.4. 3.4 Configuring Users' PCs To use any of the Token Ring capabilities, including DLC driver support, in this release, you need to update the user's configuration. Follow the steps in this section for: o The basic PC configuration o Additional configuration for Microsoft Windows and memory managers Procedures for Token Ring Configuration 3-7 3.4.1 Basic PC Configuration To configure a user's PC: 1. If you are using a Proteon controller, copy the Proteon microcode file PRORAPM.DWN to the \DECNET directory of the PC boot device: COPY A:\PRORAPM.DWN C:\DECNET\PRORAPM.DWN 2. Boot the user's PC and confirm that the PC is running PATHWORKS for DOS Version 4.1 (the version number is displayed on the screen when the PC boots). 3. Run the Netsetup utility by entering: A:\> NETSETUP 4. In the Netsetup utility, choose the following options: a. Choose either DECnet or TCP/IP: o Select DECnet if you are configuring for DLC driver support. o Select DECnet or TCP/IP for NDIS driver support. b. Choose local boot. c. Choose the destination boot device for the PC. d. Choose Token Ring for the network adapter type. e. In the Token Ring Network Adapter Type screen: o If you have an IBM, 3COM, or Compaq Network Integration Card (NIC), choose the "Full LAN Manager NDIS" option. o If you have another Network Integration Card (NIC), such as a Proteon Token Ring controller: a. Choose the "Other NDIS" option. b. At the prompt, enter the drive and path of the NDIS driver and a PROTOCOL.INI stub file. 3-8 Procedures for Token Ring Configuration o If you are configuring for a DLC driver, choose one of the following: - LAN Manager supplied NDIS - Other NDIS ________________________ Note ________________________ Do not select Other DLC at this time. ______________________________________________________ Both NDIS options let you configure a basic key diskette the first time. f. Choose support for source routing if your LAN is connected by source routing bridges. g. Select a redirector: o If you are not configuring for DLC support, choose Basic redirector. o If you are configuring for DLC support without IBM NetBEUI, choose Basic redirector. o If you plan to configure the PC for DLC driver support so the PC can concurrently access PATHWORKS servers over DECnet and IBM LAN servers over IBM NetBEUI, choose support for one of the following: - Enhanced Redirector - Full LAN Manager 2.0 Note that the Enhanced and Full LAN Manager 2.0 include the same redirector, which limits the length of service names (sharenames), user names and passwords, as follows: _____________________________________________________ Name Maximum_Length Service name 8 characters plus a 3-character extension. For example, MYFILE12.EXE User name 12 characters Password 8 characters 5. Write the key diskette. Procedures for Token Ring Configuration 3-9 6. Exit the Netsetup utility. 7. If you are using a Madge Token Ring controller, add the following parameter to the Madge controller section of the PROTOCOL.INI file in the \DECNET directory on the PC boot drive: AUTOOPEN = NO 8. If you are using Microsoft Windows and memory managers, follow the directions in Section 3.4.2. 9. If you are setting up support for DLC drivers, follow the directions in Section 3.5. 10.If you are setting up support for DLC drivers with concurrent access to DECnet and IBM NetBEUI, follow the directions in Section 3.5 and Section 3.6. 11.Reboot the PC. 3.4.2 Additional Configuration for Microsoft Windows and Memory Managers If you are using Microsoft Windows with a memory manager over a Token Ring network, you need to make the following changes to your configuration: o For non-IBM Token Ring controllers: 1. Set the TokenRingSearch parameter in the [386Enh] section of the \WINDOWS\SYSTEM.INI file to FALSE. 2. If you are using an EMS emulator, do one of the following: - If you are using a QEMM EMS emulator, set the NTR parameter on the QEMM command line in the CONFIG.SYS file. - If you are using another EMS emulator, you may require other switches to work with non-IBM controllers. Consult the emulator documentation for these switches. o For IBM Token Ring controllers: If you are using the Microsoft Windows or EMS memory maps, exclude the area between C000 and DFFF. 3-10 Procedures for Token Ring Configuration 3.5 Configuring the PC for DLC Driver Support You need to configure a PC for DLC driver support, which is required for some IBM applications, such as 3270 terminal emulators, and communications over IBM NetBEUI. This section describes: o Prerequisites o Setting up DLC driver support o Additional configuration for DLC driver support with NetWare Coexistence ________________________ Note ________________________ You must run Netsetup twice to configure your PC for DLC driver support: 1. As described in Section 3.4.1, run Netsetup to configure the PC. 2. Boot the PC using the key disk created in the step 1, then run Netsetup a second time to install the DLC driver, as described in the following sections. ______________________________________________________ 3.5.1 Prerequisites: Installing the DLC Drivers Before setting up DLC support: 1. Make sure you have run the Netsetup utility as described in Section 3.4. 2. Determine the drive and path to which you want to install the DLC drivers. The drive must be a local drive, for example, C. 3. Copy the DLC drivers that support the IEEE 802.5 (Token Ring) interface to a common subdirectory (for example, C:\DECNET). Copy the files listed in Table 3-3, depending on the controller type, to the common subdirectory. Procedures for Token Ring Configuration 3-11 Table_3-3_Controller_Files_________________________________ For this controller: Copy: From: IBM Token Ring DXMA0MOD.SYS IBM PC LAN Support Program diskette DXMC0MOD.SYS IBM PC LAN Support Program diskette Proteon DXMA0MOD.SYS IBM PC LAN Support Program diskette CFGP139X.SYS Proteon diskette PRO16EUI.SYS Proteon diskette PROLLC.OUT Proteon diskette Other DLC drivers[1] Controller distribution diskette DXMA0MOD.SYS IBM PC LAN Support Program diskette [1] For the names of the drivers, refer to the installation guide for the controller. DLC drivers are usually on the distribution diskette for the controller. ___________________________________________________________ 4. If you plan to use the IBM PC LAN Support Program to access the IBM LAN servers over IBM NetBEUI, copy the DXMT0MOD.SYS driver on the IBM PC LAN Support Program diskette to the common directory. 3-12 Procedures for Token Ring Configuration 3.5.2 Setting Up DLC Driver Support Follow the directions in this section for DLC driver support and access to IBM NetBEUI. To configure the system to use the DLC drivers instead of the NDIS drivers that come with PATHWORKS for DOS, complete the following steps: ________________________ Note ________________________ Throughout this procedure: o Drive C refers to the device that boots the PC. o C:\DECNET refers to the common directory for the drivers. Depending on your PC configuration, you may need to substitute another drive and directory. ______________________________________________________ 1. Edit the CONFIG.SYS file, which should be in the root directory of the PC's boot device. a. Delete the following lines: DEVICE=C:\DECNET\PROTMAN.SYS DEVICE=C:\DECNET\IBMTOK.DOS ________________________ Note ________________________ In your file, the ends of these lines may include command line switches. Also, if you use a driver other than IBMTOK.DOS, the driver name in the second of these lines corresponds to that driver. ______________________________________________________ b. After these lines, add the lines shown in Table 3-4, depending on the controller you use. Be sure to enter the lines in the order listed in the table. Procedures for Token Ring Configuration 3-13 Table_3-4_Commands_to_Enter_in_the_CONFIG.SYS_File_________ For this controller: Enter these lines: IBM Token Ring DEVICE=C:\DECNET\DXMA0MOD.SYS [1 ] DEVICE=C:\DECNET\DXMC0MOD.SYS [2 ] Proteon DEVICE=C:\DECNET\DXMA0MOD.SYS [1 ] DEVICE=C:\DECNET\CFGP139X.SYS [3 ] DEVICE=C:\DECNET\PRO16EUI.SYS Other DEVICE=C:\DECNET\DXMA0MOD.SYS DEVICE=C:\DECNET\third_party_driver.sys [4] [1]Entry for the interrupt arbitrator device driver [2]Entry for the adapter device driver [3]You can include switches for any settings you have changed. Consult the controller installation guide for the meanings of specific switches. [4]Substitute the name of the driver. ___________________________________________________________ c. For concurrent access to DECnet and IBM NetBEUI, add the following lines after the line with the DXMC0MOD.SYS (or equivalent) entry: device=C:\DECNET\DXMT0MOD.SYS ES=3 S=12 C=14 S=12 FCBS=16,8 2. For concurrent access to DECnet and IBM NetBEUI, make sure you have already run the Netsetup utility to configure the PC for the Enhanced Redirector or Full LAN Manager support. See Section 3.4 for instructions. 3. Run the Netsetup utility a second time (you should have already run the utility once as described in Section 3.4). The Netsetup utility sets the LG_BUFFERS and HEURISTICS parameters in the PROTOCOL.INI file, which are required for PATHWORKS support for DLC drivers. 3-14 Procedures for Token Ring Configuration ________________________ Note ________________________ Do not reset these parameters if you have already used Netsetup to configure the PC for DLC driver support. ______________________________________________________ a. Make sure you are running the Netsetup utility in the PATHWORKS for DOS Version 4.1 system service, not the PATHWORKS for DOS Version 4.1A Update UPDATE diskettes. b. After you enter the destination drive letter, load the existing profile as prompted. ________________________ Note ________________________ Be sure to use the existing profile by pressing at the prompt. This saves the network connection information created the first time you ran Netsetup. Do not press . ______________________________________________________ If you do not have a profile on that drive, you need to find the drive that stores the profile you created when you ran Netsetup. c. At the Workstation Profile screen, move the cursor to the Network Adapter field and choose DLC drivers. 4. Write the key diskette. 5. Exit Netsetup. 6. If you are using NetWare Coexistence, go to Section 3.5.3. 7. For concurrent access to DECnet and IBM NetBEUI, go to Section 3.6. 8. Reboot the PC. Procedures for Token Ring Configuration 3-15 3.5.3 Additional Configuration for DLC Driver Support with NetWare Coexistence If you are running Netware Coexistence and have configured your PC for DLC driver support, you need to to create a IPX.COM file for DLC drivers. NetWare requires this file for the IBM PC LAN Support Program. The IPX.COM file that comes with NetWare Coexistence is for NDIS drivers, not DLC drivers. Create IPX.COM files as follows: 1. Make a backup of the original IPX.COM file to IPX_ NDIS.COM. x:\NETWARE> COPY x:\NETWARE\IPX.COM x:\NETWARE\IPX_NDIS.COM 2. Insert the Novell Wsgen diskette into the diskette drive. 3. Run WSGEN. 4. From the drivers menu, select IBM PC LAN Support Program driver. WSGEN creates an IPX.COM for DLC drivers. 5. Exit WSGEN. 6. Copy the new IPX.COM file from the Wsgen diskette in drive A to the system service so all PCs can use the file. Enter the following command, substituting the system service drive for x: C:\> COPY A:\IPX.COM x:\NETWARE\IPX.COM 7. Remove the Wsgen diskette from the diskette drive. 8. If you are running NetWare Coexistence and have configured some PCs for DLC driver support and others for NDIS driver support, you now have two IPX.COM files, one for DLC drivers, and one for NDIS drivers: o IPX.COM for DLC drivers o IPX_NDIS.COM for NDIS drivers When you run Netsetup, it copies the IPX.COM file from the NETWARE directory to the PC. 3-16 Procedures for Token Ring Configuration 9. If a PC has an NDIS driver, copy IPX_NDIS.COM from the system service to the DECNET directory on the PC (after running Netsetup): C:\> COPY X:\NETWARE\IPX_NDIS.COM C:\DECNET\IPX.COM 10.Reboot the PC. 3.6 Setting Up Concurrent Support for DECnet and IBM NetBEUI You can optionally set up DLC driver support so the PC can concurrently access: o PATHWORKS for VMS or OS/2 servers over DECnet o IBM LAN servers over IBM NetBEUI To set up this concurrent support: 1. Make a backup of the original STARTNET.BAT file, located in the \DECNET directory on the PC boot drive, to STARTNET.OLD. 2. In the STARTNET.BAT file, change the line with the DNNETH.EXE entry to read: %BOOT%\DNNETH.EXE /rem:2 /LANA:1 /I2A:N This command tells DECnet to use the LAN adapter (LANA) number 1 and disables interrupt 2A, which is the alternate DOS interrupt used to access NETBIOS. 3. Configure LAN Manager to use both the DECnet NETBIOS and IBM NetBEUI interfaces. In the LANMAN.INI file in the \LMDOS directory of the PC boot drive, change the wrknets parameter in the [WORKSTATION] section to the following: wrknets=0,1 Where: Parameter Represents 0 IBM NetBEUI 1 DECnet Procedures for Token Ring Configuration 3-17 ________________________ Note ________________________ The order of the numbers is the order in which the stacks are accessed. If you want the DECnet NETBIOS stack accessed first, reverse the order of the numbers to 1,0. ______________________________________________________ 4. Copy the STARTNET.BAT file and rename it to another file, for example, STARTNET.NB. If you run the Netsetup utility in the future, Netsetup creates a new STARTNET.BAT file and ignores the changes you just made. STARTNET.NB serves as a record of these changes so you can make them easily again. 5. Reboot the PC. 3.7 Setting the MAC Address You need to set the MAC address (or station address), which uniquely identifies your computer on the network, if: - Your administrator wants you to use a locally administered address - The PC is configured for Phase IV and one of the following: o An NDIS or DLC driver does not support the SetStationAddress function o Concurrent support for DECnet and IBM NetBEUI To set the MAC address: 1. Determine the MAC address as described in Section 3.7.1. 2. Configure the PC for the MAC address as described in Section 3.7.2. 3-18 Procedures for Token Ring Configuration 3.7.1 Determining the DECnet Phase IV MAC Address To determine the MAC address, you need the DECnet address for your PC. Suppose the DECnet address of your workstation is 12.34. Convert the DECnet address to the MAC address as follows: 1. Use the following formula: (12 * 1024) + 34 = 12322 or 3022H (Hex) 2. 3022H is byte-swapped to become 22-30. 3. Use the station address format AA-00-04-00-XX-YY, substituting the byte-swapped address for XX-YY. In this example, the station address for the PC is AA- 00-04-00-22-30. 4. When you use a Token Ring adapter, you must swap the bits of the DECnet station address. Reverse the order of the most significant bit and least significant bit. For example, to bit swap the station address for the PC: AA--00--04--00--22--30 The address becomes in binary: 10101010--00000000--00000100--00000000--00100010--00110000 When you swap bits, the address becomes: 01010101--00000000--00100000--00000000--01000100--00001100 And in hex, the address becomes: 55--00--20--00--44--0C 3.7.2 Configuring the PC for MAC Addresses This section describes how to configure the PC to use MAC addresses for: o NDIS drivers o DLC drivers Procedures for Token Ring Configuration 3-19 3.7.2.1 Configuring the PC for MAC Addresses with NDIS Drivers To configure the PC for MAC addresses and NDIS drivers, include the address in the PROTOCOL.INI file as follows: 1. Using the installation guide for the Network Interface Controller (NIC), determine the keyword that sets the MAC address. For example, IBM Token Ring drivers use the NETADDRESS keyword. 2. In the PROTOCOL.INI file, find the section that identifies the Token Ring driver, for example IBMTOK.DOS. In that section, insert the NETADDRESS (or equivalent) keyword and the bit-swapped address as shown: [IBMTOK.DOS] DRIVERNAME = IBMTOK$ MAXTRANSMITS = 16 NETADDRESS = "550020001234" Refer to the NIC installation guide for the command syntax. 3.7.2.2 Configuring the PC for MAC Addresses with DLC Drivers To configure the PC for MAC addresses and DLC drivers, include the address in the CONFIG.SYS file as follows: 1. In the CONFIG.SYS file, find the device command for the Token Ring driver, for example, DEVICE=DXMC0MOD.SYS. 2. At the end of the line, insert the bit-swapped address, as follows: DEVICE=DXMA0MOD.SYS DEVICE=DXMC0MOD.SYS 550020001234 3.8 Alternate Configurations You need to change the PC configuration in either of the following circumstances: o You need to configure the PC for Phase IV Prime support because you are not using a bilingual router and you have both Phase IV and Phase IV Prime nodes on the network; or because your network has a router that routes DECnet traffic to the Ethernet. 3-20 Procedures for Token Ring Configuration o You are inserting a source routing bridge between the PC and another node on the network. 3.8.1 Configuring the PC for Phase IV You need to set up Phase IV support if: o Some nodes on the Token Ring are running Phase IV because they have not been fully updated and you are not using a router that supports Phase IV Prime o You are using a bridge configured to handle DECnet traffic to connect to the Ethernet ________________________ Note ________________________ Phase IV configuration is supported as a migration path only until all nodes are running Phase IV Prime. ______________________________________________________ You need to set a parameter in the PROTOCOL.INI file, which is used to pass parameters for both NDIS and DLC clients. To set up the client for DECnet Phase IV support: 1. Determine if there is a HEURISTICS value in the [DATALINK] section of the PROTOCOL.INI file (located in the \DECNET directory of the PC boot device): o If there is, modify the value for the HEURISTICS parameter to be 32 more than the value in the file. For example, if the original HEURISTICS value is 16, enter the following as shown: HEURISTICS=48 o If there is not, insert a value of 32 as shown: HEURISTICS=32 2. Edit the STARTNET.BAT file in the \DECNET directory of the PC boot drive to include the /rem:2 and /P4P:N switches for the DECnet driver: %BOOT%\DECNET\DNNETH.EXE /rem:2 /P4P:N 3. Reboot the PC. Procedures for Token Ring Configuration 3-21 3.8.2 Configuring for Source Routing Environments If you are inserting a source routing bridge between your PC and another node you communicate with in the Token Ring network, you need to reconfigure your PC as follows: 1. Run the Netsetup utility and select source routing (See Section 3.4.) 2. Reboot the PC. If the PC is running NetWare Coexistence and is connected to the network by source routing bridges: 1. Run the Netsetup utility and select source routing as described in Section 3.4. 2. Run the NetWare program ROUTE. 3. Run any of the NetWare programs that corresponds to your DOS version, for example: NET3, NET4, NET5, or NETx. 4. Reboot the PC. 3.9 Troubleshooting Tips This section describes problems you may encounter when running in a Token Ring environment and hints on how to correct them. 3.9.1 Using the PERMIT Command With NetBEUI Cause: A client that is using both NetBEUI and DECnet transports with the PERMIT command cannot communicate to other clients using DECnet only. Action: Run the PERMIT command with the /N1 switch. For example, if you offer the service TOOLS from the MYTOOLS directory, enter: C:\> PERMIT TOOLS=C:\MYTOOLS /N1 * 3-22 Procedures for Token Ring Configuration For more information on the PERMIT command, see Client Commands Reference. 3.9.2 Eliminating Address Conflicts Cause: When a default functional address used by DECnet conflicts with a functional address used by other protocol stacks, certain utilities do not work. For example, if there is a NETBIOS address conflict, the USE utility does not work. Token Ring support in PATHWORKS is implemented as an emulation of Ethernet. The emulation maps the multicast addresses used on the Ethernet to functional addresses used on the Token Ring. Therefore, a limited number of addresses are available. Action: Eliminate the conflict by adding the address you want to change to the PROTOCOL.INI file. The functional addresses and their defaults are listed in Table 3-5. ________________________ Note ________________________ Unless you enter them, the PROTOCOL.INI file (located in the \DECNET directory of the PC boot drive) does not contain any functional addresses. ______________________________________________________ To change a functional address, add it to the [DATALINK] section of the PROTOCOL.INI file in the following format, without spaces in the address: parameter = "address" For example, to change the address for the ENDNODE parameter, enter: ENDNODE = "C00001000000" Reboot the PC. Procedures for Token Ring Configuration 3-23 Table 3-5 lists the parameters, their descriptions, and their defaults. Table_3-5_Parameters_and_Default_Addresses_______________________ Parameter Description Default Address ENDNODE DECnet end nodes C0 00 08 00 00 00 ROUTER Level 1 routers C0 00 10 00 00 00 NETBIOS PCSA NETBIOS C0 00 04 00 00 00 emulation MOP_DL MOP dump/load C0 00 40 00 00 00 assistance MOP_RC MOP remote console C0 00 20 00 00 00 LOOPBACK Loopback C0 00 00 10 00 00 PHIVP_ROUTER Phase IV Prime C0 00 10 00 00 00 routers PHIV_UNKDEST Phase IV Prime C0 00 08 00 00 00 unknown destination 3.9.3 System Reboots or Hangs During Heavy Network Activity Cause: If your PC reboots or hangs during heavy network activity, it may be due to stack overflow. Action: Correct this problem by: 1. Edit the CONFIG.SYS file in the root directory of the boot drive and increase the values for the STACKS= parameter. For example, if the STACKS= value is 0,0, change it to: STACKS= 9,256 3-24 Procedures for Token Ring Configuration 3.9.4 Failure when Booting a PC Cause: Several problems may prevent a node from using the Token Ring network, including: o Improper cabling o Duplicate addresses on the Token Ring o Incorrect interrupt request (IRQ) levels o Hardware errors These errors are reported as a "general failure" in the NETBIND program when you start your PC. Action: To determine which of these problems is the cause, run the diagnostics that come with your controller. 3.9.5 Error When Booting a PC Cause: If you previously configured the PC for LAN Manager 2.1 and reconfigure for PATHWORKS for DOS Version 4.1A Update, you get the following error when the PC boots: Error: datalink not initialized. Run NETBIND before sch Action: If you are not running LAN Manager 2.1 and the \DECNET directory has the NETBIND.COM and NETBIND.EXE files, delete the NETBIND.COM file from that directory. 3.9.6 Failure with Third-Party Applications Procedures for Token Ring Configuration 3-25 Cause: PATHWORKS for DOS Version 4.1A Update tries to open the adapter when it is already open by other applications. Errors of this type are reported as a "general failure" in the NETBIND program when you start your PC. Action: To correct this problem: 1. Add 128 to the current HEURISTICS value in the [DATALINK] section of the \DECNET\PROTOCOL.INI file. The HEURISTICS parameter prevents the NDIS driver from opening the adapter. For example, if the HEURISTICS value is 10, enter: HEURISTICS=138 If there is no HEURISTICS value, enter: HEURISTICS=128 2. Reboot the PC. 3.9.7 Problems Using PC DECwindows Cause: You may have are problems using PC DECwindows, such as poor performance or disappearing windows because you are running many DECwindows applications at the same time that are doing network I/O. Action: Correct this problem by: 1. Check the LDB allocation failures by entering: C\> NCP SHOW EXEC COUNTERS 2. If the display shows LDB failures: a. In the PROTOCOL.INI file, set the LG_BUFFERS parameter to 24. 3-26 Procedures for Token Ring Configuration b. Reduce the receive pipe quota to 3 by entering: C:\> NCP DEFINE EXEC RECEIVE PIPE QUOTA 3 ________________________ Note ________________________ If you rerun Netsetup, you need to reset these parameters. ______________________________________________________ Procedures for Token Ring Configuration 3-27 4 _________________________________________________________________ Changes in PATHWORKS for DOS Version 4.1A Update 4.1 New Procedures This section contains client procedures and commands that are new to PATHWORKS for DOS Version 4.1A Update. 4.1.1 Changing an Expired Password PATHWORKS for DOS clients can now change an expired password by using the NET PASSWORD command. To use this feature: 1. Make sure that PATHWORKS for VMS Version 4.1-1 is installed on the server. Follow the directions in the PATHWORKS for VMS Version 4.1-1 Release Notes to enable this feature. 2. Make sure that the client is running one of the following versions of LDU.EXE, which is required for the NET PASSWORD command: o LDU.EXE Version 4.1.8, or later o LDU.EXE Version 4.1.009 included in PATHWORKS for DOS Version 4.1A Find the LDU version number by entering: LDU If you installed PATHWORKS for DOS Version 4.1A, you have the correct LDU version. Changes in PATHWORKS for DOS Version 4.1A Update 4-1 4.1.2 Using File Names Starting with "-" If you are using a PATHWORKS for VMS Version 4.1-1 server, you can use DOS file names that start with a hyphen (-). These file names are translated to a VMS name starting with __2D. The DOS file name does not change. For example: DOS file name: _FILE1.DOC VMS file name: __2DFILE1.DOC This change affects only files that you create after you install PATHWORKS for VMS Version 4.1-1. For more information on file translation between the server and the client, see the User's Handbook. 4.1.3 Using File Names Starting with "DIR" If you use a PATHWORKS for VMS Version 4.1-1 server, you can now use DOS files with a .DIR extension (file type). the VMS operating system translates the DIR extension to .__DIR. The DOS file name does not change. For example: DOS file name: FILE1.DIR VMS file name: FILE1.__DIR This change affects only files that you create after you install PATHWORKS for VMS Version 4.1-1. For more information on file translation, see the User's Handbook. 4.1.4 Using PATHWORKS Mail Observe the following guidelines when using Mail: o FILE Command Omitted The FILE command was omitted from the manual. It works exactly like the MOVE command. o Printing Multiple Jobs You cannot print more than one message at a time. That is, the following command prints only the first message specified: Mail> PRINT 3,5 4-2 Changes in PATHWORKS for DOS Version 4.1A Update o Printing the Current Message The right-pointing cursor points to the current message. For example, assume the current message is 3. If you enter the following command, Mail prints message 3: Mail> PRINT 16 o Creating a Folder To create a new folder, either from the Browser or while reading a message, enter the following command: Mail> MOVE Mail prompts you to enter the name of the new folder. Enter the name and press the Return key. Because you used the MOVE command, Mail marks the file in the current folder as deleted. o Deleting a Folder You cannot delete a folder in Mail. However, you can delete all the files in a folder. After you exit Mail and then re-enter it, the folder will be gone. o Sending Mail - No MAIL.MAI Use the following procedure to send mail if there is no MAIL.MAI file on the server: 1. Run MAILSETU. 2. Change to the drive letter of you Mail server. For example, if you are on drive C and your Mail server is on drive I, enter the following: C:\> I: 3. Change to the PCAPP directory. For example: I:\> CD PCAPP 4. Enter the following command: I:\PCAPP> MAILSEND Mail displays the user name you defined in MAILSETU. For example: From: SERVR1::USER1 To: Changes in PATHWORKS for DOS Version 4.1A Update 4-3 5. Enter the server name and user name of the person to whom you want to send mail. For example: From: SERVR1::USER1 To: SERVR1::USER2 Enter message below, type control z and press return. After you press Ctrl/Z, Mail displays the following message: Sending mail to node SERVR1 -- connected USER2 -- ok o Scrolling When Replying to the Current Message When you reply to a message, Mail splits the screen with the original message in the top screen and your reply in the bottom screen. To scroll through the top screen, use Ctrl/Pg Up and Ctrl/Pg Dn. To scroll through the bottom screen, use Pg Up and Pg Dn. o Returning to the Browser If you are not in the Browser, and want to be there, enter the following: Mail> DIR NEWMAIL o Flagging and Marking Messages Mail allows you to flag or mark messages. Flagged messages: - Are highlighted in the Browser - Have an F in their message flag area - Can be copied, deleted, displayed, extracted, moved, printed, read, or undeleted as a group Marked messages: - Have an asterisk in their message flag area - Can be copied, deleted, displayed, extracted, moved, printed, read, or undeleted as a group 4-4 Changes in PATHWORKS for DOS Version 4.1A Update Basically, then, flagged messages are easier to see in the Browser. However, you can perform the same operation on flagged messages that you can perform on marked messages. 4.1.5 Setting Up a Local Area Transport (LAT) Print Service on a PATHWORKS for ULTRIX Server This section describes how to set up a printer attached to a PC client (called a parallel, or LAT, printer) as a shared print service on a network with a PATHWORKS for ULTRIX server. The PATHWORS for ULTRIX server is not supported on a Token Ring network. ________________________ Note ________________________ If your system runs ULTRIX Version 4.1 or higher, the following procedure supersedes the one described in the Client Installation and Configuration Guide for the ULTRIX Server. If your system runs ULTRIX Version 4.0 or lower, use the procedure described in Chapter 7 of the Client Installation and Configuration Guide for the ULTRIX Server with the following modification: When you specify the printer connection type as instructed in the section 'Add the Printer' in Chapter 7, enter "lat" in lowercase letters, not in capital letters. ______________________________________________________ 4.1.5.1 Step 1: Use LATCP to Share a Print Service Before you can share a printer in your group, the owner of the printer or the system administrator has to run LATCP to offer it as a LAT service: 1. Make sure that the printer is connected to the PC and the power is on. Changes in PATHWORKS for DOS Version 4.1A Update 4-5 2. Make sure that Version 4.1.17j (or higher) of LAT.EXE is installed on the PC by entering: C:\> LAT A message similar to the following is displayed: PATHWORKS for DOS LAT V4.1.17j If the version of LAT.EXE is lower than 4.1.17j, this procedure may not work. To obtain the most recent version of LAT.EXE, contact your Digital representative. 3. Delete or rename the \DECNET\DECLAT.DAT file. This ensures that the LATCP commands you enter in the following steps create a new \DECNET\DECLAT.DAT file. 4. At the client, start the LATCP utility by entering: C:\> LATCP LATCP> ________________________ Note ________________________ LATCP provides online help. To access help on any LATCP command, enter: LATCP> HELP ______________________________________________________ 5. Add the print service with the following command: LATCP> ADD LPTn service_name ________________________________________________________ Variable Description LPTn The port on the PC where the printer is attached service_name The name (which you supply) of the print service you are offering (for example, LA75) ________________________________________________________ For example, to add an LA75 printer attached to LPT1, enter: LATCP> ADD LPT1 LA75 4-6 Changes in PATHWORKS for DOS Version 4.1A Update By default, the print service does not require a password. To add a service password and learn about other ADD LPTn qualifiers, see the PATHWORKS for DOS Client Commands Reference. 6. Determine the server name of the PC by entering: LATCP> SHOW CHARACTERISTICS Record the server name, which is displayed in a format similar to LAT_AA00040018FD. You need this information to set up the ULTRIX print queue on the server. 7. In the LAT service table, add the name of the server where you plan to set up the print queue for the prefered service. The LAT service table stores a list of services offered on the network. To add a preferred service to the LAT service table, enter: LATCP> ADD node_address node_name service_name ________________________________________________________ Variable Value node_address The DECnet address of the server node offering the service node_name The name of the ULTRIX server offering the service service_name The LAT service name of the server ________________________________________________________ For example, to add the ULTRIX server ULTSRV with a node address of 9.811 and LAT service ULTSRV to the LAT service table, enter: LATCP> ADD 9.811 ULTSRV ULTSRV You can also enter the ADD command without arguments. The screen displays instructions on how to proceed. 8. To leave LATCP, enter: LATCP> EXIT Changes in PATHWORKS for DOS Version 4.1A Update 4-7 4.1.5.2 Step 2: Verify the Print Service To verify the service you just added: 1. Make sure you have exited LATCP. If the LATCP prompt is displayed, enter: LATCP> EXIT 2. Unload the LAT by entering: C:\> LAT /U 3. Reload the LAT by entering: C:\> LAT 4. Start LATCP by entering: C:\> LATCP 5. Verify the print service by entering: LATCP> SHOW PORTS A list of print services is displayed. Check the list for the new service you added. 6. Verify the preferred service that you just added by entering: LATCP> LIST A list of preferred services is displayed. Check the list for the new service you added. 7. To leave LATCP, enter: LATCP> EXIT For more information on LATCP commands, see the PATHWORKS for DOS Client Commands Reference. 4.1.5.3 Step 3: Set Up an ULTRIX Print Queue Before users can access the printer, you must set up the appropriate queues on the ULTRIX server. You must have ULTRIX system administrator privileges to do this task. 4-8 Changes in PATHWORKS for DOS Version 4.1A Update 4.1.5.4 Step 3a: Check LAT Ports Start by checking the LAT on your ULTRIX system: 1. Log in to the root account. 2. See whether the LAT is active by entering: # lcp -d If the resulting message indicates that the LAT is inactive, activate it by entering: # lcp -s 3. See whether the LAT ports are configured by entering: # file /dev/tty* | more If the LAT ports are configured, the resulting display includes lines like this: /dev/tty04: character special (39/4) LAT #0 terminal #4 4.1.5.5 Step 3b: Create LAT Ports If you do not have any LAT ports, you need to create some: 1. Change directories: # cd /dev 2. Create a port: # MAKEDEV lta 3. Check the tty numbers for your LAT ports by entering: # file /dev/tty* | more You see a display like this: /dev/tty00: character special (39/0) LAT #0 terminal #0 /dev/tty01: character special (39/1) LAT #0 terminal #1 /dev/tty02: character special (39/2) LAT #0 terminal #2 /dev/tty03: character special (39/3) LAT #0 terminal #3 /dev/tty04: character special (39/4) LAT #0 terminal #4 /dev/tty05: character special (39/5) LAT #0 terminal #5 /dev/tty06: character special (39/6) LAT #0 terminal #6 /dev/tty07: character special (39/7) LAT #0 terminal #7 Choose a LAT port to configure and write down the tty number displayed on your screen. Changes in PATHWORKS for DOS Version 4.1A Update 4-9 4.1.5.6 Configure LAT Ports Configure the LAT port as follows: 1. In the /etc/ttys file, change the tty parameters for the printer port as follows: tty## "/etc/getty 8bit.9600" vt100 off nomodem # LAT printer In place of tty##, use the tty number you chose when you create the LAT port (for example, tty04). 2. Exit the /etc/ttys file. 3. Start the LAT by entering: # lcp -h /dev/tty## # lcp -s In place of tty##, use the tty number you chose when you create the LAT port (for example, tty04). 4.1.5.7 Autostart the LAT You need to autostart the LAT each time you reboot. To do this, modify the existing LAT startup entry in the /etc /rc.local file as follows, or add these lines to the bottom of the file: if [ -f /etc/lcp]; then /etc/lcp -h /dev/tty## /etc/lcp -s && echo 'Starting LAT' >/dev/console fi In place of tty##, use the tty number you chose when you create the LAT port (for example, tty04). 4.1.5.8 Run the lprsetup Utility Now you are ready to create an ULTRIX printer queue using the lprsetup utility. However, lprsetup may not let you specify your exact printer type. In this case: 1. Create the printer queue using the Manager Menu. 2. Modify the queue using lprsetup and specify a new connection type (ct), terminal server name (ts), and output port (op) or output service (os) according to the guidelines described in step 4 of the following procedure. 4-10 Changes in PATHWORKS for DOS Version 4.1A Update For more information on using lprsetup, see the ULTRIX Guide to System and Network Setup and lprsetup(8) in the ULTRIX Reference Pages. To create the printer queue using lprsetup: 1. Log in to the root account. 2. Run lprsetup: # lprsetup 3. Enter add at the following prompt: Command < add modify delete exit view quit help >: add 4. Respond to the utility prompts as appropriate for your printer, or choose the defaults provided. For the following prompts, however, make sure that you use these specific responses: Set device pathname 'lp' [/dev/tty02] ? /dev/tty## In place of /dev/tty##, use the tty number you chose when you created the LAT port (for example, tty04). Set device connection type 'ct' [dev] ? lat Make sure that you enter lat in lowercase. If you use uppercase or mixed case, other symbols are set incorrectly. Set terminal server name 'ts' [] ? TERMINAL_SERVER In place of TERMINAL_SERVER, use the LAT server name you recorded in Step 1: Use LATCP to Share a Print Service. Make sure that you enter the LAT server name in uppercase letters (for example, LAT_AA00040018FD). Set terminal server output port 'op' [] ? LPTn If you use ULTRIX Version 4.2, press Return without supplying a response to this prompt. Changes in PATHWORKS for DOS Version 4.1A Update 4-11 If you use ULTRIX Version 4.1, you must respond with port on the PC where the printer is attached (for example, LPT1). You specified this port when you created the print service at the client in Step 1: Use LATCP to Share a Print Service. Set terminal server output service 'os' [] ? SERVICE_NAME If you use ULTRIX Version 4.1, press Return without supplying a response to this prompt. If you use ULTRIX Version 4.2, you must respond with the name of the service you specified in Step 1: Using LATCP to Share a Print Service. Make sure that you enter the service name in uppercase letters (for example, LA75). 4.1.5.9 Verify the LAT Printer Setup 1. Check the status of the LAT on your ULTRIX system by entering: # lcp -d 2. Check the status of the ULTRIX print queue by entering: # lpc status queue_name In place of queue_name, enter the name you supplied in lprsetup when you created the queue. 3. Check the setup by sending a text file to the printer: # lpr -Pqueue_name file_name 4.1.5.10 Step 4: Add a Print Service with the Manager Menu When you use lprsetup to add a local printer, lprsetup creates a print queue but not an associated print service. Now you are ready to use the Manager Menu to create an associated print service. For information on the Manager Menu, see the Server Administrator's Guide. 4-12 Changes in PATHWORKS for DOS Version 4.1A Update 4.1.5.11 Step 5: Connecting to a Shared Printer PC users connect to the shared printer with the USE command regardless of the operating system the client or server is running. For example: C:\> USE LPT1: \\ULTSRV\PRINT_SERVICE In this example, ULTSRV is the ULTRIX server where the PRINT_SERVICE service is offered. 4.2 Problems Using PATHWORKS for DOS Version 4.1A Update This section describes problems you may encounter using PATHWORKS for DOS Version 4.1A Update. 4.2.1 Creating Files in Another User's Account A DOS user User1 can connect to another user User2's VMS account. If User1 and User2 are part of the same UIC group, User1 can create a file in User2's account. However, assuming both users are in the same UIC group, files created from the PC follow different rules than if they were created directly from the VMS account. Consider the following example with User1 and User2 in the same UIC group: 1. Suppose User1's directory has the RMS protection (System:RWE;Owner:RWE; G:E;W:E). 2. User1 connects to User2's account. 3. The owner of the file is different depending on the platform User1 uses to connect to the account: ___________________________________________________________ Platform Used to Connect Who Owns File Created in User2's to VMS Account VMS Account VMS User2 PC User1 Changes in PATHWORKS for DOS Version 4.1A Update 4-13 4.2.2 Copying Short Files Using the Enhanced Redirector When using the Enhanced Redirector and copying a file of exactly 51 bytes from a VMS or ULTRIX server to a PC, the PC may get a network error or hang. To avoid this problem copying very small files, use the Basic Redirector instead. 4.2.3 Problems Using the VT320 Terminal Emulator with LAT If you are having problems using the Local Area Transport (LAT) and the VT320 terminal emulator, load only two VT320 sessions at the same time in the WIN.INI file. The WIN.INI file is in the same directory where Microsoft Windows is installed. For information on including commands in the WIN.INI file, see "Customizing Your VT320 Terminal Emulator Environment" in the PATHWORKS for DOS Microsoft Windows Support Guide (or see your Microsoft documentation). 4.2.4 Problems Running PATHWORKS MAIL Cause: If you run PATHWORKS MAIL and exceed DISKQUOTA on the server, the following occurs: 1. A VMS error box is displayed. You are prompted to continue. 2. You get the following misleading informational message: "message sent OK" Action: Ignore this message. The message was not sent and you need to resend it when more disk space is made available on the server. 4-14 Changes in PATHWORKS for DOS Version 4.1A Update Cause: If you are using Mail on an OS/2 server with Token Ring or Ethernet, and send mail to a non-existent account, the following message is displayed: Mail error No such user: xxx Action: If you press , you get the following message: Mail sent OK. 4.2.5 Creating a Root Directory on a Network Drive Do not issue a DOS MAKEDIR command with the root of a network drive as the target directory, for example: M:\>MAKEDIR M:\ If you do, a directory is created on the network drive that is inaccessible to users. 4.3 Documentation Changes This section describes additions and corrections to the PATHWORKS for DOS Version 4.1 documentation. 4.3.1 Choosing Between Basic Redirector and Full or Enhanced LAN Manager Redirector PATHWORKS supports: o Basic Redirector o Full Redirector o Enhanced Redirector Unlike the Basic Redirector, which allows long service and user names, the Enhanced and Full Redirectors limits the length of service names (sharenames), user names and passwords, as follows: Changes in PATHWORKS for DOS Version 4.1A Update 4-15 Table 4-1 Length Limitations in Enhanced and Full Redirectors Name Maximum Length service name 8 characters plus a 3-character extension. For example, MYFILE12.EXE user name 12 characters Password 8 characters The Enhanced Redirector also does not support user names and passwords in VMS or ULTRIX format. 4.3.2 Printing with the LAN Manager Full Redirector If you are running the LAN Manager Full redirector and you want to use the PATHWORKS NET PRINT command instead of the LAN Manager PRINT command, enter the NETD PRINT command: M:\>NETD PRINT 4.3.3 Correction to NET PRINT Command The Client Commands Reference incorrectly states that the NET PRINT/OPERATOR=(string) command notifies the operator when the file begins to print by sending a screen message of up to 55 characters. The limit of screen message is 255 characters, not 55. 4.3.4 Getting Help for Network Services You may have software on your personal computer, such as DOS Version 5.0, that has its own Help utility. To display help for PATHWORKS utilities and network commands, use the HELPD command. o To get help for network services commands, enter: M:\>HELPD o To get help for the USE utility, enter: M:\>HELPD USE 4-16 Changes in PATHWORKS for DOS Version 4.1A Update 4.3.5 InfoServer (CD-ROM) Support PATHWORKS for DOS provides support for the InfoServer 100 or 150, which gives you access to CD-ROM drives. ________________________ Note ________________________ The InfoServer is not supported over a Token Ring network. ______________________________________________________ To set up support for the InfoServer, run the Netsetup utility as described in the the appropriate client installation and configuration guide for your server. Select Intermediate or Advanced mode and then answer the prompts as follows: 1. Answer the prompts until Netsetup reaches the Workstation Profile screen. 2. Select the Memory Configuration menu. 3. In the Memory Configuration Menu, choose to load LAD into EMS or conventional memory. When you choose LAD, the system displays the MSCDEX option. 4. Load MSCDEX into EMS or conventional memory. 5. Select Accept Configuration. You are returned to the Workstation Profile screen. 6. In the Workstation Profile screen, check the number of LAD drives and CD-ROM drives. If you are changing the number of LAD or CD-ROM drives, do so now. 7. Write a new key disk and exit Netsetup. Changes in PATHWORKS for DOS Version 4.1A Update 4-17 A _________________________________________________________________ Trademarks The following are trademarks of Digital Equipment Corporation: DEC, DECnet, Digital, LAT, PATHWORKS, ULTRIX, VAX, and VMS. The following are third-party trademarks: Madge is a trademark of Madge Networks, Ltd. NetWare is a registered trademark of Novell, Inc. IBM is a registered trademark of International Business Machines Corporation. Windows is a trademark and Excel, InPort, Microsoft, MS, MS-DOS, MULTIPLAN, and XENIX are registered trademarks of Microsoft Corporation. Proteon is a registered trademark of Proteon Associates, Inc. Copyright © 1992 by Digital Equipment Corporation. All rights reserved. Trademarks A-1