Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

VB6, W2K, always crashes 2nd time run in VB design mode.

In VB6 design mode, start up app which performs a SendIFC, then ibdev's and ibonl's the devices connect to the GPIB interface. Exit app which takes all devices off line (ibonl). If start app again the SendIFC crashes Win 2000 and automatically reboots PC. The VB created executable works fine.

This sounds very similar to the David Montigny of 4/4/2000.
0 Kudos
Message 1 of 6
(3,725 Views)
Pablo wrote:
>
> In VB6 design mode, start up app which performs a SendIFC, then
> ibdev's and ibonl's the devices connect to the GPIB interface. Exit
> app which takes all devices off line (ibonl). If start app again the
> SendIFC crashes Win 2000 and automatically reboots PC. The VB created
> executable works fine.
>
> This sounds very similar to the David Montigny of 4/4/2000.

Pablo,

Having EXACT same problem, NI claims it is a WINDOWS/microsoft problem.
I tried several configurations ( vb5/win98se, vb6/win98se ) but it
only happens with vb6(sp4)/win2000.

My program:
Private Sub Form_Load()
Dim GPIB_BD As Integer
ibfind "GPIB0", GPIB_BD
End
End Su

This will be interesting, talking to microsoft. They probably don't
know what GPIB is, but we are in the middle, h
aving this problem.

Keep me informed.
TooN
0 Kudos
Message 2 of 6
(3,725 Views)
This sounds very familiar. Could you attach a sample project with minimal code that reproduces this problem?
0 Kudos
Message 3 of 6
(3,725 Views)
Randy Solomonson wrote:
>
> This sounds very familiar. Could you attach a sample project with
> minimal code that reproduces this problem?

My (Antoon) program:
Private Sub Form_Load()
Dim GPIB_BD As Integer
ibfind "GPIB0", GPIB_BD
End
End Sub

Tried with VB6/WIN2000/NI-GPIB 1.60 and VB6/WIN2000/NI-GPIB 1.70, both
crashed.
Seems to happen ONLY with VB6/WIN2000, VB5 no problem, also VB6/WIN98 no
problem.

Antoon
0 Kudos
Message 4 of 6
(3,725 Views)
It may be that you're swapping the parameter of the ibonl call. It's typically ibonl(ud,0) to bring an instrument offline.
0 Kudos
Message 5 of 6
(3,725 Views)
Remember, if you don't use an ibonl(ud,0) for all ud's at the end of your program, it is likely to give the BAD_POOL_CALLER blue screen in Windows 2000.
0 Kudos
Message 6 of 6
(3,725 Views)