http://bugs.winehq.org/show_bug.cgi?id=14083
--- Comment #5 from Juan Lang juan_lang@yahoo.com 2008-06-25 11:13:02 --- (In reply to comment #4)
I'll be glad to do the test but the instructions I received from the forum moderator, see http://forum.winehq.org/viewtopic.php?t=1414&sid=9d79596120e384ef5138a5e..., said to replace my oleaut32.dll with one from my Windows PC. So, I moved the dll over from a Windows XP install into my Wine System32 folder, I did not use the winetricks dcom98. My last set of changes included setting the winecfg for Logbook Pro to run oleaut32 in Native mode.
Don't worry, I was able to reproduce the bug, which is why I confirmed it.
If you have a copy of Windows (and therefore a copy of oleaut32.dll), you can copy oleaut32.dll from it rather than using 'winetricks dcom98'.
If you can tell me where I can get the builtin wine oleaut32.dll to put back into the System32 folder I'll be glad to do your test. I assume it's pointless to toggle the "native" mode on the Windows XP oleaut32 file
While this isn't a support forum, I'll explain this for you: you don't need to replace oleaut32.dll with the builtin one, they're installed in different locations. You can choose which one is used by using winecfg. Setting a DLL to be "native" will use oleaut32.dll from your windows/system32 directory, while using "builtin" will use oleaut32.dll.so from wherever Wine is installed. That's what "native" vs. "builtin" means: which version of the DLL does Wine try to load. It doesn't run them in different modes.