CompuServe Thread

#_fstat broken?

4 messages in this thread
#50475From: Lee Hart [Microsoft]Aug 3, 1993 12:35 AM
>>>_fstat is returned -1 under win32s. Under NT it is returning 0 (which is expected). Is the _fstat broken under win32s? Several questions: (1) Are you linking against crtdll.lib, libc.lib or libcmt.lib? (2) Are you running a debugging version of Win32s and Windows 3.1? If so, is anything useful being spit out as a debug message? Lee There is 1 Reply.
#50569From: C.W.ChungAug 3, 1993 1:49 PM
I am not using crtdll.lib; I am using libc.lib i.e. $(conflags) $(conlibs). Also, no I am not using the debugging version of win32s. Karl There is 1 Reply.
#51100From: Lee Hart [Microsoft]Aug 6, 1993 3:18 PM
>>>I am not using crtdll.lib; I am using libc.lib Is there are reason that you can't switch to crtdll? >>>Also, no I am not using the debugging version of win32s. I think you would find it useful and productive to use this, at least for a while. Lee There is 1 Reply.
#51302From: C.W.ChungAug 9, 1993 2:20 PM
I believe that I have tried using crtdll.dll before. The underlying mechanism to _fstat seems to be broken. We can't switch to crtdll because C++ stream are not suppported… What I would like is for you to tell me if there is a work around for the _fstat problem or tell me that it will be fixed soon. Karl