Hi, I read at this post[1] a problem that I'm also having. The possible solution offered was to run the wine commando overriding the order in which the DLLs are searched, well that didn't do the trick. I'm trying to execute Outlook 97 with wine and I'm getting: $ WINEDLLOVERRIDES="olemsg=b" wine OUTLOOK.EXE err:module:import_dll No implementation for MAPI32.dll.173 imported from L"C:\\Program Files\\Microsoft Office\\Office\\OUTLLIB.dll", setting to 0xdeadbeef [...] err:module:import_dll No implementation for MAPI32.dll.239 imported from L"C:\\Program Files\\Microsoft Office\\Office\\OUTLLIB.dll", setting to 0xdeadbeeferr:module:import_dll No implementation for ole32.dll.CoInitializeEx imported from L"C:\\WINDOWS\\SYSTEM\\shlwapi.dll", setting to 0xdeadbeeffixme:keyboard:X11DRV_KEYBOARD_DetectLayout Your keyboard layout was not found!Using closest match instead (United States keyboard layout (phantom key version)) for scancode mapping.Please define your layout in dlls/x11drv/keyboard.c and submit them to us for inclusion into future Wine releases. See the Wine User Guide, chapter "Keyboard" for more information. fixme:seh:EXC_RtlRaiseException call to unimplemented function mapi32.dll.EnableIdleRoutinewine: Unhandled exception (thread 000d), starting debugger... WineDbg starting on pid c No debug information in ELF 'wine' ((nil)) No debug information in 32bit DLL 'C:\Program Files\Microsoft Office\Office\OUTLOOK.EXE' (0x30000000) [...] Unhandled exception: unimplemented function mapi32.dll.EnableIdleRoutine called in 32-bit code (0x00bb8058).In 32-bit mode. 0x00bb8058 (MAPI32.DLL..text+0x7058 in MAPI32.DLL): subl $4,%esp Wine-dbg>quit WineDbg terminated on pid c $ wine -v Wine 20031212 $ Is there any way around this? I'm using Fedora 1 with wine version 20031212 thanks a lot, daniel/// [1]: http://www.winehq.org/hypermail/wine-users/2004/01/0046.html
> Wine-dbg>quitWhen you get this, type bt, it will return some information useful on knowing where wine crashed. Also, have a look at http://www.winehq.com/site/docs/wine-user/bugs Ivan.
On Fri, 23 Jan 2004 13:13:18 -0300 (ART), you wrote:> Hi, I read at this post[1] a problem that I'm also having. The possible > solution offered was to run the wine commando overriding the order in > which the DLLs are searched, well that didn't do the trick.Please tell us what you tried! If you want us to guess, this is not going to work.> I'm trying to execute Outlook 97 with wine and I'm getting: > > $ WINEDLLOVERRIDES="olemsg=b" wine OUTLOOK.EXE > err:module:import_dll No implementation for MAPI32.dll.173 imported from > L"C:\\Program Files\\Microsoft Office\\Office\\OUTLLIB.dll", setting to > 0xdeadbeef > [...] > > err:module:import_dll No implementation for MAPI32.dll.239 imported from > L"C:\\Program Files\\Microsoft Office\\Office\\OUTLLIB.dll", setting to > 0xdeadbeeferr:module:import_dll No implementation for ole32.dll.CoInitializeEx > imported from L"C:\\WINDOWS\\SYSTEM\\shlwapi.dll", setting to 0xdeadbeefTry with native mapi and mapi32 dll's. Try with native ole2, ole32, oleaut32 dll's Try with builtin shell32, shell and shl* dll's (just guessing) Rein. -- Rein Klazes rklazes@xs4all.nl
> This Outlook version is in Spanish, does it matter?No, at least it's very improbable> Any ideas?If you can't get this to work using mixed native/builtin dlls, and if everything else listed at http://www.winehq.com/site/docs/wine-user/bugs fails, I think you should open a bug report on If you open a bug report, it's a good idea to tell the wine-devel mailing list, you have better chances of getting a developer to look into it, as quite a few developers like the idea of office working smoothly. If you open a bug report, provide all the information you can on which version of wine you're using, you're system specs (Kernel, glibc, distro name and version, wine release), and the complete log with the backtrace (Don't cut anything, if it's quite long just copy it to a text file and add it to the bug report as an attachment). Ivan.