make builtin dlls visible for applications?

Belxjander Serechai belxjander_serechai at yahoo.com.au
Fri Nov 18 08:31:50 CST 2005


On Thu, 2005-11-17 at 17:05 -0800, Juan Lang wrote:
> > 2) place dummy files for all builtin dlls in c:\windows\system32
> 
> I believe this is the correct approach.  I know of at least one
> InstallShield installer (that uses MSI) that searches for IE by looking
> for the file shdocvw.dll and checking its version.  Presumably we'd like
> our users to have the option of installing programs using all builtin
> DLLs, even with silly checks like this.
> 
> Eric once mentioned he had some hacky program that parsed PE headers that
> we might be able to coerce into creating such dummy DLLs.  What we're
> looking for (besides him posting the code) is a volunteer to work on it.
> 
> > hmm I guess you would get into trouble if you use WINEDLLOVERRIDE.
> > Wouldn't LoadLibrary try to load those dummy files?
> 
> Someone proposed a hack where the loader would know that these DLLs are
> dummies based on a wine-specific flag in the header.
> 
> --Juan

Doesn't have to be a flag specifically...
  I have the PE documentation and there is allowance for hacky tricks in
  the PE loader from what I remember reading...

Im also looking at porting wine to another platform as well so need such
information myself...

Jeremy


Send instant messages to your online friends http://au.messenger.yahoo.com 




More information about the wine-devel mailing list