This is an archive of CompuServe forum messages from 1985 to 1995, as saved in transcripts by John Foust.
Search Results (23 messages)
#51365-
Metaware C?
Message #51405
John, I don't know of any details about the Metaware /Pharlap tools that you purchased. I would ask the companies directly. There are several different approaches to getting started with the Win32 API's. The first is to purchase the Win32 SDK and VC++/NT (When it becomes available). The second is…
Robert, The Win32 Comm API's are not supported under Win32s. In order to access the Windows 3.1 Comm API's you will need to create a Universal Thunk and a 16-bit DLL that does the work. Thanks, Michael Markley [Microsoft Developer Support]
Mark, I don't think that it is possible to talk directly to the SCSI driver from within a POSIX application. Can you tell me why you need to access the driver directly? Thanks, Michael Markley [Microsoft Developer Support]
Issie, I am not familiar with WINEXIT. What does it do? I looked around and could not find it in the MSWIN32 forum. Also Win32s should be ready to run once Windows comes up. All of the files are loaded on an as needed basis. I can have Win32s apps…
Stephen, Place your DOS/Windows Comm access functions in a DLL and the use the Universal Thunks to load and access this DLL from your Win32s application. You can then use these functions for your comm calls. For Windows NT have a different DLL that uses the Win32 Comm API's to…
Stephen, There is very little difference between executables and DLL's under Windows NT. The biggest difference is in the entry point and how it is called. Both DLL's and executables are in the PE format. There is a pe.txt file located in the doc\sdk\filefrmt directory of the SDK CD. If,…
cron equivilant ?
Message #51082
George, I am looking into this and should have an answer for you soon. Sorry that it is taking so long to get you an answer on this. Thanks, Michael Markley [Microsoft Developer Support]
Tom, Sorry that this response has taken so long. I've been doing some research and have reached a point where I need additional information from you before continuing. Are you trying to use the Win32 API's or is the a POSIX or C-runtime type of question? Also are you trying…
Issie, I have not been able to reproduce this problem. I have tried FreeCell and several other applications and they all start without any problems. Have you tried putting FreeCell into your Startup Group to see if it will run? Thanks, Michael Markley [Microsoft Developer Support] There is 1 Reply.
Jan, Thanks, I re-read my post and noticed that I said ftp.rhino.com when I meant rhino.microsoft.com. Unfortunately I don't type as fast as I think so I tend to lose characters sometimes :^). Thanks, Michael Markley [Microsoft Developer Support] There is 1 Reply.
Bill, You need to have mstools\h in the include path. What I recommend doing is running setenv and the use the set command to see what env variables are set. Then use the control panel applet to set the values for path, include, lib and any others that have been…
Bruce, I have been unable to reproduce this problem on the released version of the OS. You might try changing to _getpid() and _fcvt() but I don't think that this should make a difference. Also try placing libcom.lib after the other libraries. Thanks, Michael Markley [Microsoft Developer Support] There is…
This is a known problem with the build that was included with the 475 build. It has been fixed in version 1.1 that is shipping now. Thanks, Michael Markley [Microsoft Developer Support] There is 1 Reply.
Rob, We have not seen any reports of similar behavior. The Windows debugging kernel would probably be of some help. To obtain this you will need to get a copy of the Windows 3.1 SDK. Thanks, Michael Markley [Microsoft Developer Support]
Paul, I recommend that you start by reading through the Win32s Programmer's Guide to get an idea of what Win32s really means. You can use the Win32s.dat file located in mstools\bin to test your sources for compatibility with Win32s. Writing a Win32s app is not difficult if you follow the…
Martin, There should not be any problems with 16-bit apps using NetBIOS calls. If you have specific questions or problems they will be addressed quicker if you post them in Section 12 of this forum. Also if it appears to be a compatibility problem then the questions/comments should go into…
Allen, I will be glad to take a look at the application but I'm not sure how useful that will be without being able to see the sources so that I can see if you are using any unsupported API's. Have you tried running the sources through PORTTOOL with the…
Bill, Thanks for the information on your use of Stacker with Win32s. Its really nice to hear that something works as expected rather than that you are having a problem with something. As to the installation problem, you should repost this question in the WINNT forum since the engineers there…
David, You can use the Tls API's and you can also declare variables as __declspec(thread). Version 1.1 of Win32s supports the __declspec(thread) modifier. For more information on __declspec(thread) see the modif.hlp file. There is an icon labeled Storage Class Modifier QuickRef in the Online References group that is created by…
Wayne, Have you tried rebuilding the sources? The version that is available on CIS was built for a version of the OS prior to the March release and this is probably the reason that the program dies. Thanks, Michael Markley [Microsoft Developer Support]
Named Pipes APIs
Message #50379
Dag, Under Windows NT the file system contains support for named pipes which vastly simplifies the task of implementation. To the best of my knowledge the named pipes under DOS were supplied by LAN Manager. The Win32 named pipe API's are calls into the underlying file system. Since they rely…
#Win32s data
Message #50365
David, Memory allocations under Win32s are always above the 2Gb point. It is not possible to get memory below this address. The recommended solution is to use the low bit as a mark bit. You can use the GetSystemInfo() API to determine the upper and lower limits of application address…
Win32s – performance
Message #50193
The Win32s API set is a subset of the Win32 API so recompiling for non-Intel environments will not result in any performance penalty when compared to the Intel binary. Also it is not necessary to recompile a Win32s app for Intel platforms. The same binary runs on Windows NT as…