📑 Table of Contents▼

PATHWORKS was the trade name used by Digital Equipment Corporation of Maynard, Massachusetts for a series of programs that eased the interoperation of Digital's minicomputers and servers with personal computers. It was available for both PC and Mac systems, with support for MS-DOS, OS/2 and Microsoft Windows on the PC.[1] Before it was named PATHWORKS, it was known as PCSA (Personal Computing Systems Architecture).

PATHWORKS server ran on OpenVMS and Ultrix (and later Digital UNIX) and enabled a system or cluster to act as a file and print server for client IBM PC compatible and Macintosh workstations. A version of PATHWORKS server for OS/2 was also available, allowing a PC with OS/2 to act as a server to other PCs.[2] PATHWORKS server was derived from LanMan/X, the portable version of OS/2 LAN Manager.[3]

In 1992 DEC said that PATHWORKS revenue would soon be larger than for VMS.[4] PATHWORKS was one of DEC's most successful products ever. Analysis of sales showed that on average, each PATHWORKS license brought in at least $3,000 USD in server revenue (server HW, SW, storage, printers, networking, and services), so it was a major driver for DEC's revenue in the mid and late 1980s.

Later versions of PATHWORKS were known as Advanced Server for OpenVMS (or Advanced Server for Unix for Tru64). Advanced Server was replaced on OpenVMS by Samba at the time of the porting of VMS to Itanium.[3] This was due to the amount of effort required to keep Advanced Server compatible with new versions of Windows and the Server Message Block (SMB) protocol.

Features

edit

Once installed onto the PCs, the PATHWORKS client provided the following features:[5]

  • DECnet, and later TCP/IP and NetBEUI, end-node connectivity with the host and client systems
  • PowerTerm 525 Terminal emulation software from Ericom
  • eXcursion, an X11 server for Windows.
  • File-transfer software. This was a DECnet-DOS file transfer utility, although it was somewhat superfluous because the PATHWORKS server software presented VMS or UNIX files to the PC clients as if they were PC files being served by a Windows server.

The PATHWORKS server software provided access to server file storage and print services using the native Microsoft protocols. Later versions of PATHWORKS servers on VMS supported NetWare and Macintosh clients, but they never achieved the volumes of the Microsoft clients. For clients running a GUI such as Windows 3.x, additional components available included an X window system server, allowing clients to access graphical apps running on VMS or UNIX hosts, and clients for DEC's ALL-IN-1 email and groupware system. Although primitive by modern standards, PATHWORKS was very sophisticated for its time; far more than just a file and print server, it made client microcomputers into terminals and workstations on a DEC network.

Implementation

edit

LanMan normally ran across Microsoft's basic, non-routable NetBIOS/NetBEUI NBF protocol, but PATHWORKS included a DECnet stack, including layers like the LAT transport used for terminal sessions. The complexity of DECnet by 1980s PC standards meant that the PATHWORKS client was a huge software stack to have resident in MS-DOS; configuring the PATHWORKS client was a complex task, made more so by the need to preserve enough conventional memory for DOS applications to run. To keep a reasonable amount of base memory free mandated the use of QEMM or a similar memory manager. This problem went away once 386-based PCs became prevalent and MS Windows provided built-in support for large amounts of memory.

References

edit
  1. ^ Alan Abrahams; David A. Low (1992). "An Overview of the PATHWORKS Product Family" (PDF). Digital Technical Journal. 4 (1). Archived from the original (PDF) on 2021-12-15. Retrieved 2021-01-01.
  2. ^ "PATHWORKS for DOS Overview" (PDF). bitsavers.org. August 1991. Retrieved 2021-01-01.
  3. ^ a b Andy Goldstein (2005). "Samba and OpenVMS" (PDF). de.openvms.org. Retrieved 2021-01-01.
  4. ^ "Digital Sizes Up The Desktop". InfoWorld. Vol. 14, no. 46. 1992-11-16. p. DEC3. Retrieved 2025-06-30.
  5. ^ Brad Cooper (1998-04-30). "Pathworks and NT". ITPro Today. Retrieved 2021-11-06.

Lawrence W. White - PATHWORKS Product Manager

Bob Nusbaum - PATHWORKS Product Manager

📚 Artikel Terkait di Wikipedia

DECnet

stack. Digital also released a product called the PATHWORKS client, and more commonly known as the PATHWORKS 32 client, that implemented much of DECnet Phase

Samba (software)

using a packet sniffer to do network analysis of the protocol used by DEC Pathworks server software. It did not have a formal name at the time of the first

Server Message Block

variety of non-Windows operating systems such as Xenix, OS/2 and VMS (Pathworks). X/Open standardized it partially; Microsoft had submitted Internet-Drafts

Microsoft Configuration Manager

Macintosh, and OS/2 desktops on Windows NT Server, NetWare, LAN Manager, and Pathworks networks. Systems Management Server 1.1, released in 1995 to help customers

Barbara Brennan

called the Pathwork, drawing on the ideas of Wilhelm Reich and Alexander Lowen. Brennan worked with the Pierrakos, and became a Pathwork Helper and Core

John Pierrakos

Institute in New York, NY with Lowen (1955-1970), and co-founder of The Pathwork Center, Phoenicia, NY, in association with his wife, Eva Pierrakos. John

OpenVMS

protocols such as SSH, DHCP, FTP and SMTP. DEC sold a software package named PATHWORKS (originally known as the Personal Computer Systems Architecture or PCSA)

Robert Thurman

whose mission is to help preserve Tibetan Culture in exile. In 2001, the Pathwork Center, a 320-acre (1.3 km2) retreat center on Panther Mountain in Phoenicia