Professional Documents
Culture Documents
Product
Description
PRODUCT NAME: PATHWORKS for DOS (TCP/IP). Version 1.1A SPD 33.45.02
October 1991
AE-PESXC-TH
PATHWOAKS for DOS (TCPIIP). Version 1.1A SPD 33.45.02
2
PATHWORKS for DOS (TCP/IP), Veralon 1.1A SPD 33.45.02
File Services The PATHWORKS for DOS MAIL utility enables the
DOS client to:
The client is provided with a remote DOS file system
that appears as a transparent extension of the client's • Read, delete, forward, file, print, annotate, and reply
local facilities through the integration of Microsoft's LAN to messages.
Manager file and print protocol with TCP/IP and RFC
1001/1002 NETBIOS. • Send messages to a distribution list as well as to a
remote address. Messages can be sent to primary
Permit Services
addressees and to carbon copy addressees.
PATHWORKS for DOS software provides DOS client
systems with the ability to offer other users access to • Create messages with the built-in editor (or a se-
local resources via the PERMIT command. A client may lected callable editor, such as SEDT) which can out-
offer other client systems access to its local disk; only put an ASCII file.
a single connection is possible at any given time.
• Organize messages into folders which may be stored
Print Services remotely on a server or locally on the system's hard
disk.
The client is provided with a remote DOS printing sys-
tem that appears as a transparent extension of the • Receive notification of new messages upon login and
client's local facilities. This allows the redirection of lo- during PATHWORKS sessions.
cal printing to a server-based printer. This functionality
is provided through the integration of Microsoft's LAN • Receive notification of incoming messages using the
Manager with TCP/IP and RFC 1001/1002 NETBIOS. Receive utility. In most cases, notification is achieved
via sound while using a graphics application, and via
Refer to the System Support Addendum (SSA 33.45.02- a pop-up window on the user's display while using
x) for a list of supported printers. character cell applications. This feature may be op-
tionally disabled.
Refer to PATHWORKS for VMS (SPO 30.50.xx), PATH-
WORKS for ULTRIX (SPD 32.44.xx), or PATHWORKS
• Send a binary file attachment (one binary file per
for OS/2 server software (SPO 55.24.xx) for more infor-
message).
mation on remote printer support.
Print Screen Support • Configure the user interface as either command line
or menu-driven.
Users can print the contents of a screen to a local or
remote printer over the network by using Print Screen Note: The client implementation of mail services is not
functionality while using a DOS-based application (in- implemented via the Simple Mail Transport Protocol
cluding the SETHOST terminal emulator). (SMTP) or Postoffice Protocol (POP).
Print Screen Support Is not available while using PC Date and Time Services
DECwlndows Motif.
Clients can receive the date and time from the PATH-
Mail Services WORKS server. The benefit of this feature is that the
user is assured of consistent timestamps on any given
The MAIL component included In the PATHWORKS for
file that is created, shared, or updated by other users.
DOS product allows DOS clients to send and receive
messages and documents to and from users of MAIL
software on systems that operate within the same TCP Broadcast and Receive
liP network. The PATHWORKS for ULTRIX V1.0 or V1.1
mail server must already be Installed to utilize MAIL. The Broadcast feature allows users to send (broadcast)
messages to DOS and/or OS/2 clients. The Receive
MAIL is a PC-style utility for sending and reading mail. feature allows DOS clients to receive the messages.
It contains horizontal menu bars, pull-down menus, and This feature allows DOS clients to notify other DOS
help listed by topics. MAIL allows the user to read mail clients of various network events, such as system shut-
without having to log into the server. downs for backups.
3
PATHWORKS for DOS (TCP/IP), Version 1.1A SPD 33.45.02
Broadcast and receive functionality is only supported 8088, 8086, and 80286 Intel processors, the PC must
between PCs utilizing the same network transport. For be configured with both a user-supplied EMS, V4.0
example, users can send a message from a PC us- software driver and hardware.
ing TCP/IP to another PC using TCP/IP as the network
• The LAN Manager Basic Redirector (if using either
transport; users cannot send a message from a PC us-
the PATHWORKS for DOS V4.0 or V4.1 client soft-
ing TCP/IP to a PC using DECnet as the network trans-
ware) can be loaded into the High Memory Area
port.
(HMA) portion of extended memory.
LAN Manager V2.0 Support
The Enhanced Redirector (if using PATHWORKS for
Because the PATHWORKS for DOS V4.1 client soft- DOS V4.1 client software) can be loaded into HMA
ware includes Microsoft's LAN Manager V2.0 software, or into Expanded Memory (EMS). Users should use
the PATHWORKS for DOS (TCP/IP) client has access the Enhanced Redirector to take advantage of the full
to the full set of LAN Manager capabilities with a PATH- LAN Manager capabilities in conjunction with a PATH-
WORKS for OS/2 server: WORKS for OS/2 server.
• Full set of LAN Manager Application Programming In- The configuration must have a minimum of 64KB of
terface (API) functions (such as named pipes) which extended memory (if either redirector is loaded in ex-
allow for the development and support of distributed tended memory) and either the Digital-supplied driver,
applications. HIMEM.SYS, or a vendor-supplied high memory man-
ager which supports Extended Memory Specification
Note: Support of distributed applications requires (XMS), V2.06.
full API support on both the client and server sys~
• Provides the ability to unload several network com-
tem. Therefore, a LAN Manager server-client appli-
ponents from either conventional or EMS memory.
cation is currently only supported between a PATH-
The exact amount of conventional memory available
WORKS for DOS or PATHWORKS for OS/2 client
for user applications will vary depending on:
and a PATHWORKS for OS/2 server.
- Availability and size of EMS drivers
• Net commands.
• Basic Redirector - Use the Basic Redirector to ac- - Whether the LAN Manager Basic or Enhanced
cess the file and print services of a PATHWORKS Redirector is used and what portion of memory
for VMS, ULTRIX, and/or OS/2 server(s). The Basic they are loaded into
Redirector supports user names (share names) up to - Whether an Ethernet or Token Ring controller is
32 characters. used
• Enhanced Redirector - Use the Enhanced Redirec- - NDIS driver size
tor to access the full LAN Manager V2.0 capabilities
with a PATHWORKS for OS/2 server. - DOS version
Note: The Enhanced Redirector supports user - Parameters and drivers specified in CONFIG.SYS
names (share names) up to eight characters. and PROTOCOLINI
- Other features of the TCPIIP network environment
Task-to-Task Communications (via Socket Library)
that may be loaded, such as TELNET, SOCKETS
A Berkeley Software Distribution (850) V4.3 compatible
- Other Terminate and Stay Residents (TSRs) that
socket library is included. It allows developers to easily
may be loaded
develop or port UNIX® - style socket applications to their
PCs running PATHWORKS for DOS (TCPIIP). PATHWORKS for DOS and PATHWORKS for DOS
(TCPIIP) software supports the use of Expanded Mem-
Memory Savings Techniques
ory Specification (EMS) applications that are V4.0 com-
PATHWORKS for DOS and PATHWORKS for DOS pliant. Every effort has made to ensure the software ad-
(TCPIIP) software supports several techniques for sav- heres to the EMS, V4.0 specification. However, individ-
Ing conventional PC memory. By using these tech- ual applications may have interpreted the specification
niques, additional conventional PC memory becomes differently and, therefore, may not function in Digital's
available for user applications. PATHWORKS for DOS (TCPIIP) network environment.
• Several network components can be optionally Background EMS applications are usually device drivers
loaded into expanded memory simultaneously. For and terminate and stay resident programs (TSRs).
80386 and 80486 Intel™ processors, the PC must When PATHWORKS for DOS software is loaded Into
be configured with a user-supplied Expanded Mem- EMS with other background EMS applications, unpre-
ory Specification (EMS), V4.0 software driver. For dictabie results may occur.
4
PATHWORKS for DOS (TCP/IP), Version 1.1A SPD 33.45.02
Some EMS drivers and disk caching programs provided A minimum of 1 MB of system memory must be free and
by PC vendors may conflict with HIMEM.SYS which pro- accessible to start PC DECwindows Motif after configur-
vides XMS support. ing the system with the required PATHWORKS network
components. This memory may be made up of free
Installation and Configuration Utilities conventional and extended memory.
5
PATHWORKS for DOS (TCP/IP), Version 1.1A SPD 33.45.02
A KEYSYM compiler, DWKEYSYM, is provided so users • Programmers can program to Microsoft Windows,
can build custom keyboard layouts to support applica- VS.O with the standard socket library. The TELNET
tions. and BAPI interfaces may be used. Programs can
run in a full screen, exclusive mode window if they
A font compiler, DWFONT, is provided which compiles use synchronous socket operations only. Any asyn-
fonts in the Adobe Bitmap Distribution Format, V2.1 into chronous calls to the socket library will produce un-
a format for the X Server. predictable results.
The REXEC shell is required on the ULTRIX system to • PIFs (Program Information Files) for most DOS-
start applications from the X Server over TCP/IP. based PATHWORKS for DOS (TCP/IP) applications
futilities are provided. (These PIFs are provided as
On a VMS system with the VMS/ULTRIX Connection examples and should work with most configurations.
product, the X Server uses a TELNET login to commu- The user may need to tailor them given the applica-
nicate with the DECnet Remote Application Startup Pro- tion mix and specific personal computer configura-
gram to start applications. Therefore, the DEC net Re- tion.)
mote Application Startup Program must be installed on
VMS systems with the VMSfULTRIX Connection prod- Only one transport, either DECnet or TCP/IP, is sup-
uct. ported at anyone time regardless of the number of win-
dows running.
Print Screen Support is not available while using PC
Terminal Emulators
DECwindows Motif.
The PATHWORKS for DOS software includes two ter-
Microsoft Windows VS.0/3.00A Support minal emulators that can be used in conjunction with
the PATHWORKS for DOS (TCP/IP) software that al-
PATHWORKS for DOS (TCP/IP) software supports Mi-
lows users to establish terminal sessions with a host
crosoft Windows, VS.O, including:
computer such as VMS or ULTRIX:
• Access to file services provided through the Microsoft • VTS20 for Microsoft Windows, VS.O (A VTS20-like
Windows, VS.O File Manager. Microsoft Windows terminal emulator if using PATH-
• Access to print services provided through the Mi- WORKS for DOS V4.1 client software) - The VTS20
crosoft Windows, VS.O Control Panel. does not support full modem control or replaceable
character sets (ORCS).
o The ability to run the networking software in ex-
• SETHOST (A VTS20-like character-cell terminal em-
panded memory (EMS) with Windows, VS.O in Real,
ulator) - SETHOST supports control of asyn-
Standard, or S86 Enhanced modes.
chronous modems but does not support replaceable
If using Microsoft Windows, VS.O in S86 Enhanced character sets (ORCS).
Mode, the Basic Redirector must be loaded into con:-
Terminal sessions can be established using either a se-
ventional memory.
rial communications port, or through an Ethernet or To-
EMMS86.SYS is the memory manager shipped with Mi- ken Ring controller on the client.
crosoft Windows, VS.O. PATHWORKS for DOS (TCP
Note: Both terminal emulators are not fully VTS20
liP) does not support the use of other third-party mem-
compatible; for example, SETHOST does not support
ory managers while using Microsoft Windows, VS.O.
double-height, double-width characters.
• A windowed VTS2Q-like terminal emulator support- VTS20 Features for Microsoft Windows, VS.O
ing TELNET is provided (if using PATHWORKS for
DOS V4.1 client software). (See Terminal Emulators The VTS20 is included with the PATHWORKS for DOS
section for more detail.) V4.1 client software.
• A DOS-based menu-driven utility (WINSSETU) is o Support for TELNET and serial terminal communica-
provided to simplify the installation of PATHWORKS tion.
for DOS Microsoft Windows, VS.O support software.
o User-definable color attributes, background/foreground,
• A Terminal Access Library (TRMNLAXS) that pro- reverse, bold, underline.
vides TELNET access to Microsoft Windows, VS.O
o Support for the Microsoft Windows Clipboard to cut
applications is included if using PATHWORKS for
and paste information.
DOS V4.1 client software). The library is provided
for programmers who wish to write terminal emula- o Ability to log characters received from the host into
tors that execute under Microsoft Windows, VS.O. a file.
6
PATHWORKS for DOS (TCP/IP), Version 1.1A SPD 33.45.02
• Ability to send characters to the host from a file in- • Support for the following list of character sets
stead of from the keyboard. (but does not support replaceable character sets
(DRCS»: ISO Latin-1 (ISO), DEC Multinational
• Setup feature allows selection and saving of terminal
(MCS), DEC Technical (TCS), and the following 7-bit
characteristics.
National Character Replacement Sets (NRCS):
• Printing to a Digital remote or local printer; printing
may be a screen at a time or a toggle-like function ASCII British
may be used to print everything from the screen until
French German
the toggle is switched off.
Italian Spanish
• Digital multinational and ISO multilingual character
sets and compose sequences as defined below: Finnish Swedish
Norwegian/Danish Swiss
- ISO (default) - International Standards Organi-
zation character set Canadian Dutch
• Support for TCP/IP's TELNET protocol via the SAP I File transfer is supported via the File Transfer Protocol
interface (BAPI is an INT 14 interface), and serial (FTP) utility. FTP commands can be used to perform
terminal communication. network file operations. Once a FTP session is estab-
lished to a remote host, users can choose from a wide
• Terminal sessions can be established using either
variety of commands.
a serial communications port, or via an Ethernet or
Token ring port on a supported Ethernet or Token SEDT Screen Editor
Ring controller on the client.
SEDT is a text editor which allows the display and edit-
• Support for a maximum of four simultaneous ing of a full screen of text. It may be used as the callable
SETHOST sessions via TELNET. Only one session editor for creation of text messages within the PATH-
can be enabled when SETHOST uses the asyn- WORKS for DOS MAIL utility. The features and capa-
chronous communication port for an asynchronous bilities of SEDT include:
terminal connection.
• Simultaneous editing of up to four files in separate
• Ability to use SETHOST with TELNET and BAPI in
buffers
EMS. The TELNET protocol and the BAPI interface
are dynamically loaded into EMS as needed. • Text selection, insertion, deletion, and search
• Support of asynchronous modems. • Cut and paste capability
• Setup feature allows selection and saving of terminal • Use and definition of multiple rulers, with tab, margin
characteristics. and justification settings
7
PATHWORKS for DOS (TCpnp), Version 1.1A SPD 33.45.02
• An information line with displays the current editing RFC 1001/1002 NETSIOS Interface Support
modes, such as forward versus reverse search, in-
sert versus replace, and cut and paste modes TCPIIP supports the session level NETBIOS interface
through interrupt 5C HEX. Applications written to the
• A file information line which displays the name of the RFC 100111002 NETBIOS speCification can be layered
file being edited, the current line and column position on TCP/IP. This TCPIIP network is an RFC 1001/1002
in the file, and the file buffer in use NETBIOS B-node implementation.
• Customization of commands and configuration This allows computers running TCP/IP and NETBIOS
• Definable keyboard maps applications to communicate with other computers run-
ning TCPIIP and RFC 1001/1002 NETBIOS applica-
Enhanced DOS Utilities tions. This feature preserves the user's investment in
These utilities include support for Digital's LK250 key- industry standard applications.
board (including international versions) and Microsoft The NETBIOS naming service and datagram service is
Mouse emulation, V7.0 of the Digital VSXXX-AA mouse supported only in Ethernet LAN configurations as a B-
(for use with a DEC EtherWORKS Ethernet controller node implementation.
that is equipped with a mouse port).
The INETNAME utility is included to define remote
Multilinguality adapter names, which allows wide-area NETBIOS con-
Some PATHWORKS for DOS components are available nections.
in languages other than English. More than one lan-
Note: Users can program to one NETBIOS interface
guage variant can be run from the PC without rebooting.
only.
Refer to the following SPDs for further information.
Network Device Interface Specification
Swedish (SPD 55.17.xx)
Spanish (SPD 55.18.xx) PATHWORKS for DOS and PATHWORKS for DOS
Dutch (SPD 55.19.xx) (TCPIIP) networking software is Network Device Inter-
French (SPD 55.20.xx) face Specification (NDIS), V2.0.1 compatible. NDIS
German (SPD 55.21.xx) is a standard developed by Microsoft Corporation and
Italian (SPD 55.22.xx) 3Com® Corporation.
TCPIIP Network Management Facilities Digital's implementation of the NDIS standard is in-
tended to allow users a greater choice of Ethernet or
The following network management facilities are pro-
Token Ring controllers. This implementation is not in-
vided for system administrators to manage the TCPIIP
tended to support the simultaneous operation of the
network environment:
PATHWORKS for DOS product and other vendors' net-
• PING (Packet INTERNET Groper) - An exercise working products.
program used to test the INTERNET communications
Because the PATHWORKS for DOS (TCPIIP) software
channel between stations.
is written to the NDIS interface, users can use third-
• ARP - An INTERNET utility that uses the Address party Ethernet or Token Ring controllers if accompanied
Resolution Protocol to translate INTERNET names by an NDIS V2.0.1 driver. Every effort has been made
to INTERNET addresses. to ensure that the software adheres to the NDIS V2.0.1
specification. However, individual vendors' interpreta-
• NETSTAT - A utility that displays network statistics.
tion of the specification may vary and therefore may not
Totals of received and transmitted packets, retries,
function in Digital's PATHWORKS for DOS network en-
and jams (Ethernet) are counted. Data may be dis-
vironment.
played over any time interval in seconds.
The PATHWORKS for DOS product contains several
Domain Name Resolver
NDIS drivers for the convenience of our users. The
The Domain Name Resolver resolves network domain NO IS drivers are furnished "As Is", and Digital cannot
names to INTERNET addresses, allowing applications be held liable for any speCial, indirect, inCidental, or con-
(for example: FTP, TELNET) to use domain names sequential damages.
rather than INTERNET addresses. The Domain Name
Resolver communicates with the domain name server
to resolve names to INTERNET addresses.
8
PATHWORKS for DOS (TCPIIP), Version 1.1A SPD 33.45.02
Note: The Digital Ethernet NO IS drivers can also be If the PATHWORKS for DOS (TCPIIP) software is used
used with previous versions of the Digital Ethernet con- in a server /client environment, the following client prod-
troller family, DEPCAs. uct is required:
To create a floppy key disk, a disk greater than or equal PATHWORKS for VMS (SPD 30.50.xx)
to 720KB is required for booting purposes.
PATHWORKS for ULTRIX (SPD 32.44.xx)
Any application which does not properly mask and un-
mask interrupts is Incompatible with this product. For PATHWORKS for OS/2 (SPD 55.24.xx)
example, applications which use IBM BASICA, V1.0 in-
terpreter or compiler, or GW-BASIC, V1.0 do not un- Refer to the System Support Addendum for availability
mask the interrupts when they exit. In these cases, a and required versions of prerequisite/optional software
BASIC program must be interpreted or recompiled using (SSA 33.4S.02-x).
a version of BASIC that would unmask the interrupts.
PATHWORKS for DOS, V4.0 and V4.1 and PATH- TCP/IP User's Reference: QA-YV9AA-GZ
WORKS for DOS (TCP/IP), V1.1 A software have been
tested on several supported configurations (refer to SSA TCPIIP Programmer's Guide: AA-PESZA-TK
33.45.02-x). If a customer problem with PATHWORKS
for DOS (TCPIIP) software can be reproduced by the * Denotes variant fields. For additional information on
customer on one of these supported configurations, Dig- available licenses, services, and media, refer to the
ital will work the problem to resolution on these sup- appropriate price book.
ported configurations. If the customer problem cannot
9
PATHWORKS for DOS (TCPIIP), Version 1.1A SPD 33.45.02
SOFTWARE WARRANTY
10
IBIBIIO'"
AV-PJEYA-TH
Depending on which PATHWORKS for DOS version you have, you may not need to use all the
components contained in this release.
Refer to the following chart for guidance:
If you currently have... And you receive PATHWORKS for DOS (TCPIIP) V1.1A...
PATHWORKS for DOS V4.0 1. Install the utilities only if you want bug fixes.
and
PATHWORKS for DOS (TCPIIP) V1.1
PATHWORKS for DOS V4.1 1. Install the utilities only if you want bug fixes.
and
PATHWORKS for DOS (TCPIIP) V1.1
We hope you find this release useful. We appreciate your use of Digital's PATHWORKS family of PC
Integration products and look forward to your future business.
Sincerely,
Digital Equipment Corporation
Personal Computing Systems Group
The Makers of PATHWORKS