Which ( any ) windows dlls should be moved to wine?

sean seandarcy at hotmail.com
Thu Jan 8 18:03:53 CST 2004


Duane Clark wrote:
> sean wrote:
> 
>> I'm runiing wine-20031212 on a dual boot machine. I have both win98 
>> and w2k installed.
>>
>> Other posts have suggested these be copied. Is the the right - 
>> complete?   -set?
>>
> 
> It doesn't hurt to copy all the DLLs over. But my suggestion is that in 
> the ~/.wine/config file, you use the default settings that comes with 
> Wine, which configures Wine to use mostly builtin DLLs:
> [DllOverrides]
> "msvcrt"       = "native, builtin"
> "mciavi.drv"   = "native, builtin"
> "mcianim.drv"  = "native, builtin"
> "msi"          = "native, builtin"
> "*" = "builtin, native"
> 
> And then if a particular application is having a problem with a 
> particular Wine DLL, then add a section for just that app to change the 
> default:
> [AppDefaults\\winword.exe\\DllOverrides]
> "oleaut32"     = "native, builtin"
> "ole32"        = "native, builtin"
> "comctl32"     = "native"
> "rpcrt4"       = "native"
Thanks.

But to be clear. I copy all the dll's over from win98, so that 
/usr/lib/wine/wine would have the wine dll.so's and the win98 dll's.
Then I just make the changes in the config file. Right?

Looking at the config file, I see - before any changes:

"msvcrt"       = "native, builtin"
"mciavi.drv"   = "native, builtin"
"mcianim.drv"  = "native, builtin"

Does this mean it's looking is /usr/lib/wine/wine for the native 
(*.dll) files, but will fall back to wine dll's ( *.dll.so)?

sean




More information about the wine-users mailing list