http://bugs.winehq.org/show_bug.cgi?id=11994
sqweek sqweek@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sqweek@gmail.com
--- Comment #4 from sqweek sqweek@gmail.com 2008-05-04 05:21:44 --- Note that the bug only happens with the updated Battleye. Using a fresh install of soldat (don't forget to wipe %appdata%/Soldat), the battleye client initialises fine. But of course, it's not the same version the server is running, so it goes and downloads the update. As soon as it finishes and initialises the new battle eye client, you get the external exception. If you hamstring BE's update process (eg by making %appdata%/Soldat/Battleye/BEClient_x86.dll owned by root and non-writable), then the update doesn't succeed - you get to play a bit longer before the server kicks you with "Battleye client not responding".
Though I guess this isn't necessarily version related. At any rate, it rules out any battleye connection problems - the update code path works fine, it's just the anti-cheat code path that blows up. -sqweek