Windows 2000 terminates LV app

Question

My LabVIEW5 or 6 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 LV serial driver (non-VISA), 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 bS nS T NS
T T @S T 0T yInitializeCrit
icalSection L DeleteCriticalSection LeaveCriticalSection nSetCommState ( GetCommState ' GetCommProperties ;SetupComm CloseHandle C CreateThread . CreateEventA oSetCommTimeouts ) GetCommTimeouts 1 CreateFileA X EnterCriticalSection BPurgeComm ?Sleep SetEvent jWaitForSingleObject 3SetThreadPriority j EscapeCommFunction ClearCommBreak kSetCommBreak ClearCommError
GetOverlappedResult t GetLastError {WriteFile aResetEvent VReadFile 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
Certified LabVIEW Architect

Answer 1

I have now discovered that these temp files are also created by the serial compatability VIs, which do not contain CIN's or DLL's i.e. "Bytes At Serial Port.vi". I have no idea why windows2K thinks that these are not valid windows images. I have now worked around the problem by using VISA, but would be very interested to know if this is unique to my application/PC's(x6).
Certified LabVIEW Architect