Error Loading Pathworks Terminal Library
Library". The VT320.exe emulator works okay from the Pathworks 32 disk, but not Powerterm. Can you help as it's dri ving me crazy?? The Answer is : It sounds like you are using PowerTerm from PATHWORKS 32 V7.0 or V7.0a. The PowerTerm Release Notes (ptreadme.txt) include the following information: INSTALLATION REQUIREMENTS ========================= PowerTerm will install without first checking whether the PATHWORKS 32 components have been installed. This occurs because PowerTerm can use only the COM port, which does not require any PATHWORKS 32 networking components. If CTERM, LAT, and Telnet are to be used, you must also install certain PATHWORKS 32 components, before or after installing PowerTerm. For example, to install Telnet, DECnet and LAT support, choose the "Custom" option in "Network Connectivity" from the PATHWORKS 32 installation menu, and select DECnet and LAT support. PATHWORKS 32 can also install the base connectivity to allow a user to run PowerTerm over Telnet only, without installing any other PATHWORKS 32 options. To install the base functionality, choose the "Custom" option in "Network Connectivity" from the PATHWORKS 32 installation menu, and deselect all optional choices. This procedure will install the base functionality that will allow PowerTerm to run without installing DECnet, LAT, VT320, Remote Access, Licensing or PWprint. PATHWORKS 32 V7.1a resolves this issue with PowerTerm. answer written or last revised on ( 22-JUL-1999 ) »close window
Terminal Access Library. Reinstallation has http://h41379.www4.hpe.com/wizard/wiz_2753.html failed to quell the problem which is frustrating as there are no problems running it on the '95 machines we have. Can you help?? http://h41379.www4.hpe.com/wizard/wiz_1714.html Thanks for any help, Phil Stoker The Answer is : Please see existing discussions around the version of the PATHWORKS client software required for use on Microsoft Windows 98: PATHWORKS 32 V7.1A is the required version. If you are presently running PATHWORKS 32 V7.1A (or later) and are encountering problems, please contact the Compaq customer support center for assistance. answer written or last revised on ( 22-DEC-1998 ) »close window
WindowsWindows 10 Windows Server 2012 Windows Server 2008 Windows Server 2003 Windows 8 Windows 7 Windows Vista Windows XP Exchange ServerExchange Server 2013 Exchange Server 2010 Exchange Server 2007 Exchange Server 2003 Outlook Unified Communications/Lync http://windowsitpro.com/systems-management/pathworks-and-nt SharePoint Virtualization Cloud Systems ManagementSystem Center PowerShell & Scripting Active Directory & Group Policy Mobile Networking Storage TrainingOnline Training IT/Dev Connections Webcasts VIP Library Digital Magazine Archives InfoCentersIT Innovators Mobile Computing Business Now Desktop VDI All About Converged Architecture Advertisement Home > Systems Management > Pathworks and NT Pathworks and NT Apr 30, 1998 Brad Cooper | Windows IT Pro EMAIL Tweet Comments 7 Advertisement Will integration or migration work error loading best for you? Many people wish they had bet on Microsoft 10 years ago; that bet would sure be paying off now. Some of us inadvertently made that lucky wager by installing Digital Equipment's PATHWORKS for OpenVMS (known in 1987 as VMS services for MS-DOS) on our servers and PCs. PATHWORKS has long been aligned with Microsoft networking, so it is a perfect environment for integrating with or migrating error loading pathworks to Windows NT. I didn't decide to add PATHWORKS to my clients' networks because of foresight, though. PATHWORKS made sense at the time. Only years after I installed the system did I realize I had bet on Microsoft networking. Now my clients and I get to reap the rewards. If you run PATHWORKS, you're probably trying to decide whether to stick with PATHWORKS, integrate NT into your current system, or migrate to a strictly NT environment. Deciding what to do with your system is complex. You need to examine why your company began using PATHWORKS, what your company uses the software for today, and which solution will work best for your organization. If you run PATHWORKS for OpenVMS, this article will help you examine these issues and decide whether to move to an NT environment. What Is PATHWORKS? In working with clients around the world, I've found that few people understand what PATHWORKS is, or why and how their company uses it. PATHWORKS began as a product that provided Microsoft-oriented network connectivity between Digital VAX computers running VMS and DOS-based PCs. Over the years, PATHWORKS expanded into a suite of server and client products that provided NetWare 3.x-like network connectivity for DOS PCs and Macintosh Apple fi
be down. Please try the request again. Your cache administrator is webmaster. Generated Wed, 12 Oct 2016 02:45:58 GMT by s_wx1131 (squid/3.5.20)