🚀 go-pugleaf

DA>I'd like to get a description of the entry points and calling
DA>sequences for all the "standard" Windows 3.1 .DLLs (e.g. commdlg.dll).
DA>Is there such a thing?  I don't suppose there is any way to examine a
DA>.DLL and get this information.  Of course, it wouldn't tell you WHY to
DA>call the entry point, but if you could at least get the entry point
DA>names and calling sequences you would have a fighting chance of
DA>figuring out how to use the buggers.

David A. Bright,

There was an interesting article in Windows Tech Journal, August 1992,
titled, Spying on Windows that discusses something like what you have
mentioned.  The author, Brett Glass, wanted to use the calls in
LZEXPAND.DLL, and tried various paths of investigation.  The author
finally got a copy of the Windows 3.1 SDK and discovered how well he had
done.  He conclusion was that he "didn't discover absolutely everything
about the routines..." he felt he "had a good enough grasp of the basics
to put the DLL to use" in his own programs.  I personally would probably
just by the SDK rather than go through what he had to do to get what he
did.  Read the article.

- Larry Koester, Bloomer, WI
---
 þ DeLuxeý/386 1.25 #641s þ Now using Qmail DeLuxeý...and loving it!
--
Executive Network Information System  (914) 667-4567
International ILink Host