CrossOver Support - Community Forums

Hello all,

Used to poke around with Warhammer Online on MTW2 a while back, not used Crossover for a while but coming back again.

Want to get rid of the XP boot camp partition on my Macbook Pro (latest public Leopard build), and FM2009 is the only game I am currently playing; therefore this is an obstacle for me.

I'm working with a clean install of Crossover Games, and running FM2009 through Steam.

The first thing I noticed, looking at the log file when I ran the game directly using the fm.exe file using the 'Run' option is that it is looking for two .dll files that aren't present; msvcr80.dll and msvcp80.dll. Searching on Google for these brings you straight to download locations for both files, which need to go into the windows/system directory within the bottle Steam/FM2009 is installed in.

So, I tried to run the game, again with logging turned on, now that the .dll file are present.

A window comes up shortly after attempting to launch (this happens whether you're executing from within Steam or directly launching the fm.exe executable) with a 'runtime error' with error code R6034. In the log file, the missing .dll errors are gone, but have been replaced with:

fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" (8.0.50608.0)
err:ntdll:RtlpWaitForCriticalSection section 0x7bc893c4 "loader.c: loader_section" wait timed out in thread 004f, blocked by 0026, retrying (60 sec)
err:module:attach_process_dlls "MSVCR80.dll" failed to initialize, aborting
err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program Files\\Steam\\steamapps\\common\\football manager 2009\\fm.exe" failed, status c0000142

Hope this helps. Would love to get FM2009 working in OS X.

Cheers,
Dave

Hi,

The error R6034 is a recurrent issue it seems (not just with this title but
others as well) -- a lot of the time, this error can be caused by not having
.NET 2.0 installed into the same bottle. Other times, this is not the case
and something else is going awry.

A good reference for the problem is presented in winebug #16577 -- this is my
guess at what you're seeing;

http://bugs.winehq.org/show_bug.cgi?id=16577

The is some more info over at WineHQ AppDB regarding this title ;

http://appdb.winehq.org/objectManager.php?sClass=application&iId=8597

The information contained there relative to the 9.3.0 patch version seems relevant;

http://appdb.winehq.org/objectManager.php?sClass=version&iId=15809

Hope this helps....

Cheers!