https://bugs.winehq.org/show_bug.cgi?id=15796
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- URL|https://gamefront.online/fi |https://web.archive.org/web |les/12340819/AADeployClient |/20200401220538/https://fil |Installer.exe |es.downloadnow.com/s/softwa | |re/11/02/80/68/AADeployClie | |ntInstaller.exe?token=15858 | |14617_f62138c885d6ad78d2a36 | |b2772f14d85&fileName=AADepl | |oyClientInstaller.exe Status|NEEDINFO |NEW Summary|America's Army Deploy |America's Army Deploy |Client v1.2.4 (.NET 2.0) |Client v1.2.x (.NET 2.0) |installer fails with |installer fails with |Wine-Mono |Wine-Mono
--- Comment #16 from Anastasius Focht focht@gmx.net --- Hello folks,
I've created a snapshot via Internet Archive:
https://web.archive.org/web/20200401220538/https://files.downloadnow.com/s/s...
@ joaopa
--- quote --- I manage to install the client in a fresh wine prefix with wine-5.5
Can an administrator close this bug as FIXED? --- quote ---
Although the installer claims success it seems questionable. One of the last messages in console (like comment #12):
--- snip --- 0090:err:msi:__wine_msi_call_dll_function Custom action (L"C:\users\focht\Temp\msi1743.tmp":"ManagedInstall") caused a page fault: c0000005 --- snip ---
The client itself doesn't start which could be another indication of a broken/partial installation or a follow-up problem.
I've encountered several bugs in the past where installers claimed success but it was just a lie. So be sceptical of everything. Challenge things - including yourself ;-)
In this case one could approach the problem at different levels.
If a broken/partial installation is suspected, a simple approach would be to compare the content of both WINEPREFIXes (Wine-Mono vs. MS .NET) after installation. It doesn't require much knowledge, except maybe knowing which non-overlapping components of each .NET Framework to exclude from comparison. There could be missing files in app/game client folder and/or missing assemblies in GAC, missing registry entries etc.
A more elaborate approach would be to create WINEDEBUG=+seh,+relay,+msi installer trace logs with Wine-Mono and MS .NET each and check what that failing custom action is trying to do by looking at the succeeding one.
A more advanced level involves the analysis of Wine-Mono trace and decompilation of the installer .NET assemblies involved in the (managed) custom action.
$ sha1sum AADeployClientInstaller.exe 47dfb2e8d5575da3ee5dd5f3ba5b1621de705c8b AADeployClientInstaller.exe
$ du -sh AADeployClientInstaller.exe 9.1M AADeployClientInstaller.exe
$ wine --version wine-5.5-126-g5c0e699dba
Regards