<br><br><div class="gmail_quote">On Mon, Jul 12, 2010 at 12:44 PM, Peter Urbanec <span dir="ltr"><<a href="http://winehq.org">winehq.org</a>@<a href="http://urbanec.net">urbanec.net</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Can I get wine to ignore the manifests and just load DLLs from the app directory?<br>
<br><br></blockquote><div>I am not sure if our loader was every updated to mimic this behavior (Alexandre and I discussed it before), but older versions of windows used to support local dlloverriding by making a dummy file called appname.exe.local and placing that in the same folder of the application and the dlls you want to load. For example, say you have iexplore.exe and you want to force using some local dlls for testing, you can create a dummy file called iexplore.exe.local which would be placed in the same folder.</div>
<div><br></div><div>Like I said, I don't know if support for this was added to Wine, iTunes and Internet Explorer 5 both made use of this behavior under Windows 2000 and it's possible the behavior has changed in newer windows versions.</div>
</div><br clear="all">Thanks<br>-- <br>Steven Edwards<br><br>"There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo<br>