01-29-2002 06:00 PM
01-30-2002 04:37 PM
09-09-2008 01:22 PM
Hi, I have absolutely the same problem. Is there any solution meanwhile?
Greetings
Oliver
09-09-2008 04:26 PM
Hi Oliver,
Assuming that the problem you're seeing is the same as the one in this thread, then it was was fixed with CVI 7.0 and later.
Do you only see the problem in Windows 2000? The reason I'm asking is because if it is the same problem, then it should show up in any version of Windows that is newer than Windows 98. Basically, the problem turned up in CVI when Microsoft fixed this bug. CVI then adjusted for it in version 7.0. So, if you're seeing this problem with CVI 5.5 in Windows 2000 but not, say, in Windows XP, then it's probably something else.
Luis
09-10-2008 01:39 AM
Hi Luis,
we have the problem also under XP. One of our machines, running XP, has the same problem.
Additionnally I could not use 7.x or later because we optimize our code with an external compiler. It is difficult to change.
Is there any other solution than using CVI 7.x or later?
Thanks
Oliver
09-10-2008 11:17 AM
Hi Oliver,
Unfortunately, there's no workaround that I can think of, other than upgrading.
You can always download the latest runtime engine, and at least your running program will not manifest the problem, even if it will still show up in CVI's User Interface Editor. One word of caution about this, however: if you do decide to download and install the runtime engine you should do so in a test machine first, and see how your application runs. The runtime engine is supposed to be backwards compatible, but upgrading from 5.5 to 8.5.1 is a very big leap, and there is always the possibility that minor changes over the years could now make a big difference for you.
Having said, I don't completely understand the external compiler rationale. Neither the CVI 5.5 nor the CVI 7.x compiler does code optimization, so does it really make a difference whether you use one or the other? By the way, starting with CVI 8.0, it's possible to specify an external compiler in the CVI environment which will optimize your release builds. You can do that without leaving the CVI environment.
Luis