how do you keep windows 2000 from crashing with labwindows V6

[milkb1]

I have a program that was written in labwindows v.6 under windows 95 then under windows 98. Change OS to Windows 2000 and still using labwindows v.6 for the program. Now the computer crashes several times a day. Is there a known problem with Labwindows v6 and windows 2000? Is there a way to resolve this problem? I cant go back to windows 98.

Thank you

[mvr]

This proves very little, but I have CVI 6 on a win2000 system that has been running without any issue for some time [version 6.0.0 (105)].  Of course setups vary, DLLs, instrument drivers, versions of NIDAQ or 488.2, there can be a lot of variables with each configuration beyond just CVI.

[Alex D]

This is just a guess, but Windows 2000 and XP  (which are based on NT) have more strict enforcement of memory boundaries/etc. than 95/98/ME and therefore you can see crashes on those platforms that would not crash a 95/etc. system. It is very possible that a bug exists in your program which is causing the crash but for whatever reason it works ok on other flavors of Windows. Have you tried debugging the issue on win2k? If you can provide some more details about the crash (is the system blue-screening? if so, what is the crash code; or does the program just crash?) we might be able to shed some more light on the situation. Does the program use any driver software (DAQ, etc.)? As far as I know, there are no compatibility problems with CVI 6.0 on Windows 2000.

Also, the CVI Runtime engine is freely available for download and is API backwards compatible; if you believe the crash is a problem in the CVI runtime engine, you could upgrade to a newer version and see if that resolves your issue. The CVI 8.0 runtime engine is available here.

Hope this helps,

-alex

[milkb1]

Im sorry, there is no blue screen.  The system seems to just reboot  on its own. Meaning that the system would just shut down, then start to reboot and checking disk.  This may happen twice a day.  The driver software that im using are IMAO v.2.61.0, NI-488.2 v2.20, and Traditional NI-DAQ v6.9.1f28

Thank you

[Alex D]

The default configuration for windows 2000 is to automatically restart when you get a blue screen error. You can change your system configuration to stop in this case so you can see what error happened.

To do this, right click My Computer and go to properties. Go to the Advanced tab and click Startup and Recovery.... Uncheck Automatically Reboot. Then see if you can get the crash to happen. If you get a blue screen error then, note the code etc. and let us know. If you are still just spontaneously rebooting, you could also look in your system log to see if anything is reported there.

My only other idea would be to put some logging into your program that (for example) logs to a file when it does various things. Then you could get the crash to happen and look in the log and see what it was up to when the crash happened. This should help narrow down where the problem lies.

Hope this helps,

-alex