Why don't .exe's built under NT and LabVIEW 5.0.1 run under Windows 2000?

[Jim Heathfield]

I've got an application built under Windows NT 4 and LabVIEW 5.0.1 which involves a fair amount of basic IO e.g. Parallel port, serial port addressing. I've built the .exe and moved it to the target environment, a Windows 2000 PC and it doesn't load, it looks like it gets stuck searching for "cvirte.dll" - I thought this was for CVI or LabWindows, not LabVIEW... HELP?!!!

[Dennis_Knutson]

I don't believe that NI ever certified that 5.0.1 would run under Win2k. I think it's similar to their policy regarding 6.0 and WinXP - it might or might not work. The first official release that supported WinXP was 6.1 and the first official release that supported Win2k was either 6.0 or 5.1.

You could try installing the full development system on the Win2k pc and see if you can get the source code to run but if it fails there, your only options might be to stick to WinNT or to upgrade to something more recent (5.0.1 is really pretty old and 6.1 has a lot of nice, new features).

[eh]

Some IO routines might be written in LabWindows. Find this file on the PC that it works on and copy it to the target PC.

[Jeremy Braden]

I have seen this error before when I used a library of inport oand outport VIs from the web (accesshw). Essentially they were LabVIEW wrappers for CVI memory calls.
http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B45EACE3DEBD56A4E034080020E74861&p_node=DZ52058&p_submitted=&p_rank=&p_answer=&p_source=External

I think you could fix the problem by copying cvirte.dll to the same directory as your executable or into the data folder.