PCI-GPIB/Win2000 blue screen-resolved yet?

[Yuri Zuev]

Hi,

I have been kind of out of the loop lately, so can anybody enlighten me
on the subject?
Has the blue-screening (BAD POOL CALLER) error with PCI-GPIB board under
win2000 resolved yet and everything is hunky-dory, or it's still there?

Sincerely
Yuri

[Randy Solomonson]

Hello-

This error is caused by a faulty process that does not close GPIB sessions. With these orphan sessions, a call to open another GPIB session will cause Windows to assert this screen.

The solution to the problem is to call ibonl(ud,0) for each session that is open. This typically needs to occur just before terminating the process using GPIB.

If this solution is not working, please write back.

Randy Solomonson
Application Engineer
National Instruments

[peppy_]

Hey Randy;

I am using LabVIEW 6.2. MAX 2.0.3.6. WIN2000.

I get BAD_POOL_CALLER (BSOD) when I start MAX. NOT even scan for inst. This solution does not apply to me, can you help on LabVIEW, not VB.

Thanks
Tim