<div class="gmail_quote">On Mon, Aug 3, 2009 at 22:18, waraltca <span dir="ltr"><<a href="mailto:wineforum-user@winehq.org">wineforum-user@winehq.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">
</div>thanks for answering james...<br>
How do I set the dlls to native using Winecfg for isqlw.exe??<br>
<br>
thanks for tour help.<br>
</blockquote></div><br>Run winecfg, add your .exe to the list on the first tab, select it, switch to "DLL overrides" tab, add needed dlls there and set them to "Native, Builtin" order. But if you just set all dlls that program use to "native, Builtin", it will most probably not work. Windows dlls, especially "core" ones will almost surely crash in Wine. Wine is compatible (to some degree) with Windows on the external, "visible" API, but it do the internals differently (no Wine developers are actually know how Windows do these internals - it would be copyright violation that'd make the whole Wine project vulnerable to legal threats). Applications use that API and work. On the contrary, "core" Windows DLLs rely exactly on those hidden and undocumented internals and copying those DLLs from Windows will often do more harm than good.<br>
<br>You should by all means use winetricks to install needed dlls, and try to copy dlls from Windows manually only as the last resort. And you should not copy all dlls, only those that not present in Wine or don't work properly, one at a time. It may be tricky to determine, which ones are not working, yes.<br>
<br>Also, you should note that to maximize your chances, you should install everything to the clean prefix (just rename your current ~/.wine directory and run winecfg - it will create a shiny new prefix for you).<br clear="all">
<br>Related links:<br><a href="http://wiki.winehq.org/winetricks">http://wiki.winehq.org/winetricks</a><br><br>-- <br>Best regards,<br>Danila Sentiabov aka dsent<br>