Error Loading Pathworks Terminal
Power Term, I get the error message "error loading Terminal Access Library". This happened after I tried to install D ecNet from the same Pathworks 32 CD. Earlier the telnet sessions were fine. how can I get back TELNET functioning in Power Term? The Answer is : PATHWORKS 32 V7.1a supports the Microsoft Windows 95, Windows 98, and Windows NT 4.0 platforms. PATHWORKS 32 V7.2 adds support for Microsoft Windows 2000 to the platforms supported by V7.1a, and is the minimum supported version for Windows 2000 platforms. Please update your configuration to PATHWORKS 32 V7.2. If you wish to attempt to get PATHWORKS 32 V7.1a PowerTerm Telnet to work in your Windows 2000 system configuration, the OpenVMS Wizard would encourage you to de-install PATHWORKS 32, de-install PowerTerm, and then re-install the packages. answer written or last revised on ( 3-OCT-2001 ) »close window
Terminal Access Library. Reinstallation has http://h41379.www4.hpe.com/wizard/wiz_7116.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 http://windowsitpro.com/systems-management/pathworks-and-nt 2010 Exchange Server 2007 Exchange Server 2003 Outlook Unified Communications/Lync 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 error loading and NT Apr 30, 1998 Brad Cooper | Windows IT Pro EMAIL Tweet Comments 7 Advertisement Will integration or migration work 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 error loading pathworks 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 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