















                     PATHWORKS_for_DOS_____________________________
                     Release Notes


                     October 1991







                     Revision/Update Information: This document
                                                  supersedes the
                                                  PATHWORKS for DOS
                                                  Version 4.0 Release
                                                  Notes

                     Software Version:            PATHWORKS for DOS
                                                  Version 4.1





	     _____________________________________________
             September, 1991

             Copyright Digital Equipment Corporation  1991.

             All rights reserved.

             The following are trademarks of Digital Equipment Corporation:

	     DDIF, DEC, DEClaser, DECnet, DECnet-DOS, DECrouter, DECstation,
	     DECwindows, DEPCA, Digital, EtherWORKS, LA50, LA75 Companion,
	     LAT, LN03, LN03 ScriptPrinter, PATHWORKS, PrintServer, ULTRIX,
	     VAX, and VMS

	     3Com, EtherLink, EtherLink II, and EtherLink Plus are registered
	     trademarks of 3Com Corporation. 

	     COMPAQ is a registered trademark of COMPAQ Computer Corporation.

	     HP, Hewlett-Packard, and Vectra are registered trademarks of 
	     Hewlett-Packard Corporation. 

	     IBM, PS/2, Personal Computer AT, Personal System/2, and OS/2 are
	     registered trademarks of International Business Machines
	     Corporation.

	     IRMA is a registered trademark of Digital Communications
	     Associates, Incorporated.

	     Madge is a trademark of Madge Networks, Ltd.

	     Motif is a registered trademark of Open Software Foundation, Inc.

	     PostScript is a registered trademark of Adobe Systems, Inc.

	     NetWare is a registered trademark of Novell, Incorporated.

 	     Windows is a trademark and MS, MS-DOS, are registered trademarks
	     of Microsoft Corporation.

	     Motif is a registered trademark of Open Software Foundation, Inc.

	     Olicom is a registered trademark of Ing C. Olivetti.

	     Zenith is a registered trademark of Zenith Electronics Corporation.




 











         ________________________________________________________________

                                                                  Preface



         These release notes contain information that you should read
         before you install PATHWORKS for DOS Version 4.1.

         In these release notes, Chapter 1 describes new functionality.
         The remaining chapters provide:

         o  Guidelines for using the software that are not in the
            documentation set

         o  Ways to troubleshoot known problems and limitations
























         vi

 









                                                                        1
         ________________________________________________________________

                              What's New in PATHWORKS for DOS Version 4.1



         This section describes new features and changes:

         o  Installation

         o  Configuration

         o  Token Ring support

         o  LAN Manager Version 2.0 support

         o  DOS Version 5.0 and Task Switcher support

         o  PATHWORKS for DOS (NetWare Coexistence) support

         o  Microsoft Windows Version 3.0 support

         o  PC DECwindows Motif

         o  Network utilities and remote boot

         o  Mail

         o  DECnet components

         o  SETHOST

         o  MOP (Maintenance Operations Protocol)

         o  Programming components

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

         o  PATHWORKS for DOS Version 4.1 is shipped on either 5 1/4-inch
            high density or 3 1/2-inch low-density diskettes labeled:

                               PWRKS V4.1 for DOS 1/n

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

                                                                      1-1

 






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

         The VMS and ULTRIX installation procedures have not changed.

     CONFIGURATION
     -------------
         Client configuration has changed in the following areas:

         Netsetup
	 --------
         Netsetup now includes:

         o  Token Ring configuration support.

         o  Separate Memory Configuration menu

            The memory configuration information has been removed
            from the Client Profile screen and moved to the Memory
            Configuration Menu.

            You access the Memory Configuration Menu from the Client
            Profile screen in Intermediate and Advanced mode.

         o  Support for the following Redirectors:

            -  Basic Redirector

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

            -  Enhanced Redirector

               The Enhanced Redirector recognizes all PATHWORKS for DOS
               commands. It also allows DOS clients to use servers
               that offer full Microsoft 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.

         o  Full LAN Manager Version 2.0 Support

            Full LAN Manager Version 2.0 Support uses the Enhanced
            Redirector and recognizes all PATHWORKS for DOS commands.
            It also allows DOS clients to use servers that offer full
            Microsoft LAN Manager Version 2.0 functionality. With the
            Full LAN Manager Version 2.0 Support option, Netsetup copies

         1-2

 






            all the LAN Manager files to the local hard disk. This option
            is available only when the destination is a hard disk.

         o  DOS Version 5.0 support

            Netsetup automatically configures the DECnet client software
            to work in a DOS Version 5.0 environment when you specify DOS
            Version 5.0 in the DOS Version field. The DOS Version field
            is available in the Intermediate and Advanced mode.

         o  PATHWORKS for DOS (NetWare Coexistence) support

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

            The feature is only available when PATHWORKS for DOS (NetWare
            Coexistence) is installed on the server. PATHWORKS for
            DOS (NetWare Coexistence) must be purchased and installed
            separately.

         o  Support for DECnet disk and print services print.

            The Memory Configuration Menu includes support for:

            -  Network Disk Driver (NDDRV.SYS)

               NDDRV.SYS gives you access to disk services over local
               area networks, wide area networks, and over asynchronous
               connections.

            -  Network Print Driver (NPDRV.SYS)

               NPDRV.SYS gives you access to print services over local
               area networks, wide area networks, and over asynchronous
               connections.

         o  Network CDROM support

            CDROM support gives you access to CDROM drives on an
            InfoServer 100. The InfoServer 100 hardware must be ordered
            and installed separately.

            You add CDROM support by selecting MSCDEX on the Memory
            Configuration Menu.

         o  Ethernet adapter support

            -  Netsetup includes LAN Manager supplied NDIS drivers and
               PROTOCOL.INI stubs for a number of Ethernet and Token Ring
               controller cards. See Netsetup for a full list of cards.

                                                                      1-3

 






            -  If you are using a DEC EtherWorks or DEPCA card, you can
               now choose between the native datalink (DLLDEPCA) or NDIS
               (DLLNDIS) configuration.

         DOSLOAD
         -------
         DOSLOAD now includes:

         o  The ability to install a version of DOS from a network drive.
            This function lets you reinstall a DOS from a PATHWORKS for
            DOS Version 4.0 service to a Version 4.1 service.

         o  Loading DOS Version 5.0 to the system file service.

         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.

         See the Client Commands Reference Manual for more information on
         these utilities.

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

         o  DDNDCPPC.EXE-the debug version of asynchronous DNP

         o  DDNETH.EXE-the debug version of ethernet DNP

         o  DEBUG.DOC-undocumented debugging features of various
            PATHWORKS for DOS V4.1 components

         o  DSNAGNI.DOC- debugging features of DSNAGNI.EXE

         o  DSNAGNI.EXE-the debug version of SNAGNI.EXE

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

         o  SHOW.DOC-a list of SHOW.EXE features

         1-4

 






         o  SHOW.EXE-a tool to aid in the debugging and analysis of
            PATHWORKS configurations.

         o  SHOW.HLP- SHOW help file

     TOKEN RING SUPPORT
     ------------------
         The PATHWORKS for DOS Version 4.1 Token Ring support allows the
         DECnet process to work over a Token Ring network. To the user,
         Token Ring network access works in the same way as Ethernet
         network access.

     DOS VERSION 5.0 AND TASK SWITCHER SUPPORT
     -----------------------------------------
         PATHWORKS for DOS Version 4.1 includes DOS Version 5.0 support.
         This support includes the DOS Task Switcher.

     PATHWORKS FOR DOS (NetWare COEXISTENCE) SUPPORT
     -----------------------------------------------
         PATHWORKS for DOS Version 4.1 includes the ability to configure
         a client to access the PATHWORKS for DOS (NetWare Coexistence)
         product. PATHWORKS for DOS (NetWare Coexistence) must be
         purchased and installed separately.

      MICROSOFT WINDOWS 3.0 SUPPORT
      -----------------------------
         PATHWORKS for DOS Version 4.1 support for Microsoft Windows 3.0
         includes new or changed features for the following:

         o  WIN3SETU Installation/Configuration Utility, including:

            -  Ability to restart WIN3SETU with the F8 key

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

         o  Terminal Access Library (TRMNLAXS.DLL), which gives Microsoft
            Windows 3.0 applications access to LAT, CTERM, and TELNET
            (TCP/IP) sessions. The documentation in the Programmer's
            Reference Book Appendix J has also been updated.

         o  VT320 terminal emulator now includes:

            -  Telnet support for the Windows VT320 Terminal Emulator.
               When used with the PATHWORKS for DOS (TCP/IP) product,
               VT320 can connect over Telnet.

            -  Script language improvements for the Windows VT320
               Terminal Emulator.

                                                                      1-5

 






               Added script language enhancements from the DOS-based
               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 your boot directory.
               Previous versions of VT320 wrote the log file to the
               current directory.

         o  The DEPCA mouse driver for Windows (DECMOUSE.DRV) now
            supports NDIS in addition to 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 (all new for V4.1), 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  NFT (Network File Transfer) for Windows

            -  NFT now uses the Windows 3.0 Help facility.

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

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

         o  FAL (File Access Listener) for Windows now uses the Windows
            3.0 Help facility.

         o  Windows 3.0 PIF support for the SETHOST Terminal Emulator.
            With Windows you can hot key between SETHOST and other
            applications, including other copies of SETHOST. SETHOST
            can be run in a window in 386 Enhanced Mode.

         o  Performance improvements in DECNET and NETBIOS operations
            have been made because both the VDNET.386 and VNETBIOS.386
            Virtual Devices for DECNET and NETBIOS can now convert syn-
            chronous 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.   



         1-6

 




	    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 PATHWORKS for DOS V4.0 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.

           ___________________________________________________________

     PC DECWINDOWS MOTIF
     -------------------
         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. It
            allows DWDOS386 to better coexist with XMS memory managers
            such as HIMEM.SYS.

         o  DWDOS286 supports off-screen images larger than 64 KB,
            allowing DECpaint to be used on a 286 machine.

     NETWORK COMPONENTS
     ------------------
         The PATHWORKS for DOS network components have the following new
         features:

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

            -  Connection to InfoServer 100 CDROM services

            -  Wildcard and ambiguous device support for printer devices

                                                                      1-7

 






         o  SCH (Scheduler) offers the following:

            -  The SCHK variant. SCHK saves memory on 80286-based PCs and
               above.

            -  /M switch to conserve memory on 80386-based PCs.

         o  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
               the use of both port names and service names.

               See the Client Installation and Configuration Guide for
               more information.

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

         o  DNP/NETBIOS includes the following changes:

            -  DNP Version 4.1 is smaller and faster than DNP Version 4.0

            -  It has only two variants: DNNETH and DDNETH. DDNETH is the
               debug version.

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

            -  Now uses EMSLOAD to load into EMS.

	    -  DNP does significantly more parameter checking than previous
	       releases.  It is possible for applications to run under earlier
	       releases and fail with 4.1.  If you experience problems, please
	       first carefully check all calls with the definitions specified
	       in the Programmers Reference Manual.

         o  Asynchronous DECnet supports both the Basic and Enhanced
            Redirector.

     MAIL
     ----
         MAIL has the following new features:

         o  The MAILCHK utility now accepts parameters such as node
            names, user names, and passwords. See Chapter 7 for
            information on MAILCHK.

         1-8

 






     SETHOST
     -------
         The following changes have been made to SETHOST:

         -  Ability to set the keyboard type from the command line.

         -  Ability to set the display to color or monochrome from the
            command line.

         -  Ability to enter the name or address of the system the user
            wants to connect to from the Communications Setup screen.

         -  Script language now includes keywords for the Up, Down, Left,
            and Right arrow keys.

     MOP
     ---
         MOP (Maintenance Operations Protocol) is a load and dump
         capability for supporting 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 the user
         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.

     PROGRAMMING COMPONENTS
     ----------------------
         The DECnet Programmer's Reference Manual (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 KB).

         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.




                                                                      1-9

 









                                                                        2
         ________________________________________________________________

                                           Installation and Configuration



         This section contains:

         o  Guidelines for installing and configuring PATHWORKS for DOS
            Version 4.1 that are not included in the documentation

         o  Ways to troubleshoot the known problems and limitations of
            the software.

     UPGRADING FROM PREVIOUS VERSIONS OF PATHWORKS
     ---------------------------------------------
         Not the following guidelines for upgrading to PATHWORKS for DOS
         Version 4.1:

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

            -  Before starting the upgrade, rename or copy the PCSAINFO.DAT
               file in the existing system file service to a file with a
               different name (OLDINFO.DAT for example). 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
               VPATHWORKS for DOS Version 4.0                     V4.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
               NNetware Coexistence Installed v1.0

            -  Perform the upgrade. Installing PATHWORKS for DOS Version
               4.1 to an existing file service creates a new PCSAINFO.DAT
               file.

                                                                      2-1

 
            -  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. 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
               NNetware Coexistence Installed v1.0

         o  If you are running PATHWORKS for DOS Version 4.0 and DOS
            Version 5.0 on your client, do the following to upgrade to
            PATHWORKS for DOS Version 4.1:

            -  Use Netsetup to upgrade your key disk to PATHWORKS for DOS
               Version 4.1.

            -  BEFORE you reboot, type the following DOS SETVER commands:

               setver redir.exe /delete
               setver use.exe /delete
               setver memman.exe /delete
               setver lad.exe /delete
               setver show.exe /delete
               setver netsetup.exe /delete

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

            -  Reboot your PC for the changes to take effect.

     DISKETTE INSTALLATION
     ---------------------
         If you have the diskette kit for hard disk and OS/2 server
         installation, note the following:

         o  If you are re-installing 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 F4 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 typing EXIT.
	    Typing EXIT from another drive causes the installation to fail.

         2-2

 



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

            -  Delete all read-only and hidden PATHWORKS files.

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

            -  Install PATHWORKS for DOS Version 4.1

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

     NETSETUP UTILITY
     ----------------
         Observe the following guidelines:

         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 Installation and Configuration
            Guide.

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

	 o  When using the Enhanced Redirector:

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

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

              To use the Enhanced Redirector:

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

              2. Reboot the client

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

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

                                                                      2-3

 


              Enter your password and hit return after the SYS0318 message
              is displayed. You are not prompted to enter the password and
              your input is not echoed on the screen. Once 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 the an error message
	      similar to the following:

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

	      Enter the password and press RETURN for the startup procedure
	      to continue.

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

	      netpopup = services\netpopup

	      This line MUST be before the messenger entry. 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

              You must be configured for Full LANMAN 2.0 Support to use
              Netpopup.

         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  If, at any time, F7 does not function properly, use F8 to
            restart the configuration.

         o  Before running Netsetup to create a key diskette, check
            the AUTOEXEC.BAT file for DOS APPEND commands. If you find
            the APPEND commands, add the /PATH:OFF switch to the append
            command line. For example:

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


         2-4



            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. Failure to remove or modify the APPEND
            commands could cause 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  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 the Digital Mouse.
           DECMOUSE.SYS and DECMOUSE.COM are located in the \DOSENH
           directory on the PCSAV41 file service.

           If you are upgrading a client that already loads the
           Digital Mouse, 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. For example EMSLOAD LAD >C:\NET.LOG
	    produces the following error:

	    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.


                                                                      2-5



            -  When formatting diskette to be used as a floppy remote
	       boot diskette, so 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 earlier versions of PATHWORKS
	       for VMS do not recognize the attempt to register the
	       workstation under V4.1.
 
	 o On some monochrome monitors, particularly portables, the
	   fields in the MEMORY CONFIGURATION MENU are in inverse video.
	   If this is the 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 - 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 and
	   the Do Not Load field appears highlighted. Use the the
	   non-highlighted field to load the components.

         o  With PATHWORKS for DOS (TCP/IP):

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

               help
               help $*
                   help $*

               Change the last line of the section as follows:

               help
               help $*
                   helpd $*

               This change eliminates a conflict with the DOS version 5.0
               HELP command.

	    -  You can use the internetnames parameter in the [Rfcnetbios] 
               section of your PC's 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 allows you to connect to 8 systems not in your
	       subnet.


         2-6



	       The default value for this parameter is 4.  You 
               can edit this parameter in the PROTOCOL.INI file and specify 
               any value from 0 to 32.Sample use of internetnames in
	       PROTOCOL.INI:

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

	   -  If the client is configured for Full LANMAN 2.0 Support for the
	      TCP/IP transport, you will not be able to use the net load or
	      net save LAN Manager commands to load or save a profile. Using
	      these commands gives you the following message:

	      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:

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




         Note the following problems and their solutions:
         ------------------------------------------------
           PROBLEM: The screen may be unreadable after invoking
           Netsetup.

           SOLUTION: Press F10 twice to exit 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 that contains over 59
           characters (up to 116 characters), edit the PROTOCOL.INI
           file, find the following field, and type the desired domain
           name between the quotation marks:

           DOMAIN = ""

								       2-7
                                                                      



           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 stops STOPNET.BAT from deleting the
	   reload.ini context file. The context file is typically found in
	   \DECNET 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:

	           USE /LOAD <path>reload.ini /LOG


     DOSLOAD
     -------
         Note the following 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. system file service.

           SOLUTION: To remove 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:

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


 



           2-8

                                                                      






                                                                        3
         ________________________________________________________________
						        Token Ring Support
                                                       


         This section describes:

         o  Setting the Station Address

         o  Using Proteon Token Ring Controllers

         o  Using Madge Token Ring Controllers

	 o  Using IBM Token Ring Controllers

     SETTING THE STATION ADDRESS
     ---------------------------
         DECnet Phase IV requires that every node changes it's hardware
         address to the station address. The station address uses the
         following format:

         AA-00-04-00-XX-YY.

         The variables XX and YY are based on the DECnet node number
         (area.node number).

         If you are using an NDIS driver that supports the SetStationAddress
         function, the datalink layer (DLLNDIS) and the DECnet network
         process (DNNETH) set the station address automatically.

         If you are using an an NDIS driver that does not support
         the SetStationAddress function, the station address must be
         set in the PROTOCOL.INI file. Appendix C of the PATHWORKS
         for DOS Installation and Configuration Guide describes the
         SetStationAddress function and how to set the station address
         manually.

     USING PROTEON TOKEN RING CONTROLLERS
     ------------------------------------
         If you are using either the NDIS139.DOS or NDIS199.DOS device
         drivers, you need to upgrade the device drivers to the
         RapiDrivers which are available from Proteon.  File names
         for the RapiDrivers are NDIS39XR.DOS (for the Proteon 1390
         AT bus controller) and NDIS199R.DOS (for the Proteon 1990
         Microchannel bus controller).
                                                                      3-1

 


         If you have a Proteon Token Ring controller, do the following:

         1. Use Netsetup to install the Proteon NDIS driver and
            PROTOCOL.INI stub. Select the "Other NDIS" option from the
            Token ring network adapter type screen.

            Netsetup prompts you for the location (drive and path) of the
            NDIS driver and a PROTOCOL.INI stub file.

         2. Copy the Proteon microcode file into the same directory
            as the device driver on the key diskette (the \DECNET
            directory).

            The microcode file, PRORAPM.DWN, is in the same directory
            as the device drivers on the Proteon distribution media.

         By default, Proteon controllers use DMA channel 5. DECstations
         with a SCSI hard disk controller also use DMA channel 5. If
         you are using a Proteon controller in a DECStation with a SCSI
         controller, you must change one of these DMA channel values.

         The following are the version numbers of the Proteon routers
         that can PATHWORKS for DOS version 4.1 supports the following
         Proteon routers:

         o  Proteon 4100+ Multi Protocol Bridging Router version 11.0

         o  Proteon CNX 500 Multi Protocol Bridging Router version 11.0

     USING MADGE TOKEN RING CONTROLLERS
     ----------------------------------
         Use the following guidelines when using a Madge Token Ring
         Controller with PATHWORKS for DOS:

         o  The Madge Token Ring Controller NDIS driver does not support
            the SetStationAddress function.

            To set the station address of a Madge Token Ring Controller,
            add he following line to the Madge controller section of the
            PROTOCOL.INI file:

            NODEADDRESS = "55002000****"

            The value of **** is dependent on your DECnet node address
            (see Using NDIS Drivers appendix of the PATHWORKS for DOS
            Installation and Configuration Guide).

         o  Add the following parameter to the Madge controller section
            of PROTOCOL.INI:

            AUTOOPEN = NO

         3-2

 






    USING OLICOM TOKEN RING CONTROLLERS
    -----------------------------------
         The Olicom Token Ring Controller NDIS driver does not support
         the SetStationAddress function.

         To set the station address of an Olicom Token Ring Controller,
         add the following line to the Olicom controller section of the
         PROTOCOL.INI file:

         NODEADDRESS = 0x5500 0x2000 0x****"

         The value of **** is dependent on your DECnet node address
         (see Using NDIS Drivers appendix of the PATHWORKS for DOS
         Installation and Configuration Guide).


     Using IBM Token Ring Controllers
     --------------------------------

	 On systems using an IBM Token Ring controller, a small number of 
	 network applications may cause the system to hang or reboot.
	 This problem is caused by interactions between nested interrupts
	 generated by the IBM Token Ring device driver and the functions
	 performed by the application as it exits.

	 If this problem occurs, set the HEURISTICS parameter in the
	 [DATALINK] section of the \DECNET\PROTOCOL.INI file to 8 (or add
	 8 to the current HEURISTICS value.)


     LIMITATIONS OF DECNET OVER TOKEN RING
     -------------------------------------
         o DECnet VMS Token Ring does not currently support source routing.
           As a result, VMS servers in configurations requiring source
           routing are not be accessible from the client. For example,
           servers on token rings connected by a source routing bridge are
           not reachable from the client. However, the client can access
           servers on token rings connected by routers.


                                                                     3-3





         o PATHWORKS running over the DECnet transport requires a DECnet
           specific station address in the following format:

           AA-00-04-00-XX-YY

           Certain applications running in the Token Ring environment
           require the node address to be changed to a different value.
           Possible conflicts exists with certain 3270 terminal emulators
           that require the node's network address be in the following
           format:

           40-xx-xx-xx-xx-xx.

           Since both DECnet and the application require the address to be
           set but require it to be set to different values, the two can
           not co-exist on the same system.

         o Token Ring operation requires mapping Ethernet multicast
           addresses to functional addresses used on the Token Ring.
           The format of the functional addresses limits the number of
           functional addresses available to the network vendors. As a
           result, there may be conflicts between the functional addresses
           used by Digital and those used by other vendors.


           The IBM 8209 LAN Bridge is not currently supported in DECnet
           environments. Operation of PATHWORKS clients and servers over an
           IBM 8209 bridge is limited. For example, due to the interactions
           of the 8209 bridging algorithms and the implementation of source
           routing in PATHWORKS for DOS and PATHWORKS for OS/2, nodes using
           the DECnet protocol CAN NOT communicate between an Ethernet and
           a Token Ring over the 8209 bridge. The same limitation does not
           apply to nodes using TCP/IP.



















         3-4


 









                                                                        4
         ________________________________________________________________

                                                  DOS Version 5.0 Support



         Support for DOS Version 5.0 is included in PATHWORKS for DOS
         Version 4.1. Follow these guidelines when 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 V3.0, use it for task switching and
            not the DOS Shell. Windows has its own task switcher or
            multitasker built-in. 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 and waste
            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 Version 5.0 task
            switcher, DOSSWAP, does not save and restore the EMS page
            frame when switching.

         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 Version 5.0 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.

                                                                      4-1

 






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

         Note the following for running PATHWORKS with 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, and SMARTDRV.SYS.

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


































         4-2

 







                                                                        5
         ________________________________________________________________

                                       Network Components and Remote Boot



         This chapter discusses the known limitations of the PATHWORKS
         for DOS network components. This chapter includes:

         o  Undocumented guidelines

         o  Ways to troubleshoot the known limitations

     GENERAL GUIDELINES
     ------------------
         Observe the following guidelines:

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

         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, 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, LAT will not be able to use those printer
            ports when it is reloaded.

            If you unload the network when LAT is serving printers, make
            sure to unload LAT (LAT/U) 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. If it is not, your client cannot connect to
            file services.

         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.

                                                                      5-1

 

         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" manual lists a /HELP qualifier to display PRINT
            help. This qualifier is not valid. Use the NET HELP PRINT
            command to display the NET PRINT help.

         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 data base 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 remedies 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 modify the
            application programs to have a more reasonable locking
            strategy. See Appendix A in the the OS/2 Lan MANAGER
            Administrator's Guide for information on the the MAXLOCKS=
            parameter in the LANMAN.INI file.

	 o  The USE /SETDIR command switch is not supported on application or
	    common file services on a PATHWORKS for VMS server.  The /SETDIR
	    switch 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 USE /SETDIR 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 the device and directory you
            were connected to when the network link failed.

            You must USE /SETDIR to reestablish the association device and
            directory.

	 o  The DCL command SET PROT=(...) /DEF command and the
            NET ATTRIB M: /PROT=(...) /DEF command are independent of one
	    another. Files created under VMS have maintain DCL protection
	    while files created from DOS maintain the default protection
	    specified by NET ATTRIB.


         5-2



         Note the following problems 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.

           PROBLEM: If you run a large application, such as Microsoft
           Windows 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, on your client, you run DOS Version 4.0 with
           SHARE.EXE loaded, you may have problems (hung system, sharing
           violations, mount/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 is unable to determine the
           correct number of buffers available and does not allow data
           transfers.

           SOLUTION: Place 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 receive
	   "Drive not ready" errors for some ethernet boards (for example, the
	   3Com 3C503).

	   SOLUTION:  Do the following:
	   1) Use the NCP SHOW EXEC CHAR 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 \DECNET\STARTNET.BAT 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 \DECNET\STARTNET.BAT to
                %BOOT%\decnet\lansess.exe /R:2 /W:2
	   4) Reboot the client for the changes to take effect.

                                                                      5-3

 

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

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


     CTERM
     -----
         Observe 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 defaults
            to the system default terminal type. For VMS, use the SET
            TERMINAL/INQUIRE command to get the correct terminal type.

         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.

         o  When you type 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.

         5-4

 






     DATA TEST SENDER/DATA TEST RECEIVER (DTS/DTR)
     ---------------------------------------------
         Observe 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 set does
            not include information about DTR or DTS. However, the file
            \DECNET\DTS.TXT describes these tools.

         o  Under Microsoft Windows, DTR will 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.

            The 4.0 version of DTR fails if messages are received faster
            than they can be transmitted. This is an application-level
            logic bug. The DTR program 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 personal computer
            is running DTR, this message may appear 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
            >512K hangs the system. (SINK test does not have this
            problem.)

     NETBIOS AND DNP
     ---------------
         Observe the following guidelines when using DNP and NETBIOS:

         o  DNP V4.1 must be used with the version 4.1 datalink.
            Otherwise, "ncp show line char" and "ncp show line counters"
            won't work.

         o  DNP V4.1 does not add local names. For USE and PERMIT to
            work, you must run SETNAME first. SETNAME sets the local
            names for you.

                                                                      5-5

 






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

            EMSLOAD DNNETH.EXE

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

         Restrictions
         ------------
         Unloading DNP by doing NCP SET EXE STATE OFF is no longer
         supported. Use MEMMAN/U to unload the network.

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

     NETWORK DEVICE UTILITY (NDU)
     ----------------------------
         Observe the following guidelines when using the NDU:

         o  Version V4.1.00 of NDU will only work with version V4.1.00 of
            NDDRV.SYS and NPDRV.SYS. It is not backward compatible with
            older version 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 or RMS) and stream
            files on stream systems (such as DOS).



         5-6

 


         o  Systems using IBM DOS Version 4.00 may hang when you run NDU.
            Do one of the following to avoid this PROBLEM:

            -  Contact IBM for the correct CSD upgrade.

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

            -  Make sure to load NDDRV.SYS from your CONFIG.SYS file
               before running NDU.

     VIRTUAL PRINTER DRIVER (NPDRV.SYS)
     ----------------------------------
         Using the virtual printer with the background print spooler can
         cause the system to hang.

     NETWORK FILE TRANSFER (NFT)
     ---------------------------
         When printing remote files using wildcards, NFT prints only the
         first file that satisfies the wildcard specification.

     NETWORK VIRTUAL TERMINAL (SETHOST)
     ----------------------------------

	 Note the following:

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

	 o When using the VMS TPU 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 F3 to access the SETHOST setup menus.

	   To prevent this problem, try the following:

	   - Do not use auto-repeat excessively
	   - Use the EDT editor instead
	   - Use CTERM as your transport
                                                        





                                                                      5-7

 







                                                                        6
         ________________________________________________________________

                                             Microsoft Windows 3.0 Support



         This section contains the following:

         o  Guidelines for using Microsoft Windows 3.0 with PATHWORKS for
            DOS V4.1

         o  Using the VT320 emulator

     GUIDELINES
     ----------
         Observe the following guidelines when using Microsoft Windows
         3.0 with PATHWORKS for DOS V4.1:

	 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 and all 80486-based models)
	    require the "IBM or compatible" setting.  Note that Hewlett-Packard
	    personal computers 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 and/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
            Microsoft Windows 3.0. If you run Microsoft Windows Enhanced
            mode and have network software loaded into EMS, you should
            use EMM386. Keep in mind that currently shipping versions of
            EMM386:

            -  Do not support Standard mode (WIN /S)

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

            -  The version of EMM386 that accompanies DOS 5.0 allows you
               to load components in high memory.

         o  It is recommended that you upgrade to Windows Version 3.00a,
            a maintenance update, that has been available from Microsoft
            since December, 1990. If you are a registered Windows 3.0
            owner, you can receive a copy of Windows 3.00a by submitting
            a Service Request through Microsoft OnLine. Customers

                                                                      6-1

 






            requiring multiple Windows 3.00a updates should contact
            Microsoft Corporate Accounts at (800) 227-6444.

            Windows 3.00a includes improvements to the setup program and
            fixes many problems resulting in Unrecoverable Application
            Errors (UAEs), hangs, and data loss and/or packet cor-
            ruption in networking applications. Windows 3.00a can be
            distinguished from version 3.00 in the Program Manager, File
            Manager, and/or Control Panel Help About dialog boxes.

         o  The Microsoft Windows printer drivers distributed with
            PATHWORKS Version 4.1 use the GENDRV.DLL common printer
            library. GENDRV.DLL is distributed with PATHWORKS along with
            the current and future versions of Microsoft Windows. Always
            use the the latest version of GENDRV.DLL. You can see the
            version number for GENDRV.DLL in the printer setup dialog.

            Other vendor's 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 are having 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 a Digital 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:

         6-2

 






               \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 Microsoft Windows in protected mode. This includes
               any network access from a Microsoft Windows application
               in Standard or Enhanced mode, and any access from a DOS
               application in Enhanced mode. If this occurs, try Windows
               Standard Mode, use a lower baud rate, or both

            -  If you have an asynchronous DECnet configuration, running
               Microsoft Windows 3.0 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
            Microsoft Windows 3.0:

            -  MEMMAN /XMS
            -  PERMIT
            -  EMSSPEED

         o  Applications that use TFA or TTT may produce unpredictable
            results when run under Microsoft Windows.

         o  If you use Microsoft Windows 3.0 in Enhanced mode and the
            broadcast receiver receives a message, subsequent messages
            are not received until the network is stopped and restarted,
            or the user's PC is rebooted.

         o  With Standard mode Microsoft Windows 3.0, 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 the use of
            standard NETBIOS calls. This restriction does not apply for

                                                                      6-3

 




             Windows applications or non-Windows applications running in
             Enhanced mode.

	   o Lan Manager API calls (NetUseAdd, NetUseDel, etc) are not
             currently supported in Windows applications. 

         Note the following problems and their solutions:
         ----------------------------------------------
           PROBLEM: When printing to an LN03R ScriptPrinter connected
           to an ULTRIX server, the printer driver currently shipped
           with Microsoft 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 DELETE 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 Control-Y, or on the DOS side
           by shutting down FAL.

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

           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  Contact IBM for a new set of XGA Windows drivers.




         6-4

 



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

	  SOLUTION: Start the application after you start Microsoft Windows.


     RUNNING THE VT320 TERMINAL EMULATOR
     -----------------------------------
         Observe the following guidelines:

         o  To comply with some countries' local regulations regarding
            access to public telecommunications networks, you must
            use SETHOST instead of the VT320 emulator for all direct
            connections to these public networks. This restriction exists
            because Full Modem Control problems occur when you use the
            Microsoft Windows 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.































                                                                      6-5

 









                                                                        7
         ________________________________________________________________

                                                                     MAIL



     ADDITIONS TO DOCUMENTATION
     --------------------------
         The MAILCHK utility allows you to connect to the server and
         display the number of new messages without starting mail.

         The MAILCHK utility has the following qualifiers:

         ________________________________________________________________
         Qualifier           Description
	 ________________________________________________________________

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

         MAILCHK /STATUS     Displays the following mail status: 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 and server operating system.

         MAILCHK /SHOW       Displays the number of new messages.

         MAILCHK /STOP       Closes the network link.

         MAILCHK /VERBOSE    Displays the number of new messages with
                             the following information: date, sender, and
                             subject.

         MAILCHK /V          Same as /VERBOSE.
         _________________________________________________________________


                                                                      7-1

 


           ___________________________Note ___________________________

           MAILCHK is not currently supported over the TCP/IP
           transport.

           ___________________________________________________________

	 Also note the following:

	 o When you run MAILSETU using TCP/IP to an ULTRIX server, the node
	   name specified in MAILSETU must match the node name specified in
	   HOSTS. For example, if the node name is lower case in HOSTS, then
	   you must specify the node name in lower case in MAILSETU.

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

	 Known Problems and Limitations
         ------------------------------
         The following are limitations of the MAIL utility and ways to
         troubleshoot those limitations:

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

           SOLUTION: Do one of the following:

           o  Set the Keep Network Link option in MAILSETUP to "on,"

           o  Upgrade to the Ultrix V1.1A server (PATHWORKS for ULTRIX
              V1.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 the Mail
           setup program, MAILSETU, or do not load the mouse driver
           (MOUSE.COM).

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

           SOLUTION: Add the SET DNETMAIL=C:\MAIL command to your
           AUTOUSER.BAT, AUTOEXEC.BAT, or STARTNET.BAT file and create
           the directory C:\MAIL. To change the default location of
           temporary and local mail files, use the advanced mode of
           MAILSETU (press F10).

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

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

         7-2

 



           PROBLEM: When viewing a directory, pressing the Enter key
           displays the NEXT message listed. Therefore, when you first
           display a directory and press the Enter key, you read the
           second message listed.

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

           o  Type R, then press the Enter key.

           o  Type 1, then press the Enter key.

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

           PROBLEM: You receive 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 (for example, 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 Mailsetup 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: You must 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.

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

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

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



                                                                      7-3

 
	   

 









                                                                        8
         ________________________________________________________________

                                                      PC DECwindows Motif



         This chapter discusses the known limitations of PC DECwindows
         Motif. This chapter includes:

         o  Guidelines not documented in the  PC DECwindows Motif Guide

         o  Ways to troubleshoot the known limitations

         Observe the following guidelines:
         ---------------------------------
         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) are not
            designed to run on a remote display and do 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). If not,
            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. 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. Use the
            MEMMAN/SUMMARY or SHOW command to find out how much of
            the various types of memory is available during a suspended
            session.

                                                                      8-1

 






         o  Do not use the DOS PRINT command, other TSR programs, or
            other programs that run in the background during a suspended
            session.

         o  If multiple applications are defined to start up automati-
            cally 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.
            Use DWDOS386 or a monochrome video mode to use the DDIF
            Viewer.

         o  Keyboard input may be lost on very slow machines (IBM AT
            6MHz, for example), 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:

            SET DOS16M=FAST

         o  The help command line switch "help" displays all the
            available switches and is too large to fit on one screen. To
            see the entire page, use the DOS MORE command. For example:

            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. Users should migrate to the DECwindows
            Window Manager (DECW$WINMGR on VMS or dxwm on ULTRIX) or the
            DECwindows Motif Window Manager (DECW$MWM on VMS or dxmwm on
            ULTRIX).

         o  When you are not using the X server in the TCP/IP environ-
            ment, 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 call unloads the
            BAPI driver, the second call unloads the TELNET driver, and
            the third call 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 that use key sequences with MB2.

         8-2

 






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

         o  Using an application, such as DECpaint, to draw large arcs
            and ellipses is very slow, and at times it seems to hang the
            system.

         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 reboot your PC at this
            prompt, 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.

         Note the following problems 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 DECwindow Motif
           while it is suspended, the network may run out of resources 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 your ULTRIX 4.0 or 4.1

                                                                      8-3

 






           system. For information about installing the rexec daemon,
           see the PATHWORKS for ULTRIX Version 1.1 release notes.


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

           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 may PC also display the following error message: "illegal
           instruction"

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


















         8-4

 









                                                                        9
         ________________________________________________________________

                                                         DOS Enhancements



         This chapter describes the known limitations of the DOS
         Enhancements supplied with PATHWORKS for DOS. Observe the
         following guidelines:

         o  Do not load KEYBRD, XONXOFF, or DECMOUSE into Upper Memory
            Blocks (UMBs). For example, do not use Quarterdeck QEMM's
            LOADHI or DOS 5.0 LOADHIGH to load these functions in UMBs.

         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 because KEYBRD does not pass keystrokes on to
               other TSR keyboard programs.

            -  KEYBRD handles special keystrokes differently than the
               native keyboard BIOS program does. For example, Ctrl-
               Alt-Del 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
               will not affect your PC's operation.

                                                                      9-1

 



                                                                       10
         ________________________________________________________________

                                                   Programming Components



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

           DNP does significantly more parameter checking than previous
	   releases.  It is possible for applications to run under earlier
	   releases and fail with 4.1.  If you experience problems, please
	   first carefully check all calls with the definitions specified
	   in the Programmers Reference Manual.


    ADDITIONS TO THE DOCUMENTATION
     ------------------------------

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

           This routine prompts the user for a password. It is called
           by dnet_conn if a user name was specified without a password.
           The application developer may supply a different routine,
           using the same calling sequence, in place of the routine
           supplied in the library.

           ___________________________Note ___________________________

           The version of this routine supplied for Microsoft Windows
           is a placeholder that always supplies a null password.
           If prompting is desired, the application developer must
           supply his own routine.

           ___________________________________________________________

                                                                     10-1

 






           INPUT ARGUMENTS:

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

           node1       Specifies the address of a string containing the
                       node name.

           inlen       Specifies the address of an integer that will be
                       filled in.

           OUTPUT ARGUMENTS:

           acc_data    The acc_pass and acc_passl fields will be filled
                       in.

           inlen       The integer that this points to will contain the
                       length of the password entered by the user.

           RETURN VALUE:

           none

     TRANSPARENT FILE ACCESS UTILITY (TFA)
     -------------------------------------
           Observe the following guidelines when using 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  The DOS Version 4.0 TYPE command cannot access a remote
              file with TFA if the remote file is not in the current
              directory.

           o  The DOS Version 4.0 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:.

           o  Under DOS Version 4.0, COMMAND.COM uses undocumented calls
              for file access instead of the standard, documented ones
              that are supported by TFA.

         10-2

 






           o  TFA supports some calls made from the DOS command line.
              It does, however, support all calls made from application
              programs. (You can find a complete list of the DOS calls
              that TFA supports in the DECnet Programmer's Reference
              Manual.)

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

           ___________________________Note ___________________________

           Use NFT TYPE and NFT COPY for remote file access. NFT does
           note have the restrictions of TFA.

           ___________________________________________________________

     NETWORK APPLICATIONS THAT USE 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 mapping in the
         background. EMS mapping by applications is supported only in
         the foreground.
















                                                                     10-3

 









                                                                       11
         ________________________________________________________________

                                DECnet/SNA Gateway NETBIOS Access Routine



         Observe 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
               command from the VMS prompt:

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

               In this command:

               gateway_name     Is the DECnet node name of the gateway
                                you are using.

               max_rusize       Is the value in the the SNAGNI configura-
                                tion file for the MAX_RUSIZE parameter.

               Consult the DECnet/SNA Gateway Management Guide for more
               information about using NETTRACE.

            Use the debug version of SNAGNI, called DSNAGNI.EXE, from
            \DEBUG directory on the system file service. Attempt to
            reproduce the problem using DSNAGNI.EXE. If you re-produce
            the problem, send the log file which is created to your
            Digital representative. Included with DSNAGNI.EXE is a file
            called DSNAGNI.DOC, which explains how to use DSNAGNI.EXE.

                                                                     11-1

 






         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 will always show 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.

         o  If you are using IRMALAN DOS Client for DECnet/SNA Gateway,
            there is currently no support for DCA's Ram Expander product.




























         11-2
