[Bug 922] - Baldur's Gate II Setup.exe fails to run

[wine-bugs at winehq.com]

http://bugs.winehq.com/show_bug.cgi?id=922





------- Additional Comments From tony_lambregts at telusplanet.net  2002-08-08 14:55 -------
Here is the relevant part of the trace using --debugmsg +virtual,+module

trace:module:open_app_key searching 'F:\Setup.exe' in
AppDefaults\winedbg.exe\DllOverrides
trace:module:MODULE_GetLoadOrder got hardcoded default "n,b" for "F:\\Setup.exe"
trace:module:PE_LoadImage loading F:\Setup.exe
trace:virtual:CreateFileMappingW (4,(nil),01000000,0000000000000000,(null))
trace:module:map_image mapped PE file at 0x400000-0x425000
trace:module:map_image mapping section .text at 0x401000 off 400 size 4400 flags
60000020
trace:module:map_image mapping section .rdata at 0x406000 off 4800 size 1000
flags 40000040
trace:module:map_image mapping section .data at 0x407000 off 5800 size 600 flags
c0000040
trace:module:map_image mapping section .rsrc at 0x408000 off 5e00 size 1c200
flags 40000040
View: 0x400000 - 0x424fff 16
      0x400000 - 0x424fff c-r--
trace:virtual:VIRTUAL_SetProt 0x401000-0x405fff c-r-x
View: 0x400000 - 0x424fff 16
      0x400000 - 0x400fff c-r--
      0x401000 - 0x405fff c-r-x
      0x406000 - 0x424fff c-r--
trace:virtual:VIRTUAL_SetProt 0x406000-0x406fff c-rw-
View: 0x400000 - 0x424fff 16
      0x400000 - 0x400fff c-r--
      0x401000 - 0x405fff c-r-x
      0x406000 - 0x406fff c-rw-
      0x407000 - 0x424fff c-r--
trace:virtual:VIRTUAL_SetProt 0x407000-0x407fff c-rw-
View: 0x400000 - 0x424fff 16
      0x400000 - 0x400fff c-r--
      0x401000 - 0x405fff c-r-x
      0x406000 - 0x407fff c-rw-
      0x408000 - 0x424fff c-r--
trace:virtual:VIRTUAL_SetProt 0x408000-0x424fff c-r--
View: 0x400000 - 0x424fff 16
      0x400000 - 0x400fff c-r--
      0x401000 - 0x405fff c-r-x
      0x406000 - 0x407fff c-rw-
      0x408000 - 0x424fff c-r--
                   ^^^^^^    ^
                   ||||||    |

When the module map is set up in the first place 0x4239dc is int the range
0x408000 - 0x424fff So if I understand correctly it should be the default
exception handler that should catch this.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=922>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.