WINE server messages

Alexandre Julliard julliard at
Wed May 30 14:05:24 CDT 2001

David Howells <dhowells at> writes:

> I'm having a little trouble deciding exactly how to emulate the "module
> registration" functionality in my kernel module. It occurs to me that this
> might be easier to accomplish with a change to the current wine server message
> set. My idea is:
>  * Have the server only deal with NT Section objects and views of Sections.
>  * Have no separate module table attached to a process.
>  * Implement NtQuerySectionInformation/NtSetSectionInformation calls (or
>    whatever they're called) as wineserver messages.
>  * Add an extra Wine-specific information class for the purpose of recording
>    the extra module information.
>  * The wineserver process structure can then be changed so that rather than
>    keeping a separate list of process_dlls, they can just keep a list of
>    section views, some of which will be images/modules.

Maintaining a section list in the server is certainly something we
could do, but I don't really see why you want to get rid of the
modules list. What would you gain by doing that?>

Alexandre Julliard
julliard at

More information about the wine-devel mailing list