Motocross Madness 2 Forum

CrossOver Games 8.1.4 on Gentoo Linux

Installation goes fine, no errors. Executing the game creates a desktop flash (like it is trying to access the video card) and dies. The following is the verbose console output:

randy@pluto ~ $ .cxgames/Motocross\ Madness\ 2/desktopdata/cxmenu/Desktop.C\^5E3A\^5Fusers\^5Fcrossover\^5FDesktop/Motocross+Madness+2 --verbose
CXConfig->read(/opt/cxgames/etc/cxgames.conf)
CXConfig->read(/home/randy/.cxgames/cxgames.conf)
Product version=8.1.4
2502: Grabbing the lock '/tmp/.wine-500/cxgames-wine.lock'
2502: Got the lock
CXConfig->read(/home/randy/.cxgames/Motocross Madness 2/cxbottle.conf)
Mode = 'private'
Environment:
  CX_ROOT = "/opt/cxgames"
  CX_BOTTLE = "Motocross Madness 2"
  WINEPREFIX = "/home/randy/.cxgames/Motocross Madness 2"
  CX_WINDOWS_VERSION = <undefined>
  PATH = "/opt/cxgames/bin:/usr/local/bin:/usr/bin:/bin:/opt/cxoffice/bin:/opt/cxgames/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.3.4:/usr/qt/3/bin"
  LD_LIBRARY_PATH = "/opt/cxgames/lib"
  WINEDLLPATH = "/opt/cxgames/lib/wine"
  WINEDLLOVERRIDES = <undefined>
  LD_PRELOAD = ""
  LD_ASSUME_KERNEL = <undefined>
  WINELOADER = "/opt/cxgames/bin/wineloader"
  WINESERVER = "/opt/cxgames/bin/wineserver"
  WINEDEBUG = <undefined>
  CX_LOG = <undefined>
  CX_DEBUGMSG = <undefined>
  CX_WINE_USAGE_LOGFILE = "/home/randy/.cxgames/usage.log"
  DISPLAY = ":0.0"
2502: Releasing the lock
Command:
/opt/cxgames/bin/wineloader winewrapper.exe --wait-children --start -- C:/users/crossover/Desktop/Motocross Madness 2.lnk

** Wed Mar 31 20:17:53 2010
Starting '/opt/cxgames/bin/wineloader' 'winewrapper.exe' '--wait-children' '--start' '--'
'C:/users/crossover/Desktop/Motocross Madness 2.lnk'

fixme:exec:SHELL_execute flags ignored: 0x00000100
fixme:exec:SHELL_execute flags ignored: 0x00004100
fixme:shell:DllCanUnloadNow stub
fixme:dinput:SysMouseAImpl_Acquire Clipping cursor to (0,0)-(3840,1080)
fixme:win:EnumDisplayDevicesW ((null),0,0x33edf0,0x00000000), stub!
fixme:system:SystemParametersInfoW Unimplemented action: 110 (SPI_GETSHOWIMEUI)
fixme:system:SystemParametersInfoW Unimplemented action: 111 (SPI_SETSHOWIMEUI)
fixme:dinput:SysMouseAImpl_Acquire Clipping cursor to (0,0)-(112,27)
fixme:dinput:SysMouseAImpl_Acquire Clipping cursor to (0,0)-(112,27)

Any ideas?

Thanks!
Randy

Hi Randy,

  Hmmm..well that looks like dinput.dll being obnoxious,  

but those sort of traces don't really tell a lot...

The 'off the top of my head' idea would be to grab a native
dinput.dll and copy it into the bottle's ../../drive_c/windows/system32
location, and then set a library override in winecfg so the
load order for dinput is native,builtin

Otherwise, I would get a more meaningful debug log with something like
(going by what you've pasted, but you'll have to specify the name of
the actual game executable where I've put game.exe and the exact path
to where that file is, because what you've pasted used a desktop link
whch doesn't obviate the paths and such...like I say, of limited worth);

cd "/home/randy/.cxgames/Motocross Madness 2/drive_c/full/path/to/directory/containing/game.exe"

/opt/cxgames/bin/wine --bottle "Motocross Madness 2" --debugmsg +seh,+trace,+ntdll,+dinput game.exe &> ~/mm2.log

There's more than one way to grab such a log, but I use the above method as
I know some games -require- that they be launched from a PWD=$installdir and
as such, the launcher links/scripts in crossover may not work because of this.
So I always use this route, to help catch any such titles. Sorry if the above
looks messy, but you seem to use whitespace in bottlenames and as such, parts
of the commandline need encapsulating inside " " to work (whitespace is evil)

• a bottle name of MotocrossMadness2 is easier to deal with B)

Then check through the mm2.log file in your homedir for any meangingful clues
(or gzip the thing and upload it to rapidshare or the like and post the URL
back here so others can grab it and have a look - DON'T paste that log here,
it'll be big and detailed ;) The list of available debug channels you can poke
at is here - we invoke things differently than with wine, but else it's the same;

http://wiki.winehq.org/DebugChannels?action=show&redirect=WINEDEBUG

Hope this helps...

Cheers!