 





















                    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  Installation

         1.1  Installing PATHWORKS for DOS Version 4.1.........    1-2
         1.1.1  Diskette Installation .........................    1-3
         1.1.2  Upgrading from Previous Versions of
                PATHWORKS......................................    1-4
         1.2  Installing PATHWORKS for DOS Version 4.1A Update
              Diskettes........................................    1-6
         1.3  DOSLOAD..........................................    1-8
         1.4  Netsetup Utility.................................    1-9
         1.4.1  Guidelines ....................................    1-9
         1.4.2  Using Netsetup with TCP/IP and NDIS Drivers ...   1-13
         1.4.3  Problem Solving ...............................   1-15
         1.5  Next Steps.......................................   1-17

     2  Procedures for Token Ring Configuration

         2.1  Required Software and Hardware...................    2-5
         2.2  Network Configuration Guidelines.................    2-5
         2.3  Using Routers....................................    2-6
         2.3.1  Choosing Bilingual or Phase IV Prime Routing
                ...............................................    2-6
         2.3.2  Setting the MS-NET Flag .......................    2-7
         2.4  Configuring Users' PCs...........................    2-7
         2.4.1  Basic PC Configuration  .......................    2-8
         2.4.2  Additional Configuration for Microsoft Windows
                and Memory Managers ...........................   2-10
         2.5  Configuring the PC for DLC Driver Support .......   2-11
         2.5.1  Prerequisites: Installing the DLC Drivers .....   2-11
         2.5.2  Setting Up DLC Driver Support .................   2-13
         2.5.3  Additional Configuration for DLC Driver Support
                with NetWare Coexistence ......................   2-16


                                                                   iii

 







           2.6  Setting Up Concurrent Support for DECnet and IBM
                NetBEUI..........................................    2-17
           2.7  Setting the MAC Address..........................    2-18
           2.7.1   Determining the DECnet Phase IV MAC Address ...   2-19
           2.7.2   Configuring the PC for MAC Addresses ..........   2-19
           2.7.2.1   Configuring the PC for MAC Addresses with
                     NDIS Drivers................................    2-20
           2.7.2.2   Configuring the PC for MAC Addresses with
                     DLC Drivers.................................    2-20
           2.8  Alternate Configurations.........................    2-20
           2.8.1   Configuring the PC for Phase IV ...............   2-21
           2.8.2   Configuring for Source Routing Environments ...   2-22
           2.9  Troubleshooting Tips.............................    2-22
           2.9.1   Using the PERMIT Command With NetBEUI .........   2-22
           2.9.2   Eliminating Address Conflicts .................   2-23
           2.9.3   System Reboots or Hangs During Heavy Network
                   Activity.......................................   2-24
           2.9.4   Failure when Booting a PC .....................   2-25
           2.9.5   Error When Booting a PC .......................   2-26
           2.9.6   Failure with Third-Party Applications .........   2-26
           2.9.7   Problems Using PC DECwindows ..................   2-27

        A  Trademarks


        Tables

           1-1     Installing and Configuring PATHWORKS  .........    1-1

           2-1     Procedures for Token Ring Configuration .......    2-2

           2-2     Required Hardware and Associated Software .....    2-5

           2-3     Controller Files ..............................   2-12

           2-4     Commands to Enter in the CONFIG.SYS File ......   2-14

           2-5     Parameters and Default Addresses  .............   2-24







        iv

 










                                                                        1
        _________________________________________________________________

                                                             Installation


              Table 1-1 describes the steps you must follow to install
              and configure PATHWORKS for DOS Version 4.1A.

              The distribution kit for PATHWORKS for DOS Version 4.1A
              includes media labeled V4.1 and V4.1 UPDATE.

              Table_1-1_Installing_and_Configuring_PATHWORKS_____________

              Follow these steps:             And read:                  

              1. Install PATHWORKS for DOS    Section 1.1.1 and
                 4.1.                         Section 1.1.2 in this
                                              chapter and the appropriate
                                              client installation and
                                              configuration guide for
                                              your server


              2. Install PATHWORKS for        Section 1.2 in this
                 DOS Version 4.1A UPDATE      chapter.
                 diskettes.


              3. Make an initial connection   The appropriate client
                 between the PC and the       installation and
                 server.                      configuration guide for
                                              your server.

                                                 (continued on next page)





                                                         Installation 1-1

 







              Table_1-1_(Cont.)_Installing_and_Configuring_PATHWORKS_____

              Follow these steps:             And read:                  


              4. Familiarize yourself with    Section 1.3 in this
                 the DOSLOAD utility.         chapter.


              5. Run the DOSLOAD utility.     The appropriate client
                                              installation and
                                              configuration guide for
                                              your server.


              6. Familiarize yourself with    Section 1.4 in this
                 the guidelines for running   chapter.
                 the Netsetup utility.


              7. Configure the PC:

                 o  If you are using the      Chater 2. 
                    Token Ring features       
                    included in this
                    release, configure for
                    them.

                 o  If you are not using      The appropriate client
                    the Token Ring features   installation and
                    in this release, run      configuration guide for
                    Netsetup.                 your server.

              ___________________________________________________________

        1.1 Installing PATHWORKS for DOS Version 4.1

              Follow the guidelines in this section when installing
              PATHWORKS for DOS Version 4.1.





        1-2 Installation

 







        1.1.1 Diskette Installation

              If you are using the diskette kit to install PATHWORKS for
              DOS to an OS/2 server or to a client hard disk, note the
              following changes:

              o  PATHWORKS for DOS Version 4.1 is shipped on either
                 5¼-inch high density or 3½-inch low-density diskettes
                 labeled:

                 PWRKS FOR DOS V4.1  1/n

                 The number (n) of diskettes depends on your media.

                 Low density 5 1/4-inch diskettes are no longer shipped.

              o  The INSTALL program is now menu driven. The Installation
                 menu lists all the PATHWORKS components and lets you
                 select which components to install.

              o  If you are reinstalling or upgrading from a previous
                 version of PATHWORKS for DOS, delete any old PATHWORKS
                 files that you may have set read-only or hidden before
                 running INSTALL.

                 INSTALL fails if it finds existing PATHWORKS files set
                 to read-only or hidden.

              o  If you use the <F4> key to spawn to DOS while installing
                 the Configuration Utilities, make sure to set your
                 default back to the floppy drive from which you were
                 running the installation before entering EXIT. Exiting
                 from another drive causes the installation to fail.

              o  If you installed PATHWORKS for DOS (NetWare Coexistence)
                 on your OS/2 server or hard disk, do the following:

                 1. Delete all read-only and hidden PATHWORKS files.

                    The PATHWORKS for DOS (NetWare Coexistence) kit
                    includes several read-only and hidden files.

                 2. Install PATHWORKS for DOS Version 4.1.

                    If you do not delete the read-only and hidden files,
                    the installation fails.

                                                         Installation 1-3

 







                ________________________ Note ________________________

                The VMS and ULTRIX installation procedures have not
                changed.

                ______________________________________________________

        1.1.2 Upgrading from Previous Versions of PATHWORKS

              Note the following guidelines for upgrading to PATHWORKS
              for DOS Version 4.1:

              o  If you plan to install PATHWORKS for DOS in the same
                 directory on a VMS server as a previous version of
                 PATHWORKS, do the following:

                 1. Before starting the upgrade, rename or copy the
                    PCSAINFO.DAT file in the existing system file
                    service to a file with a different name (for example,
                    OLDINFO.DAT).

                    The PCSAINFO.DAT file contains information about
                    add-on kits and any versions of DOS loaded on the
                    system file service. The following shows a sample
                    PCSAINFO.DAT file for a PATHWORKS for DOS Version 4.0
                    system:

                    The default language.                              US
                    PATHWORKS for DOS Version 4.0                      4.0
                    DCQSYSD40    Compaq DOS V4.01                      4.0
                    DISSYSD40    IBM DOS V4.01                         4.0
                    DISSYSD33    IBM DOS V3.30                         3.3
                    DZNSYSD40    Zenith DOS V4.01                      4.0
                    Netware Coexistence Installed V1.0

                 2. Perform the upgrade.

                    Installing PATHWORKS for DOS Version 4.1 diskettes to
                    an existing file service creates a new PCSAINFO.DAT
                    file.

                 3. When the upgrade is complete, append the old
                    PCSAINFO.DAT file to the new one.

                    Edit the new PCSAINFO.DAT to remove the old version
                    record, redundent records, and any other records that
                    no longer apply.

        1-4 Installation

 







                    Keep any add-on kit or DOS version information from
                    the old PCSAINFO.DAT file that still applies. Do not
                    change the length of any lines.

                    For example, you would copy the following information
                    from the OLDINFO.DAT file to the new PCSAINFO.DAT
                    file:

                    DCQSYSD33    Compaq DOS V3.31                     3.3
                    DISSYSD40    IBM DOS V4.01                        4.0
                    DISSYSD33    IBM DOS V3.30                        3.3
                    DZNSYSD40    Zenith DOS V4.01                     4.0
                    Netware Coexistence Installed V1.0

              o  If your client is running DOS Version 5.0 and PATHWORKS
                 for DOS Version 4.0, do the following to upgrade to
                 PATHWORKS for DOS:

                 1. Use Netsetup to upgrade your key disk to PATHWORKS
                    for DOS.

                 2. Before rebooting enter the following SETVER commands:

                    C:\> SETVER REDIR.EXE /DELETE
                    C:\> SETVER USE.EXE /DELETE
                    C:\> SETVER MEMMAN.EXE /DELETE
                    C:\> SETVER LAD.EXE /DELETE
                    C:\> SETVER SHOW.EXE /DELETE
                    C:\> SETVER NETSETUP.EXE /DELETE

                    If you used SETVER on any other PATHWORKS components,
                    make sure to undo each with SETVER /DELETE commands.

                 3. Reboot your PC for the changes to take effect.

Next Steps

              Install PATHWORKS for DOS Version 4.1 as described in the
              appropriate client installation and configuration guide for
              your server.





                                                         Installation 1-5

 







              

        1.2 Installing PATHWORKS for DOS Version 4.1A Update Diskettes

              This section describes how to install the software on the
              PWRKS FOR DOS V4.1A UPDATE diskettes.

              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

        1-6 Installation

 







              To install PATHWORKS for DOS Version 4.1A:

              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.






                                                         Installation 1-7

 







              9. Insert each diskette when prompted for it.

              10.Remove the PWRKS FOR DOS V4.1A UPDATE 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

              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

                 This file includes a bug fix not available in PATHWORKS
                 FOR DOS (TCP/IP) Version 2.0.

              12.Proceed to Section 1.3.

        1.3 DOSLOAD

              DOSLOAD now includes:

              o  The ability to install a version of DOS from a network
                 drive.

                 This lets you reinstall DOS from a PATHWORKS for DOS
                 Version 4.0 service to a Version 4.1A service.

              o  Loading DOS Version 5.0 to the system file service.

              Note the following DOSLOAD problem and its solution:

              PROBLEM:    If DOSLOAD fails while copying a DOS to
                          the system file service, the DOS files and
                          directory may remain on the system file
                          service.

        1-8 Installation

 








              SOLUTION:   To delete the files and the directory:

                          1. Connect to the PCSAV41 system file service
                             with read/write access.

                          2. Make the drive assigned to the system file
                             service the current drive.

                             In the following example, the system file
                             service is assigned to drive J:.

                          3. Enter the following DOS commands, specifying
                             the directory you want to delete:

                              J:\> \DOSENH\ATTRIB -RHS \directory\*.*
                              J:\> DEL \directory\*.*
                              J:\> RD directory

              Next Steps

              You are now ready to load DOS to the server, if necessary,
              as described in the appropriate client installation and
              configuration guide for your server.

        1.4 Netsetup Utility

              This section describes new and changed features of the
              Netsetup utility, guidelines for using Netsetup, and ways
              to troubleshoot the known limitations.

        1.4.1 Guidelines

              Note the following guidelines for using Netsetup:

              o  STARTNET adds PATHWORKS directories to your path. If
                 your existing path is long, your system may hang when
                 running STARTNET.

              o  Netsetup requires a minimum of 395 Kbytes to run.
                 This value supersedes the value listed in the Client
                 Installation and Configuration Guide.

              o  Memory configuration information has been moved from
                 the Client Profile screen to a new, separate Memory
                 Configuration menu.

                 You access this menu from the Client Profile screen in
                 Intermediate and Advanced mode.

                                                         Installation 1-9

 







              o  You must use Advanced Mode in Netsetup to load LANSESS
                 from the Memory Configuration screen.

              o  Netsetup lets you configure the client to run Novell
                 NetWare concurrently with PATHWORKS for DOS.

                 The feature is available only when the server has
                 PATHWORKS for DOS (NetWare Coexistence), which is
                 purchased and installed separately.

              o  To use the Netpopup service, add the following line to
                 the [services] section of the \LMDOS\LANMAN.INI file:

                 netpopup = services\netpopup.exe

                 For example:

                 [services]
                 workstation = netprog\netwksta.exe
                 chknet      = netprog\chknet.exe
                 minses      = netprog\minses.exe
                 messenger   = services\msrv.exe
                 netpopup    = services\netpopup.exe
                 encrypt     = services\encrypt.exe

                 To use Netpopup, you also:

                 1. Must be configured for Full LAN Manager Version 2.0
                    support.

                 2. In the STARTNET.BAT file, after the command that
                    starts the network and before the command that
                    connects the PC to the system service, add the
                    following lines:

                       NET START MESSENGER
                       NET START NETPOPUP

              o  If the <F7> key does not function properly at any time,
                 use the <F8> key to restart the configuration.

              o  Before running Netsetup to create a key diskette, check
                 the AUTOEXEC.BAT file for APPEND commands.

                 If you find APPEND commands, add the /PATH:OFF qualifier
                 to the APPEND command line. For example:

                 APPEND /E
                 APPEND C:\DOS /PATH:OFF

        1-10 Installation

 







                 After modifying the AUTOEXEC.BAT file, reboot the client
                 for the changes to take effect.

                 If you do not need the APPEND commands, remove them
                 from the AUTOEXEC.BAT file; otherwise, you may have
                 problems with your COMMAND.COM when you run Netsetup.
                 For example, Netsetup may display an error message
                 similar to the following:

                 INT 21 ERROR #2 while setting attributes of file H:\COMMAND.COM

                 In addition to the Netsetup error, when you reboot the
                 client, the system hangs and displays the following:

                 Incorrect DOS version.
                 Bad or missing Command Interpreter.

              o  For NDIS drivers:

                 -  If you specify an NDIS driver with the same name as
                    the previously configured driver, Netsetup does not
                    update the driver or PROTOCOL.INI.

                    To update the NDIS driver, rename or delete the
                    original driver and PROTOCOL.INI files on the key
                    disk.

                 -  If you are supplying the NDIS driver for the Ethernet
                    card (Other NDIS option), make sure the disks with
                    the driver and PROTOCOL.INI files does not have the
                    disk label KEYDISK.

              o  Netsetup no longer prompts you to load the Digital Mouse
                 driver (DECMOUSE).

                 If your EtherWORKS (DEPCA) controller card has a
                 mouse port, you must manually edit your CONFIG.SYS or
                 AUTOEXEC.BAT file to load DECMOUSE.

                 DECMOUSE.SYS and DECMOUSE.COM are located in the \DOSENH
                 directory on the PCSAV41 system file service.

                 If you are upgrading a client that already loads
                 DECMOUSE, Netsetup does not delete the lines in
                 CONFIG.SYS or AUTOEXEC.BAT that load the mouse.

              o  Do not redirect the output of the LAD command to a file
                 when LAD is loaded into EMS.

                                                        Installation 1-11

 







                 For example:

                 EMSLOAD LAD > C:\NET.LOG
                 General failure
                 R(etry), I(gnore), F(ail), or A(bort)

                 This restriction applies to LAD loaded from both the
                 STARTNET.BAT file and from the command line.

              o  For remote boot:

                 -  Netsetup creates the EXECINFO.BAT file containing the
                    SET_WSNODE and SET_WSADDR lines to define the client
                    node name and network address. If you add or modify
                    a Remote Boot key disk from the server with the PCSA
                    Manager Menu and use the /TEMPLATE qualifier, the
                    PCSA Manager rewrites EXECINFO.BAT.

                 -  If you delete the client profile on a remote boot
                    client's key disk, you cannot re-enter the node
                    address with the "Modify a remote-boot workstation"
                    option of Netsetup Version 4.1. Netsetup does not
                    prompt you for the node address and displays ##.####
                    on the Workstation profile screen.

                    If this happens, remove the LAD disk and add it from
                    scratch.

                 -  When formatting diskette to be used as a floppy
                    remote boot diskette, do not specify a disk label.

                 -  To configure remote boot clients with Netsetup,
                    PATHWORKS for VMS Version 4.1 must be installed
                    on the server. Servers with previous versions of
                    PATHWORKS for VMS do not recognize the attempt to
                    register the workstation under Version 4.1.

              o  On some monochrome monitors, particularly portables,
                 the fields in the Memory Configuration Menu are in
                 inverse video. In this case, the Memory Configuration
                 Menu heading is lower in intensity than the component
                 names displayed on the left side of the screen.

                 With inverse video, when you select a field (Do Not
                 Load, LOAD, RAM etc), it is not highlighted; instead,
                 the unselected field is highlighted. For example, if you
                 place the cursor over the LOAD field to load CTERM, when
                 you press <Return> the LOAD field is not highlighted

        1-12 Installation

 







                 and the Do Not Load field appears highlighted. Use the
                 non-highlighted field to load the components.

        1.4.2 Using Netsetup with TCP/IP and NDIS Drivers

              Note the following guidelines for using Netsetup with
              PATHWORKS for DOS (TCP/IP) and NDIS drivers.

              o  When you install an NDIS driver for the 3Com Etherlink
                 II adapter, the PROTOCOL.INI file uses the following
                 default from the
                 \LMDOS\DRIVERS\ELNKII\PROTOCOL.INI file on the PCSAV41
                 system file service:

                 TRANSCEIVER = EXTERNAL

                 If the adapter is connected to a ThinWire segment, this
                 value should be:

                 TRANSCEIVER = ONBOARD

                 The default TRANSCEIVER value (EXTERNAL) is a safety
                 measure. If the value is ONBOARD and the adapter is
                 connected to a transceiver (for example, H4000) instead
                 of ThinWire, the board may be damaged.

                 You can change the TRANSCEIVER value when Netsetup
                 displays the PROTOCOL.INI file before writing the key
                 disk, or by editing PROTOCOL.INI after Netsetup is
                 completed.

                 Note that the following Etherlink II variants do not
                 have this problem:

                    3Com Etherlink II TP (3C503-TP)
                    3Com Etherlink II/16 (3C503-16)
                    3Com Etherlink II/16 TP (3C503-16/TP)

                 If you have these versions, or if none of the original
                 Etherlink II boards can be connected to an external
                 transceiver, you can change the TRANSCEIVER default to
                 ONBOARD in the
                 \LMDOS\DRIVERS\ELNKII\PROTOCOL.INI file on the PCSAV41
                 system file service.

              o  Open the \TCPIP\MSNET.INI file on the PCSAV41 system
                 file service with any text editor and find the following
                 section:

                                                        Installation 1-13

 







                 help
                 help $*
                     help $*

              o  Change the last line of the found section as follows:

                 help
                 help $*
                     helpd $*

                 This change prevents a conflict with the DOS Version 5.0
                 HELP command.

              o  You can use the internetnames parameter in the
                 [Rfcnetbios] section of your PROTOCOL.INI file to
                 specify the maximum number of Internet names that your
                 PC can support.

                 The internetnames parameter defines the maximum number
                 of Internet names that can be added to a workstation's
                 Internet name table. For each node name and address you
                 add to the table, 2 entries are placed in the table. For
                 example, changing the value to 16 lets you connect to 8
                 systems not in your subnet.

                 The default for the internetnames parameter is 4. You
                 can edit the PROTOCOL.INI file and specify any value for
                 the is parameters from 0 to 32. For example:

                 [Rfcnetbios]
                 drivername = tcpnb$
                 bindings = tcpip
                 internetnames = 16

              o  If the client is configured for Full LAN Manager Version
                 2.0 support for TCP/IP, you cannot use the NET LOAD or
                 NET SAVE commands to load or save a profile. Using these
                 commands results in the following error:

                 error:  "System cannot find path specified."

                 To use the NET LOAD or NET SAVE commands on the client,
                 do an XCOPY of the \LMDOS\PROFILE\NETLOGON.PRO file on
                 the system file service to your boot disk. For example:

                 C:\> XCOPY J:\LMDOS\PROFILES\NETLOGON.PRO C:\LMDOS\PROFILES\NETLOGON.PRO

        1-14 Installation

 







        1.4.3 Problem Solving

              Note the following problems with Netsetup and their
              solutions:

              PROBLEM:    The screen may be unreadable after invoking
                          Netsetup.

              SOLUTION:   Press <F10> twice to exit from Netsetup and
                          make sure that the video mode is set properly
                          (80x25 characters). For more information,
                          consult your DOS manual or the manual the came
                          with the video card.

              PROBLEM:    Netsetup does not verify the version of DOS
                          selected when reading a previous workstation
                          profile. If the version of DOS is not on the
                          system service, an invalid directory is put on
                          the path and in COMSPEC. Any time COMSPEC is
                          used, the system halts.

              SOLUTION:   Add the SET COMSPEC command to the AUTOEXEC.BAT
                          file after :end so that COMSPEC points to a
                          local COMMAND.COM file and removes the DOS
                          directory from the path.

              PROBLEM:    When you configure a TCP/IP workstation, the
                          Domain Name field accepts only 59 characters,
                          not the 116 characters allowed for a valid
                          domain name.

              SOLUTION:   To enter a domain name of more than 59
                          characters (up to 116 characters):

                          1. Edit the PROTOCOL.INI file.

                          2. Find the DOMAIN field.

                          3. Insert the desired domain name between the
                             quotation marks:

                                  DOMAIN = ""



                                                        Installation 1-15

 








              PROBLEM:    Running STOPNET.BAT to stop the network
                          followed by STARTNET.BAT does not restore all
                          network connections.

              SOLUTION:   Do the following to make sure all your network
                          connections are restored:

                          1. Remove the following line from the
                             STOPNET.BAT file:

                                  del %PCSA%\reload.ini

                             This prevents STOPNET.BAT from deleting the
                             RELOAD.INI context file which is typically
                             found in the \DECNET directory on your boot
                             device.

                          2. Run STOPNET.BAT then STARTNET.BAT to stop
                             and start the network.

                          3. Restore your network connections with the
                             following command:

                              C:\> USE /LOAD <PATH>reload.ini /LOG




















        1-16 Installation

 







        1.5 Next Steps

              You are ready to do the following:

              o  If you are using the Token Ring features included in
                 this release, read Chapter 2.

              o  Otherwise, run Netsetup as described in the appropriate
                 client installation and configuration guide for your
                 server.



































                                                        Installation 1-17

 










                                                                        2
        _________________________________________________________________

                                  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 2.7 describes this feature in more detail.
















                              Procedures for Token Ring Configuration 2-1

 







              Table 2-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_2-1_Procedures_for_Token_Ring_Configuration__________

              Follow these steps:                       And read:         


              1. Check for required software and        Section 2.1 in
                 hardware.                              this chapter.


              2. Follow the network configuration       Section 2.2 in
                 guidelines, including all              this chapter.
                 restrictions.


              3. If you are using a router other than   Section 2.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 2.3.1
                    routing.                            in this chapter.


                 b. Set the MS-NET flag.                Section 2.3.2

                                                        in this chapter.

                                                 (continued on next page)











        2-2 Procedures for Token Ring Configuration

 







              Table_2-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 2.4 and
                 Ring networks.                         Section 2.4.1 in

                                                        this chapter.


              6. Configure the PC for Microsoft         Section 2.4.2
                 Windows and memory managers, if        in this chapter.
                 desired.


              7. Configure the PC for DLC driver        Section 2.5,
                 support:                               Section 2.5.1,

                                                        and Section 2.5.2
                                                        in this chapter.


                 o  With NetWare Coexistence            Section 2.5
                                                        in this chapter.

                 o  With concurrent access to IBM       Section 2.6 in
                    NetBEUI                             this chapter.


                                                 (continued on next page)





                              Procedures for Token Ring Configuration 2-3

 







              Table_2-1_(Cont.)_Procedures_for_Token_Ring_Configuration__

              Follow these steps:                       And read:        


              8. Set the MAC address if desired:        Section 2.7,
                                                        Section 2.7.1,
                                                        and Section 2.7.2
                                                        in this chapter.



                                     
                 o  With NDIS drivers                   Section 2.7.2.1
                                                        in this chapter.




                                    
                 o  With DLC drivers                    Section 2.7.2.2
                                                        in this chapter.

              ___________________________________________________________

              Alternate configurations are discussed in Section 2.8.
              Troubleshooting tips are discussed in Section 2.9.

















        2-4 Procedures for Token Ring Configuration

 







        2.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 2-2.

              Table_2-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)                  

        2.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 2-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 2.3.

              If not using a router, proceed to Section 2.4.

        2.3 Using Routers

              If using a Proteon router, read Section 2.3.1 and
              Section 2.3.2.

              For all routers, read Section 2.3.2.

        2.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.

        2-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.

        2.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 2.4.

        2.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 2-7

 







        2.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.

        2-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 2-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 2.4.2.

              9. If you are setting up support for DLC drivers, follow
                 the directions in Section 2.5.

              10.If you are setting up support for DLC drivers with
                 concurrent access to DECnet and IBM NetBEUI, follow
                 the directions in Section 2.5 and Section 2.6.

              11.Reboot the PC.

        2.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.

        2-10 Procedures for Token Ring Configuration

 







        2.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 2.4.1, run Netsetup to
                   configure the PC.

                2. Boot the PC using the key disk created in step 1,
                   then run Netsetup a second time to install the DLC
                   driver, as described in the following sections.

                ______________________________________________________

        2.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 2.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 2-3, depending on the
                 controller type, to the common subdirectory.

                             Procedures for Token Ring Configuration 2-11

 







              Table_2-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.










        2-12 Procedures for Token Ring Configuration

 







        2.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 2-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 2-13

 







              Table_2-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 2.4 for instructions.

              3. Run the Netsetup utility a second time (you should
                 have already run the utility once as described in
                 Section 2.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.

        2-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 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
                <Return> at the prompt. This saves the network
                connection information created the first time you
                ran Netsetup. Do not press <F7>.

                ______________________________________________________

                    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 2.5.3.

              7. For concurrent access to DECnet and IBM NetBEUI, go to
                 Section 2.6.

              8. Reboot the PC.




                             Procedures for Token Ring Configuration 2-15

 







        2.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.

        2-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.

        2.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:

                 This
                 Parameter   Represents                                  

                 0           IBM NetBEUI

                 1           DECnet                                      

                             Procedures for Token Ring Configuration 2-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.

        2.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 2.7.1.

              2. Configure the PC for the MAC address as described in
                 Section 2.7.2.





        2-18 Procedures for Token Ring Configuration

 







        2.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

        2.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 2-19

 







        2.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.

        2.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

        2.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.

        2-20 Procedures for Token Ring Configuration

 







              o  You are inserting a source routing bridge between the PC
                 and another node on the network.

        2.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 2-21

 







        2.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 2.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 2.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.

        2.9 Troubleshooting Tips

              This section describes problems you may encounter when
              running in a Token Ring environment and hints on how to
              correct them.

        2.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 *

        2-22 Procedures for Token Ring Configuration

 







              For more information on the PERMIT command, see Client
              Commands Reference.

        2.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 2-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 2-23

 







              Table 2-5 lists the parameters, their descriptions, and
              their defaults.

        Table_2-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                             

        2.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

        2-24 Procedures for Token Ring Configuration

 







        2.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.






















                             Procedures for Token Ring Configuration 2-25

 







        2.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, 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.

        2.9.6 Failure with Third-Party Applications

              Cause:

              PATHWORKS for DOS Version 4.1A 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.

        2-26 Procedures for Token Ring Configuration

 







        2.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.

                 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 2-27







                                                                        3
        _________________________________________________________________

                                Changes in PATHWORKS for DOS Version 4.1A


              This chapter describes the new and changed features of
              PATHWORKS for DOS Version 4.1A, which includes the V4.1 and
              V4.1A UPDATE diskettes in your distribution kit.

        3.1 New Token Ring Features

              Token Ring features in PATHWORKS for DOS Version 4.1A
              include:

              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.


                            Changes in PATHWORKS for DOS Version 4.1A 3-1
 







                ________________________ 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.

                ______________________________________________________

        3.2 Configuration Utilities

              PATHWORKS for DOS includes two new configuration utilities:

              o  NETSYS creates a bootable DOS diskette using the system
                 files from a subdirectory on the system service.

              o  NETVER displays information about the PATHWORKS for DOS
                 version, including add-on kits and any versions of DOS
                 loaded on the system file service.

              For more information on these utilities, see the Client
              Commands Reference.

        3.3 Online 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

        3.4 DOS Version 5.0 and Task Switcher Support

              PATHWORKS for DOS supports DOS Version 5.0, including
              the DOS Task Switcher (DOSSWAP). This section describes
              guidelines for running DOS Version 5.0 and the DOS Task
              Switcher.

        3-2 Changes in PATHWORKS for DOS Version 4.1A
 







        3.4.1 Guidelines for Running DOS Version 5.0

              Note the following guidelines for running DOS Version 5.0:

              o  The device drivers supplied with DOS Version 5.0
                 supersede the device drivers supplied with Microsoft
                 Windows 3.0. These drivers are:

                    HIMEM.SYS
                    EMM386.EXE
                    SMARTDRV.SYS

              o  Codepage 852 (Slavic), available in MS-DOS Version 5.0,
                 is not currently supported.

        3.4.2 Guidelines for Using the DOS Task Switcher

              Note the following guidelines for using the DOS Version 5.0
              Task Switcher over DECnet:

              o  Task switching can be slow if the network is busy. If
                 the PC beeps when trying to switch tasks, try again a
                 few seconds later. After several tries, either wait
                 or cancel any outstanding requests running over the
                 network.

              o  After doing a task switch, pause a few seconds before
                 typing; otherwise the first one or two keystrokes will
                 be lost.

              o  In general, multiple instances of the same PATHWORKS
                 program are not supported under a task switcher.
                 Multiple instances means starting the same program twice
                 under the task switcher using two different sessions.

              o  If you run Windows Version 3.0, use Windows for task
                 switching instead of the DOS Shell.

                 Windows has its own task switcher. Do not run Windows
                 from within the DOS Shell. Do not run the DOS Shell
                 from a Windows DOS prompt. Both task switchers use the
                 same switching keys. Running both task switchers wastes
                 memory.

              o  If your application uses EMS and is not yet supported
                 under DOS Version 5.0, then you should disable EMS
                 use by the application. This is because the DOS Task
                 Switcher does not save and restore the EMS page frame
                 when switching.

                            Changes in PATHWORKS for DOS Version 4.1A 3-3
 







              o  PC DECwindows Motif does not allow task switching
                 directly from the application.

                 To use the task switcher, you must return to DOS by
                 suspending the PC DECwindows Motif session.

              o  The DOS Task Switcher does not support all video modes.

                 Any nonstandard video mode must have a DOSSHELL.GRB file
                 provided by the vendor of the video hardware.

              o  LAD drives cannot be used as the swapping device for the
                 DOS Task Switcher.

        3.5 DEBUG Utilities

              A \DEBUG directory has been added to the PCSAV41 system
              file service. This directory contains the following
              undocumented debugging aids:

              ___________________________________________________________
              File          Contents                                     

              DDNDCPPC.EXE  The debug version of asynchronous DNP

              DDNETH.EXE    The debug version of Ethernet DNP

              DEBUG.DOC     Undocumented debugging features of various
                            PATHWORKS for DOS components

              DSNAGNI.DOC   Debugging features of DSNAGNI.EXE

              DSNAGNI.EXE   The debug version of SNAGNI.EXE

              DTP.EXE       A DNP test program to dump important
                            information about DNP such as link data
                            structures, internal major data structures
                            (REQ, DSD, RDD) and datalink buffer usage

              SHOW.DOC      A list of SHOW.EXE features

              SHOW.EXE      A tool to aid in the debugging and analysis
                            of PATHWORKS configurations

              SHOW.HLP      Help file for SHOW                           

        3.6 Basic, Full, and Enhanced Redirector Support

              PATHWORKS for DOS supports the Basic, Full, and Enhanced
              Redirectors.

        3-4 Changes in PATHWORKS for DOS Version 4.1A
 







              o  The Basic Redirector recognizes all PATHWORKS for DOS
                 commands. The Basic Redirector is recommended for DOS
                 clients that connect only to a VMS or ULTRIX server.

              o  The Enhanced Redirector recognizes all PATHWORKS for
                 DOS commands. It also lets DOS clients use servers that
                 offer full LAN Manager Version 2.0 functionality. With
                 the Enhanced Redirector option, only those files needed
                 to start the Redirector are copied to the key disk; the
                 remainder of the files are stored on the server.

        3.6.1 Configuring the System to Use the Enhanced Redirector

              To use the Enhanced Redirector:

              1. Run Netsetup to configure the client with the Basic
                 Redirector.

              2. Reboot the client.

              3. Reconfigure the client using Netsetup from the PCSAV41
                 system file service.

              4. When you create a floppy key disk for DECnet with the
                 Enhanced Redirector, Netsetup does not copy the NET.MSG
                 file to the floppy key disk. When you boot the PC using
                 the floppy key disk, the system displays the following
                 message:

        Because this is a floppy key disk the NET.MSG file was not copied
        in order to provide space for full configurations. Although there
        may be room on the floppy for the file that is not always the case.
        Please ignore any error messages related to \LMDOS\NETPR
        PLEASE ENTER YOUR PASSWORD AFTER THE ERROR MESSAGE APPEARS . . .
        SYS0318: Message file J:\LMDOS\NETPR cannot be found.

                 Type your password and press <Return> after the SYS0318
                 message is displayed. You are not prompted to enter the
                 password and your input is not echoed on the screen.
                 After your password is entered, the startup procedure
                 continues.

                 Some configurations hang after the password is
                 entered. On these configurations, create a dummy
                 \LMDOS\NETPROG\NET.MSG file on the floppy key disk.
                 When you reboot, the system displays the message listed
                 above and an error message similar to the following:

                            Changes in PATHWORKS for DOS Version 4.1A 3-5
 







                 SYS0319: The system cannot read message file J:\NETPROG\NET.MSG

                 To continue the startup procedure, type the password and
                 press <Return>.

        3.6.2 Guidelines for Using the Enhanced Redirector

              Note the following guidelines and restrictions for using
              the Enhanced Redirector:

              o  If you have an XT, you must load the Enhanced Redirector
                 into conventional memory.

              o  You cannot configure your client to use the Enhanced
                 Redirector from the Client Setup diskettes.

              o  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:

              Table 3-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.

              o  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, use the Basic Redirector when you
                 are copying very small files.

        3.6.3 Guidelines for Using the Full LAN Manager Redirector

              If you are running the Full LAN Manager Version 2.0 Support
              Redirector, and you want to use the PATHWORKS NET PRINT
              command instead of the LAN Manager PRINT command, enter the
              NETD PRINT command.

        3-6 Changes in PATHWORKS for DOS Version 4.1A
 







        3.7 Microsoft Windows Version 3.0 and 3.1 Support

              This section describes the new and changed features of
              PATHWORKS for DOS support for Microsoft Windows Version
              3.0 and 3.1, guidelines for using Windows, and ways to
              troubleshoot the known limitations.

        3.7.1 New and Changed Features

              PATHWORKS for DOS support for Microsoft Windows Version
              3.0 and 3.1 has the following new or changed features since
              PATHWORKS for DOS Version 4.0:

              o  The WIN3SETU Installation/Configuration Utility now
                 includes:

                 -  Restarting WIN3SETU with the <F8> key

                 -  Installation of the appropriate DECterm font in the
                    WIN.INI file

              o  The Terminal Access Library (TRMNLAXS.DLL) gives Windows
                 Version 3.0 and 3.1 applications access to LAT, CTERM,
                 and now also Telnet (TCP/IP) sessions

                 The documentation in the Programmer's Reference Book
                 (Appendix J) has also been updated.

              o  The DEPCA mouse driver for Windows (DECMOUSE.DRV) now
                 supports NDIS as well as proprietary datalink

                 NDIS support is necessary for use with PATHWORKS for DOS
                 (TCP/IP) and PATHWORKS for DOS (NetWare Coexistence).

              o  Digital ANSI printer drivers, including:

                 -  DEClaser 2200

                 -  DEClaser 2100

                 -  LA70 Dot Matrix Personal Printer (use with LA75s for
                    now)

                 -  LA324 Dot Matrix Color MultiPrinter

                 -  LJ250/LJ252 Color Ink Jet Companion Printer

              o  Network File Transfer (NFT) for Windows has the
                 following new or changed features:

                 -  NFT now uses the Windows Version 3.0 and 3.1 Help
                    facility.

                            Changes in PATHWORKS for DOS Version 4.1A 3-7
 







                 -  You can copy a file by dragging an icon to the
                    destination directory window.

                 -  You can now display a text file by double-clicking on
                    it.

              o  File Access Listener (FAL) for Windows now uses the
                 Windows Version 3.0 and 3.1 Help facility

              o  Windows Version 3.0 and 3.1 PIF support for the SETHOST
                 Terminal Emulator

                 With Windows you can use a hot key to switch between
                 SETHOST and other applications, including other copies
                 of SETHOST, and you can run SETHOST in a window in 386
                 Enhanced Mode.

              o  Performance improvements in DECnet and NETBIOS
                 operations

                 Both the VDNET.386 and VNETBIOS.386 Virtual Devices for
                 DECnet and NETBIOS can now convert synchronous requests
                 to asynchronous requests.

                 To enable this option, set DNETNoBlock=true (for DECNET
                 socket calls) and NetNoBlock=true (for NETBIOS calls) in
                 the [386ENH] section of SYSTEM.INI.

                 This option may require a higher setting of DNETHeapSize
                 (for DECNET calls) and NETHeapSize (for NETBIOS).
                 DNETHeapsize can still be set to a lower value in
                 most cases than with previous versions due to other
                 enhancements to VDNET.386.

              o  RPLMEM.EXE has been updated to allow the network to run
                 in EMS with 386 Enhanced Mode Windows remote boot.

              o  Improved interoperability with PC DECwindows Motif

                 You can now run DWDOS286 in all Windows modes and
                 DWDOS386 in all modes except 386 Enhanced.

                ________________________ Note ________________________

                Microsoft Windows 2.1 is no longer supported and the
                support files have been removed from the kit.

                ______________________________________________________

        3-8 Changes in PATHWORKS for DOS Version 4.1A
 







              As part of the Microsoft Windows V3.1 kit, you will find
              three types of PATHWORKS-related components:

              o  PATHWORKS network drivers

                 -  Driver for PATHWORKS file, disk and print services
                    (PCSA.DRV) Lets you connect to and disconnect from
                    PATHWORKS DECnet network services from a Microsoft
                    Windows environment. Provides file, disk, and print
                    services.

                 -  Driver for DECnet for DOS (DECNET.386) The virtual
                    device driver for the DECnet socket interface (called
                    VDNET.386 on the PATHWORKS for DOS V4.1 kit).

                 -  Driver for Digital-enhanced NETBIOS (DECNB.386) The
                    virtual device driver for standard and Digital-
                    enhanced NETBIOS (called VNETBIOS.386 on the
                    PATHWORKS for DOS V4.1 kit). Digital's Enhanced
                    NETBIOS functions support DECnet's wide area
                    networking capabilities.

              o  DIGITAL printer drivers

                 Microsoft Windows printer drivers are included on the
                 Microsoft Windows 3.1 kit for the following Digital
                 PostScript printers:

                 -  Colormate PS

                 -  DEClaser 1150

                 -  DEClaser 2150

                 -  DEClaser 2250

                 -  DEClaser 3250

                 -  LN03R ScriptPrinter

                 -  PrintServer 20 (LPS20)

                 -  PrintServer 40 (LPS40)

                    Other printer drivers can be found in the PATHWORKS
                    for DOS V4.1 kit.

              o  PATHWORKS icons

                            Changes in PATHWORKS for DOS Version 4.1A 3-9
 







                 There are icons and PIFs (Program Information Files)
                 included on the Microsoft Windows 3.1 Kit for the
                 following PATHWORKS for DOS-based applications and
                 utilities:

                 -  SEDT (DOS-based screen editor)

                 -  DECnet NCP Utilities (Network Control Program)

                 -  Spawner (DOS-based job spawner)

                 -  PATHWORKS Mail for DOS (a client for VAXmail)

                 -  SETHOST (DOS-based VT320 terminal emulator)

                 -  PC DECwindows Motif (DOS-based X Window servers for
                    286/386)

              Note the following information during installation:

              o  When installing Microsoft Windows 3.1, choose: DEC
                 PATHWORKS (version 4.1 or higher) for your network. This
                 will install the PATHWORKS network drivers for you. The
                 PATHWORKS network drivers on the Microsoft Windows 3.1
                 kit are newer than the drivers that accompany PATHWORKS
                 for DOS V4.1, and contain specific support for Microsoft
                 Windows 3.1.

              o  To avoid overwriting the new drivers when running
                 WIN3SETU, answer NO to the question:

                 Do you wish to access PATHWORKS network services under
                 Windows 3.0?

                 This will prevent the older PATHWORKS network drivers
                 from being installed.

              o  You must still run WIN3SETU:

                 -  To install the LK250 and DEPCA mouse drivers

                 -  If you wish to have your Microsoft Windows directory
                    added to your path

                 -  If you are planning to use the VT320 Terminal
                    Emulator for Microsoft Windows. Additionally, the
                    VT320 DECterm font must be installed in the Microsoft
                    Windows 3.1 Control Panel.

        3-10 Changes in PATHWORKS for DOS Version 4.1A
 







        3.7.2 Guidelines

              Note the following guidelines for using Microsoft Windows
              Version 3.0 and 3.1 with PATHWORKS for DOS:

              o  The WIN3SETU option "HP Vectra" is not supported.

                 The option is intended for older Vectra models. Newer
                 models (including the 286/12, 386/25, most other 80386-
                 based models, and all 80486-based models) require the
                 "IBM or compatible" setting.

                 Note that Hewlett-Packard PCs are not officially
                 supported under PATHWORKS.

              o  WIN3SETU adds \MSWINV30 to your path. The new path does
                 not take effect until you reboot your machine.

              o  To improve performance of Windows in Enhanced Mode with
                 PATHWORKS, put the network in conventional memory or
                 upper memory blocks rather than EMS.

              o  At the time of this release, EMM386 (as supplied by
                 Microsoft) is the only supported 386 EMS emulator for
                 Windows Version 3.0 and 3.1.

                 If you run Windows Enhanced mode and have network
                 software loaded into EMS, you should use EMM386. Keep
                 in mind that EMM386:

                 -  Does not support Standard mode (WIN /S) with Windows
                    Version 3.0, but does support Standart mode with
                    Windows Version 3.1

                 -  Must be installed with the D=48 command line
                    parameter

                 -  Lets you load components in high memory

              o  Digital recommends that you upgrade to Windows Version
                 3.1, a new release which has been available from
                 Microsoft since April, 1992. )

                 Windows Version 3.1 includes improvements to the file
                 management, user-defined shortcut keys, and diagnostics.
                 It also includes PATHWORKS drivers, as described below.

                 Windows Version 3.1 can be distinguished from earlier
                 versions by the dialog boxes for the Program Manager,
                 File Manager, and Control Panel Help About.

                           Changes in PATHWORKS for DOS Version 4.1A 3-11
 







              o  The Windows printer drivers distributed with PATHWORKS
                 for DOS use the GENDRV.DLL common printer library.

                 GENDRV.DLL is distributed with PATHWORKS along with the
                 current and future versions of Windows. Always use the
                 latest version of GENDRV.DLL. You can see the version
                 number for GENDRV.DLL in the printer setup dialog.

                 Other vendors' printer drivers also use GENDRV.DLL. When
                 installing different printer drivers, check the GENDRV
                 version.

              o  With a Digital LK250 keyboard:

                 -  If you use an LK250 keyboard in 386 Enhanced mode
                    with DECKEYB and KEYBRD loaded, make sure when you
                    switch from one application to another you set the
                    correct keyboard mode for the current application.
                    To switch from DEC mode to Industry Standard mode
                    (or from Industry Standard mode to DEC mode), press
                    <Alt/F17>. When the Special LED on the keyboard is
                    illuminated, the keyboard is in Industry Standard
                    mode and emulates an AT keyboard.

                 -  If you have problems with Windows applications such
                    as Word for Windows, and have an LK250 keyboard,
                    then try changing the following line in the [386enh]
                    section of the SYSTEM.INI file in your Windows
                    directory:

                    Old line:   keyboard=vkd250.386
                    Change to:  keyboard=*vkd

                 -  If you have both an LK250 keyboard and a DEPCA mouse,
                    and the mouse has problems responding in Windows
                    Enhanced mode, comment out the following lines in
                    your AUTOEXEC.BAT file:

                    \DECNET\KEYBRD
                    \DECNET\DECKEYB

                    These lines are added by Netsetup and provide key
                    translation for international characters under DOS.

              o  With asynchronous DECnet:

                 -  Asynchronous DECnet at 9600 baud may drop logical
                    links because of data overruns when using the network
                    from within Windows in protected mode. This includes

        3-12 Changes in PATHWORKS for DOS Version 4.1A
 







                    any network access from a Windows application in
                    Standard or Enhanced mode, and any access from a DOS
                    application in Enhanced mode. If this occurs, use
                    Windows Standard Mode, a lower baud rate, or both.

                 -  If you have an asynchronous DECnet configuration,
                    running Windows Version 3.0 and 3.1 in 386 Enhanced
                    mode and loading the network into EMS memory is is
                    not recommended due to data overruns.

              o  You cannot execute the following DOS commands while
                 running Windows Version 3.0 and 3.1:

                    MEMMAN /XMS
                    PERMIT
                    EMSSPEED

              o  Applications using TFA or TTT may produce unpredictable
                 results when run under Windows.

              o  If you use Windows Version 3.0 and 3.1 in Enhanced mode
                 and the broadcast receiver gets a message, subsequent
                 messages are not received until the network is stopped
                 and restarted, or the PC is rebooted.

              o  With Standard-mode Windows Version 3.0 and 3.1, wait
                 until all network activity completes before switching
                 from a non-Windows application that uses the DECnet
                 socket library to another application. Switching
                 before the activity is complete may cause unpredictable
                 results.

                 This restriction applies to NFTNOWIN, FALNOWIN, NCP,
                 NDU, NML, SETHOST, and any non-Windows application
                 written to use the DECnet-DOS socket library. This
                 restriction does not apply to accessing file or
                 disk services or using standard NETBIOS calls. This
                 restriction does not apply for Windows applications or
                 non-Windows applications running in Enhanced mode.

              o  LAN Manager API calls (NetUseAdd, NetUseDel, and so on)
                 are not currently supported in Windows applications.



                           Changes in PATHWORKS for DOS Version 4.1A 3-13
 







        3.7.3 Problem Solving

              Note the following problems with Windows Version 3.0 and
              3.1 and their solutions:

              PROBLEM:      When printing to an LN03R ScriptPrinter
                            connected to an ULTRIX server, the printer
                            driver currently shipped with Windows 3.0
                            is incorrect and does not process PostScript
                            files.

              SOLUTION:     Do one of the following:

                            o  On the client, choose IBM Pageprinter when
                               you configure the printer driver.

                            o  On the server, using the PCSA Manager
                               Menu, create the printer queue for the
                               printer, and associate the HP_LASERJET
                               printer type with the queue.

              PROBLEM:      When running FAL, DELETE/LOG commands issued
                            from a VMS system fail with DAP protocol
                            errors.

              SOLUTION:     Use the DELETE command without the /LOG
                            qualifier.

                            FAL should have at least 5 logical links
                            available to it for VMS wildcard operations
                            to work correctly. If FAL runs out of logical
                            links these transactions may not complete.
                            They can be aborted on the VMS side with
                            <Ctrl/Y> or on the DOS side by shutting down
                            FAL.

              PROBLEM:      For systems using the XGA drivers for Windows
                            and loading the broadcast receiver (RCV),
                            the system hangs when a broadcast message is
                            received.





        3-14 Changes in PATHWORKS for DOS Version 4.1A
 








              SOLUTION:     Do one of the following:

                            o  Replace the XGAHI.DRV or XGALO.DRV files
                               supplied with the IBM supplemental drivers
                               kit with the standard VGA.DRV file.

                            o  Get a new set of XGA Windows drivers from
                               IBM.

              PROBLEM:      If you are using a DECstation 433 running
                            Windows Version 3.00a in enhanced mode
                            using the TIGA video drivers, and you start
                            applications from the Windows command line
                            (for example, WIN /E D\WINWORD\WINWORD), then
                            when when you exit from Windows, the monitor
                            is in a non-visible video mode.

              SOLUTION:     Start the application after starting Windows.

        3.7.4 VT320 Terminal Emulator

        3.7.4.1 New and Changed Features

              The VT320 Terminal Emulator now includes:

              o  Telnet support for the Windows VT320 Terminal Emulator

                 When used with the PATHWORKS for DOS (TCP/IP), VT320 can
                 connect over Telnet.

              o  Script language improvements for the Windows VT320
                 Terminal Emulator

                 Script language has been added from the SETHOST terminal
                 emulator so that the same scripts can be used for either
                 terminal emulator.

                 If an error occurs while executing a script, the log
                 file (ERROR.LOG) is now written to the boot directory.
                 Previous versions of VT320 wrote the log file to the
                 current directory.



                           Changes in PATHWORKS for DOS Version 4.1A 3-15
 







        3.7.4.2 Guidelines

              Note the following guidelines for running the VT320
              Terminal Emulator:

              o  To comply with some countries' local regulations
                 regarding access to public telecommunications networks,
                 you must use SETHOST instead of the VT320 Terminal
                 Emulator for all direct connections to these public
                 networks.

                 This restriction exists because Full Modem Control
                 problems occur when you use the Windows Version 3.0
                 VT320 Terminal Emulator.

              o  Do not run a VT320 session using the COM port and a LAT
                 session at the same time.

                 Running them concurrently may cause transmission errors.

              o  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).

              o  There are some restrictions with VT320 and using the
                 mouse.

                 In particular, if a long listing is being displayed,
                 such a directory or the contents of a file, and you
                 click the mouse in the VT320 window, some of the
                 arriving characters may be lost. Do not click the mouse
                 button while the system is receiving data.

        3.8 PC DECwindows Motif

              This section describes the new and changed features of PC
              DECwindows Motif, guidelines for using PC DECwindows Motif,
              and ways to troubleshoot the known limitations.

        3-16 Changes in PATHWORKS for DOS Version 4.1A
 







        3.8.1 New and Changed Features

              PC DECwindows Motif has the following new features:

              o  DWDOS386 includes support for 4- and 8-plane display
                 adapters using the TIGA Version 2.0 graphics interface
                 standard.

                 A TIGA driver is available for many video interfaces
                 based on the 34010 and 34020 graphics coprocessors from
                 Texas Instruments.

              o  DWDOS386 includes a new version of the DOS Extender
                 which lets DWDOS386 coexist better with XMS memory
                 managers such as HIMEM.SYS.

              o  DWDOS286 supports off-screen images larger than 64
                 Kbytes, allowing DECpaint to be used on a 80286-based
                 PCs.

        3.8.2 Guidelines

              Note the following guidelines for using PC DECwindows
              Motif:

              o  PC DECwindows Motif uses large amounts of extended
                 memory and may cause problems with incorrectly
                 configured memory managers.

                 If PC DECwindows Motif crashes or hangs on a system
                 running a memory manager, try running it again without
                 the memory manager. If this fixes the problem, see your
                 memory manager documentation to resolve configuration
                 problems.

              o  The DECwindows Session Manager (VMS and ULTRIX) is not
                 designed to run on a remote display and does not run on
                 PC DECwindows Motif.

                 Some versions run if the account used has full
                 privileges.

                 When using the DECwindows Session Manager, be sure that
                 the Backward Compatibility parameter is set to 1 (ON).
                 Otherwise, the session manager may modify the keyboard
                 map, causing the right <Shift> key to act as a locking
                 shift key.

              o  The /L option of ANSI.SYS (DOS Version 4.0) may cause
                 video problems when you return from a suspended session.

                           Changes in PATHWORKS for DOS Version 4.1A 3-17
 







                 Do not use this option if you intend to suspend the
                 session.

              o  Do not run the DOS CHKDSK command under a suspended
                 DWDOS386 session, even when there is sufficient memory.

                 Instead, use the MEMMAN/SUMMARY or SHOW command to find
                 out how much of the various types of memory is available
                 during a suspended session.

              o  During a suspended session, do not use:

                    DOS PRINT command
                    Other TSR programs
                    Other programs that run in background

              o  If multiple applications are defined to start up
                 automatically in the DWDOS.INI file and an error occurs,
                 some of the applications may not start.

              o  The DECwindows DDIF Viewer performs poorly in the
                 DWDOS286 executable with a color video when you view
                 complex graphics.

                 To use the DDIF Viewer, use DWDOS386 or a monochrome
                 video mode.

              o  Keyboard input may be lost on very slow machines (for
                 example, the IBM AT 6MHz) because of the time involved
                 to switch the machine to and from protected mode.

                 To improve this switch time, enter the following command
                 at the DOS prompt:

                 C:\> SET DOS16M=FAST

              o  The -help option displays all the available switches and
                 is too large to fit on one screen.

                 To see the entire page, use the MORE command. For
                 example:

                 C:\> DWDOS286 -help | MORE

              o  The DWDOS286 and DWDOS386 executables cannot be started
                 from within a suspended session.

              o  The PCX Window Manager (PCX$WINMGR) will not be provided
                 in future releases.

        3-18 Changes in PATHWORKS for DOS Version 4.1A
 







                 Switch to the DECwindows Motif Manager (DECW$WINMGR on
                 VMS or dxwm on ULTRIX) or the DECwindows Motif Window
                 Manager (DECW$MWM on VMS or dxmwm on ULTRIX).

              o  If you are not using the X server over TCP/IP, you can
                 unload the BAPI, TELNET, and SOCKTSR network drivers to
                 save memory.

                 To unload the drivers, enter the TCPUNLD /TOP command
                 three times. The first command unloads the BAPI driver,
                 the second unloads the TELNET driver, and the third
                 unloads the SOCKTSR driver. You must reload the three
                 drivers before using the X server.

              o  Three-button mouse emulation may be incompatible with
                 window managers and applications using key sequences
                 with MB2.

              o  Before starting a remote Session Manager (DECW$SESSION
                 for VMS, dxsession for ULTRIX), use DWCONFIG to define
                 the remote node as a controlling host.

              o  If you use DWDOS386, the number that indicates how much
                 memory is being used does not decrease if more memory is
                 made available.

                 This number decreases if you use DWDOS286.

              o  When you run DWCONFIG for the first time, a checklist
                 screen is displayed. This screen contains information
                 that helps you configure PC DECwindows Motif. However,
                 before this screen is displayed, the "Reboot for new
                 maxlinks value" screen is displayed. If you then reboot
                 the PC, the checklist screen is never displayed. Read
                 the checklist and then reboot.

              o  The drawing of very wide dashed lines does not conform
                 to the X protocol. Wide line joins may also produce
                 non-conforming results in some cases.






                           Changes in PATHWORKS for DOS Version 4.1A 3-19
 







        3.8.3 Problem Solving

              Note the following problems with PC DECwindows Motif and
              their solutions:

              PROBLEM:      You cannot run DWDOS386 from a hard disk
                            drive on which the SHARE program is
                            installed. This prevents DWDOS386 from
                            opening files in exclusive mode.

              SOLUTION:     Use DWDOS286.

              PROBLEM:      If many graphics requests are sent to PC
                            DECwindows Motif while it is suspended, the
                            network may run out of resources and close
                            one or more of your network connections. If
                            this happens, one or more applications may be
                            lost and the remaining applications may take
                            several minutes to complete the accumulated
                            requests and resume normal operation.

              SOLUTION:     Before you suspend the session, shrink
                            windows to icons to reduce the number
                            of graphics requests and the chance of a
                            timeout.

              PROBLEM:      To start remote applications from an ULTRIX
                            system over TCP/IP, the rexec daemon must
                            reside on the ULTRIX system. With ULTRIX
                            Version 4.0, rexec does not work. With ULTRIX
                            Version 4.1, rexec works only in BSD Security
                            mode.

              SOLUTION:     PATHWORKS for ULTRIX Version 1.1 provides a
                            working rexec daemon which you can install
                            on ULTRIX Version 4.0 or 4.1 systems. For
                            information about installing rexec, see the
                            PATHWORKS for ULTRIX Version 1.1 release
                            notes.

              PROBLEM:      The LK250 keyboard (with old ROMs) may
                            produce unpredictable results, or the
                            keyboard may freeze.


        3-20 Changes in PATHWORKS for DOS Version 4.1A
 








              SOLUTION:     Use an Industry Standard keyboard or the
                            following LK250 keyboards:

                            o  LK250-xx with a ROM version F01 (or
                               higher)

                            o  70-27433-xx with a ROM Version A01 (or
                               higher)

              PROBLEM:      When running DWDOS386.EXE under DOS Version
                            5.0, the following components loaded in
                            CONFIG.SYS may cause the PC to hang:

                            DOS=HIGH
                            DEVICE=HIMEM.SYS
                            DEVICE=SMARTDRV.SYS

                            The PC may also display the following error
                            message:

                            illegal instruction

              SOLUTION:     Remove the DOS=HIGH or the
                            DEVICE=SMARTDRV.SYS line from the CONFIG.SYS
                            file and then reboot.

        3.9 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

                           Changes in PATHWORKS for DOS Version 4.1A 3-21
 







                 If you installed PATHWORKS for DOS Version 4.1A, you
                 have the correct LDU version.

        3.10 Using File Names

              PATHWORKS for DOS clients can use:

              o  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.

              o  File names with a .DIR extension

                 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.


        3-22 Changes in PATHWORKS for DOS Version 4.1A
 







        3.11 Using the 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.

        3.12 Mail

              This section decribes the new and changed features of MAIL,
              guidelines for using Mail, and ways to troubleshoot the
              known limitations.

        3.12.1 MAILCHK

              The MAILCHK utility now accepts parameters such as node
              names, user names, and passwords. MAILCHK lets you connect
              to the server and display the number of new messages
              without starting mail.

              MAILCHK has the following qualifiers:

              ___________________________________________________________
              Qualifier          Description                              

              /START             Connects to the default node, user name,
                                 and password, if they are defined in
                                 DECALIAS.DAT. If the information is not
                                 in the data file, MAILCHK accepts the
                                 parameters in the following order:

                                    Node name
                                    User name
                                    Password









                           Changes in PATHWORKS for DOS Version 4.1A 3-23
 






              ___________________________________________________________
              Qualifier__________Description_____________________________

              /STATUS            Displays the following information:

                                    Mail version number
                                    Number of new messages
                                    Personal name
                                    Forwarding information
                                    Buffer size
                                    Mail directory
                                    Mail protocol version
                                    Mail server version
                                    User name
                                    Node name
                                    Server operating system

              /SHOW              Displays the number of new messages.

              /STOP              Closes the network link.

              /VERBOSE           Displays the number of new messages with
              or /V              the following information:

                                    Date
                                    Sender
                                    Subject
              ___________________________________________________________

              MAILCHK is not currently supported over TCP/IP.

              For more information on MAILCHK, see the Mail User's
              Reference.

        3.12.2 Guidelines

              Note the following guidelines for using Mail:

              o  When you run MAILSETU over TCP/IP to an ULTRIX server,
                 the node name specified in MAILSETU must match the node
                 name specified in the HOSTS database file.

                 For example, if the node name is lowercase in HOSTS,
                 then you must specify the node name in lower case in
                 MAILSETU.

        3-24 Changes in PATHWORKS for DOS Version 4.1A
 







              o  If you spawn to DOS from Mail and accidentally delete
                 the temporary file (_XS####.TMP), you cannot return
                 to Mail without rebooting. There is no loss of mail
                 messages in this case.

              o  Do not use the SPAWN function of Mail over TCP/IP.
                 Otherwise, your Mail session may fail unpredictably
                 any time after the SPAWN action.

              o  The FILE command was omitted from the manual. It works
                 exactly like the MOVE command.

              o  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 <Return>

              o  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 <Return>

              o  To create a new folder, either from the Browser or while
                 reading a message, enter the following command:

                 Mail> MOVE <new folder name> <Return>

                 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  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  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: <Return>

                           Changes in PATHWORKS for DOS Version 4.1A 3-25
 







                 3. Change to the PCAPP directory. For example:

                    I:\> CD PCAPP <Return>

                 4. Enter the following command:

                    I:\PCAPP> MAILSEND <Return>

                    Mail displays the user name you defined in MAILSETU.
                    For example:

                    From: SERVR1::USER1
                    To:

                 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  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  If you are not in the Browser, and want to be there,
                 enter the following:

                 Mail> DIR NEWMAIL <Return>

              o  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

        3-26 Changes in PATHWORKS for DOS Version 4.1A
 







                 Marked messages:

                 -  Have an asterisk in their message flag area

                 -  Can be copied, deleted, displayed, extracted, moved,
                    printed, read, or undeleted as a group

                 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.

        3.12.3 Problem Solving

              Note the following problems with MAIL and their solutions:

              PROBLEM:      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"

              SOLUTION:     Ignore this message. The message was not
                            sent and you need to resend it when more disk
                            space is made available on the server.

              PROBLEM:      Sending Mail to a Non-Existent Account

                            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

              SOLUTION:     If you press <Escape>, you get the following
                            message:

                            Mail sent OK.

              PROBLEM:      If you unload the network (STOPNET.BAT) after
                            exiting from MAIL over TCP/IP, your system
                            may hang.

                           Changes in PATHWORKS for DOS Version 4.1A 3-27
 








              SOLUTION:     Do one of the following:

                            o  Set the Keep Network Link option in
                               MAILSETU to ON.

                            o  Upgrade to PATHWORKS for ULTRIX Version
                               1.1A.

              PROBLEM:      MAIL may have problems with video mode
                            switching and some mouse drivers. Garbled
                            text may be displayed or function keys may
                            fail with invalid command errors.

              SOLUTION:     Change the screen mode to default in MAILSETU
                            or do not load the MOUSE.COM mouse driver.

              PROBLEM:      By default, MAIL tries to create local mail
                            folders and temporary files on your key
                            diskette.

              SOLUTION:     Add the following command to your
                            AUTOUSER.BAT, AUTOEXEC.BAT, or STARTNET.BAT
                            file and create the C:\MAIL directory:

                            SET DNETMAIL=C:\MAIL

                            To change the default location of temporary
                            and local mail files, use the advanced mode
                            of MAILSETU (press the <F10> key).

              PROBLEM:      If you have a color adapter connected to a
                            monochrome monitor, you may have problems
                            reading the MAIL display.

              SOLUTION:     To fix the display, enter the MAIL /MONO or
                            MAILSETU /MONO command. The /MONO qualifier
                            overrides the default colors and forces MAIL
                            to use a monochrome display.

              PROBLEM:      When you view a directory, pressing the
                            <Enter> key displays the next message listed.
                            Therefore, when you first display a directory
                            and press <Enter>, you read the second
                            message listed.

        3-28 Changes in PATHWORKS for DOS Version 4.1A
 








              SOLUTION:     To read the first message, do one of the
                            following:

                            o  Type R and press <Enter>.

                            o  Type 1 and press <Enter>.

                            o  Move the cursor down, then back up to the
                               first message, and press <Enter>.

              PROBLEM:      You get the following error message when
                            trying to edit a file:

                     ERROR: Ran out of far heap memory! [^Z to abort MAIL]

              SOLUTION:     MAIL's default editor ran out of available
                            memory while reading or forwarding or
                            including a large file. Use a callable editor
                            that provides better memory management of
                            large text files (such as SEDT or BRIEF).

              PROBLEM:      MAIL can fail to create its temporary files
                            if your system does not have sufficient disk-
                            space. The following error is displayed:

                            Disk full while writing to temporary file.

              SOLUTION:     Use MAILSETU and make sure that the Temporary
                            File Directory specifies a hard drive or RAM
                            drive with sufficient storage.

              PROBLEM:      The DIR command does not filter out folder
                            entries when you have the "show deleted
                            messages" switch set to OFF in MAIL.INI.

              SOLUTION:     Read the entire mail folder before applying
                            this switch. To get the desired effect, page-
                            up through all the folder entries or apply a
                            search.





                           Changes in PATHWORKS for DOS Version 4.1A 3-29
 








              PROBLEM:      If you delete mail messages stored on an
                            ULTRIX server, you may get the following
                            error message when you exit from MAIL:

                                Error writing to file:
                     /usr/users/username/Mail/mail/.pcsamailcache

              SOLUTION:     When you finish deleting messages, enter the
                            PURGE command before exiting from MAIL.

        3.13 Network Components and Remote Boot

              This section describes the new and changed features of
              PATHWORKS for DOS network components, guidelines for using
              network components, and ways to troubleshoot the known
              limitations.

        3.13.1 New and Changed Features

              The PATHWORKS for DOS network components have the following
              new and changed features:

              o  New and modified qualifiers for the USE command,
                 including:

                 -  Connection to InfoServer 100 CD-ROM services

                 -  Wildcard and ambiguous device support for printer
                    devices

              o  The Scheduler (SCH) offers the following:

                 -  The SCHK variant to save memory on 80286-based PCs
                    and above

                 -  /M qualifier to conserve memory on 80386-based PCs

              o  The Local Area Transport (LAT) offers the following new
                 features:

                 -  All parameters are now set using the LATCP program.

                 -  On both VMS and ULTRIX servers (DECnet only), you
                    can set up a printer queue which, over the LAT, sends
                    print jobs to a parallel printer attached to a PC.
                    LAT now supports port names and service names.

                    For more information, see the Client Installation and
                    Configuration Guide.

        3-30 Changes in PATHWORKS for DOS Version 4.1A
 







                 -  When a node stops advertising a service, LAT now
                    deletes information about that service. LAT does not
                    delete preferred services.

              o  PATHWORKS for DOS fixes a connection problem with the
                 Local Area System Transport (LAST) and LANSESS.

              o  Asynchronous DECnet supports both the Basic Redirector
                 and Enhanced Redirector.

        3.13.2 General Guidelines

              Note the following guidelines for using PATHWORKS for DOS
              network components:

              o  If you use remote boot using a remote boot diskette
                 and your remote boot LAD is a different size from your
                 remote boot diskette, then to read drive A:, you must
                 open and close the diskette drive door after remote
                 booting.

              o  The NDIS datalink does not work properly if there is a
                 "Bad or missing COUNTRY.SYS" error or any other error in
                 CONFIG.SYS just before loading PROTMAN.SYS.

              o  You cannot diskcopy from a LAD drive to a floppy drive
                 using the Zenith DOS (Version 3.3) version of DISKCOPY.

              o  LAT writes data, but does not read data, from the
                 parallel port. If you offer a PostScript printer or
                 plotter, the printer queue stalls waiting for data from
                 the PostScript printer.

              o  If you run STOPNET or unload the network with LAT loaded
                 and serving printers, then when LAT is reloaded, it
                 cannot use those printer ports.

                 If you unload the network when LAT is serving printers,
                 be sure to unload LAT (by entering the LAT/U command)
                 before unloading the network.

              o  If you manually modify STARTNET.BAT or manually create a
                 network startup file, you must run SETNAME after loading
                 the Basic Redirector.

                 Otherwise, your client cannot connect to file services.

                           Changes in PATHWORKS for DOS Version 4.1A 3-31
 







              o  The MEMMAN documentation in the Client Commands
                 Reference states you can use MEMMAN/U as an alternative
                 to STOPNET.BAT to unload the network. STOPNET.BAT uses
                 the MEMMAN/U command to do the actual unloading and
                 should be used to unload the network components after
                 using STARTNET to load the network.

              o  If you use the NET PRINT command with an ULTRIX printer
                 service and include the /PAGES qualifier, all the file's
                 pages are printed, regardless of the range you specify.

              o  The NET PRINT documentation in the Client Commands
                 Reference lists a /HELP qualifier. This qualifier is
                 not valid.

                 To get help on NET PRINT, use the NET HELP PRINT
                 command.

              o  Disk caches that run as EMS background programs are
                 not supported. When the network is in EMS, run the disk
                 cache in extended memory.

              o  Some applications make repetitive byte range locks on an
                 OS/2 server without freeing them. Other applications may
                 make excessive lock requests on different ranges. This
                 behavior can exhaust the lock database on the server.

                 This can be a problem in several ways: Applications with
                 valid lock requests can be denied a lock because the
                 server does not have any available locking database or
                 in the case of the OS/2 server, exhaustion of the lock
                 database is not reversible and necessitates a reboot of
                 the server.

                 The only solutions are to increase the size of the
                 locking database on the server until it is of sufficient
                 size not to be exhausted by application programs,
                 or to modify the application programs to have a more
                 reasonable locking strategy.

                 See the Microsoft LAN Manager User's Guide for MS
                 OS/2 for information on the MAXLOCKS parameter in the
                 LANMAN.INI file.

              o  The USE /SETDIR command qualifier is not supported on
                 application or common file services on a PATHWORKS for
                 VMS server.

        3-32 Changes in PATHWORKS for DOS Version 4.1A
 







                 The USE /SETDIR qualifier is supported on personal
                 services.

              o  When a network link to a service fails, the Redirector
                 automatically tries to reconnect to the service when you
                 try to access it again.

                 If you use the USE /SETDIR command to change the
                 associated directory for a connection or if you
                 connect directly to another directory through
                 your personal file service (for example, USE ?:
                 \\SERVR1\WRK:[REVIEWS]%USER1 *), the Redirector
                 reconnects you to your personal service, not the device
                 and directory you were connected to when the network
                 link failed.

                 To reestablish the association device and directory, use
                 USE/SETDIR.

              o  The SET PROTECTION=( . . . ) /DEFAULT command in DCL
                 and the NET ATTRIB M: /PROT=( . . . ) /DEF command are
                 independent of each other.

                 Files created under VMS keep the DCL protection
                 specified by SET PROTECTION. Files created from DOS
                 keep the default protection specified by NET ATTRIB.

        3.13.3 Problem Solving

              Note the following problems with PATHWORKS for DOS network
              components and their solutions:

              PROBLEM:      DECMOUSE.COM does not work when using NDIS.

              SOLUTION:     Load the DEPCA mouse driver, DECMOUSE.SYS,
                            before PROTMAN.SYS in CONFIG.SYS.

              PROBLEM:      Some older DEPCAs (Revs D, E, F, and H)
                            sometimes hang during a warm boot.

              SOLUTION:     Perform a cold boot.

              PROBLEM:      ROM checksum errors occur during startup with
                            a DEPCA installed.

              SOLUTION:     Turn off the machine and wait one minute
                            before turning it on again.

                           Changes in PATHWORKS for DOS Version 4.1A 3-33
 








              PROBLEM:      If you run a large application, such as
                            Microsoft Windows Version 3.0, before running
                            NETBIND, you get a "fail to bind" message and
                            the PC hangs when STARTNET.BAT runs.

              SOLUTION:     Run the DLLNDIS and NETBIND programs before
                            starting the other application.

              PROBLEM:      If your client is running DOS Version 4.0
                            with SHARE.EXE loaded, you may have problems
                            (hung system, sharing violations, or mount
                            and dismount errors) running applications
                            stored in file services.

              SOLUTION:     Use DOS Version 3.3 or 5.0.

              PROBLEM:      You get a Net 804 error while using LANSESS.
                            Under certain circumstances, LANSESS cannot
                            determine the correct number of buffers
                            available and does not allow data transfers.

              SOLUTION:     Add the following command line qualifiers on
                            the LANSESS line in the STARTNET.BAT file:

                                    %BOOT%\DECNET\LANSESS /W:1 /R:1

              PROBLEM:      You have poor network performance and get
                            "Drive not ready" errors for some Ethernet
                            boards (for example, the 3Com 3C503).















        3-34 Changes in PATHWORKS for DOS Version 4.1A
 








              SOLUTION:     Do the following:

                            1. Use the NCP SHOW EXEC CHAR command to
                               check the Receive pipe quota. The default
                               is 6. Set the Receive pipe quota to 2 with
                               the following command:

                                NCP> DEFINE EXEC RECEIVE PIPE QUOTA 2

                            2. If you load LAD, set the transaction size
                               to 2.

                               For example, change the LAD line in the
                               \DECNET\STARTNET.BAT file to:

                                    %BOOT%\DECNET\LAD.EXE /R:2 /W:2 /A:-1

                            3. If you load LANSESS, set the transaction
                               size to 2.

                               For example, change the LANSESS line in
                               the \DECNET\STARTNET.BAT file to:

                                    %BOOT%\DECNET\LANSESS.EXE /R:2 /W:2

                            4. Reboot the client for the changes to take
                               effect.

              PROBLEM:      If you enter the NET PRINT command and
                            include the /AFTER qualifier to specify the
                            date and time a job should be queued for
                            printing, the print job is queued at midnight
                            regardless of the time specified if both of
                            the following are true:

                            o  The system file service to which your
                               client is connected is on an ULTRIX
                               server.

                            o  The date you specify is the same as the
                               current date.

              SOLUTION:     Specify only the time (and not the date) that
                            the job should be queued for printing.

              PROBLEM:      LATCP fails to add a preferred service.

                           Changes in PATHWORKS for DOS Version 4.1A 3-35
 








              SOLUTION:     Delete the old \DECNET\DECLAT.DAT file and
                            rerun LATCP to create a new DECLAT.DAT file.

              PROBLEM:      The USE command displays file services
                            without an associated drive letter. For
                            example:

                            Status  Dev   Type   Connection name
                            ------  ---   ----   ------------------
                                    I:    FILE   \\SERVR1\PCSAV41
                            ERROR         FILE   \\SERVR2\PCCOMMON
                                          FILE   \\SERVR3\PCCOMMON

              SOLUTION:     This problem results from a TSR application
                            not closing open files when disconnecting
                            from a network drive. This condition does not
                            cause any operational problems. You cannot
                            delete the error from the display.

              PROBLEM:      When using NET PRINT to display print jobs
                            on printer service (for example: NET PRINT
                            \\server\service_name), you get the following
                            error:

                            Invalid queue name: service_name

              SOLUTION:     Connect to the printer service with the
                            USE command (for example, USE LPT1:
                            \\server\service_name) and run NET PRINT
                            again.

        3.13.4 CTERM

              Note the following guidelines when using CTERM:

              o  Command line editing over a CTERM connection does not
                 support command lines that contain tab characters.

              o  When using a CTERM SETHOST connection, the terminal is
                 set to the system default terminal type.

                 To set the correct terminal type on VMS, enter the SET
                 TERMINAL/INQUIRE command.

              o  When you use the VMS command recall feature immediately
                 after switching from one CTERM session to another, the
                 first line that is recalled may be from the first CTERM
                 session.

        3-36 Changes in PATHWORKS for DOS Version 4.1A
 







              o  When you enter command lines that are longer than one
                 line, the <Delete> key works only on the second line.

                 You cannot delete the input on the first line.

        3.13.5 Data Test Sender/Data Test Receiver (DTS/DTR)

              Note the following guidelines when using the Data Test
              Receiver (DTR) and the Data Test Sender (DTS):

              o  DTR and DTS are tools that test the network and measure
                 its performance.

                 The PATHWORKS for DOS documentation does not
                 include information about DTR or DTS. However, the
                 \DECNET\DTS.TXT file describes these tools.

              o  Under Microsoft Windows, DTR does not run while
                 iconized.

              o  DTS Data and Interrupt Echo tests may fail when run
                 against DECnet-RSX and DECnet-VAX DTRs. The symptom is
                 a sequence number failure in which the sequence number
                 received is higher than the one expected.

                 DTR Version 4.0 fails if messages are received faster
                 than they can be transmitted. This is an application-
                 level logic bug. DTR uses a fixed number of buffers and
                 does not prevent receiving new messages if old ones have
                 not been sent. Eventually, an incoming receive message
                 overwrites an outgoing message, effectively losing the
                 unsent messages.

              o  If you use <Ctrl/C> repeatedly while your PC is running
                 DTR, the following message may be displayed followed by
                 the DOS prompt:

                 run-time error R6000 -- stack overflow

                 C:\>

                 Use NCP to disconnect the DTR link before rerunning DTR.

              o  Running DTR/DTS ECHO test in user buffer mode with
                 buffers greater than 512 Kbytes hangs the system. (SINK
                 test does not have this problem.)

                           Changes in PATHWORKS for DOS Version 4.1A 3-37
 







        3.13.6 NETBIOS and DNP

        3.13.6.1 New and Changed Features

              DNP/NETBIOS includes the following changes:

              o  DNP Version 4.1 is smaller and faster than Version 4.0.

              o  DNP has only two variants: DNNETH and DDNETH (which is
                 the debug version).

              o  DNP supports only NIOCB. It does not support the old
                 IOCB format. Applications must convert to NIOCB.

              o  DNP now uses EMSLOAD to load into EMS.

              o  DNP does significantly more parameter checking than
                 previous releases. It is possible for applications
                 to run under previous releases and fail with Version
                 4.1. If you have problems, first check all calls with
                 the definitions specified in the DECnet Programmer's
                 Reference.

        3.13.6.2 Guidelines

              Note the following guidelines when using NETBIOS and DNP
              Version 4.1:

              o  DNP Version 4.1 requires the Version 4.1 datalink.

                 Otherwise, the following NCP commands do not work:

                    SHOW LINE CHAR
                    SHOW LINE COUNTERS

              o  DNP does not add local names.

                 For the USE and PERMIT commands to work, you must run
                 SETNAME first, which sets the local names for you.

              o  DNP uses EMSLOAD to load into EMS. Use the following
                 command line:

                 C:\> EMSLOAD DNNETH.EXE

              o  DNP does not support the IOCB data structures.
                 Applications must convert to NIOCB.

              o  Unloading DNP with the NCP SET EXEC STATE OFF command is
                 no longer supported. Instead, use the MEMMAN/U command
                 to unload the network.

        3-38 Changes in PATHWORKS for DOS Version 4.1A
 







              o  The DNP/NETBIOS combination in EMS or DNP in EMS can
                 produce receive data overruns when doing file transfers
                 of 4 Kbytes or greater. This generally occurs when
                 running at 9600 baud or greater. This is not a fatal
                 error.

        3.13.6.3 DECnet/SNA Gateway NETBIOS Access Routine

              Note the following guidelines when running the DECnet/SNA
              Gateway NETBIOS Access Routine:

              o  All problems reported to your Digital representative
                 must include the following:

                 -  A description of the problem with explicit directions
                    for reproducing it

                 -  The current SNAGNI configuration file

                 -  The current 3270 emulator configuration file

                 -  A NETTRACE file in binary format

                 To create the required NETTRACE file, enter the
                 following DCL command:

                 $ TRACE START/OUT=NETTRACE.OUT gateway_name::NSP -
                 _$ /MAX=300 /CAPT=max_rusize

                 ________________________________________________________
                 Variable      Description                               

                 gateway_name  The DECnet node name of the gateway you
                               are using

                 max_rusize    The value for the MAX_RUSIZE parameter in
                               the SNAGNI configuration file             

                 For more information about using NETTRACE, see the
                 DECnet/SNA Gateway Management Guide.

                 Use the debug version of SNAGNI (called DSNAGNI.EXE)
                 from \DEBUG directory on the system file service and
                 try to reproduce the problem. If you reproduce the
                 problem, send the log file which is created to your
                 Digital representative.

                 For information on using DSNAGNI.EXE, see the
                 DSNAGNI.DOC file in the \DEBUG directory.

                           Changes in PATHWORKS for DOS Version 4.1A 3-39
 







              o  If you are using an IRMALAN DOS Client for DECnet/SNA
                 Gateway:

                 -  The LU numbers on the status line of the IRMALAN
                    workstation do not represent the actual LU number
                    of the session between the terminal emulator and the
                    host.

                    The emulator status line always shows the LU numbers
                    as starting with LU number 2 and increasing by 1 for
                    each additional session up to a maximum of 6 for a
                    fully configured workstation.

                 -  There is currently no support for DCA's Ram Expander
                    product.

        3.13.7 Network Device Utility (NDU)

              Note the following guidelines when using the Network Device
              Utility (NDU):

              o  Version 4.1.00 of NDU works only with Version 4.1.00 of
                 NDDRV.SYS and NPDRV.SYS.

                 It is not compatible with older versions of NDDRV.SYS
                 and NPDRV.SYS.

              o  You cannot diskcopy to or from NDU disks.

              o  NDU does not work properly with TOPS-10 and TOPS-20
                 systems because of limitations on the TOPS-10 and
                 TOPS-20 File Access Listener (FAL).

                 For virtual disks, FAL must support image mode
                 sequential files with 512-byte, fixed-length records
                 accessed randomly by relative record number.

                 For virtual printers, FAL must support variable-length
                 ASCII sequential files with implied CR/LF (carriage
                 return line feed) on record management systems (such as
                 VMS) and stream files on stream systems (such as DOS).

              o  Systems using IBM DOS Version 4.00 may hang when you run
                 NDU.

                 To avoid this problem, do one of the following:

                 -  Get the correct CSD upgrade from IBM.

        3-40 Changes in PATHWORKS for DOS Version 4.1A
 







                 -  Upgrade your system to a supported version of DOS
                    (see the System Support Addendum that comes with the
                    software kit).

                 -  Load NDDRV.SYS from your CONFIG.SYS file before
                    running NDU.

        3.13.8 Virtual Printer Driver (NPDRV.SYS)

              Using the virtual printer with the background print spooler
              can cause the system to hang.

        3.13.9 Network File Transfer (NFT)

              When printing remote files using wildcards, the Network
              File Transfer utility (NFT) prints only the first file that
              satisfies the wildcard specification.

        3.14 SETHOST

              The following changes have been made to SETHOST:

              o  Setting the keyboard type from the command line

              o  Setting the display to color or monochrome from the
                 command line

              o  Entering the name or address of the system you want to
                 connect to, from the Communications Setup screen

              o  Script language keywords for the arrow keys

              Note the following when using SETHOST:

              o  When connecting to a VMS system running the VMS/ULTRIX
                 Connection (UCX), older versions of UCX require pressing
                 <Return> after SETHOST displays the "Connecting to
                 Service:" message.

              o  When using the VAXTPU editor with SETHOST running over
                 LAT, if you hold down a function key or keypad key too
                 long, the terminal session may freeze. If the session
                 freezes, you can create a new session by pressing the
                 <F3> key to access the SETHOST setup menus.

                 To prevent this problem, try one or more of the
                 following:

                 -  Do not use auto-repeat excessively.

                 -  Use the EDT editor instead.

                           Changes in PATHWORKS for DOS Version 4.1A 3-41
 







                 -  Use CTERM as your transport.

              o  SETHOST has problems with the DOS SHARE utility when you
                 run more than one copy of SETHOST. Therefore, do not run
                 SHARE in this circumstance.

              o  When you spawn to a DOS shell (by using <Ctrl/F9>), DOS
                 automatically closes all open files.

                 For example, if you logging a session and then switch
                 to a DOS shell, DOS closes the session logging file.
                 When you return to SETHOST from that shell, SETHOST
                 incorrectly displays "Receive: On" because it does not
                 know that DOS closed the file.

                 In this case, to continue session logging to the
                 original (now closed) file, do the following:

                 1. Press <Ctrl/F3> to return SETHOST to the correct
                    state.

                 2. Press <Ctrl/F1> to restart session logging.

                 3. Specify the file name of the session logging file.

                 4. Select Append.

        3.15 Maintenance Operations Protocol (MOP)

              The Maintenance Operations Protocol (MOP) is a load and
              dump capability to support Digital's terminal servers and
              routers.

              MOP.EXE is a foreground application that works as a server
              listening for load or dump requests. It lets you trigger
              a reboot of the target terminal server or router. It
              includes a configuration utility to manipulate the database
              containing the load and dump information for specific
              nodes.

        3.16 DOS Enhancements

              This section describes the known limitations of the DOS
              enhancements provided by PATHWORKS for DOS.

              o  Do not load KEYBRD, XONXOFF, or DECMOUSE into Upper
                 Memory Blocks (UMBs).

                 For example, do not use Quarterdeck QEMM's LOADHI or DOS
                 Version 5.0 LOADHIGH to load these functions in UMBs.

        3-42 Changes in PATHWORKS for DOS Version 4.1A
 







              o  KEYBRD:

                 -  Do not use KEYBRD with other keyboard mapping
                    programs.

                    If KEYBRD is running and you load a TSR keyboard
                    program, such as PROKEY, your PC may hang.

                 -  Load KEYBRD before you load any other TSR keyboard
                    programs.

                    This is because KEYBRD does not pass keystrokes to
                    other TSR keyboard programs.

                 -  KEYBRD handles special keystrokes differently from
                    the native keyboard BIOS program.

                    For example, <Ctrl/Alt/Delete> is handled by KEYBRD
                    and not passed to the BIOS program.

              o  DECMOUSE:

                 -  DECMOUSE treats all EtherWORKS (DEPCA) network
                    controllers the same. Therefore, load DECMOUSE.SYS or
                    DECMOUSE.COM only on cards that have the appropriate
                    mouse port.

                    If DECMOUSE runs on a card that does not have the
                    appropriate mouse port, the network software may not
                    initialize correctly.

                 -  When you exit from applications, DECMOUSE may display
                    a text cursor on the screen. This is a cosmetic
                    problem and does not affect the PC's operation.

        3.17 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.

                           Changes in PATHWORKS for DOS Version 4.1A 3-43
 







              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.

        3.18 Programming Components

              This section describes guidelines for using the PATHWORKS
              for DOS programming components. These components are
              discussed in detail in the DECnet Programmer's Reference,
              which is ordered separately.

        3.18.1 DECnet Programmer's Reference Changes

              The DECnet Programmer's Reference (ordered separately)
              includes the following new information:

              o  The MSG_USRBUF flag, used with the send and receive
                 routines, is now supported for the C Programming
                 Library. This flag is used to send and receive large
                 data buffers (up to 64 Kbytes).

              o  The MSG_TASKSWITCH flag is added to the Assembly
                 Programming Interface. The MSG_TASKSWITCH flag provides
                 more efficient task switching and may be necessary when
                 using a nonblocking I/O call.

        3-44 Changes in PATHWORKS for DOS Version 4.1A
 







        3.18.2 Additions to the Documentation (dnet_ask_for_password)

              dnet_ask_for_password

              Prompts for a password.

              Syntax:

              #include <dn.h>
              #include <dnfundef.h>

              void dnet_ask_for_password (acc_data, node1, in_len)
              struct accessdata_dn *acc_data;
              char *node1;
              int *in_len;

              Description:

              The dnet_ask_for_password is called by dnet_conn if a
              user name was specified without a password. You can use
              a different routine, using the same calling sequence, in
              place of the routine supplied in the library.

              The version of dnet_ask_for_password supplied for Microsoft
              Windows is a placeholder which always supplies a null
              password. If prompting is desired, you can use your own
              routine.

              Input Arguments:

              acc_data    The address of an access_data_dn structure
                          which has the acc_user and acc_userl fields
                          filled in.

              node1       The address of a string containing the node
                          name.

              inlen       The address of an integer that will be filled
                          in.

              Output Arguments:

              acc_data    The filled in acc_pass and acc_passl fields.

              inlen       The length (integer) of the password entered by
                          the user.

              Return Value:

              None

                           Changes in PATHWORKS for DOS Version 4.1A 3-45
 







        3.18.3 Transparent File Access Utility (TFA)

              Observe the following guidelines when using the Transparent
              File Access utility (TFA):

              o  There is an interaction between all versions of TFA and
                 the Microsoft C runtime library, which can cause ASCII
                 data to be sent as binary.

              o  In DOS Version 4.0:

                 -  The TYPE command cannot access a remote file with TFA
                    if the remote file is not in the current directory.

                 -  The COPY command cannot access a remote file with TFA
                    if the remote file to be copied is not in the root
                    directory and the COPY command is not issued from C:.

                 -  COMMAND.COM uses undocumented calls for file access
                    instead of the standard, documented calls supported
                    by TFA.

              o  TFA supports some calls made from the DOS command line.
                 It supports all calls made from application programs.

                 For a complete list of the DOS calls supported by TFA,
                 see the DECnet Programmer's Reference.

              o  Applications using TFA or TTT may produce unpredictable
                 results when run under Microsoft Windows 3.0 or 3.1.

                ________________________ Note ________________________

                For remote file access, use NFT TYPE and NFT COPY,
                because NFT does not have the restrictions of TFA.

                ______________________________________________________

        3.18.4 Network Applications Using EMS

              Several programming design restrictions are required for
              programs that make network calls to NETBIOS or the DECnet
              socket library. These restrictions apply when the network
              application uses EMS and PATHWORKS is loaded into EMS.

              Network control blocks such as NCBs or NIOCBs must not
              reside in EMS. Network callback addresses cannot be in
              EMS. When an application receives a network callback, the
              EMS page frame cannot be changed. In other words, no EMS

        3-46 Changes in PATHWORKS for DOS Version 4.1A
 







              mapping in the background is supported. EMS mapping by
              applications is supported only in the foreground.

        3.18.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.

                ______________________________________________________

        3.18.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.

              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

                           Changes in PATHWORKS for DOS Version 4.1A 3-47
 







                 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

                 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

        3-48 Changes in PATHWORKS for DOS Version 4.1A
 







                 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

        3.18.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

                           Changes in PATHWORKS for DOS Version 4.1A 3-49
 







              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.

        3.18.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.

        3.18.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

        3-50 Changes in PATHWORKS for DOS Version 4.1A
 







                 If the LAT ports are configured, the resulting display
                 includes lines like this:

                 /dev/tty04: character special (39/4) LAT #0 terminal #4

        3.18.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.

        3.18.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

                           Changes in PATHWORKS for DOS Version 4.1A 3-51
 







                 In place of tty##, use the tty number you chose when you
                 create the LAT port (for example, tty04).

        3.18.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).

        3.18.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.

              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.

        3-52 Changes in PATHWORKS for DOS Version 4.1A
 







                 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.

                    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).


                           Changes in PATHWORKS for DOS Version 4.1A 3-53
 







        3.18.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

        3.18.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.

        3.18.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.







        3-54 Changes in PATHWORKS for DOS Version 4.1A
 










                                                                        A
        _________________________________________________________________

                                                               Trademarks


              The following are trademarks of Digital Equipment
              Corporation:

              DDIF, DEC, DECnet, DECnet-RSX, DECnet-VAX, DECwindows,
              Digital, LN03 ScriptPrinter, PATHWORKS, RSX, TOPS-10,
              TOPS-20, ULTRIX, VAX, VMS, VMS/ULTRIX Connection, and the
              DIGITAL logo.

              The following are third-party trademarks:

              3Com, EtherLink, EtherLink II, and EtherLink Plus are
              registered trademarks of 3Com Corporation. COMPAQ is
              a registered trademark of COMPAQ Computer Corporation.
              Hewlett-Packard, HP, Laserjet, and Vectra are registered
              trademarks of Hewlett-Packard Corporation. IBM, OS/2,
              and Personal Computer AT are registered trademarks of
              International Business Machines Corporation. IRMA is a
              registered trademark of Digital Communications Associates,
              Inc. Motif is a registered trademark of Open Software
              Foundation, Inc. NetWare is a registered trademark of
              Novell, Inc. Proteon is a registered trademark of Proteon
              Associates, Inc. PostScript is a registered trademark of
              Adobe Systems, Inc. UNIX is a registered trademark of
              UNIX System Laboratories, Inc. Windows is a trademark
              and Microsoft, MS, and MS-DOS are registered trademarks
              of Microsoft Corporation. Zenith is a registered trademark
              of Zenith Electronics Corporation.

              Copyright © 1992 by Digital Equipment Corporation.

              All rights reserved.





                                                           Trademarks A-1
 










                                                                         
                                                                         

                                                                         


                                                               
                          

                                                                    
                                                                   
                                                                       
                           

                                                       

                                                                   
                                                                  
                                                                    
                                                                      
                                                                   
                                                                   
                                                                    
                                                                        
                                                                   
                                                                   
                                                                       
                                                                      
                                                                   
                                                                   
                                                                     
                                                                        
                                                

                                                                

                                  







