http://bugs.winehq.org/show_bug.cgi?id=34098
--- Comment #5 from Mr Nobody limited_choice@hotmail.com 2013-07-24 19:42:12 CDT --- ... in the process of backtracking where this broke again after wine-1.5.15 (to get a fix on where to look for the actual regression..if any), I discovered a couple of things...
... going backwards from wine-current, @ wine-1.5.18 or such, the helper program 'winOSext.exe' started hoisting an error message about it's requirement for .NET 4.0 .. (?).. indeed, the gamefly installer exe now actually bundles 'dotNetFx40_Full_setup.exe' (which is the web-installer version), but that part of the installation never fires and/or quietly fails...
... creating a wineprefix & preparing that by adding .net4 to it prior to running the gamefly installer, doesn't change the situation... ie; .net4 is there but the client still fails to install any game it downloads. There are two helper apps the gamefly client calls to - 'winOSext.exe' and 'GameflyGameInstallManager.exe' -- although I hit the 'install game' widget 3 times in the +file log, it never seems as though GameflyGameInstallManager.exe ever gets called at all ... the other helper app is seen to be accessed ...
... these observations make me wonder whether or not it *should* still work in wine-1.5.15, but it does still work there and then without any .net4 being involved. In any event, I've no idea what debug channels to poke at, as most all I've tried thus far return very little chatter at all. I should also mention that I believe previous versions of the gamefly client *didn't* bundle the .net4 installer, and this could very much be as much to do with changes to the gamefly client itself, as it has to do with changes to wine...if anyone has an idea on where/what I should look at, let me know...