I am checking an old bug http://bugs.winehq.org/show_bug.cgi?id=9637 which happens to affect several games. Before arriving to the bug in question, one has to workaround another bug relate to shdocvw.dll. It is recommended to override a set of libraries which I believe should be put in system32. However, at least some of the dlls are already there. Are these the wine builtins or rather proxies as mentioned here: http://winehq.org/site/docs/wineusr-guide/config-wine-main. Could someone clear up where are the wine builtin dlls and where should I put the overrides in such a way that I can choose between both with winecfg?
On Sun, Mar 29, 2009 at 2:33 PM, fcmartins <wineforum-user at winehq.org> wrote:> I am checking an old bug http://bugs.winehq.org/show_bug.cgi?id=9637 which happens to affect several games. Before arriving to the bug in question, one has to workaround another bug relate to shdocvw.dll.Careful, that dll depends on a few others (mshtml/urlmon/etc.)> It is recommended to override a set of libraries which I believe should be put in system32. However, at least some of the dlls are already there. Are these the wine builtins or rather proxies as mentioned here: http://winehq.org/site/docs/wineusr-guide/config-wine-main.Yes, they are placeholders.> Could someone clear up where are the wine builtin dlls and where should I put the overrides in such a way that I can choose between both with winecfg?In system32, or the application's directory. -- -Austin
Thanks, out of curiosity, how does wine provide its dlls? I'm guessing they are packed in some file(s) out of Windows installation and depending on overriding information, a dll func call is directed to the builtin or the native dll. Where the builtin really exists, its hidden from the calling function. Something like this or another approach?