[Wine Weekly News]
> System DLLs
>
> The Wine team has determined that it is necessary to create fake DLL files to
> trick many applications that check for file existence to determine whether a
> particular feature (such as Winsock and its TCP/IP networking) is
> available. If this is a problem for you, you can create empty files in the
> "system" directory to make the application think it's there, and Wine's
> built-in DLL will be loaded when the application actually asks for it.
> (Unfortunately, tools/wineinstall does not create such empty files itself.)
>
> Applications sometimes also try to inspect the version resources from the
> physical files (for example, to determine the DirectX version). Empty files
> will not do in this case, it is rather necessary to install files with
> complete version resources. This problem is currently being worked on. In the
> meantime, you may still need to grab some real DLL files to fool these apps
> with.
> ...
Can you instead construct a system32 directory and populate it with symlinks
to appropriate wine DLL replacements, for example:
ln -s /opt/wine/lib/libshell32.so /opt/wine/share/system32/shell32.dll
The people can dynamically load them for resources or code without wine having
to anything more special than check the magic number on the front of the DLL
to see what type it is.
David Howells
