CompuServe Thread

>>>The article I read, "Calling a Win32 DLL from a Windows 3.x Application" showed in the diagram three modules that I would have to create in addition to my Win 3.x application and my Win32 DLL; a 16-bit DLL (UT), a Win32 EXE (stub), and a Win32 DLL (UT). What exactly goes into each of these modules? If I do these correctly I shouldn't have to change my Win 3.x application or my Win32 DLL? Please point me to an example or template I can start from for this task as I am fairly new to windows programming.. I have not yet written a sample that shows this (it is high on my list of priorities, but answering questions on CIS is even higher). I believe the article describes generally what goes where. The Win16 DLL, when it initializes, looks to see if the Win32 EXE has been loaded (for example you could use a unique atom to indicate this.) If it has not, it WinExecs the Win32 EXE. The Win32 EXE, on init, will call UTRegister to set up the 2 way link to the Win16 DLL, including a 16->32 CallBack proc. It is via this proc that the Win16 DLL will call services in the Win32 DLL. When the Win16 DLL calls this proc (in the exact same manner as a Win32 DLL calling the Win16 UTProc), the dispatcher on the 32 bit side (that you write) will extract the arguments from the passed array and call the appropriate function in the Win32 DLL. Does this make sense? If not, please ask specific questions. If you have suggestions on hwo I could improve that article, please let me know. Lee There is 1 Reply.