LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

error cvirte 7.1

Hi guys,

 

We've had the customer uninstall, manually remove all CVI files, and reinstall and he's still seeing the error.  I'm going to send him a new burn to see if that clears it up.  I've also had him check the DEP and he has it to the minimal setting.

 

Judy

0 Kudos
Message 11 of 12
(727 Views)

Judy -

 

I would consider giving the customer a debug build, you can rename the executable to eliminate the "dbg" suffix.  Then, when the error occurs, if it's in the developer written CVI code, the customer should see a popup identifying the error and giving a module and line number reference to the origin.

 

As far as VirtualAlloc, I do know the heap allocation methods have undergone change / revision over the years - I recall we had an allocation of some kind that failed on XP Pro so I found sample Win32 code that used a LocalHeapAlloc of some kind instead of GlobalHeapAlloc I think it was and the problem went away.

 

This may be as simple as the application overflowing the buffer allocated by VirtualAlloc.

 

Menchar

0 Kudos
Message 12 of 12
(717 Views)