LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Where do I start troubleshooting the release version of an excutable?

All,I am getting this failure: "ModName: cvirte.dll ModVer: 9.0.1.376 Offset: 0038e11a" when I run the release version of the executable.  I am new to CVI, I am picking up some old code and attempting to build with 9.0.1.  The application works in debug mode.  I think this may have something to do with the EasyTab.fp However I am unsure where to begin.  Any suggestions would be appreciated!Thanks,Rich
0 Kudos
Message 1 of 5
(3,578 Views)

A couple of quick suggestions:

 

1. Try recompiling the c files that define the EasyTab fp. You may be working with old .obj files. (See CVI help on Instrument >> Edit, and Loading / Unloading drivers)

 

2. Note that there is now a native tab control in CVI that you might want to move to, but I don't think it would be necessary.

 

Are you running the executable from within the IDE on the development machine or on another one?

 

--Ian

 

 

0 Kudos
Message 2 of 5
(3,564 Views)
You may also want to recompile the application having checked the "Create map file" in Build >> Target settings menu item: the map file lists individual calls and subroutine offsets so you may have some information comparing the offset listed in the error message with the map file.


Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 3 of 5
(3,557 Views)

 

Ian,

 

Thanks.  I tried to recompile the instrument (EasyTabs.fp)  this had no affect. 

I may need to look into the new CVI tab control that is native.

 

Thanks,

Rich

0 Kudos
Message 4 of 5
(3,556 Views)

Rich,

 

If your project has a reference to the easy tab library, remove it and re-add it just to be sure it's linking to the library included in CVI 9.0.1.

 

Going forward, the easy tab library is not being updated because of the newer native tab control, so if you can move to that, I'd recommend it, but there's no reason your old code shouldn't work...we just have to figure out what's wrong with it if you want to continue to go in that direction.

Eric B.
National Instruments
0 Kudos
Message 5 of 5
(3,513 Views)