On Thu, Apr 24, 2008 at 4:50 AM, Dan Kegel <<a href="mailto:dank@kegel.com">dank@kegel.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Thu, Apr 24, 2008 at 2:36 AM, Alexandre Julliard <<a href="mailto:julliard@winehq.org">julliard@winehq.org</a>> wrote:<br>
> You certainly don't want to call through explorer for that, showing a<br>
> message box directly is fine.<br>
<br>
</div>Well, that's easier :-)<br>
<div class="Ih2E3d"><br>
> You have to be careful to only do it when<br>
> loading the main exe, not for any random dll load<br>
<br>
</div>Yeah, I guess some apps tolerate missing DLLs by loading them manually.<br>
We'll miss a few problems (e.g. apps that delay-load but can't handle<br>
the missing dll) but that's ok.<br>
<div class="Ih2E3d"><br>
> also you have to properly handle the case of a missing X display<br>
<br>
</div>right, and just not call MessageBox.<br>
<br>
Hmm, ideally we would send them to a web page that gave<br>
information tailored to the dll in question, but a MessageBox is<br>
good enough for 1.0.<br>
<br>
<br>
</blockquote></div>A link to a wiki page (<a href="http://wiki.winehq/MissingDLL">http://wiki.winehq/MissingDLL</a> ?) with list of common dlls/where they come from/what they do/how to use winetricks/etc.) would be a bit easier/quicker to implement.<br>