Modman is a simple Visual Basic application which makes use of the tool helper DLL distributed with Windows 3.1 to give you access to the list of currently loaded Windows modules. A module is the memory image of a loaded DLL or EXE (not to be confused with a Windows instance or task, of which there can be more than one per module, for EXE's at least). The list box on the left hand side of the main Modman window displays the names of all modules in memory (this name is not necessarily the same as that of the file from which the module was loaded). When an entry is clicked on, the right hand side of the screen is filled in with the following information about the module: Handle - the internal Windows module handle (HMODULE) Reference count - the number of times the module has been loaded Path - the file from which the module was originally loaded The list can be updated at any time by clicking the Refresh button. To decrement the reference count of the selected module by one, click the Free button. When the reference count reaches zero, the module will be unloaded. This can be very handy for cleaning up DLL's after a program crash without having to restart Windows--it can also be very dangerous, since if a DLL is actually still being used, the system will crash the next time a call is made to it. To force-load a module, click the Load button and select the file of interest. The new module should appear immediately in the list. This can be useful when debugging a DLL with a tool such as Turbo Debugger for Windows, which does not allow a module to be loaded explicitly. Load and Free should really only be used with dynamic link libraries, not executables, since LoadLibrary and FreeLibrary are used. This program was developed mainly as a development utility. It can help in telling whether and when a library is actually getting loaded, and where it is getting loaded from (a problem when a file server or local disk has an extensive search path and multiple versions of the DLL lying around). If you have comments and suggestions, or would like a copy of the source code, contact John Sichi 1676 Samedra Sunnyvale, CA 94087 or sushi@netcom.netcom.com Note: you need TOOLHELP.DLL and COMMDLG.DLL, distributed with Microsoft Windows 3.1, to run MODMAN