Created attachment 43195 [details]
CaesarIV crashes during Autorun execution

> wine /media/Disk1/CaesarIV.exe 

use windows paths, not unix. Something like:
$ wine start D:\CaesarIV.exe may help.

Created attachment 43204 [details]
CaesarIV crashes during Autorun execution

Comment on attachment 43195 [details]
CaesarIV crashes during Autorun execution

>wine /media/Disk1/AutoRun.exe 
>Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
>fixme:msxml:domdoc_get_parseError (0x16211c)->(0x32fd10): creating a dummy parseError
>wine: Unhandled exception 0xc000000d in thread 9 at address 0x320023:0x004065b5 (thread 0009), starting debugger...
>Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
Process of pid=0008 has terminated
>No process loaded, cannot execute 'echo Modules:'
>Cannot get info on module while no process is loaded
>No process loaded, cannot execute 'echo Threads:'
>process  tid      prio (all id:s are in hex)
>0000000e services.exe
>        00000020    0
>        0000001f    0
>        00000019    0
>        00000018    0
>        00000017    0
>        00000015    0
>        00000010    0
>        0000000f    0
>00000012 winedevice.exe
>        0000001d    0
>        0000001a    0
>        00000014    0
>        00000013    0
>0000001b plugplay.exe
>        00000021    0
>        0000001e    0
>        0000001c    0
>00000022 explorer.exe
>        00000023    0
>winedbg: Internal crash at 0x7ed45e1a

Comment on attachment 43195 [details]
CaesarIV crashes during Autorun execution

>wine /media/Disk1/AutoRun.exe 
>Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
>fixme:msxml:domdoc_get_parseError (0x16211c)->(0x32fd10): creating a dummy parseError
>wine: Unhandled exception 0xc000000d in thread 9 at address 0x320023:0x004065b5 (thread 0009), starting debugger...
>Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
Process of pid=0008 has terminated
>No process loaded, cannot execute 'echo Modules:'
>Cannot get info on module while no process is loaded
>No process loaded, cannot execute 'echo Threads:'
>process  tid      prio (all id:s are in hex)
>0000000e services.exe
>        00000020    0
>        0000001f    0
>        00000019    0
>        00000018    0
>        00000017    0
>        00000015    0
>        00000010    0
>        0000000f    0
>00000012 winedevice.exe
>        0000001d    0
>        0000001a    0
>        00000014    0
>        00000013    0
>0000001b plugplay.exe
>        00000021    0
>        0000001e    0
>        0000001c    0
>00000022 explorer.exe
>        00000023    0
>winedbg: Internal crash at 0x7ed45e1a

(In reply to comment #3)
> Created attachment 43204 [details]
> CaesarIV crashes during Autorun execution
(In reply to comment #2)
> > wine /media/Disk1/CaesarIV.exe 
> 
> use windows paths, not unix. Something like:
> $ wine start D:\CaesarIV.exe may help.


(In reply to comment #2)
> > wine /media/Disk1/CaesarIV.exe 
> 
> use windows paths, not unix. Something like:
> $ wine start D:\CaesarIV.exe may help.


Thanks for your quick answer.
Unfortunately, I obtain the same reports using Unix paths :
- Calling Caesar IV.exe leads to exactly same execution log
- Calling Autorun.exe leads to display of Autorun menu. By clicking "Run Caesar IV", I obtain the following report (see updated "CaesarIV crashes during Autorun execution" log) and a "Runting Error" box is displayed.
- Same problem, by using the "~/.wine/drive_c/Program Files (x86)/..." path (CaesarIV.exe or C4Exec.exe)

(In reply to comment #3)
> Created attachment 43204 [details]
> CaesarIV crashes during Autorun execution
(In reply to comment #2)
> > wine /media/Disk1/CaesarIV.exe 
> 
> use windows paths, not unix. Something like:
> $ wine start D:\CaesarIV.exe may help.


(In reply to comment #2)
> > wine /media/Disk1/CaesarIV.exe 
> 
> use windows paths, not unix. Something like:
> $ wine start D:\CaesarIV.exe may help.


Thanks for your quick answer.
Unfortunately, I obtain the same reports using Unix paths :
- Calling Caesar IV.exe leads to exactly same execution log
- Calling Autorun.exe leads to display of Autorun menu. By clicking "Run Caesar IV", I obtain the following report (see updated "CaesarIV crashes during Autorun execution" log) and a "Runting Error" box is displayed.
- Same problem, by using the "~/.wine/drive_c/Program Files (x86)/..." path (CaesarIV.exe or C4Exec.exe)

Does the demo have the same problem?
http://www.fileplanet.com/166503/160000/fileinfo/Caesar-IV-Demo

Created attachment 43222 [details]
CaesarIV Demo also crashes

(In reply to comment #8)
> Does the demo have the same problem?
> http://www.fileplanet.com/166503/160000/fileinfo/Caesar-IV-Demo

Yes, same problem with the demo (see CaesarIVDemo_exe_backtrace.txt)

I can't reproduce the crash here on Fedora 17. What distro are you using?

The demo needs .net20 and certain d3dx9 libraries (d3dx9_30 and d3dx9_36). I suppose those are installed for you as well. The demo here is loading fine to the menu then it hits bug #25677.
My other suspect would be Securom, as the demo is protected with Securom 7.26, and probably the disc version also uses some kind of protection.

(In reply to comment #11)
> I can't reproduce the crash here on Fedora 17. What distro are you using?
> 
> The demo needs .net20 and certain d3dx9 libraries (d3dx9_30 and d3dx9_36). I
> suppose those are installed for you as well. The demo here is loading fine to
> the menu then it hits bug #25677.
> My other suspect would be Securom, as the demo is protected with Securom 7.26,
> and probably the disc version also uses some kind of protection.

I'm using Kubuntu 12.10 (x64 version) upgraded to KDE 4.9.5 through the KDE ppa.
Today I have upgraded to the last wine 1.5.22 version. I always meet the same issues.

The installation phase seems to be normal, but with some ole, setuapi and richedit error messages(see CaesarIVDemo_installation_backtrace.txt).

During the installation of the Demo (same with the retail version), it is demand to install DirectX 9. 
I did both tests installing and not installing Direct X, and change wine settings to use native or integrated d3d9 library. Each time I obtain the same issues :

- A runtime "Mcirosoft Visual C+ Runtime Library" error box opens
- Caesar IV crashes with the same log as previously


In an other hand (I don't know if there is a link), when I launchs the last Wine Test exe (http://test.winehq.org/data/9f18a03b14a3405fb04da73cb87f421576825cfc/), I obtain a error during the d3d9_test.exe (see d3d9test_backtrace.txt)

Created attachment 43249 [details]
Caesar IV demo installation backtrace

Created attachment 43250 [details]
d3d9_test.exe log (from wine test 9f18a03b14a3 for wine 1.5.22)

Created attachment 43251 [details]
Runtime error box during CaesarIV execution

Please leave original version set.

Same problem using wine 1.5.28

I have the exact same issue with Wine 1.6-rc3 on a MacBook Air running MacOS X 10.8.4.

After some more tinkering I found that the game _does_ work if you launch Caesar\ IV.exe after changing into that directory.

As I figured, invalid.

Closing.

Created attachment 44968 [details]
Backtrace during execution of Caesar IV after installation

Same problem using wine 1.6-rc3
See attachment backtrace_CaesarIV.txt

(In reply to comment #19)
> After some more tinkering I found that the game _does_ work if you launch
> Caesar\ IV.exe after changing into that directory.


Same problem, after renaming CaesarIV into Caesar\ IV and calling :

wine ~/.wine/drive_c/Program\ Files/Sierra/Caesar\ IV/Caesar\ IV.exe 


Impossible to rename into D:/ (cdrom)

Created attachment 44969 [details]
Autorun_exe_backtrace.txt

Created attachment 44970 [details]
Same problem using CaesarIV Demo

Always same problem using CaesarIVDemo

(In reply to comment #23)
> (In reply to comment #19)
> > After some more tinkering I found that the game _does_ work if you launch
> > Caesar\ IV.exe after changing into that directory.
> 
> 
> Same problem, after renaming CaesarIV into Caesar\ IV and calling :
> 
> wine ~/.wine/drive_c/Program\ Files/Sierra/Caesar\ IV/Caesar\ IV.exe 
> 
> 
> Impossible to rename into D:/ (cdrom)

You have to launch from that directory. This isn't a wine bug.

Closing.

(In reply to comment #26)
> (In reply to comment #23)
> > (In reply to comment #19)
> > > After some more tinkering I found that the game _does_ work if you launch
> > > Caesar\ IV.exe after changing into that directory.
> > 
> > 
> > Same problem, after renaming CaesarIV into Caesar\ IV and calling :
> > 
> > wine ~/.wine/drive_c/Program\ Files/Sierra/Caesar\ IV/Caesar\ IV.exe 
> > 
> > 
> > Impossible to rename into D:/ (cdrom)
> 
> You have to launch from that directory. This isn't a wine bug.

Hi Austin,
After reinstalling completly from cdrom, whithout any problem and launching directly from the directory I still encounters the same crash...

1. Launching from directory after installation
user1@MyPC:~/.wine/drive_c/Program Files/Sierra/Caesar IV$ wine ./CaesarIV.exe
==> winedbg: Internal crash at 0x7ed2b5ea


2. Launching from directory after renaming .exe as "Caesar IV" as suggested by David Holm :
user1@MyPC:~/.wine/drive_c/Program Files/Sierra/Caesar IV$ wine ./Caesar\ IV.exe
==> winedbg: Internal crash at 0x7ed2b5ea

3. Launching directly from D:/, as you suggested on 2013-01-16
user1@MyPC:~$ wine start D:/CaesarIV.exe
==> wine: Unhandled exception 0x40000015 in thread 25 at address 0x6b0609 (thread 0025), starting debugger...


4. Launching using Autorun.exe  :
user1@MyPC:~$ wine start D:/Autorun.exe
==> wine: Unhandled exception 0xc000000d in thread 25 at address 0xf75c0023:0x004065b5 (thread 0025), starting debugger...

5. Launching CaesarIV Demo as suggested by GyB :
user1@MyPC:~/.wine/drive_c/Program Files/Sierra/Caesar IV Demo$ wine ./CaesarIVDemo.exe 
==>  winedbg: Internal crash at 0x7ed225ea


During this last attempt, a message box appears with the following message :
"Unable to register COM interop. Message : the requested feature is not implemented".

At the same time, the following message appears in the console :

"err:rpc:I_RpcGetBuffer no binding
fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub!

err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded

fixme:ole:CoCreateInstance no instance created for interface {00000000-0000-0000-c000-000000000046} of class {45224aff-d811-4fc2-adb2-645cea444135}, hres is 0x80131044"

And after leads to the "internal crash"

Notice that exactly the same error message sequence appears using the demo and the retail version.

Thank you in advance for your help

Well, turns out there is a bug. I noticed this when installing the demo:
fixme:mscoree:CLRMetaHost_GetRuntime Unrecognized version L"v1.0.3705"
fixme:mscoree:CLRMetaHost_GetRuntime Unrecognized version L"v1.0.3705"
fixme:mscoree:CLRMetaHost_GetRuntime Unrecognized version L"v1.0.3705"

on start, I get the COM error. If I run winetricks dotnet20 before installing, the game starts successfully. The game menu has no text, but that's a separate bug.

austin@aw25 ~ $ wine --version
wine-1.6-rc3-38-g9c49367
austin@aw25 ~ $ sha1sum caesar4_demo_en_FP.exe 
993144afd33ded60b0fce3e1c6e3a33904d0f5da  caesar4_demo_en_FP.exe
austin@aw25 ~ $ du -h caesar4_demo_en_FP.exe  
447M	caesar4_demo_en_FP.exe

Confirming.

(In reply to comment #30)
> austin@aw25 ~ $ wine --version
> wine-1.6-rc3-38-g9c49367
> austin@aw25 ~ $ sha1sum caesar4_demo_en_FP.exe 
> 993144afd33ded60b0fce3e1c6e3a33904d0f5da  caesar4_demo_en_FP.exe
> austin@aw25 ~ $ du -h caesar4_demo_en_FP.exe  
> 447M    caesar4_demo_en_FP.exe
> 
> Confirming.

Thanks

The following patches should fix the follow issues.
1. .NET 1.0 cannot be found. (installer)
2. Loading of an assembly from the application directory if it cannot be found elsewhere. 

http://source.winehq.org/patches/data/97879
http://source.winehq.org/patches/data/97880

.

Same problem using wine 1.7.1

Sorry, I'm not able to test the patch :
I can not compile wine from git directory
I'm probably not enough exeprimented to do this ... :(

Still remains using wine-1.7.4


Runtime Error at launch, unable to launch the game

log:
err:rpc:I_RpcGetBuffer no binding
wine: Unhandled exception 0x40000015 in thread 9 at address 0x110023:0x006b0609 (thread 0009), starting debugger...
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.

Fixed by commit 
http://source.winehq.org/git/wine.git/?a=commit;h=a3a19518f4acc9f48fa77e040ba6f2533c2b6022

Closing bugs fixed in 1.7.7.