I am trying to track down a complete lockup caused by sending a Group Execute Trigger to a system running the attached program. The program is based on a console application in the NI article "How to Use Asynchronous Callback Functions with GPIB Events in Windows NT/98/95". The original used ibnotify and a callback to process RQS events. I have modified the program to call back on DTAS events, which seems to work fine on its own. However, the I also want to process CMPL events resulting from an ibrda() call. You will find this ibrda() call about half way down the source code. If this call is included in the build then a Group Execute Trigger initiated by another device on the bus causes the PC running the pr
ogram to hang and thus require a hard reset. Note that I haven't even got to the point where CMPL is included as part of the ibnotify() call. It is the mere fact that there is an asynchronous ibrda() happening in the background when the DTAS happens that seems to be causing the problem.
The system involved is a 1.4GHz Pentium running Windows 2000. I have ensured that version 1.6 of the NI 488.2 software is installed. The NI card is a PCI-GPIB.
I'm sure there must be something subtle that I'm doing wrong but I would expect to get errors back from the driver if that were the case, rather than a lock up.
