CompuServe Thread

#fseek() rets -1

5 messages in this thread
#50248From: C.W.ChungJul 30, 1993 6:15 PM
I am having a similar problem with fstat. It always seems to return -1. Under identical conditions under NT it returns zero. I wonder what they did to the win32s stuff. KQ There are 2 Replies.
#50309From: james lopesAug 1, 1993 1:53 AM
Lets keep in touch on this. We are porting a Unicode build are you also?. We are now getting a valide file handle and converting it to a file pointer and getting bad data in the stat_buf. I forget whT what the condition was at the moment. I at home and the code is at work. When I get there I'll send a message with the latest data. James There is 1 Reply.
#50480From: Lee Hart [Microsoft]Aug 3, 1993 1:17 AM
>>>Lets keep in touch on this. We are porting a Unicode build are you also?. You are converting your Win32 app to Unicode? If so, the *W forms of the Win32 APIs are not supported by Win32s, and you will have lots of API failures. Lee There is 1 Reply.
#51231From: james lopesAug 9, 1993 8:28 AM
All I can say is, OH!, Well… *W forms? James.
#50478From: Lee Hart [Microsoft]Aug 3, 1993 1:17 AM
>>>I am having a similar problem with fstat. It always seems to return -1. Under identical conditions under NT it returns zero. I wonder what they did to the win32s stuff. I need the same information – which C Runtimes, and is anything useful (like unsupported API calls) being reported by the debug Win32s? Thanks. Lee