Win2000pro terminates applicatio​n

Question

My LabVIEW5x application (exe or not) is closed by win2000pro because it creates several temp files in the temp directory. Windows suggests that these temp files are "NOT A VALID WINDOWS IMAGE". The temp files are created by CINS or dlls, ie. SQL toolkit, old style serial driver, etc. Any ideas? This is a cutting from one of the temp files, is this normal? They are cleaned-up when the app closes (if it doesn't crash).
Temp file cutting:
LVRTTable Fatal Error LABVIEW.LIB was not called from a LabVIEW process. �S JT âS îS T ÎS
T T ÀS T 0T yInitializeCriti
calSection L DeleteCriticalSection �LeaveCriticalSection îSetCommState ¨ GetCommState § GetCommProperties ;SetupComm CloseHandle C CreateThread . CreateEventA ïSetCommTimeouts © GetCommTimeouts 1 CreateFileA X EnterCriticalSection ÂPurgeComm ?Sleep SetEvent jWaitForSingleObject 3SetThreadPriority j EscapeCommFunction ClearCommBreak ëSetCommBreak ClearCommError
GetOverlappedResult ô GetLastError {WriteFile áResetEvent ÖReadFile GetProcAddress þ GetModuleHandleA KERNEL32.dll r __p__pctype d __p___mb_cur_max _isctype Dexit MSVCRT.dll Yfree _initterm �malloc � _adjust_fdiv �MessageBoxA USER32.dll Q DisableThreadLibraryCalls
è 000!0%0+0/05090?0D0]0i0�0²0¾0Ë0Ö0ù0141C1a1�1³1î1*2O2k2q2¨2å2í23\3�3�3¬3»3Z4n4t44�4Â​4ú4 55!5A5W5a5v5|5�5 5¨
Certified LabVIEW Architect

Answer 1

Are all of your Dlls and CINs W2k compatible ("old style serial driver")?
Do you have any other processes running in the background which may be
influencing these files?
Shane
martins bit schrieb in Nachricht
<[email protected]>​...
My LabVIEW5x application (exe or not) is closed by win2000pro because
it creates several temp files in the temp directory. Windows suggests
that these temp files are "NOT A VALID WINDOWS IMAGE". The temp files
are created by CINS or dlls, ie. SQL toolkit, old style serial driver,
etc. Any ideas? This is a cutting from one of the temp files, is this
normal? They are cleaned-up when the app closes (if it doesn't crash).
Temp file cutting:
LVRTTable Fatal Error LABVIEW.LIB was not called from a LabVIEW
process.
�S JT âS îS T ÎS
T T ÀS T 0T yInitializeCriticalSection L
DeleteCriticalSection �LeaveCriticalSection îSetCommState ¨
GetCommState § GetCommProperties ;SetupComm CloseHandle C
CreateThread . CreateEventA ïSetCommTimeouts © GetCommTimeouts 1
CreateFileA X EnterCriticalSection ÂPurgeComm ?Sleep SetEvent
jWaitForSingleObject 3SetThreadPriority j EscapeCommFunction
ClearCommBreak ëSetCommBreak ClearCommError
GetOverlappedResult ô GetLastError {WriteFile áResetEvent
ÖReadFile GetProcAddress þ GetModuleHandleA KERNEL32.dll r
__p__pctype d __p___mb_cur_max _isctype Dexit MSVCRT.dll Yfree
_initterm �malloc � _adjust_fdiv �MessageBoxA USER32.dll Q
DisableThreadLibraryCalls
è
000!0%0+0/05090?0D0]0i0�0²0¾0Ë0Ö0ù0
141C1a1�1³1î1*2O2k2q2¨2å2í23\3�3�3¬3»3Z4n4t44�4Â​4ú4
55!5A5W5a5v5|5�5 5¨
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)