Does NI use a different GPIB controller driver from Windows 2000 than in Windows XP?

[RF_ATE_PRGR]

I have written a kernel mode filter driver that is attached as an upper filter on the gpibprtk driver. When I run an ATE program, I can see all the IRP's sent to gpibprtk and that is what I want. However, on XP, my filter driver will not load but I see the gpibprtk driver loaded and running. Also, when I view debug statements, I see the DriverEntry and then a DriverExit function calls from the SCUM but no add device is called. What's different between the XP and Window's 2000 driver which takes to the NI GPIB Controller?

[Matt_S.]

Hello,

I want to get a little clarification so that hopefully we can be helpful for you. What exactly is it you're trying to do in this application? There may be some other way to go about what you're trying to do than writing your own kernal mode filter.

Regards,
Matt S.

[RF_ATE_PRGR]

Hey Matt,

I have wrote an ATE station monitoring application to track station utilization by activity. A user selects an activity say Manual Testing (or Auto Testing, Calibration, Engineering) and this information is stored to a database for reporting. Then the software monitors the station's mouse movement, keyboard and equipment communications to determine if the station should revert to Idle state. Thus, if no mouse, keyboard or equipment communications are detected within a specified time, the software records that the station is idle (not being utilized).

To monitor equipment communications, I wrote a kernel mode filter driver to intercept IRPs to the NI GPIB controller. If I see IRPs to the NI controller we assume station activity. I basically use the timestamp difference between the lasted IRP received with the current time to determine equipment idle state. This approach was selected because Test Engineers use various custom libraries to communicate via GPIB which do not provide any hooks for me to query equipment activity. 

Thanks

Billy Henderson