Matrix Games Forums

I believe there was a setting where one could have an automatic autosave after each phase of the player turn.

I am using the latest beta.

This should be automatic. Are you not seeing autosave files in the \Save folder or when you select Load Game?

Thanks for that. No autosave files being generated. I believe this might be an installation issue. I'll get back to you on the specifics.

I see the AI has been stiffened. I have been playing around with alt 1805 as France and had the most difficult time ever with Austria, Prussia and Russia 1805 - 1809. It's great to see.

pzgndr wrote: Sat Jan 20, 2024 1:38 pm This should be automatic. Are you not seeing autosave files in the \Save folder or when you select Load Game?

OK here it goes.

Autosave files are not being generated and no save folder to be found.

I have an ACER Helios 300. Intel i7, Windows 10.

The original installation file, EmpireinArms-SetupRelease-DRv1.exe , will not complete the installation.

It ends up: Error
C:\Windows\Fonts\65659__.TFF
A decompression error has occured (#5)

Could not open output file

Abort Retry Ignore

If I hit Ignore, it messages;

C:\Matrix Games\Empires in Arms\Widowshelp\Windows6 0-KB917607x86 msu

Decompression error

and the Install stalls and then It stops responding.


Then if I hit Cancel, the Installation stops and freezes.

Next I hit Cntl, Alt, Delete to bring up the Task Manager to kill the operation.

I then bring up the EmpiresInArms-SetupRelease-v1.23.08.exe and the install completes to finish and i can start the game.

However the files and folders discussed above are missing.

I can also install EmpiresinArms-UpdateComp-v1.25.03.exe and it completes to finish and can still start the game.

I also can copy the hotfixes over the existing files and did so on: EiANW 12600 Beta[0], and EiANW 12601 Beta[0]

A year or 2 ago I bought EiA for a second time since the First one I bought in 2009 would not recognize my Authorization code, but the second one worked fine.

Now two years later Neither completes the installation routine.

The second one worked fine back then but I believe this could be the cause of installation issue is that I have two distinct authorization codes assigned to my name for EiA causing this a conflict.

Any thoughts or ideas most welcome. You might know who I could speak with about eliminating one of my Authorization codes.

Thanks much Bill. It's good to see you hanging in there with EiA.

P.S.When I do save a game it saves the 'C:\Windows\Documents\Game' folder.

RichWall wrote: Mon Jan 22, 2024 10:07 pm The original installation file, EmpireinArms-SetupRelease-DRv1.exe , will not complete the installation.

When I go to MY PAGE above and check out home/my account/downloads for Empires in Arms, I see [PC] Empires in Arms Setup Installer v1.23.08 EmpiresInArms-SetupRelease-v1.23.08.zip for the Remaster Installer, and then [PC] Update v1.25.03.

I would recommend uninstalling whatever you have, reboot, download and install the v1.23.08 Remaster Installer, then the latest patch, and then the latest beta (or set up separate installations for the official version and beta version). The remaster fixed a LOT of installation issues with the old installer and multiple updates that were required. You probably have some legacy garbage somewhere that's messing things up. Start with that and let me know if that fixes it for you?

Thanks Bill,

That worked, I did not realize the original Installation file, EmpireinArms-SetupRelease-DRv1.exe , is no longer needed and the need to reboot after uninstalling for a clean install.

The autosave function is working.

One last question. Is there still a need to have the EiANW.exe be run as admin, and compatibility set to WinXP service pack 2 ?

Thanks again,

Rich Wall

RichWall wrote: Wed Jan 24, 2024 1:10 am The autosave function is working.
One last question. Is there still a need to have the EiANW.exe be run as admin, and compatibility set to WinXP service pack 2 ?

Good. I recommend running as admin and setting compatibility to WinXP SP2 (consistent with the 2008 compiler). You risk odd behaviors otherwise and I'd rather go bug hunting for any reported issues based on the recommended settings.