From the TASM individual (me) who refuses to switch a 354KB .ASM pgm to MASM. I found in one of my TASM .txt files a make file for DLL's and to use 'implib.exe' to build a .lib - both worked fine. The pgm assembled w/ no errors, but still did not work - no comm. w/ the machine.

However, I noted in one of Hutch's responses to someone else that you should use LoadLibrary and GetProcAddr and you must push the params manually. This is probably a stupid question, but if I push the params, does this mean I also have to pop them manually or will the funct. call do it?
Posted on 2001-11-24 13:08:33 by DaveTX47

When you manually call a procedure with LoadLibrary() GetProcAddress() the stack manipulation depends on the calling convention. With windows API calls they are almost exclusively STDCALL so you push your parameters in reverse order when you make the call and the STDCALL procedure cleans up the stack on return.

Now here is a little bait to further play with MASM, the different object file formats where MASM is COFF as against TASM using the OLD OMF format cash out in smaller EXE files when built in MASM.

Posted on 2001-11-24 16:49:43 by hutch--
Sorry Hutch, but don't understand what 'cash out' means. Borland states OMF is the Intel object file format.
Posted on 2001-11-24 20:37:49 by DaveTX47