Pathworks 32 installation on a Windows 7, 8, 10, Server 2012, Server 2016

[SteFetS2112]

Clearly, is it possible to install PATHWORKS 32 on a Windows 7, 8, 10, Server 2012, Server 2016?

I tried in all ways, I disabled the verification of the signature of the drivers but it does not work.

Has anyone managed to install PATHWORKS 32 on a Windows whose version is beyond version 7?

Is it even possible?

[Steven Schweda]

> Pathworks 32 [...]

   Does your Pathworks kit have a version?

> I tried in all ways, [...]

   Not a useful description of what you did.  Even less useful as a
description of what happened when you did it.  Are you running some
installer or other?  Are you getting some sort of error message or
other?

[Volker Halle · Accepted solution]

The most recent SPD for HP Pathworks 32 V7.4 states support on:

Windows 2000, Windows XP Professional, and Windows 2003.

While PowerTerm and eXcursion still work on at least Windows 7, the other components might not. 

Volker.

[SteFetS2112]

Hi Steven,

I tried version 7.2 and 7.4

I disable driver signature validation in Win7, Win10 and Win2016 in all the possible ways, with bcedit, gpo, registry. The installation works but in the Event Viewer there is a PnPDriverImportError for DECITOT.INF, DECNDIS.INF, decdnpitot.inf 

When the installation is done, PWBIND.EXE is executed and it ask me to select one of the adapters for DECNET but there is no network adapter listed, and the protocol is not injected in the network adapters.

[SteFetS2112]

Hi Volker, 

Do you have a link about that please ?

Thanks !

[Volker Halle]

Google is your friend: 'pathworks 32 v7.4 spd'

http://h30266.www3.hpe.com/PDFs/PW32SPD.pdf

Volker.

[Steven Schweda]

> [...] there is no network adapter listed, [...]

   My Pathworks and Windows expertise are both very close to nil, but I
have seen similar complaints about some old Netgear routers which were
supplied with a Windows software CD-ROM to use for configuring the
router.  When a user attempts to run the (old) router configuration
program on a modern Windows system, it complains that it can't find a
network adapter (and, hence, can't communicate with the router).

   My speculation is that, someplace along the line, there was a
significant change in Windows network drivers, and you're doomed because
the old Pathworks code can do things in only the old way.

   If I were desperate, then I might try the oldest Ethernet card I
could find in the modern system, and see if a modern Windows will still
try to use some old driver with it, on the faint hope that the old
Pathworks code might be able to find that.  I wouldn't bet a nickel on
it, however.  That SPD is not encouraging.