DECDNP.SYS Crashes Windows XP

[Richard Bamford]

I am getting system bugcheck crashes on Windows XP running Pathworks 32.

When analysing the crash the Exception Address points to the DECDNP.SYS driver

Any help would be appreciated.

[Antoniov.]

If I right understand you have a Openvms server, running A/S (or Pathwork) ad you have a client XP with pathwork32 on it. When you do some network operation, server crash.
Is it true?
if yes, perhaps, you have my same problem.
Please post version of software and more details.
Read this thread (may be same problem) http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=236934

Bye
Antoniov

[Richard Bamford]

Thanks for the reply.

Some clarification of my situation.

I am using a VAXELN ver 4.4 300 Chip on a PLC networking communiactions card. This card acts as a Server sending PLC Data over DECNET to my Windows XP Client Running Pathworks.

I don't think this represents the same problem that you are experiencing, however I am not an Open VMS Expert.

Still if anybody has any further ideas please help!

[Antoniov.]

You have a VAX with VMS V4.4 :-o
Is it true?
Then you have installed pathwork32 on PC with winxp and you have installed Decnet protocol on PC so you can connect to VAX.
Is it true?
Yes, you have a different problem.
First question: did you connected PC in Decnet network?
Second question: crash does happen on PC or on VAX?

Antoniov

[Richard Bamford]

The Chip running VAXELN 4.4 is not in a VAX Computer but is on a PLC Communications Card using a DIGITAL VAXELN 4.4 Chip onboard to allow DECNET protocl between PC and PLC.

Yes PW32 is installed on Windows XP PC to use DECNET Protocol to communiacte with VAX Chip on PLC Comms Board

Yes PC Is In the DECNET Network

It is the PC which is crashing

More info:

PC Runs and communicates without any problems for about 24 hours then it crashes, reboots and starts working for another 24 hours. This cycle repeats.

[Martin P.J. Zinser]

Sounds like a resource on the PC is leaking. Anything obvious like increasing memory used?

Also which version of Pathworks32 do you run?
For Win XP it should be the latest and greatest
7.3 ,-)

Greetings, Martin

[Veli Körkkö]

I have also tried PAthworks 32 (V7.3) on top of XP. One problem I noted is that after Pathworks is bound to adapter, one cannot any more change adapter settings on the fly.

Moving with laptop from environment to another
one needs occasionally tweak e.q. MEDIA SPEED etc settings.

Running Pathworks 32 V7.3 on top of W2K this was possible. Running on top of XP, BSOD on DECNDIS.

_veli

[Antoniov.]

Hi Richard,
I read pathwork32 documentation on CD but I don't see nothing about your problem.
However I think you are using Decnet to activate a RPC on PC and exchange data with your PLC controller; to make this you have installed SP3.

This note may be intersting for you:
[Quote]
When a DECnet application halts abnormally, the PATHWORKS 32 DECnet layer might not properly release the application's DECnet Listening Socket. If this happens, the DECnet application might fail to run the next time a user attempts to start it.

1. Check for unreleased DECnet Listening Sockets by issuing the following NCP command in a DOS box:
NCP> SHOW KNOWN LINKS
2. Use the following NCP command to release any links associated with your application:
NCP> SET LINK n STATE OFF
Once the links are cleared, the DECnet applications should again work properly.
[/Quote]
Also you could read Pathwork event logger to find any clue.

Bye
Antoniov

[Nogalj]

I've the same Problem with XP and PW32 7.3 ! I have done some testing with Windows API WNet, where I figured out that using WNetAddConnection2 crashes (sometimes WNetCancelConnection does this too). Taking a look into the DUMP DECDNP.SYS is shown !
BTW: I tried to connect a NetBT-Node, not a DECnet node !
After disabling the Binding for DECnet for MS-Client and MS-Server no crash occured. But also no DECnet API is available (using DECnet-Socket functions for direct DECnet communications).