http://bugs.winehq.org/show_bug.cgi?id=16051
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #2 from Anastasius Focht focht@gmx.net 2008-11-19 18:04:09 --- Hello,
--- quote --- 1. download lotro installer from URL above 2. run the installer, it should run a subinstaller for dotnet 1.1 --- quote ---
You forgot to mention that the installer downloads a whopping 5.5 GiB first - before doing anything useful :)
--- snip --- [focht@localhost lotr]$ ls -lsa total 5762640 4 drwxrwxr-x 2 focht focht 4096 2008-11-19 22:38 . 4 drwxrwxr-x 9 focht focht 4096 2008-11-18 21:27 .. 824548 -rw-rw-r-- 1 focht focht 843503843 2008-11-18 21:15 lotrosetup-1a.bin 927904 -rw-rw-r-- 1 focht focht 949237987 2008-11-18 22:02 lotrosetup-1b.bin 927904 -rw-rw-r-- 1 focht focht 949237987 2008-11-18 22:31 lotrosetup-1c.bin 927904 -rw-rw-r-- 1 focht focht 949237987 2008-11-18 23:00 lotrosetup-1d.bin 927904 -rw-rw-r-- 1 focht focht 949237987 2008-11-18 23:26 lotrosetup-1e.bin 927904 -rw-rw-r-- 1 focht focht 949237987 2008-11-18 23:56 lotrosetup-1f.bin 296964 -rw-rw-r-- 1 focht focht 303787822 2008-11-19 00:06 lotrosetup-1g.bin 868 -rwxrwxr-x 1 focht focht 881560 2008-11-19 00:06 lotrosetup.exe 732 -rw-rw-r-- 1 focht focht 742784 2008-11-18 20:24 LOTRO-US-Book14-Downloader-StandardRes.exe --- snip ---
Although the installer succeeds in the end, it contains a couple of more or less known/reported bugs which are not subject of this bug report.
--- quote --- 3. run TurbineLauncher.exe from the directory where lotro was installed
This will pop up a dialog saying:
"Fatal execution engine error".
And if you click that away you'll get another one:
"Failed to load resources from resource file" "Please check your Setup" --- quote ---
You seem to get farther. Really no native gdiplus install/override? ... that would be cheating ;-)
GdipNewPrivateFontCollection stub is the first showstopper, it needs a real implementation.
--- snip --- $ wine ./TurbineLauncher.exe fixme:virtual:NtAllocateVirtualMemory MEM_WRITE_WATCH type not supported fixme:virtual:NtAllocateVirtualMemory MEM_WRITE_WATCH type not supported fixme:shell:URL_ParseUrl failed to parse L"mscorlib" fixme:shell:URL_ParseUrl failed to parse L"System.Windows.Forms" fixme:shell:URL_ParseUrl failed to parse L"System.Windows.Forms" fixme:shell:URL_ParseUrl failed to parse L"System" fixme:shell:URL_ParseUrl failed to parse L"System" fixme:shell:URL_ParseUrl failed to parse L"System.Drawing" fixme:shell:URL_ParseUrl failed to parse L"System.Drawing" fixme:mscoree:LoadLibraryShim (0x49b85e8 L"Gdiplus.dll", (nil), (nil), 0x32df18): semi-stub fixme:gdiplus:GdipNewPrivateFontCollection stub 0x49b8458 --- snip ---
The runtime callable wrapper (rcw)/interop maps GdipNewPrivateFontCollection's NotImplemented result to CLR NotImplementedException exception and throws a (first chance) exception of that type.
--- snip --- First chance exception generated: (0x049ccf24) <System.NotImplementedException> Unhandled exception generated: (0x049ccf24) <System.NotImplementedException> --- snip ---
The managed handler catches it and throws a TypeInitializationException CLR exception (class constructor method failed) to be handled by app.
--- snip --- First chance exception generated: (0x049ccf88) <System.TypeInitializationException> Unhandled exception generated: (0x049ccf88) <System.TypeInitializationException> _typeName=(0x049ccfcc) "com.turbine.launcher.Launcher" _className=<null> _exceptionMethod=<null> _exceptionMethodString=<null> _message=(0x049ce44c) "The type initializer for "com.turbine.launcher.Launcher" threw an exception." _innerException=(0x049ccf24) <System.NotImplementedException> _helpURL=<null> _stackTrace=(0x049ce548) array with dims=[12] _stackTraceString=<null> _remoteStackTraceString=<null> _remoteStackIndex=0x00000000 _HResult=0x80131534 _source=<null> _xptrs=0x00000000 _xcode=0xe0434f4d --- snip ---
This is unexpected for app (no other handler will swallow this one), hence either CLR debugger (if registered) or winedbg will be spawned.
--- snip --- ... wine: Unhandled exception 0xe0434f4d at address 0x7b8449b0 (thread 0039), starting debugger... wine: Call from 0x7b8449b0 to unimplemented function gdiplus.dll.GdiplusNotificationHook, aborting First chance exception generated: (0x049ce5b4) <System.Runtime.InteropServices.SEHException> --- snip ---
That second part reveals another shortcoming, GdiplusNotificationHook.
Your managed callstack looks like a different issue. The launcher process spawns several child processes which each end up in bugs. In such case it's better to use at least +tid,+process debug channels to get sorted out where the exception/dialog actually originates from.
Regards