NetNews Usenet Archive 1992 #31/NN_1992_31.iso/spool/vmsnet/networks/desktop/pathwork/3818

Internet Message Format | 1992-12-22 | 26.4 KB

Path: sparky!uunet!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!kuhub.cc.ukans.edu!lanworks!list
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: RE: White paper on Windows for Workgroups & Pathworks
Message-ID: <[e-mail]>
From: [e-mail]
Date: 21 Dec 1992 09:24:00 -0500
Sender: A discussion of Digital's PCSA product <[e-mail]>
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Lines: 605

     HOWDY!

     Well, this will be my third attempt at posting this white
     paper.  The first time was my fault - I couldn't get MAIL
     to read in the document and then I typed CNTRL-Z instead of
     cancel.  Oh well.  The second time, the paper just went
     into the ether.  So, I'll try it again.  Sorry for the
     confusion!

     Anyway, the only catch to the following is that you must
     set your workstation name and password to be the same as
     your username password on the VAX server.  Otherwise, the
     following steps work like a charm.  Happy networking!

     Jenett Tillotson
     [e-mail] or [e-mail]
     Ames Laboratory
     [phone]

     P.S. (Have a happy holiday!)

-----------------------------------------------------------------------

PATHWORKS & Windows For Workgroups With the Microsoft Enhanced Redirector
Last Technical Review:  1-DEC-1992                            Size: 585 lines

Copyright (c) Digital Equipment Corporation, 1991,1992 All Rights Reserved.
Unpublished Rights Reserved Under The Copyright Laws Of The United States.

Any party granted access to this information pursuant to a duly executed
Digital Service Agreement may, under the terms of such agreement, use, copy,
download, store, or transmit such information internally for the exclusive
purpose of maintaining and operating the products covered by such agreement.
No other use, copying, storage or transmission is permitted except with
Digital's prior written consent.



PRODUCT: PATHWORKS for VMS, Version 4.1, 4.1-1, 4.1-2
         PATHWORKS for DOS, Version 4.1a

OP/SYS: VMS, Version 5.3, 5.4, 5.5
        DOS, Version 3.3, 4.0, 5.0

SOURCE: Customer Support Center / USA


=========================================================================


Implementing Windows For Workgroups & PATHWORKS with
the Microsoft Enhanced Redirector
----------------------------------------------------


This article contains general information and recommendations about
the implementation of PATHWORKS in conjunction with Microsoft's
Windows for Workgroups Version 3.1.


Preliminary PATHWORKS Installation
----------------------------------

PATHWORKS should be installed on the DOS/Client first. This includes
new installations of Windows for Workgroups (WFW) or the upgrade of
an existing installation of Windows 3.0, 3.0a, or 3.1. The following
guidelines will be useful.

-> Install PATHWORKS with either the "basic" or "enhanced" version of
   the Redirector. The version selected for the "PATHWORKS" Redirector
   is not critical with respect to WFW, since it will be using its own
   Redirector when this implementation is completed.

   However, if the "basic" Redirector is chosen, the WFW installation
   will display an error message indicating that an "incompatible"
   network is being used. This error message can be ignored, as we will
   be modifying the PATHWORKS startup after we finish installing WFW.

-> Install PATHWORKS using the NDIS drivers for the network adapter
   (i.e. select the "EtherWORKS NDIS" as the Ethernet adapter from
   the NETSETUP utility).

-> The following PATHWORKS files should be moved to the "\DECNET"
   directory on the DOS/Client's boot disk, if they are not already
   there. This is required so that they can be loaded before WFW is
   started, since the connection to the PCSAV4x file service will be
   made after WFW is started.

        \\pcsav4X\lmdos\drivers\pcsa\LAD.EXE
          (if Disk Services will be in use from DOS or WFW)

        \\pcsav4X\lmdos\drivers\pcsa\LADCDDRV.SYS
        \\pcsav4X\lmdos\drivers\pcsa\MSCDEX.EXE
          (if CDROM's will be used from an INFOSERVER with DOS or WFW)

        \\pcsav4X\decnet\LAT.EXE
        \\pcsav4X\decnet\LATCP.EXE
        \\pcsav4X\decnet\CTERM.EXE
          (if SETHOST or VT320 will be used)

        \\pcsav4X\pcapp\SETHOST.EXE
        \\pcsav4X\pcapp\KBDxxxx.KBD (specific keyboard file)
          (if SETHOST will be used from DOS)

        \\pcsav4X\dosenh\KEYBRD.EXE
        \\pcsav4X\dosenh\DECKEYB.COM
          (if an LK250 or LK450 keyboard will be used)

        \\pcsav4X\lmdos\drivers\pcsa\EMSLOAD.EXE
          (if EMS will be used on the system)

        \\pcsav4X\decnet\NFT.EXE or \\pcsav4X\decnet\NFTNOWIN.EXE
        \\pcsav4X\decnet\FAL.EXE or \\pcsav4X\decnet\FALNOWIN.EXE
          (if these utilities will be used from DOS)

        \\pcsav4X\decnet\NCP.EXE
          (if this utility will be used from DOS)

-> If SETHOST or VT320 will be used, the "SET NVTWIN=1" DOS variable
   must be defined before starting WFW (preferably in the
   AUTOEXEC.BAT file. It is also recommended that any modifications to
   the DECLAT.DAT file such as expanding the "LAT Service Table",
   modifying the number of "Application Session Control Blocks" (SCB's),
   or adding "Preferred LAT Services", be completed (using the LATCP
   utility) before installing WFW.

-> If additional information is required in the NCP database, such as
   the node names/addresses of other DOS/Clients or additional PATHWORKS
   servers, it is recommended that this work is completed at this time.

-> The WFW installation does not include a copy of the DECNET.386
   (VxD) protected mode driver that ships with Windows 3.1. If you are
   installing WFW over an existing copy of Windows 3.1, and "DEC
   PATHWORKS" was selected as the network during the SETUP, this driver
   has already been copied into the "\WINDOWS\SYSTEM" directory.

   However, if this is a new WFW installation, or if the WFW
   installation is also an upgrade from Windows 3.0 (or 3.0A), a new
   DECNET.386 driver should be obtained ahead of time. The copy of
   DECNET.386 (or DECNB.386) provided in the "\\pcsav4X\mswinv30"
   directory should not be used. These drivers are out-of-date with
   respect to any Windows 3.1 installation.

   The most up-to-date drivers can be obtained over DSNlink by
   downloading CSCPAT_3046, by contacting the Customer Support Center
   (CSC), or from the DECPCI forum on CompuServe.

Additional modifications will be made after WFW installation has
completed (see the section on "PATHWORKS Post Installation Tasks"
below).


Installing Windows for Workgroups
---------------------------------

After completing the steps listed in the section above (Preliminary
PATHWORKS Installation), start the WFW installation. Be prepared to
supply the following information.

-> You must know the type of Ethernet Adapter in your DOS/Client along
   with its IRQ setting, "Base I/O Port", and "Base Memory Address"
   (if the adapter uses Upper Memory Blocks).

-> A selection for the "Computer Name" and "Password" for the
   DOS/Client, and the "Workgroup" to which it will belong. The length
   of each of these items should be limited to 12 characters.

-> When prompted to specify the "Network in Use", "Microsoft LAN
   Manager" should be selected for a PATHWORKS network.

When you have completed the WFW installation, DO NOT REBOOT THE
MACHINE! Return to the "DOS Prompt" and perform the post installation
tasks described in the next section.


PATHWORKS Post Installation Tasks
---------------------------------

The following tasks are required to bring the DOS/Client to a state
where WFW will run properly.

-> CONFIG.SYS
   ----------
   The CONFIG.SYS file will require modification. The references to
   PROTMAN.SYS and DEPCA.DOS (both located in the "\DECNET" directory)
   should be changed to reference the "equivalent" files supplied by
   WFW (in the "\WFW" directory). The WFW installation will also add a
   reference to a WORKGROUP.SYS file. The reference to the DLLNDIS.EXE
   file should be added manually.

   The following example CONFIG.SYS file illustrates these references.
   The Windows for Workgroups directory for this example is "D:\WFW".
   The memory management uses the drivers provided with WFW. This file
   is for a DOS/Client equipped with a DEC "DE200" (Turbo) Ethernet
   adapter using the UMB range of C800-Cfff. Two LAD (disk) services
   and two LADCDROM (INFOSERVER/CD) services are specified. Note that
   the memory drivers are called from the WFW directory. The drivers
   loaded in the example file (below) are order dependent. The loading
   order illustrated is recommended.

        files=40
        buffers=10
        stacks=9,256
        device=d:\wfw\himem.sys
        device=d:\wfw\emm386.exe on 384 ram d=48 frame=e000 x=c800-cfff
        devicehigh=c:\decnet\laddrv.sys /D:2
        devicehigh=c:\decnet\ladcddrv.sys /N:2
        device=D:\WFW\PROTMAN.DOS /I:D:\WFW
        device=D:\WFW\DEPCA.DOS
        device=C:\DECNET\DLLNDIS.EXE
        device=D:\WFW\WORKGRP.SYS
        shell=c:\dos\command.com c:\dos /e:528 /p
        lastdrive=z
        dos=high

-> AUTOEXEC.BAT
   ------------
   Any references to utilities, paths, or other DOS variables should be
   revised to point to the directory where WFW is installed. Note the
   PATH, TEMP variable, SMARTDRV.EXE, and LMOUSE.COM references in the
   sample AUTOEXEC.BAT file below. The NVTWIN variable is set to "1" for
   SETHOST and VT320.

        D:\WFW\NET START
        @echo off
        path c:\dos;c:\;D:\WFW;c:\decnet;d:\xcursion
        prompt $P$G
        set NVTWIN=1
        set TEMP=C:\WFW\TEMP
        D:\WFW\SMARTDRV.EXE 512
        loadhigh c:\dos\doskey.com
        loadhigh D:\WFW\LMOUSE.COM
        call c:\decnet\startnet.bat
        :end

   The WFW setup/installation placed the "D:\WFW\NET START" line at the
   top of the file.

-> SYSTEM.INI
   ----------
   The following line should be added to the "[386Enh]" section of the
   SYSTEM.INI file.

        Timercriticalsection=10000

   If a third party memory manager such as Quarterdeck's "QEMM" or
   Qualitas's "386MAX" is used, the following line should also be added
   to the "[386Enh]" section of the SYSTEM.INI file.

        SystemROMBreakPoint=FALSE

   If "eXcursion" or "PC DECWindows" will be used, add the following
   line to the "[386Enh]" section of the SYSTEM.INI file.

        DNETHeapSize=64

   The "network=" line in the "[386Enh]" section should be revised to
   include a reference to the DECNET.386 VxD at the end of the line.

        network=vnetbios.386,vnetsup.386,........,DECNET.386

-> PROTOCOL.INI
   ------------
   When the WFW installation is completed, the PROTOCOL.DOS file (in
   the WFW directory) will contain only the information based on the
   information supplied during the WFW setup. This file will require
   revision to enable multiple protocol stacks to be loaded. An example
   PROTOCOL.INI file follows. This example file is for a DOS/Client
   equipped with a DEC "DE200" (Turbo) Ethernet adapter using the UMB
   range of C800-Cfff and IRQ 5. The two protocols used are NETBEUI (for
   WFW) a DATALINK section for PATHWORKS. Note that the "LANA" number for
   the DATALINK is the next number available in the file (in this case
   "1" with NETBEUI using "0") and must agree with the DNNETH line in
   the STARTNET.BAT file.

        [network.setup]
        version=0x3100
        netcard=ms$ewtrb,1,MS$EWTRB
        transport=ms$netbeui,MS$NETBEUI
        lana0=ms$ewtrb,1,ms$netbeui
        LANA1=MS$EWTRB,1,DATALINK     <--------- ADDED LINE ---------

        [protman]
        DriverName=PROTMAN$
        PRIORITY=MS$NETBEUI

        [MS$EWTRB]
        DriverName=DEPCA$
        RamAddress=0xC800
        Interrupt=5
        MaxMulticast=8
        MaxTransmits=16

        [MS$NETBEUI]
        DriverName=netbeui$
        SESSIONS=10
        NCBS=32
        BINDINGS=MS$EWTRB
        LANABASE=0

        [DATALINK]                 <--- ADDED SECTION (to this file)
        DRIVERNAME   = DLL$MAC
        BINDINGS     = MS$EWTRB    <--------- ADDED LINE -----------
        LG_BUFFERS   = 16           (to a standard DATALINK section)
        SM_BUFFERS   = 6
        OUTSTANDING  = 32
        HEURISTICS   = 0

The BINDINGS for several of the DEC Ethernet adapters are listed below.

        CARD                               BINDINGS
        ----                               --------
        DEC DEPCA ........................ ms$depca
        DEC EE101 (Built-in) ............. ms$ee101
        DEC Ethernet (All Types) ......... ms$decgen
        DEC EtherWorks LC ................ ms$ewlc
        DEC EtherWorks LC/TP ............. ms$ewlctp
        DEC EtherWorks LC/TP_BNC ......... ms$ewlctpb
        DEC EtherWorks MC ................ ms$ewmc
        DEC EtherWorks MC/TP ............. ms$ewmctp
        DEC EtherWorks MC/TP_BNC ......... ms$ewmctpb
        DEC EtherWorks Turbo ............. ms$ewtrb
        DEC EtherWorks Turbo/TP .......... ms$ewtrbtp
        DEC EtherWorks Turbo/TP_BNC ...... ms$ewtbtpb
        DECpc 433 WS (Built-in) .......... ms$decpc

-> STARTNET.BAT
   ------------
   Several modifications should be made to the STARTNET.BAT file. They
   are listed below.

        - The lines referring to DLLNDIS and NETBIND should be deleted
          or remarked out.
        - The "/LANA:n" parameter should be added to the end of the lines
          referencing the DNNETH.EXE file, where "n" is the number used
          in the PROTOCOL.INI file for the "LANA" number for "[DATALINK]".
        - Add the  line "GOTO TIMEDONE", immediately after the ":lastdone"
          label.
                        :lastdone
                        GOTO TIMEDONE

        - If LAD.EXE, MSCDEX.EXE, or LAT.EXE are required, the references
          to these files should be moved to after the ":timedone" label.
          Any references to the DOS variable "%_SYSD%" should be changed
          to the local device drive letter.

   After completing these modifications, the system should be rebooted. A
   sample STARTNET.BAT file is listed below.

        echo off
        break on
        cls
        echo ------------------------------------------------------------
        echo PATHWORKS for DOS V4.1/LM 2.1  Network Operating Environment
        echo    Created by NETSETUP.EXE V4.1.080 Configuration Utility
        echo                      DNETOMO.V41  V4.1.063
        echo                      DNETWIK.V41  V4.1.060
        echo    (C)Copyright 1986-1991 by Digital Equipment Corporation
        echo ------------------------------------------------------------
        echo A license is required for every personal computer running
        echo PATHWORKS software. Please insure that your personal computer
        echo is properly licensed as a PATHWORKS client before running
        echo this software. Unauthorized copies are in violation of
        echo copyright laws.
        echo ------------------------------------------------------------
        %BOOT%\decnet\netenvi 145 48
        if errorlevel 1 goto exit
        set PCSA=%BOOT%\DECNET
        set DECNET=%BOOT%\DECNET
        %BOOT%\decnet\sch /H
        if not errorlevel 1 goto schdone
        echo ** ERROR ** Unable to start the Network Scheduler
        goto error
        :schdone
        %BOOT%\decnet\emsload %BOOT%\decnet\dnneth.exe /LANA:1 /rem:2
        if errorlevel 1 %BOOT%\decnet\dnneth.exe /LANA:1 /rem:2
        if not errorlevel 1 goto decnetdone
        :decneterror
        echo ** ERROR ** Unable to start DECnet
        goto error
        :decnetdone
        %BOOT%\decnet\emsload %BOOT%\decnet\last /N:%_WSNODE% /c:d /M:D /g:-1
        if not errorlevel 1 goto lastdone
        %BOOT%\decnet\last /N:%_WSNODE% /c:d /M:D /g:-1
        if not errorlevel 1 goto lastdone
        echo ** ERROR ** Unable to start the local Area System Transport
        goto error
        :lastdone
        echo ------------------------------------------------------------
        echo Start the local Area Disk Software
        %BOOT%\DECNET\emsload %BOOT%\DECNET\lad.exe /R:-1 /W:-1 /a:-1
        if not errorlevel 1 goto laddone
        %BOOT%\DECNET\lad.exe /R:-1 /W:-1 /a:-1
        if not errorlevel 1 goto laddone
        echo ** ERROR ** Unable to start the local Area Disk Software
        :laddone
        %BOOT%\DECNET\MSCDEX.exe /D:$LADCD /E
        echo ------------------------------------------------------------
        echo Start the local Area Transport Software
        %BOOT%\DECNET\emsload %BOOT%\DECNET\lat.exe
        if not errorlevel 1 goto latdone
        %BOOT%\DECNET\lat.exe
        if not errorlevel 1 goto latdone
        echo ** ERROR ** Unable to start the local Area Transport Software
        :latdone
        goto exit
        :error
        echo ------------------------------------------------------------
        echo                 There were start-up errors.
        echo ------------------------------------------------------------
        :exit


WFW/PATHWORKS Application Configuration
---------------------------------------

PATHWORKS applications used with WFW should be installed using the same
procedures that apply to Windows 3.1. However, it is recommended that the
PIF files for DOS applications are copied to the local WFW directory for
convenience and editing purposes. These applications can be executed from
the PCSAV4x file service as soon as it is attached to the DOS/Client.

The DOS variable "%_SYSD%, which would be defined/set with the "USE"
command during a "standard PATHWORKS installation, can still be used to
reference the network drive assigned to PCSAV4x. To take advantage of
this method, the variable should be defined before starting WFW,
preferably by adding a "SET _SYSD=X:" line to the AUTOEXEC.BAT file
(where "x" is the assigned drive letter). It is also recommended that this
drive is attached first (and always to the same device designation) when
starting WFW.


TECHNICAL NOTES
---------------

The following PATHWORKS applications will not function with this
arrangement.

-> PERMIT UTILITY AND DEVICE SHARING
   ---------------------------------
   The PERMIT utility will not function from DOS (i.e. outside of
   the WFW environment). From within WFW, the "SHARE" selection
   (accessed from the File Manager utility) is available for this
   functionality. Locally attached printers can also be shared from
   the WFW Print Manager utility.

   If another DOS/Client is connected to your shared device, the
   connection can be monitored with the "NetWatcher-2" utility
   (provided with WFW). If the other DOS/Client is using the PATHWORKS
   "USE" command from DOS, the connection will be noted as from a
   "MS Net 3.0" network. If the other DOS/Client is connecting from the
   WFW File Manager (or Print Manager), the connection will be noted as
   from a "Microsoft Workgroup Client" when displaying.

   If the connection is terminated from the "NetWatcher - 2" utility,
   the other DOS/Clients can still re-connect back to the shared device
   without re-attaching to it. This is true weather they were connected
   with "USE" or through WFW. To permanently disconnect the other
   DOS/Clients, you must use the "STOP SHARING" selection in File Manager
   or Print Manager, as applicable.

-> BROADCAST RECEIVER
   ------------------
   The "Broadcast Receiver" (the RCV and WINRCV utilities) will not
   function the same as it does with Windows 3.1 or [stand alone]
   PATHWORKS. When the RCV utility is loaded after the network is started,
   an error indicating stating "Computer name not set" will be displayed.
   If the SETNAME utility (shipped with PATHWORKS) is executed, it will
   display an error stating "Incorrect Redirector version".

   If WFW is started and then later exited (completely exited, not
   shelled to the "DOS Prompt"), the RCV utility can be successfully
   executed. The DOS/Client will now receive all broadcast messages
   directed to it (from Servers or other DOS/Clients using PATHWORKS).
   The WINRCV utility will also function.

   If you will be sending broadcasts to other DOS/Clients, the BCAST.EXE
   utility file should be copied to the local "\DECNET" directory (as the
   network copy will be unavailable from DOS). If this utility is
   executed from DOS before WFW has been used, the other DOS/Clients
   receiving the message will not see the name of the "sending" node.
   After WFW has been started and exited (or from the DOS shell within
   WFW), the sending node name will be displayed on the DOS/Client
   receiving the broadcast.

-> NETWORK FILE TRANSFER and FILE ACCESS LISTENER
   ----------------------------------------------
   Both of these utilities (NFT or NFTNOWIN, and FAL or FALNOWIN) will
   work from DOS or from the WFW environment. If you are planning to use
   these utilities from DOS (and not from WFW), a copy of these utilities
   should be placed in your local "\DECNET" directory, since you will not
   have access to the copies of these files on the SERVER unless you are
   running WFW.

-> LK250 and LK450 KEYBOARDS
   -------------------------
   For support of the LK250 and LK450 keyboards, the same installation
   procedure used with Windows 3.1 applies to WFW. If an LK450 model is
   used, it should be treated as an LK250 during the installation. Note
   that during the WFW setup, these keyboards will be listed as PS/2 type
   keyboards on the list of system hardware detected by WFW. The following
   procedure can be used to properly install/configure these keyboards.

   The following lines should be placed in the AUTOEXEC.BAT file. These
   lines can be added manually (after moving the files referenced to the
   local "\DECNET" directory), or the can be moved/placed by running the
   PATHWORKS NETSETUP utility.

        c:\decnet\KEYBRD.EXE
        c:\decnet\DECKEYB.COM /D

   To define the keyboard in the WFW system settings, use WIN3SETU
   (located in the "\\PCSAV4x\MSWINV30" directory). This utility must be
   run from within WFW, as the "PCSAV4x" file service" will not be
   available outside of WFW. When running this utility, only answer the
   questions pertaining specifically to the keyboard (i.e. language used,
   WFW directory, drive used for the network file service). Answer "NO"
   to ALL other questions (especially if it refers to Windows 3.0)!

-> USE
   ---
   Connections to file services can not be made until WFW is started.
   From inside of WFW, file service connections can be established from
   the WFW "File Manager", or by "shelling" to the "DOS Prompt" from
   within WFW and executing the "USE" command.

   Connections to print services can not be made until WFW is started.
   From inside of WFW, print service connections can be established from
   the WFW "Print Manager", or by "shelling" to the "DOS Prompt" from
   within WFW and executing the "USE" command. If the connection is made
   from the "DOS Prompt" in this manner, and the File Manager is running
   in the background, the the File Manager window must be REFRESHED to
   make the new file service visible.

   File and print service names must be limited to twelve characters (or
   less) to be accessed from WFW (with either the WFW File or Print
   Managers to the PATHWORKS "USE" command).

   When issuing the "USE" command from a WFW DOS shell, FILE SERVICES
   and PRINT SERVICES will appear with a "PAUSED" status. This message
   can be ignored. Also, note that when PRINT SERVICES are displayed
   from the WFW Print Manager, they will display with an "! ERROR"
   status. This message can also be ignored.

-> LAD & LADCDROM
   --------------
   Connections to LAD and LADCDROM devices (disk services) must be made
   from DOS. These connections are made with the "USE" command before WFW
   is started, or by "shelling" to the "DOS Prompt" from within WFW. These
   connections are not controlled by WFW and their status does not change
   when starting or stopping WFW. Note that connections to these devices
   can not be made from the WFW "File Manager".

   Do not use the "USE" command with the "/FIXUP" parameter. This will
   result in the unconnected devices allocated for LAD and LADCDROM disk
   services to be ignored by the WFW File Manager, making them available
   for future file service connections from the File Manager. This could
   cause confusion if future server connections are initiated made to disk
   services.

-> PC DECWINDOWS
   -------------
   Both DWDOS286 and DWDOS386 (if the DOS/Client is a 386 or better) can
   be used from the DOS Prompt without starting WFW. However, the files
   associated with these applications which are normally accessed in the
   PCSAV4x file service (i.e. fonts and keyboard files), would require
   relocation to allow local access. This would require a "large" amount
   of local disk space and is not recommended.

-> SEDT EDITOR
   -----------
   This application can be run from DOS, before loading WFW if the files
   associated with it are copied to a local directory. These files are
   listed below. For convenience, the local directory should be added to
   the path.

        \\pcsav4X\pcapp\SEDT.EXE        \\pcsav4X\pcapp\LKDOSM.EDT
        \\pcsav4X\pcapp\SEDT.CNF        \\pcsav4X\pcapp\NPDOSH.EDT
        \\pcsav4X\pcapp\SEDT.ENV        \\pcsav4X\pcapp\NPDOSM.EDT
        \\pcsav4X\pcapp\ATDOSH.EDT      \\pcsav4X\pcapp\PCDOSH.EDT
        \\pcsav4X\pcapp\ATDOSM.EDT      \\pcsav4X\pcapp\PCDOSM.EDT
        \\pcsav4X\pcapp\FUNDEF.EDT      \\pcsav4X\pcapp\SLTDOSH.EDT
        \\pcsav4X\pcapp\HELP.EDT        \\pcsav4X\pcapp\SLTDOSM.EDT
        \\pcsav4X\pcapp\LKDOSH.EDT
                        (15 files - approx. 210K)

-> VMS/PATHWORKS MAIL
   ------------------
   This application can be run from DOS, before loading WFW if the files
   associated with it are copied to a local directory. These files are
   listed below. If the SEDT editor will be used as the callable editor,
   this application should also be loaded locally.

        \\pcsav4x\pcapp\MAIL.EXE        \\pcsav4x\pcapp\MAILHELP.HLP
        \\pcsav4x\pcapp\MAILBRWS.DEF    \\pcsav4x\pcapp\MAILMSGS.MSG
        \\pcsav4x\pcapp\MAILCHK.EXE     \\pcsav4x\pcapp\MAILSETU.MSG
        \\pcsav4x\pcapp\MAILDEF.EXE     \\pcsav4x\pcapp\MAILUTIL.MSG
        \\pcsav4x\pcapp\MAILPARS.EXE    \\pcsav4x\pcapp\MAILSEDT.1
        \\pcsav4x\pcapp\MAILSEND.EXE    \\pcsav4x\pcapp\MAILSEDT.2
        \\pcsav4x\pcapp\MAILSETU.EXE    \\pcsav4x\pcapp\MAILSEDT.3
        \\pcsav4x\pcapp\MAILSORT.EXE    \\pcsav4x\pcapp\MAILSEDT.4
        \\pcsav4x\pcapp\MAILEDIT.DEF    \\pcsav4x\pcapp\MAILSEDT.5
        \\pcsav4x\pcapp\MAILVIEW.DEF    \\pcsav4x\pcapp\MAILSEDT.6
        \\pcsav4x\pcapp\MAILHELP.HDX
                       (21 files - approx. 580K)