<br><br><b><i>Stefan Dösinger <stefandoesinger@gmx.at></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">Many applications behave that way, and we create fake .DLL files in system32. <br>They are real PE files from their file header, but they do not contain the <br>implementation. When an app tries to LoadLibrary this DLL we load the builtin <br>one instead<br><br>So we just have to add the needed DLLs to the fake DLL list. We don't add one <br>there without an application requiring it, because it makes it harder to <br>install MS library packages. E.g. the IE6 installer fails unless the user <br>deletes a bunch of those faked DLLs first<br></blockquote>The other problem was that it also failed attempting to find l_intl.nls. <br>And is this list of fake DLLs application specific? <br>Since I'm not sure what dlls all .NET 2.0 applications are going to try to search for, would we add all the
DLLs that are central to windows?<br>The program that I am using that relies on .NET requires (imm32, lz32, iphlpapi, & l_intl.nls), before it runs into an unimplemented RAS function.<br><br><br><p> 
<hr size=1>
Get the name you always wanted with the <a href="http://au.rd.yahoo.com/mail/taglines/au/y7mail/yahoo.com.au/*http://au.yahoo.com/y7mail/?p1=ni&p2=general&p3=tagline&p4=yahoo" target=_blank>new y7mail email address</a>.