Win2000pro terminates application

[Martin.D]

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 y
InitializeCriti
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¨

[shoneill]

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
<506500000008000000A01F0000-986697009000@quiq.com>...
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 y
InitializeCriticalSection 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¨

[Martin.D]

All the CINs & DLLs should be Win2Kpro compatible i.e. SQL toolkit. By the "old style serial driver" I mean the non-VISA type shipped with LV. There may be something running in the background that I'm not aware of, started by the network log-on, I'll check.

Thanks Shane

[Mark A. Hanning-Lee]

martins bit wrote:
>
> 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).

Probably best if your app does NOT create or keep files in the Windows
temp folder. They are vulnerable to automatic clean-up and other
operations!

Best, Mark