 













             PATHWORKS for DOS
             _______________________________________________________

             Release Notes


             February 1991




             Revision/Update Information:  This document
                                           supersedes the VMS
                                           Services for PCs
                                           Release Notes Version
                                           3.1.

             Software Version:             PATHWORKS for DOS
                                           Version 4.0 (or
                                           higher)





             digital equipment corporation
             maynard, massachusetts

 





             ________________________
             First Published, February 1991

             Restricted Rights: Use, duplication, or disclosure
             by the U.S. government is subject to restrictions
             as set forth in subparagraph (c)(1)(ii) of the
             Rights in Technical Data and Computer Software
             clause at DFARS 252.227-7013.

             The information in this document is subject
             to change without notice and should not be
             construed as a commitment by Digital Equipment
             Corporation. Digital Equipment Corporation assumes
             no responsibility for any errors that may appear in
             this document.

             The software, if any, described in this document
             is furnished under a license and may be used or
             copied only in accordance with the terms of such
             license. No responsibility is assumed for the use
             or reliability of software or equipment that is not
             supplied by Digital Equipment Corporation or its
             affiliated companies.







             __________
             Copyright 1991

             The following are trademarks of Digital Equipment
             Corporation:

             DDCMP, DDIF, DEC, DECconnect, DECmate, DECnet,
             DECnet-DOS, DECnet-VAX, DECpaint, DECrouter,
             DECserver, DECstation, DECterm, DECwindows,
             DELNI, DEMPR, DEPCA, DESTA, LA50, LA75, LA210
             Letterprinter, LAN Bridge, LJ250, LJ252, LN03, LN03
             Plus, LN03 ScriptPrinter, MicroVAX, PCMAIL, PCSA,
             P/OS, PrintServer, RD33, RD54, ReGIS, RMS, RSTS,
             RSX-11, RT, RX33, ThinWire, TK50, TOPS-10, TOPS-
             20, ULTRIX, VAX, VAXcluster, VAXmate, VAX Notes,
             VAXserver, VMS, VT, WPS, WPS-PLUS, and the DIGITAL
             Logo.

             The following are third-party trademarks:

             3Com is a trademark of 3Com Corporation.

             COMPAQ is a registered trademark of the COMPAQ
             Computer Corporation.

             Hercules is a registered trademark Hercules
             Computer Technology.

             IBM is a registered trademark, and NETBIOS is
             a trademark of International Business Machines
             Corporation.

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

             OSF/Motif is a trademark of Open Software
             Corporation

             X Window System, Version 11, and its derivations
             (X, X11, and X Version 11) are trademarks of The
             Massachusetts Institute of Technology.

             This document was prepared using VAX DOCUMENT,
             Version 1.2

 










                                                         Contents
          _______________________________________________________

          1   New Functionality

          Installation and Configuration....................  1-1

          Microsoft Windows 3.0.............................  1-2

           PC DECwindows/Motif..............................  1-3

          Network Utilities and Remote Boot.................  1-9

          DOS Enhancements.................................. 1-10

          MAIL.............................................. 1-10

          SEDT.............................................. 1-11

          DECnet Components................................. 1-11

          DECnet/SNA Gateway NETBIOS Access Routine......... 1-14

          2   Installation and Configuration

          VMS Installation..................................  2-1

          ULTRIX Installation...............................  2-2

          Netsetup Utility..................................  2-3

            Netsetup in General.............................  2-3

            Netsetup to Configure DECnet....................  2-5

            Netsetup to Configure TCP/IP....................  2-6

          DOSLOAD Utility...................................  2-6

          3   Microsoft Windows 3.0

          Running PATHWORKS for DOS V4.0 with Microsoft
          Windows 3.0.......................................  3-1

          Running Microsoft Windows 3.0.....................  3-4

          Running Microsoft Windows 3.0 VT320 Terminal
          Emulator..........................................  3-5

                                                                v

 


          vi  Contents



          4   PC DECwindows/Motif


          5   Network Utilities and Remote Boot

          Known Limitations.................................  5-1

          Corrections to Documentation......................  5-4

          6   MAIL


          7   DOS Enhancements

          KEYBRD............................................  7-1

          XONXOFF...........................................  7-2

          DECMOUSE..........................................  7-2

          8   DECnet Components

          CTERM.............................................  8-1

          Data Test Sender/Data Test Receiver (DTS/DTR).....  8-2

          NETBIOS and DNP...................................  8-3

            DNP Asynchronous Limitations....................  8-3

          Network Control Program (NCP).....................  8-3

          Network Device Utility (NDU)......................  8-4

            Virtual Printer Driver (NPDRV.SYS)..............  8-4

          Network File Transfer (NFT).......................  8-5

          Network Virtual Terminal (SETHOST)................  8-5

            TCP/IP and SETHOST..............................  8-6

            SETHOST and Microsoft Windows 3.0...............  8-7

            CTERM Connections for SETHOST...................  8-8

            Asynchronous DECnet Connections for SETHOST.....  8-8

 


                                                  Contents   vii



          9   Programming Components

          Transparent File Access Utility (TFA).............  9-1

            Microsoft Windows Support in General............  9-2

          Troubleshooting and Unsupported...................  9-2

          DECnet Programming Library........................  9-3

          10   DECnet/SNA Gateway NETBIOS Access Routine

 









                                                                1

                                                New Functionality
          _______________________________________________________

             This chapter describes the new functionality added
             to PATHWORKS for DOS Version 4.0 since the last
             release of the product. This release fixes some
             known problems and provides enhanced performance.
             This chapter also describes any changed or removed
             functionality.

             This chapter discusses the following topics:

              o Installation and configuration

              o Microsoft Windows 3.0

              o PC DECwindows/Motif

              o Network utilities and remote boot

              o DOS enhancements

              o MAIL

              o SEDT

              o DECnet components

              o DECnet/SNA Gateway NETBIOS Access Routine

          Installation and Configuration

              o Netsetup - Netsetup has the following new
                functionality:

                 - TCP/IP configuration support

                 - NDIS configuration support

                 - Basic, Intermediate, and Advanced operator
                   modes

                                                              1-1

 


          1-2  New Functionality



                 - Option to configure a DECnet-DOS only
                   environment

                 - Option to configure an Asynchronous DECnet
                   environment

                 - Option to create a floppy Remote Boot key
                   diskette

              o DOSLOAD - DOSLOAD now lets you:

                 - List the versions of DOS available on the
                   system file service

                 - Remove a version of DOS from the system file
                   service

              o ULTRIX installation - With TK50 media, PATHWORKS
                for DOS V4.0 can be installed on an ULTRIX
                server.

              o OS/2 installation - With a DOS media kit,
                PATHWORKS for DOS V4.0 can be installed on an
                OS/2 server.

              o System service - The system service is now a
                file service instead of a disk service. Keep
                in mind that you cannot use the SUBST command
                to access the DOS directories, and any DOS
                commands which require files to reside in the
                root directory do not work.

              o Key diskettes - Key diskettes must now be larger
                than 360KB because of the size of the files
                needed to start the network.

          Microsoft Windows 3.0

             PATHWORKS for DOS Version 4.0 support for Microsoft
             Windows 3.0 includes:

              o Installation utility (WIN3SETU.EXE)

              o PATHWORKS network driver

              o DEPCA mouse driver

 


                                           New Functionality  1-3



              o LK250 keyboard driver, which includes 13 local
                languages

              o VT320 terminal emulator, which includes:

                 - New and revised DECterm emulation fonts (also
                   for Windows 286/2.1 VT320)

                 - Added CTERM support

                 - Improved Setup display

              o NFT (Network File Transfer)

              o FAL (File Access Listener)

              o Support for DECnet Socket Library (DNET)

              o Access to enhanced NETBIOS functions

              o Terminal Access Library (TRMNLAXS.DLL),
                which gives third-party Microsoft Windows 3.0
                applications access to LAT and CTERM sessions

              o Program Information Files (PIF) for PATHWORKS
                components that require specific environments

          PC DECwindows/Motif

              o TCP/IP - TCP/IP is now supported. You can run
                applications from any remote UNIX or ULTRIX
                system that runs TCP/IP, and any VMS system
                that runs TCP/IP (UCX). However, to start
                applications using the PC Session Manager or
                Autostart, rexec must reside on the ULTRIX
                system, and TELNET must reside on the VMS
                system. Also, the DECnet remote startup file,
                PCX$SERVER.COM, must reside on the VMS system.

              o Hardware independent mouse support - The
                Microsoft MOUSE interface Version 6.0 (or
                higher) is now supported, as well as all
                pointing devices that run with a compatible
                mouse driver.

 


          1-4  New Functionality



              o 8514/A video - The IBM 8514/A high resolution
                standard is now supported. For boards that have
                512KB of memory, 1024x768 resolution with 16
                colors is supported. For 1MB of memory, 1024x768
                resolution with 256 colors is supported. IBM,
                Western Digital Paradise, and Digital boards
                are supported. To use the high resolution, you
                must also have a compatible monitor. The 8514/A
                board running to a standard IBM or compatible
                VGA monitor is also supported. With 1MB of
                memory on the board, this provides only 640x480
                resolution, but 256 colors are provided instead
                of 16.

              o Super VGA (800x600) support - The following
                vendor's video boards, which support 800x600
                resolution, are now fully supported:

                 - Paradise

                 - Everex

                 - Video 7

                 - Ahead

              o Pseudo color support for all video types -
                The pseudo color video type is now supported
                (previously, only static color was supported).
                This allows the application to allocate colors
                from a large palette. For EGA, VGA, and the
                800x600 VGA modes, up to 16 colors can be
                allocated at a time. For 8514/A, up to 256
                colors can be allocated at a time.

              o DWCONFIG improvements - The configuration
                utility's user-interface has changed and
                additional functionality has been added.
                Now only the DWDOS.INI file is created and
                maintained by DWCONFIG. The DWDOSUSR.INI file
                is now obsolete. It must be removed from your
                path if it exists.

 


                                           New Functionality  1-5



              o Selectable configuration file - On the command
                line, you can now specify the name of your
                configuration file when you run the X server
                or DWCONFIG. Examples include:

                  C:\> DWDOS286 myfile.ini
                  C:\> DWCONFIG myfile.ini

              o Video panning - Hardware-assisted panning for
                the VGA and EGA in color or monochrome modes is
                now supported. This provides you with a virtual
                screen that is larger than the physical screen.
                You will still only see the physical limits
                of the monitor at any one time (for example,
                640x480 for VGA), but by moving the mouse
                pointer to the edges of the screen, you can
                scroll in either direction to display previously
                unseen parts of the virtual screen.

                By pressing Ctrl/F2, the viewport through which
                you view the virtual screen can be locked at any
                time when running the X server. Pressing Ctrl/F2
                again will unlock the viewport.

              o New fonts - Two sets of fonts are now provided,
                75 dots-per-inch and 100 dots-per-inch. These
                new fonts have been added to improve the
                appearance of the 8514/A video support.

              o Microsoft Windows 3.0 support - .PIF files are
                provided to spawn the X server from Microsoft
                Windows. Once the X server is started, you can
                switch directly back to Microsoft Windows by
                pressing Ctrl/Esc or Alt/Esc. .PIF files are
                also provided for the DWINFO2 and DWINFO3 memory
                information utilities.

              o New Keysym files for LK201-style keys on
                Industry Standard keyboards - LK201 keyboard
                emulation is now supported on all keyboards:
                Industry Standard 84-key and Industry Standard
                Enhanced. There are two sets of keysym files for
                each type of keyboard, one for Industry Standard
                style mappings and one for LK201 style mappings.

 


          1-6  New Functionality



              o New memory information utilities -
                PC DECwindows/Motif includes two new utilities,
                DWINFO2.EXE and DWINFO3.EXE, that you can use
                to determine how much memory is available to
                run the DWDOS286 and the DWDOS386 executables,
                respectively.

              o PC DECwindows/Motif password - This password,
                when set with DWCONFIG, adds extra security to
                the X server. When the X server is started, the
                user is prompted for this password.

              o Password encryption - DWCONFIG now encrypts
                remote startup passwords and the PC
                DECwindows/Motif password stored in the
                configuration file.

              o Improved PC Session Manager - The PC Session
                Manager has been redesigned. The main window
                is smaller, but it still contains memory
                statistics, and the Exit and Suspend Session
                buttons. The Start Application dialog is now
                displayed in a separate window. Also, there are
                Help windows for both the main window and the
                Start Application window.

              o Pause Session - By pressing a button in the PC
                Session Manager, you can pause your session
                until your PC DECwindows/Motif password is
                entered. This is useful if you leave your desk
                but want to leave the X server running.

              o Start DOS applications from PC Session Manager -
                You can now start DOS applications directly from
                the PC Session Manager.

              o Memory management improvements - The memory
                management strategy has improved. Memory is
                now used more efficiently, and the Memory Used
                number in the PC Session Manager decreases as
                memory is made available.

              o Keyboard mouse - The keyboard can now be used as
                a pointing device. Pressing Ctrl/F3 switches the
                keyboard into "Keyboard Mouse" mode.

 


                                           New Functionality  1-7



              o Three button mouse emulation - With a two button
                mouse, the user can configure a simulated third
                button by pressing a sequence of keys while
                clicking MB2.

              o Shape extension - Shape extension is now
                included in the X server. This extension allows
                for the creation of non-rectangular shaped
                windows.

              o Backing store and save unders - Both backing
                store and save unders are now supported. These
                options can greatly improve performance of some
                applications that are output intensive. However,
                using these options on color monitors requires a
                significant amount of memory.

              o Screen saver - A screen saver feature has been
                added to the X server. With a new setting, you
                can set the screen to timeout.

              o Critical error handling - Critical errors are
                now reported with a message box as they occur.
                The type of error and the drive letter are
                displayed.

              o Version information - The software version, the
                date, and the time are displayed:

                 - On the logo screen

                 - After you suspend a session

                 - At the top of the PC Session Manager Help
                   screen

              o The fast fonts feature has been removed because
                it causes many problems with applications.

              o The slide windows feature has been removed.
                Windows that are not completely displayed on the
                screen when they come up are not moved.

              o To specify a setting on the command line, you
                must now type a slash (/)  or a dash (-)  before
                the setting.

 


          1-8  New Functionality



              o The Hercules video type is no longer supported.
                A 64KB EGA card with a monochrome monitor is an
                inexpensive substitution.

              o The 83-key keysym files have been removed. The
                84-key keysym files can be used as a substitute.

              o The font file format has changed for this
                release. You must use the new fonts shipped
                with this version of PC DECwindows/Motif. If you
                compiled fonts for use with older versions,
                you will have to recompile them with the
                new font compiler (DWFONT.EXE) supplied with
                PC DECwindows/Motif.

              o The configuration files have changed. The two
                files (DWDOS.INI and DWDOSUSR.INI) have been
                merged into one. By default, it is called
                DWDOS.INI, although you can specify any name
                when you run DWCONFIG to create a new file. You
                should run DWCONFIG before running the X server
                because settings have been added, removed, and
                changed. If you have an old DWDOS.INI file, you
                must run DWCONFIG before you can run one of the
                new X servers.

              o The keysym file format has changed. Old keysym
                files are not usable with this release. Also,
                if you have created your own keysym files,
                they must be recompiled with the keysym
                compiler (DWKEYSYM.EXE) supplied with PC
                DECwindows/Motif.

              o The X servers do not close applications when out
                of memory. Error messages are returned to the
                applications that failed to allocate memory.

 


                                           New Functionality  1-9



          Network Utilities and Remote Boot

              o NDIS support - PATHWORKS for DOS now supports
                the Microsoft/3Com Network Device Interface
                Specification (NDIS) standard, Version 1.0.
                However, this support does not extend to running
                PATHWORKS for DOS and other vendor's networking
                products simultaneously.

              o LAT - LAT offers the following new
                functionality:

                 - On a server, you can set up a printer queue
                   which, over the LAT, sends print jobs to a
                   printer attached to a PC.

                 - Multiple preferred services can now be
                   defined for the same service name. Use the
                   LATCP DEF FALLBACK ON command to make LAT
                   try, if necessary, all known addresses of a
                   service to make a connection to that service.
                   By default, this functionality is disabled.

                   Any preferred service must be created using
                   LATCP. The format used to store this data in
                   DECLAT.DAT has changed in order to support
                   the LATCP FALLBACK command.

              o PSC.COM - PSC.COM now provides 3 functions:

                 - Lets you Print Screen to a network printer

                 - Closes a network print file on command

                 - Closes a network print file periodically

              o LAD, LAST, LADDRV, and USE - Internal changes
                to LAD, LAST, LADDRV, and USE make it necessary
                to install all four at the same time. In other
                words, do not mix different versions of LAD,
                LAST, LADDRV, and USE. When you run LAD or USE
                from your PC, change LADDRV as well. For USE to
                work properly, you must also use the new Remote
                Boot task images.

 


          1-10  New Functionality



              o LAD - You can now access LAD drives greater than
                32MB from a PC running DOS 4.0 or higher.

              o LANSESS for PATHWORKS for DOS - In a local area
                network, LANSESS provides faster access to file
                services stored on VMS servers.

              o New DEPCAs and DEMCAs - the Remote Boot task
                images for DEPCA-based machines now support all
                new DEPCAs and DEMCAs. However, Remote Boot will
                not support TCP/IP or NDIS.

              o RCV - RCV can now use group names. You can also
                specify how long an RCV message is displayed on
                your screen before it is automatically stored
                for later viewing and control is returned to
                your current application.

              o SETLOGON.EXE - This new file lets users connect
                to OS/2 servers with user level security.

              o NET PRINT - You can now print binary files, such
                as PCL files, using the NET PRINT command with
                the /BINARY qualifier.

              o DESQview - DESQview is not supported.

          DOS Enhancements

              o DECMOUSE - DECMOUSE now supports VGA graphics
                modes.

              o BACKLIST.EXE, BACKUP.EXE, and RESTORE.EXE -
                These three executables are no longer supported.

          MAIL

             The new MAIL utility replaces the PCMail utility.
             MAIL has an improved user interface, works with
             both the DECnet and TCP/IP network transports, and
             can be customized by the user.

 


                                          New Functionality  1-11



          SEDT

              o LK250 - For the LK250, the keyboard files
                LKDOSM.EDT, LKDOSM.INP, and LKDOSH.EDT have
                been added; the keyboard files LKKEY.TXT and
                LKHLP.TXT have been removed.

              o MAPKEY - This new utility lets users define
                their own keyboard maps.

              o COMPAQ SLT - There is a new map for the COMPAQ
                SLT keyboard.

              o SEDT.CNF - The following changes have been made
                to the SEDT.CNF file:

                 - The KEYBOARD= setting now accepts user
                   defined keys.

                 - The FIRMWARE= and JOURNALING=ON/OFF settings
                   have been removed.

                 - The AUTOSAVE=ON/OFF setting has been added,
                   which replaces the JOURNALING=ON/OFF setting,
                   for file backups.

                 - The DEFINITIONS= setting has been added,
                   which allows users to turn function
                   definitions on or off.

          DECnet Components

              o CTERM - CTERM now passes NULL characters to
                SETHOST.

              o DNP/NETBIOS - The following changes have been
                made to DNP/NETBIOS:

                 - The DNP/NETBIOS interface now allows more
                   industry standard NETBIOS applications to
                   run.

                 - Version 4.0 of DNP supports 32 MAX LINKS
                   in EMS, in Version 3.0, the maximum number
                   allowed was 12.

 


          1-12  New Functionality



                 - Version 4.0 of DNP is 10K smaller than the
                   Version 3.0 DNP.

              o NDU - The NDU has added support for greater than
                32MB virtual disks (64, 128, 256, 512). The NDU
                can also be used for wide area access to LAD
                virtual disks. Smaller virtual disks of .360,
                .720, 1.2, and 1.44 are also available.

              o NFT - The following changes have been made to
                NFT:

                 - The Help text has been moved to the external
                   file NFTHELP.BIN.

                 - The NFT utility has been updated to run under
                   Microsoft Windows V3.0 in all modes.

                 - The default file transfer mode has changed to
                   /BLOCK when the remote system is running DOS
                   or OS/2.

                 - The NFT utility can now transfer DDIF files
                   (used by CDA).

              o FAL - The following changes have been made to
                FAL:

                 - The compatibility problem with RSTS has been
                   fixed.

                 - The FAL utility has been updated to run under
                   Microsoft Windows V3.0 in all modes.

                 - The FAL utility can now transfer DDIF files
                   (used by CDA).

                 - FAL now displays a message when the access is
                   complete and when the link is closed.

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

                 - Microsoft Windows Version 3.0 compatibility
                   added.

                 - TCP/IP Telnet support added.

 


                                          New Functionality  1-13



                 - 132 Column Screen Shifting has been fixed for
                   COMPAQ VGA cards.

                 - VT320-like terminal emulation has been added
                   (see the SETHOST Terminal Emulation Guide for
                   details).

                 - Support for 3 new keymaps has been added -
                   COMPAQ SLT/286, COMPAQ LTE/286, and COMPAQ
                   LTE/286 with external numeric keypad.

                 - Script Log Files will not be created
                   unless the environment variable
                   NVTSCRIPTLOG=device:directory\ is defined
                   to tell SETHOST where to write the log files.

                 - Support for some of the new features in the
                   V4.0 LAT TSR.

              o Spawner - The problem of running out of links
                after a long time has been fixed.

              o EMSSPEED - Several math errors have been fixed.

              o DNET Libraries - The following changes have been
                made to the DNET libraries:

                 - Microsoft Windows V3.0 support has been added
                   to the programming library.

                 - Support for Microsoft Windows V3.0 Standard
                   Mode (286) DOS extender: This is mostly in
                   DECNET.ASM, and consists of code to allocate
                   blocks of memory in the lower 640KB, copy
                   everything down there, execute non-blocking
                   DECNET calls, allow Microsoft Windows to
                   process Windows messages until the call is
                   complete, and copy the results back. All
                   of this is under a feature test so it is
                   built into only the Windows versions of
                   the libraries. If the code is present, it
                   is only executed if an actual Microsoft
                   Windows application in Standard (286) mode
                   is detected. The virtual device driver takes
                   care of it in Enhanced (386) mode.

 


          1-14  New Functionality



          DECnet/SNA Gateway NETBIOS Access Routine

             The DECnet/SNA Gateway NETBIOS Access Routine lets
             users who run DCA IRMALAN Workstation software
             use Digital's DECnet/SNA Gateway to communicate
             with an IBM host system. The NETBIOS Access
             Routine is a terminate-and-stay-resident program
             which translates NETBIOS messages from a DCA
             workstation into DECnet messages for the DECnet/SNA
             Gateway. The translation is transparent to the DCA
             workstation.

 









                                                                2

                                   Installation and Configuration
          _______________________________________________________

             This chapter contains guidelines for installing and
             configuring PATHWORKS for DOS which are not in the
             documentation, and ways to troubleshoot the known
             problems and limitations of the software.

             This chapter describes:

              o VMS installation

              o ULTRIX installation

              o Netsetup utility

              o DOSLOAD utility

          VMS Installation

             Observe the following guidelines:

              o If you are reinstalling PATHWORKS for DOS
                V4.0 in a different directory than that of the
                first installation, the previous files are not
                deleted.

              o If you reinstall PATHWORKS for VMS V4.0
                after installing PATHWORKS for DOS V4.0, you
                must update PCFS_LOGICALS.COM in SYS$STARTUP
                manually. Add the following line to the end of
                the file:

                  $ DEFINE/SYSTEM/EXECUTIVE/NOLOG PCSA$SYSTEM_SERVICE_V40 -
                  _$ PCSAV40

              o Do not install PATHWORKS for DOS V4.0 to the
                root directory of the device. Otherwise, there
                will be public access to all files on the
                device, and all files on the device will be

                                                              2-1

 


          2-2  Installation and Configuration



                deleted if the service is removed using the
                Manager Menu.

          ULTRIX Installation

             Observe the following guidelines:

              o When you enter the setld command to install
                PATHWORKS for DOS, always specify the /usr file
                system as shown in the following example:

                  # setld /usr -l /dev/rmt0h

              o If you have a previous version (or field test
                version) of PATHWORKS for DOS, you must remove
                it before you install a new version. Failure
                to remove an existing version prevents the
                installation of a new version.

                To remove a version of PATHWORKS for DOS, follow
                these steps:

                 1. Log in to the root account, or switch user
                   (su) to root.

                 2. Enter the following command:

                     # setld /usr -d PCCDOS400

                   If an error message is displayed that says
                   the PCCDOS400 subset is not installed, enter
                   the following command:

                     # setld /usr -d LWCDOS400

                You can enter the pcsamgr command to run the
                Manager Menu and tell all users to log off
                the server. Choose the Broadcast option from
                the MESSAGE menu to broadcast a message to all
                users.

 


                              Installation and Configuration  2-3



          Netsetup Utility

             This section discusses using:

              o Netsetup in general

              o Netsetup to configure DECnet

              o Netsetup to configure TCP/IP

          Netsetup in General

             Observe the following guidelines:

              o Netsetup is not designed to be, and cannot be,
                aborted while copying files.

              o You should verify that the workstation profile
                screen is correct and complete before writing
                the key diskette. To make sure that the version
                of DOS you selected is available on the system
                service or to view other choices, press F4
                to exit to DOS and view which versions are
                available.

              o Netsetup can configure a DOS client so that
                it can connect to an OS/2 server running user
                level security. However, after you configure
                your DOS client, but before you reboot, edit the
                STARTNET.BAT file and delete the REM characters
                from the beginning of the line that invokes
                SETLOGON.EXE.

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

              o If you use DOS V4.0 or higher, choose DOS
                V4.0 when Netsetup prompts you for DOS version
                information.

              o In STARTNET.BAT, no default parameters are
                specified for DLLDEPCA.EXE. Therefore, you must
                perform a cold reboot to start the client after
                STOPNET.BAT runs. Alternatively, you can edit
                STARTNET.BAT and specify the adapter name, the
                IRQ, and the RAM address, which are required by
                the datalink.

 


          2-4  Installation and Configuration



                For example:

                  %BOOT%\DECNET\DLLDEPCA.EXE /ADAPTER=DE100 /IRQ=3 /RAM=C000

              o If an error occurs that causes Netsetup to abort
                prematurely, Netsetup may change the current
                directory.

              o Netsetup cannot configure the drive on which it
                resides.

              o If memory is low, Netsetup may not display
                a complete list of the files which are being
                copied. However, all the files are being copied
                correctly.

             Note the following problems and their solutions:

                Problem: Because older thick wire 3Com Etherlink
                IIs can be damaged by selecting ThinWire as the
                default transceiver wire type, the new version
                of Netsetup uses thick wire as a default for
                Etherlink IIs.

                Solution: Before you write the key diskette,
                make sure the transceiver wire type is correct
                on the workstation profile screen.

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

                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. If you are
                running DOS V3.2, however, add the SET COMSPEC

 


                              Installation and Configuration  2-5



                command to the STARTUP.BAT file instead of the
                AUTOEXEC.BAT file.

          Netsetup to Configure DECnet

             Observe the following guidelines:

              o Netsetup requires approximately 330KB to run. If
                the required memory is not available, Netsetup
                may not be able to load the DECnet transport
                code.

              o Netsetup creates the EXECINFO.BAT file, which
                contains the SET_WSNODE and SET_WSADDR lines
                to define the client workstation's node name
                and network address. This file is rewritten
                if you use the /TEMPLATE qualifier when you
                create Remote Boot key diskettes by means of the
                server.

              o The DECnet-DOS ONLY and ASYNC key diskettes
                should be created on a hard disk because of the
                large amount of disk space they require.

              o Floppy Remote Boot diskettes can only be created
                when running Netsetup from the system file
                service.

              o Floppy Remote Boot diskettes can only be created
                on a blank, freshly formatted non-system
                diskette. If you copy the FRBCON.EXE program
                to a diskette to determine the Ethernet card
                hardware address of a remote PC, make sure to
                use a different blank, freshly formatted non-
                system diskette to create the Floppy Remote Boot
                diskette for that PC.

              o On the workstation profile screen, F1 Help is
                not available. Press the question mark (?)  key
                instead to view online Help.

 


          2-6  Installation and Configuration



          Netsetup to Configure TCP/IP

             Observe the following guideline:

             After STOPNET.BAT is run, you must reboot before
             you can restart the network.

             Note the following problem and its solution:

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

          DOSLOAD Utility

             Observe the following guideline:

             DOSLOAD does not list the versions of DOS available
             on a system service properly if there are more than
             16. To see which versions of DOS are loaded, press
             F4 to exit to DOS, then view the PCSAINFO.DAT file
             or the root directory of the system service.

             Note the following problems and their solutions:

                Problem: When you run DOSLOAD to an OS/2 Server,
                the connect fails if you did not use the NET
                SHARE command to create the PCSAV40%username
                file service (with a password) on the OS/2
                server.

                Solution: Use the NET SHARE command (specifying
                a password on the command line) to create the
                PCSAV40%username file service on the OS/2
                server, then run DOSLOAD again. When DOSLOAD

 


                              Installation and Configuration  2-7



                displays the "Privileged account name on the
                server" prompt, enter username and the password.

                Problem: If loading a version of DOS fails while
                you are copying the DOS diskettes to the system
                file service, the DOS files and the directory
                remain on the system file service.

                Solution: To remove the files and the directory:

                 1. Connect to the PCSAV40 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

                The following DOSLOAD error message does
                not appear in the Client Installation and
                Configuration guide:

             Run-time error R6000 - stack overflow

                Explanation: You tried running DOSLOAD from a
                drive that did not contain a key diskette or
                from a key diskette that did not have a DECnet
                database.

                User Action: Make sure that the key diskette
                is in the drive from which you are running
                Netsetup. If this error persists after inserting
                the key diskette, exit from DOSLOAD and run
                Netsetup to reconfigure the key diskette.

 









                                                                3

                                            Microsoft Windows 3.0
          _______________________________________________________

             This chapter describes the known limitations of the
             following:

              o Running PATHWORKS for DOS V4.0 with Microsoft
                Windows 3.0

              o Running Microsoft Windows 3.0

              o Running Microsoft Windows 3.0 VT320 terminal
                emulator

             This chapter also provides guidelines for use and
             ways to troubleshoot the known limitations.

          Running PATHWORKS for DOS V4.0 with Microsoft Windows
          3.0

             Observe the following guidelines:

              o You cannot execute the following DOS commands
                while running Microsoft Windows 3.0:

                 - MEMMAN /XMS

                 - PERMIT

                 - EMSSPEED

              o If you use an LK250 keyboard in 386 Enhanced
                mode with DECKEYB and KEYBRD loaded, make sure
                that, when you switch from one application to
                another, the correct keyboard mode is set 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 Enhanced keyboard.

                                                              3-1

 


          3-2  Microsoft Windows 3.0



              o Asynchronous DECnet at 9600 baud may drop
                logical links because of data overruns in
                Standard or 386 Enhanced mode of Microsoft
                Windows 3.0.

              o The Microsoft Windows 3.0 Setup application
                in the Main group may mistake some DECnet-DOS
                components for Windows applications.

              o If you use Microsoft Windows 3.0 in 386
                Enhanced mode, you must load the redirector into
                conventional memory.

              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 To use WIN3SETU to install Microsoft Windows 3.0
                support components from a diskette:

                 1. On a formatted diskette, create a directory
                   called MSWINV30. For the remainder of this
                   procedure, this diskette is called the
                   destination diskette.

                 2. From the PATHWORKS for DOS V4.0 diskette
                   labeled PWRKS V4.0 MSWIN V3.0, copy all
                   the files to the MSWINV30 directory on the
                   destination diskette.

                   NOTE
                   If you have RX31 media, the appropriate PWRKS
                   V4.0 MSWIN V3.0 diskette number is 1 of 2.

                 3. From the appropriate PWRKS V4.0 DNET UTILS
                   diskette (see the following table), copy the
                   VDNET.386 file to the MSWINV30 directory on
                   the destination diskette.

                   The following table matches the media you
                   have to the diskette number you need.

 


                                       Microsoft Windows 3.0  3-3


                   ______________________________________________
                   Media_______Diskette_number___________________

                   RX31        6 of 10

                   RX24        3 of 5

                   RX33________2_of_3____________________________

                 4. From the appropriate PWRKS V4.0 DNET UTILS
                   diskette (see the following table), copy the
                   VNETBIOS.386 file to the MSWINV30 directory
                   on the destination diskette.

                   The following table matches the media you
                   have to the diskette number you need.

                   ______________________________________________
                   Media_______Diskette_number___________________

                   RX31        10 of 10

                   RX24        5 of 5

                   RX33________3_of_3____________________________

                 5. From the diskette you just created, run
                   WIN3SETU.

                 6. When WIN3SETU prompts you for the PATHWORKS
                   system service drive letter, enter the letter
                   assigned to the floppy drive you are using.

                 7. Continue running WIN3SETU until it
                   completes.

             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:

 


          3-4  Microsoft Windows 3.0



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

                 o On the server, enter the pcsamgr command
                   to run the Manager Menu, create the printer
                   queue for the printer, and associate the
                   hplaserps printer type with the queue.

                Problem: If you run Microsoft Windows 3.0 in 386
                Enhanced mode and PATHWORKS for DOS components
                are loaded into EMS, then SMARTDRV.SYS with
                the /A qualifier is not supported. In other
                words, SMARTDRV.SYS and PATHWORKS for DOS cannot
                use EMS memory at the same time. If you do not
                follow this limitation, Windows fails to exit to
                DOS properly.

                Solution: Use SMARTDRV.SYS without the /A
                qualifier in extended memory, where it works
                more efficiently.

                Problem: When running under Microsoft Windows
                3.0, the DEPCA mouse does not work with a DEPCA
                Ethernet controller configured for NDIS.

                Solution: Use Netsetup to configure the DEPCA
                Ethernet controller for the proprietary Digital
                datalink.

          Running Microsoft Windows 3.0

                Observe the following guidelines:

                 o If, under Microsoft Windows 3.0 in Standard
                   mode, a non-Windows application has network
                   requests pending, do not switch from that
                   application to another because the data may
                   be returned to the new application. This can
                   cause unpredictable results.

                   This restriction does not apply to accessing
                   file or disk services, nor does it apply to
                   the use of standard NETBIOS calls. It does
                   apply to NFT, FAL, NDU, NCP, NML, SETHOST,
                   DTS, DTR, and any non-Windows application
                   written to use the DECnet-DOS socket library.

 


                                       Microsoft Windows 3.0  3-5



                 o At the time of this release, EMM386.SYS (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.SYS. Keep in mind that
                   EMM386.SYS:

                    - Does not support Standard mode (WIN /S)

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

                    - Can be copied to EMM386.COM and executed
                      to display diagnostic information

                 o If you do not have access to a specific
                   directory in a file service, the Microsoft
                   Windows 3.0 File Manager displays a "System
                   Error" message box which contains a Cancel
                   and a Retry button. If you click on the Retry
                   button, the File Manager once again tries
                   to read the directory. If you click on the
                   Cancel button, the File Manager ignores this
                   directory and finishes reading all the other
                   directories, then displays the directory list
                   for the file service.

          Running Microsoft Windows 3.0 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 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.

 


          3-6  Microsoft Windows 3.0



                 o If, when running the VT320 terminal emulator
                   under Microsoft Windows 3.0 in Standard mode,
                   you press F1 or Ctrl/S to freeze the screen
                   display, any characters you type after you
                   press the key are discarded.

 









                                                                4

                                              PC DECwindows/Motif
          _______________________________________________________

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

                 o Guidelines for use that are not documented in
                   the PC DECwindows/Motif Guide

                 o Ways to troubleshoot the known limitations

                Observe the following guidelines:

                 o The PCX Window Manager (PCX$WINMGR) supplied
                   is unchanged. It will continue to be based
                   on Version 1.0 of the VMS DECwindows Window
                   Manager. Digital will not officially support
                   the use of Motif-based applications with
                   this window manager. However, the VMS/Motif
                   Window Manager (DECW$MWM) works with Motif
                   applications. A DECW$XDEFAULTS.DAT file
                   tailored for Motif may be required in the
                   user's default VMS directory.

                 o When you do not use the X servers, you can
                   unload the BAPI, TELNET, and SOCKTSR network
                   drivers by entering the TCPUNLD /TOP call
                   three times. The first call unloads the
                   BAPI driver, the second call unloads the
                   TELNET driver, and the third call unloads the
                   SOCKTSR driver.

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

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

                                                              4-1

 


          4-2  PC DECwindows/Motif



                 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 When you use DWDOS286 in 8514/A video mode,
                   you must change the picture size to 800x640
                   or smaller to use DECpaint.

                 o When you use DWDOS386, the number that
                   indicates how much memory is being used does
                   not decrease if memory is made available.
                   This number decreases when you use DWDOS286.

                 o When you use DWCONFIG to delete valid nodes
                   and controlling hosts from DWDOS.INI,
                   they are still displayed if you enter the
                   appropriate DWCONFIG screens. However, when
                   you exit DWCONFIG, DWDOS.INI is written
                   correctly.

                 o When you run DWCONFIG for the first time,
                   a "checklist" screen is displayed. This
                   screen contains information which 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 helpful "checklist" screen is never
                   displayed.

                 o The following occurs if you use either X
                   server in monochrome video mode only: If
                   you use an application such as DECwrite
                   or DECpaint to draw and you drag one end-
                   point of a rubber-band line, a few pixels
                   may still be displayed where the whole line
                   was displayed previously. These pixels do not
                   become part of the drawing, and you can erase
                   them by refreshing the screen.

             Note the following problems and their solutions:

                Problem: You cannot run DWDOS386 from a hard
                disk drive on which the SHARE program is

 


                                         PC DECwindows/Motif  4-3



                installed. This prevents DWDOS386 from opening
                files in exclusive mode.

                Solution: Use DWDOS286.

                Problem: DWDOS286 cannot allocate data
                structures over 64KB. If you use a client that
                has high resolution video (for example, 8514/A),
                the functionality of some applications, such as
                DECpaint and DECterm, is limited.

                Solution: Use DWDOS386.

                Problem: If the X server must fulfill many
                graphics requests during a suspended PC
                DECwindows/Motif session, your TCP/IP session
                may timeout.

                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 4.1, rexec
                works only in BSD Security mode.

                Solution: PATHWORKS for ULTRIX Version 1.0
                provides a working rexec daemon which you can
                install on your ULTRIX 4.0 or 4.1 system. For
                information about installing the rexec daemon,
                see the PATHWORKS for ULTRIX V1.0 release notes.

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

                Solution: Reboot the system. To prevent this
                from happening again, use an Industry Standard
                keyboard or an LK250 with a ROM, Version A01 (or
                higher).

 


          4-4  PC DECwindows/Motif



                The following problems may occur when switching
                between PC DECwindows/Motif and Microsoft
                Windows 3.0:

                Problem: Switching back to Microsoft Windows
                may cause problems with the keyboard, video, or
                mouse (or may not work at all).

                Solution: Suspend the PC DECwindows/Motif
                session, then initiate the switch. If switching
                back to Microsoft Windows still does not work,
                there may not be enough disk space. Make sure
                there is at least 2MB of disk space in the
                Microsoft Windows temporary directory.

                Problem: Microsoft Windows 3.0 does
                not recognize all the video modes PC
                DECwindows/Motif supports, such as 800x600 and
                8514/A. If you use one of these video modes,
                switching between PC DECwindows/Motif and
                Microsoft Windows 3.0 does not work.

                Solution: Use a standard VGA video mode.

                Problem: When you start DWDOS286, you may see
                the following error message:

                  Internal memory manager error: Insufficient DOS memory

                Solution: Use DWCONFIG to adjust the DOS_
                RESERVE setting. Set DOS_RESERVE to one of the
                following:

                 o 640 - To reserve the maximum amount of memory
                   allowed for suspending a PC DECwindows/Motif
                   session.

                 o At least 60 less than the current DOS_RESERVE
                   setting - For example, if DOS_RESERVE is
                   currently set at 300, change the setting to
                   any number between zero and 240.

 









                                                                5

                                Network Utilities and Remote Boot
          _______________________________________________________

             This chapter describes the following:

              o Known limitations of the software

              o Corrections to documentation

          Known Limitations

             Observe the following guidelines:

              o If you buy a new version of EtherWORKS, check
                the release date of the software provided with
                the DEPCA board. If that date is later than the
                release date of your PATHWORKS for DOS kit, use
                the datalink driver provided with EtherWORKS.
                If the date is earlier, continue to use the
                datalink driver provided with PATHWORKS for DOS.

              o Remote Boot task images do not support TCP/IP or
                the NDIS interface.

              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 (V3.3) version of
                DISKCOPY.

              o LANSESS now runs in EMS, but this is
                not directly supported by Netsetup. You
                can run LANSESS in EMS by including
                %BOOT%\DECNET\EMSLOAD in the STARTNET.BAT file
                at the beginning of the following line:

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

                                                              5-1

 


          5-2  Network Utilities and Remote Boot



                For example, you change the previous line so
                that it looks like this:

                  %BOOT%\DECNET\EMSLOAD %BOOT%\DECNET\LANSESS /W:4 /R:4

              o If LANSESS is run in a standalone environment,
                NETTIME needs a node parameter associated with
                it.

              o In LAST, the /G:-1 qualifier must be the last
                qualifier on the command line.

              o LAT printer support cannot be accessed from an
                ULTRIX printer queue.

              o LAT writes, but does not read, data from the
                parallel port. Therefore, if you offer a
                PostScript printer, such as a DEClaser 2200
                using the parallel port in PostScript mode, the
                printer queue stalls waiting for data from the
                PostScript printer.

              o SETNAME must run after the redirector is loaded.
                If it is not, your client cannot connect to file
                services.

             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: If you run a large application, such as
                Microsoft Windows 3.0, before running NETBIND,
                the datalink may not work properly.

                Solution: Run the DLLNDIS and NETBIND programs
                soon after booting your PC.

                Problem: If, on your client, you run MS-DOS
                Version 4.0 with SHARE.EXE loaded, you may have

 


                           Network Utilities and Remote Boot  5-3



                problems running applications stored in file
                services.

                Solution: Use MS-DOS Version 4.01 or higher.

                Problem: Under certain circumstances, LANSESS
                is unable to determine the correct number of
                buffers available. An error occurs that does
                not allow data transfers. The error message
                associated with this problem is a Net 804 error.

                Solution: Place special command line qualifiers
                on the LANSESS line in the STARTNET.BAT file.
                The command line is as follows:

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

                Problem: The USE command does not display the
                printer services which are available on the
                ULTRIX server.

                Solution: Log in to an ULTRIX user account
                and use the Manager Menu to display available
                printer services. For information about using
                the Manager Menu, see the PATHWORKS for ULTRIX
                Server Administrator's Guide.

                Problem: When connected to an ULTRIX server,
                the NET ATTRIB command does not display or
                change the protection of a file located
                in a subdirectory, and the "Invalid file
                specification" error message is displayed.

                Solution: To display the protection of these
                files, log in to an ULTRIX user account and
                enter the ULTRIX command ls -l; to change
                the protection, use the chmod command. For
                information about the ls command, see ls(1)
                in the ULTRIX Reference Pages. For information
                about the chmod command, see chmod(1) in the
                ULTRIX Reference Pages.

 


          5-4  Network Utilities and Remote Boot



          Corrections to Documentation

              o In Chapter 2 of the Client Commands Reference
                manual, the following NET PRINT command format
                is incorrect:

                  NET PRINT device: /jobnumber

                This command shows the status of a specific
                print job number on a device. The correct
                command format does not include a slash (/)
                before the job number you specify:

                  NET PRINT device: jobnumber

              o In Chapter 3 of the User's Handbook, in the
                section entitled "Transferring Files over
                TCP/IP," the explanation about how to close
                an FTP connection is incomplete.

                To close an FTP connection, enter the following
                at the FTP prompt:

                  CLOSE

              o The ASCII file USER_HANDBK.TXT is included on
                one of the Unsupported Disks. In the event that
                you change the USER_HANDBK.TXT file, remove the
                Digital copyright notice thereon and substitute
                the following disclaimer:

                The attached document in ASCII format is
                provided "as is", does not contain any figures,
                and Digital does not attest as to its accuracy.
                Digital will not provide any additional
                information, such as figures, for the document.
                Digital has placed the document in the public
                domain and disclaims any copyright on the
                attached document. The document may be amended
                freely, but must be copied and distributed
                without acknowledging any copyright or other
                right of Digital, or even Digital as its source.

 









                                                                6

                                                             MAIL
          _______________________________________________________

             The following are the limitations of the new
             MAIL utility and ways to troubleshoot those
             limitations.

                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 Screen Type to default in
                MAIL.INI, 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.

                Problem: When viewing a directory, pressing
                the Enter key displays the NEXT message listed.
                Therefore, when you first display a directory

                                                              6-1

 


          6-2  MAIL



                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.

 









                                                                7

                                                 DOS Enhancements
          _______________________________________________________

             This chapter describes the known limitations of the
             following DOS Enhancements:

              o KEYBRD

              o XONXOFF

              o DECMOUSE

             This chapter also provides guidelines for use which
             are not documented in the Client Commands Reference
             manual.

          KEYBRD

              o Do not use KEYBRD with LOADHI.

              o 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
                workstation may hang.

              o Load KEYBRD before you load any other TSR
                keyboard programs because KEYBRD does not pass
                keystrokes on to other TSR keyboard programs.

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




                                                              7-1

 


          7-2  DOS Enhancements



          XONXOFF

              o Do not use XONXOFF with LOADHI.

              o Load XONXOFF before any network components
                because XONXOFF does not pass INT 14 calls on
                to TSR's loaded previously.

          DECMOUSE

              o Do not use DECMOUSE with LOADHI.

              o DECMOUSE treats all EtherWORKS (DEPCA)
                network controllers the same. Therefore, load
                DECMOUSE.SYS or DECMOUSE.COM only on cards
                which have the appropriate mouse port. If
                DECMOUSE runs on a card which does not have the
                appropriate mouse port, the network software may
                not initialize correctly.

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









                                                                8

                                                DECnet Components
          _______________________________________________________

                This chapter contains guidelines and ways to
                troubleshoot the known problems and limitations
                that you may find when using the PATHWORKS
                for DOS V4.0 components. These components are
                discussed in detail in the following documents:

                 o DECnet User's Guide

                 o SETHOST Terminal Emulation Guide

                 o DECnet Network Management Guide

                 o DECnet Programmer's Reference Manual.

          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.






                                                              8-1

 


          8-2  DECnet Components



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


                                           DECnet Components  8-3



          NETBIOS and DNP

                Observe the following guidelines when using DNP
                and NETBIOS:

                 o The DNP/NETBIOS interface now allows more
                   industry standard NETBIOS applications
                   to run. Problems reported with IRMALAN,
                   ATTACHMATE and XPERT NETBIOS applications
                   have been corrected.

                 o Loading DNP into the High Memory Area
                   (HMA) is not recommended and may produce
                   unpredictable results.

                Be aware of the following restriction when using
                DNP:

                Problem: Using the command NCP SET EXEC STATE
                OFF to unload DNP causes any other application
                that processes interrupt 5C, such as LANSESS to
                hang.

                Solution: Use MEMMAN /U to unload the network.

          DNP Asynchronous Limitations

                Observe the following guideline:

                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 Control Program (NCP)

                Observe the following guidelines when using NCP:

                 o All LAT support has been removed from NCP
                   since those functions are now in LATCP.

                 o When using Async DECnet, NCP LOOP CIRCUIT
                   NODE node-name does not work. No error
                   message appears but the loop operation is
                   not performed.

 


          8-4  DECnet Components



                 o If you discontinue a loop circuit by using
                   Ctrl/C, the circuit service is left disabled.

                Be aware of the following problem and its
                solution:

                Problem: If you break the network connection,
                the personal computer links do not disconnect.

                Solution: Use the NCP SET KNOWN LINKS STATE OFF
                command to manually close the links.

          Network Device Utility (NDU)

                Observe the following guidelines when using the
                NDU:

                 o You cannot diskcopy to or from NDU disks.

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

          Virtual Printer Driver (NPDRV.SYS)

                Observe the following guideline when using the
                virtual printer device:

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


                                           DECnet Components  8-5



          Network File Transfer (NFT)

                Observe the following guideline when using the
                NFT utility:

                When printing remote files using wildcards, NFT
                prints only the first file that satisfies the
                wildcard specification.

          Network Virtual Terminal (SETHOST)

                Observe the following guidelines when using the
                SETHOST utility:

                 o The SETHOST utility lets you create a new DOS
                   process from within your terminal session.
                   The following limitations apply when creating
                   a new DOS process from SETHOST:

                    - Do not install terminate-and-stay-resident
                      programs (TSRs). When a TSR is run while
                      using the To MS-DOS feature, it can cause
                      memory fragmentation. This fragmentation
                      can cause programs to fail if they are run
                      after SETHOST exits.

                      This restriction includes the MS-DOS PRINT
                      program when it is run for the first time.
                      Note that the MODE and KEYB commands are
                      TSRs, under certain conditions.

                    - Environment variables that are set in a
                      DOS process are lost when you exit the
                      process.

                 o The SETHOST keyboard mappings have changed.
                   Refer to the DECnet SETHOST Terminal
                   Emulation Guide for more information.

                 o Running SETHOST with a keyboard buffer, which
                   has been extended using the DECMODE utility
                   from the PATHWORKS for DOS Client kit, does
                   not work. Reset the keyboard buffer to the
                   default by using DECMODE m, 16, or use the
                   public domain utilities, such as BIGBUFF or
                   KBFIX2, to extend the keyboard buffer.

 


          8-6  DECnet Components



                 o Pressing F3 to enter and exit Set-Up mode
                   produces snow on the screen when an IBM CGA
                   video card is used.

                Note the following problem and its solution:

                Problem: The SETHOST utility displays spurious
                characters if data overruns (lost data) occur
                when using the COM port.

                Solution: Restart SETHOST using the /R
                qualifier. The /R qualifier causes SETHOST to
                rotate the hardware interrupt priorities such
                that the COM port is the highest, so that data
                overruns can be overcome.

          TCP/IP and SETHOST

                You should be aware of the following guidelines
                when using the SETHOST utility with TCP/IP:

                 o For Telnet connections, the TCP/IP
                   environment does not have Microsoft Windows
                   3.0 support, so SETHOST over Telnet under
                   Microsoft Windows 3.0 is not supported.
                   However, you may need the following
                   information if you are trying to get it
                   to work under the other task switching
                   environments:

                    1. SET NVTWIN=1; Set the DOS environment
                      variable NVTWIN to 1 to prevent SETHOST
                      from trying to load or unload the network
                      terminal drivers.

                    2. Load the network terminal drivers BEFORE
                      running a task switcher. Run DNRTSR, TN,
                      and BAPI.

                    3. After exiting the task switcher
                      environment, you can unload the network
                      terminal drivers with:

                       - TCPUNLD /TOPONLY (unloads BAPI)

                       - TCPUNLD /TOPONLY (unloads TN)

 


                                           DECnet Components  8-7



                       - TCPUNLD /TOPONLY (unloads DNRTSR)

                 o TELNET connections are case sensitive on the
                   host names, so SETHOST passes to the BAPI
                   interface the exact case of the host name you
                   supply. If that name is not known to TELNET,
                   SETHOST reverses the case of the name entered
                   and tries again.

                Be aware of the following problem and its
                solution:

                Problem: The SETHOST setup screens may appear
                corrupted if you select Network Communications
                Port when using a TCP/IP configuration.

                This happens because SETHOST loads the following
                TCP/IP drivers:

                 - DNRTSR.EXE

                 - TN.EXE

                 - BAPI.EXE

                Each of these drivers displays text on the
                screen when they install.

                Solution: Press the F3 key twice to exit and
                then reenter setup to clear the problem.

          SETHOST and Microsoft Windows 3.0

                You should be aware of the following guidelines:

                 o If you want to use SETHOST running under
                   Microsoft Windows 3.0 over a LAT or CTERM
                   connection:

                    1. SET NVTWIN=1; Set the DOS environment
                      variable NVTWIN to 1 to prevent SETHOST
                      from trying to load or unload the network
                      terminal drivers.

                    2. Load the network terminal drivers BEFORE
                      running Microsoft Windows 3.0. If you want
                      to use LAT, run LAT.EXE. If you want to
                      use CTERM, run CTERM.EXE

 


          8-8  DECnet Components



                    3. After exiting windows you can unload the
                      network terminal drivers with:

                       - LAT /U (unloads LAT)

                       - CTERM /U (unloads CTERM)

                      The same restriction applies to other task
                      switching environments like DESQVIEW and
                      Software Carousel.

          CTERM Connections for SETHOST

                Observe the following guidelines when running
                SETHOST with a CTERM connection:

                 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.

          Asynchronous DECnet Connections for SETHOST

                Observe the following guideline when using an
                asynchronous DECnet configuration:

                If SETHOST finds a LAT.EXE in the path (left
                over from a previous Ethernet configuration),
                it tries to use LAT first and then it tries
                CTERM. LAT will fail because it is used only
                for Ethernet connections. You can delete or
                move LAT.EXE to a path that is used only by an
                Ethernet configuration.

 









                                                                9

                                           Programming Components
          _______________________________________________________

                This chapter contains guidelines and ways to
                troubleshoot known problems and limitations
                that you may find when using the PATHWORKS
                for DOS V4.0 programming components. These
                components are discussed in detail in the DECnet
                Programmer's Reference Manual.

          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 V4.0 TYPE command cannot access a
                   remote file with TFA if the remote file is
                   not in the current directory.

                 o The DOS V4.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 V4.0, COMMAND.COM uses undocumented
                   calls for file access instead of the
                   standard, documented ones that are supported
                   by TFA.

                 o Use NFT TYPE and NFT COPY commands for remote
                   file access from a command level.

                 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

                                                              9-1

 


          9-2  Programming Components



                   that TFA supports in the DECnet Programmer's
                   Reference Manual.)

          Microsoft Windows Support in General

                Observe the following guidelines when using
                Microsoft Windows:

                 o Asynchronous DECnet at 9600 baud may get 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. (The DECnet protocol will
                   handle the errors)

                 o If you have an asynchronous DECnet
                   configuration, running Microsoft Windows 3.0
                   in 386 Enhanced mode and loading the network
                   into EMS memory is not recommended because it
                   is not reliable.

                 o Memory resident utilities (for example, TTT,
                   TFA, LAT, CTERM) must be installed before
                   starting Microsoft Windows, so that they
                   will be available to all applications you run
                   with Microsoft Windows. Unpredictable results
                   will occur if they are loaded after Microsoft
                   Windows starts.

          Troubleshooting and Unsupported

                The pieces of the DECnet kit that covered
                troubleshooting as well as several unsupported
                utilities are now on the unsupported or
                troubleshooting disks.

 


                                      Programming Components  9-3



          DECnet Programming Library

                Observe the following guidelines when using the
                DNET libraries for V4.0:

                 o Bug fixes have been made for large model.
                   Casting is now used instead of calls to
                   loadhi (foo,dsreg()).

                 o "exptr" is now a far pointer, not a long
                   integer.

                 o If you are developing an application to
                   run under Microsoft Windows, follow the
                   instructions in the Microsoft Windows Support
                   release notes.

                Note the following problem and its solution:

                Problem: Using the C INCLUDE module DNFUNDEF.H
                in a program and compiling using MICROSOFT
                C V6.0, may result in the following compiler
                error:

                  dnfundef.h(106)  : error C2059: syntax error : '*'
                  dnfundef.h(106)  : fatal error C1022: expected '#endif'

                There are two C syntax errors in DNDUNDEF.H.

                Solution: Change lines 106 and 110. Line 106
                must be changed from:

                                  extern  int decnet(iocb *iocbptr);

                to:

                                  extern  int decnet(IOCB *iocbptr);

                Change line 110 from:

                                  extern int msdos(scb *scbptr);

                to:

                                  extern  int decnet(SCB *scbptr);

 


          9-4  Programming Components



                The library source code will be corrected in the
                next release.

 









                                                               10

                        DECnet/SNA Gateway NETBIOS Access Routine
          _______________________________________________________

             This chapter discusses:

              o Guidelines for use

              o Undocumented error codes

             Observe the following guidelines:

              o The DECnet/SNA Gateway NETBIOS Access Routine
                supports only DECnet/SNA Gateway-CT and -ST.
                There is no support for the DECSA Gateway or
                VMS/SNA.

              o The NETBIOS Access Routine requires slightly
                more than 46,000 bytes of conventional memory.
                This may cause problems if DECnet-DOS is loaded
                into conventional memory and APA graphic support
                is required. There is not enough memory to load
                the 3270 APA graphic support for a DCA IRMALAN
                Workstation without moving the network software
                into EMS memory. After loading all the network
                software, but before loading SNAGNI.EXE, there
                must be a minimum of 570,000 bytes available
                to run the DCA graphic support software. This
                assumes a fully configured IRMALAN workstation
                with four CRT sessions and one printer session.
                It may be possible to run with slightly less
                memory with a smaller workstation configuration.

              o All problem reports you send to your Digital
                representative should include:

                 - Description of the problem with explicit
                   directions for reproducing it

                 - Current SNAGNI configuration file

                 - Current LAN78S configuration file

                                                             10-1

 


          10-2  DECnet/SNA Gateway NETBIOS Access Routine



                 - 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

                Where:

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

                max_rusize       Is the value in the the SNAGNI
                                 configuration file for the MAX_
                                 RUSIZE parameter.

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

                Request a copy of the debug version of
                SNAGNI, called DSNAGNI.EXE, from the Digital
                representative. If you can reproduce the problem
                using DSNAGNI.EXE, send the log file which is
                created when you run DSNAGNI to your Digital
                representative. Included with DSNAGNI.EXE is a
                file called DSNAGNI.DOC, which explains how to
                use DSNAGNI.EXE.

              o 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 There is currently no support for DCA's Ram
                Expander product. This product may work with
                SNAGNI most of the time but there are known
                problems at this time. These problems may
                cause the PC to hang if SNAGNI is used with RAM
                Expander.

 


                  DECnet/SNA Gateway NETBIOS Access Routine  10-3



             The following error codes, which are displayed
             on the status line, are undocumented. For each
             error code, an explanation and a way to respond is
             provided.

             03

                Explanation: One or more of the gateway entries
                in the SNAGNI configuration file is not a
                DECnet/SNA gateway.

                Action: Edit the configuration file and
                make sure all gateway entries specify actual
                DECnet/SNA gateways.

             09

                Explanation: There are no more NETBIOS resources
                available.

                Action: Use the Network Control Program to
                increase the number of DECnet links. For
                example, to increase the number of links to 10,
                enter:

                  NCP> DEF EXEC MAX LINKS 10

                NOTE
                After you enter the NCP command, you must
                reboot your PC for the increase to take effect.
                Increasing the number of links increases
                the amount of memory used by DECnet and may
                prevent loading DECnet into EMS. If this
                happens and you want to maintain your current
                DECnet configuration, reduce the number of DCA
                Workstation sessions.

 


          10-4  DECnet/SNA Gateway NETBIOS Access Routine



             0D

                Explanation: There is a duplicate name in the
                local name table.

                Action: Unload SNAGNI and reload it. If
                the problem persists, contact your Digital
                representative.

             12

                Explanation: A session open request was
                rejected.

                Action: Unload SNAGNI and reload it. If
                the problem persists, contact you Digital
                representative.

             15

                Explanation: The GATEWAY name cannot be found.

                Action: Make sure the CALLNAME parameter in the
                SNAGNI.CFG file matches the GATEWAY name in the
                IRMALAN configuration file (LAN78S.CFG).

             18

                Explanation: There are too many files open at
                the same time.

                Action: Use the Network Control Program to
                increase the number of DECnet links. For
                example, to increase the number of links to 10,
                enter:

                  NCP> DEF EXEC MAX LINKS 10

                NOTE
                After you enter the NCP command, you must
                reboot your PC for the increase to take effect.
                Increasing the number of links increases
                the amount of memory used by DECnet and may
                prevent loading DECnet into EMS. If this
                happens and you want to maintain your current

 


                  DECnet/SNA Gateway NETBIOS Access Routine  10-5



                DECnet configuration, reduce the number of DCA
                Workstation sessions.

             3C

                Explanation: A connection timed out.

                Action: Check your Ethernet connection and make
                sure the cable is still connected.

             E9

                Explanation: The NETBIOS Access Routine does not
                support DECSA gateways.

                Action: Use a DECnet/SNA Gateway-CT or -ST.
