Problems of executive files after PC crash

[SolarLR]

My developing PC was crushed last week when LabView project was programming. The culprit is due to device driver conflict from both Keithley USB driver and NI 488.2 driver. After recovered the corrupted project, the executive files started showing errors like"LabVIEW:Memory is full"; "LabVIEW Load error code 33: Could not load front panel data logging...";"LabVIEW:End of file encountered" ; "LabVIEW load error code 12: Could not load connector type map" etc... when executive files were distributed to run-time PC.

I removed all LabView 8.0 developing suite and re-installed LabView 8.2. However, the problem was not resolved.  The executive files are ruuning no problems on developing PC but failed on run-time PC.

I brought same source files to another developping PC and made executive files. They are also running fine on run-time PC. Really, I totally have no idea what's wrong with developping PC after crushed. How comes the installer and execution files start having problems even I re-installed LabVIEW? Thanks your kinding answer. 

[Dennis_Knutson]

Some of those error codes have two possible causes. They are usually given as:

Possible reason(s):

LabVIEW:  Some system capacity necessary for operation is not enabled.
=========================
NI-488:  File system operation error.

Since you had problems with the NI-488 driver, my guess is that the possible reason is the second listed . Uninstalling and installing LabVIEW does not automatically uninstall and re-install the hardware drivers. Try doing a repair of NI-488 or completely uninstall that and re-install.

[Empty_Field]

Check your USB devices as well.  I have seen USB DAQ devices in the past where the only way to recover from the problem was to use Windows Device Manager to delete the device then re-boot to allow Windows to reinstall it.

Let us know what you find out.

Regards,

Walt

[SolarLR]

Thanks replies from Dennis and Walt.

I have tried to remove NI 488.2.2 driver as well as Keithley USB driver by Windows devices manager. Then only re-intalled NI 488.2.2 back. There is still problems so far.

I wonder some registry or ini files related to LabView been wrong since PC crash. That caused the VIs or SubVIs messed up when built into executable files. However, I still try to look at any info to resolve this issue before restore the whole operation system.

[Justin D]

SolarLR,

Have you tried creating a new build script?  On the development PC that does build a good executable, does it use the same build script as the PC that's not creating the good exe?  Have you tried to do a repair on the LabVIEW 8.2 installation?

Justin D