Re: load_dll: MODULE_GetLoadOrderW on filename versus libname

2004-09-22 Thread Uwe Bonnes
> "Mike" == Mike Hearn <[EMAIL PROTECTED]> writes: >> load_dll now does a find_dll_file and sees >> "L:\\temp\\IXP000.TMP\\msi.dll" . sets filename to >> "L:\\temp\\IXP000.TMP\\msi.dll" and compares >> "L:\\temp\\IXP000.TMP\\msi.dll" for the loadorder. Mike> Try using *msi

Re: load_dll: MODULE_GetLoadOrderW on filename versus libname

2004-09-22 Thread Mike Hearn
load_dll now does a find_dll_file and sees "L:\\temp\\IXP000.TMP\\msi.dll" . sets filename to "L:\\temp\\IXP000.TMP\\msi.dll" and compares "L:\\temp\\IXP000.TMP\\msi.dll" for the loadorder. Try using *msi=b in the dll overrides. That makes it apply to any path. Yes this is very unintuitive, badly d

load_dll: MODULE_GetLoadOrderW on filename versus libname

2004-09-22 Thread Uwe Bonnes
Hallo, some installer (extracted from slvc009j.zip from Texas instruments (www.ti.com)) loaded the native msi.dll, also I gave WINEDLLOVERRIDES=msi=b on the command line. The program copies some msi.dll to some directory, and prepends that directory to the loadpath. Then it calls: 000d:Call kernel