[Bug 33776] UPlay games does not work into 64Bits prefix and Wine set to Vista/Win7

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=33776

--- Comment #20 from Adam Bolte <abolte at systemsaviour.com> ---
I noticed a bunch of ACL-related patches in the wine-staging repo, so I just
added all of them to 1.7.33 using:

make -C ./patches DESTDIR="$(pwd)" install

However none of those made any difference to the execution of Far Cry 3 or 4.
Only Qian's hack works if applied (with or without the staging patches), and
only for Far Cry 3.

For reference, Far Cry 4 only prints:

fixme:heap:RtlSetHeapInformation 0xd10000 0 0x7fffc965cf00 4 stub
fixme:heap:RtlSetHeapInformation 0xf30000 0 0x23fc90 4 stub
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:process:OpenProcess hack: access is 00001400
fixme:process:OpenProcess hack: access is 00001400

There is no crash window, bad Wine exit status, or anything displayed to
indicate a failure. The first three lines seem to be related to the initial
cloud save and Uplay overlay warning windows that appear when cloud saves and
the overlay have been disabled under settings, so basically only the two
OpenProcess lines are printed. This is the same if launched by clicking "PLAY
Far Cry 4" in Uplay, or executing the FarCry4.exe directly through wine when
Uplay is already running.

Happy to assist with testing or provide any additional information which may be
helpful in solving this.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.