interactive execution caused external process to terminate

[Darkdave]

Hi,

My question deals with Drivers test trough Fp in interactive execution.

So I try to generate a driver to use some pxi board such as old Vxi board

for a new bench conception.

My driver include now my old fp(from Vxi),  c & h files skeleton with new PXI functions.

I note that I load a PNP instrument (niScope) as an instrument under CVI 7.0

(fp not included in the project). Got no errors nor warnings even in aggressive mode.

I get the Dll, lib and cdb files

Testing the fp in interactive execution (through the old fp of my driver), I sometimes

receive an error: "interactive execution caused external process to terminate".

This error can appear everywhere, in release or dbg mode.

So I used a test code (with a main) and everything works fine, but I would like to

be able to use the interactive execution to test my driver as an instrument to integrate

later tests program on the new PXI bench standard.

Anyone an idee regarding this interactive error ?

My disc space's enough, I modify the interactive memory size without any results.

Got no dynamic allocations...

The Dll works fine except I cant test it in the interactive execution window.

Thanks in advance, I join a jpeg.

David

[Wendy L]

Hello Darkdave,

Sorry to hear you are getting errors when using the interactive execution window.  I'm not sure exactly why you are seeing the error, but first, I would suggest downloading and installing the latest runtime engine: LabWindows/CVI Run-time Engine Version 8.0 for Windows 2000/XP.  The LabWindows/CVI Runtime Engine is backwards compatible and may be used with applications that were created with previous versions of LabWindows/CVI.   After upgrading your runtime engine, do you still see intermittent problems with your interactive execution window? 

Thanks, and I look forward to your response.

[Darkdave]

Hi Wendy,

I D/L the Runtime and it's up to date now. I still have the same problem but I can prococate it. In fact each error (fatal or not)

stops the execution with the same message (see Jpg in last post.). But the error could appears even if the driver work properly.

It can also crash my Computer (black screen + restart).

One more time I'm sure my driver is correctly developped & binded (works fine with calls on a main) and Errors / instability only appears in interctive window execution mode.

I still have the Problem with a niScope  (5122 driver) & a niFgen based drivers (5421)complided under Ms VC++.

Just cannot understand. I tryed to change the option (force loaded instrument into interactive window....& the other one under)...

But It's always the same.

I'll try further.

David

[Wendy L]

Hello David,

Without your code, it is going to be somewhat difficult to explain why you are getting this error.  Are you able to isolate which specific niScope functions causes this error in the interactive execution window?  Also, is it just the niScope driver functions that you are using in the code running in the interactive execution window?
If you could attach a few lines of code that easily reproduce the problem, we will be better able to isolate where the problem lies and if this has been fixed in newer versions of the the NI Scope driver / CVI environment.

Thanks

[Wendy L]

Hello again David,

I would also suggest downloading the 30 day evaluation version of CVI 8.0.   If you are able to reproduce this problem in CVI 8.0's IEW window, definitely let me know.

Thanks.