https://bugs.winehq.org/show_bug.cgi?id=46853
--- Comment #6 from Louis Lenders xerox.xerox2000x@gmail.com --- Created attachment 63908 --> https://bugs.winehq.org/attachment.cgi?id=63908 last 4000 lines of the debuglog before the MessageBox
Hi Ahmed,
As a guess i would say this is a duplicate of bug 45429; I attached last 4000 lines before MessageBox appears.
There is reference to wintb.dll in your logfile (see bug 45429). grep wintb log.txt
0036:Call KERNEL32.GetFileAttributesW(006086bc L"C:\users\ahmed\Temp\is-AHTEH.tmp\wintb.dll") ret=00479390 0036:Call KERNEL32.MultiByteToWideChar(000004e4,00000000,00637fbc "wintb.dll",00000009,0033eb58,000007ff) ret=00405611 0036:Call KERNEL32.CreateFileW(006c9574 L"C:\users\ahmed\Temp\is-AHTEH.tmp\wintb.dll",40000000,00000000,00000000,00000002,00000080,00000000) ret=004b35f2
Last lines before Messagebox:
0036:fixme:explorerframe:taskbar_list_SetThumbnailTooltip iface 0x1b0698, hwnd 0x1009c, pszTip L"Slay the Spire" stub! 0036:Call user32.MessageBoxA(00000000,075a7768 "Runtime error 229 at 075A4BCF",075a7760 "Error",00000000) ret=075a3915
If you know how to compile wine, you could try Focht`s suggestion to fake success for the called functions (see bug 45429)
"Just returning 'S_OK' is enough to make the installer work. In future there should be a more elaborate implementation though."
See https://bugs.winehq.org/show_bug.cgi?id=45429
Or maybe try a native explorerframe.dll but I don`t know if that works
@Staging people: Could such a patch (faking success) be included in Staging?