http://bugs.winehq.org/show_bug.cgi?id=33776
Berillions berillions@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|trivial |normal
--- Comment #5 from Berillions berillions@gmail.com 2013-06-27 12:14:56 CDT --- I know that this bug will not be resolved during the freeze but i would like to know if: - I understand correctly where the problem can come from (maybe ?) - This bug can be corrected in the 1.7.x release
**** Real Seven 64-bits **** I create the log thanks to "process monitor". In this log, it's explain how a game is launched from UPlay :
Uplay.exe -> UbisoftGameLauncher.exe -upc_uplay_id "RANDOM_NUMERO_GAME" -upc_game_version "RANDOM_NUMERO_GAME" -upc_exe_path "RANDOM_LETTERS" -upc_working_directory -> Uplay-Game.exe (farcry3.exe for example)
**** 64-Bits wineprefix + Wine set to WinXP **** Like you see in the log, the game (Assassin's Creed II) is launched like on Real Windows 7 by the same way. No problems, the game runs fine. (line #12338)
**** 64-Bits wineprefix + Wine set to WinVista or Win7 **** A process for "UbisoftGameLauncher.exe -arg1 -arg2 etc..." is created like in the previous systems so no problem (line #12309)
But a second process is created, wine wants to launch the game by "UbisoftGameLauncher64.exe" (line #34147). --> This is incorrect because "Real Win7" has never used "UGL64.exe" to launch my game.
**** End of tests ****
So for me (it's my opinion), Wine create a process that it should not. Wine try to launch a 32-bits game app by a 64-bits executable.
Thanks for your explaination, Max