Issues with Latest Build
Moderator: Oberlus
Forum rules
Always mention the exact version of FreeOrion you are testing.
When reporting an issue regarding the AI, if possible provide the relevant AI log file and a save game file that demonstrates the issue.
Always mention the exact version of FreeOrion you are testing.
When reporting an issue regarding the AI, if possible provide the relevant AI log file and a save game file that demonstrates the issue.
Issues with Latest Build
I've been playing with the test builds lately. I have a windows 8 system on a Toshiba laptop. Build 2017-01-23.d3d9204 has issues with the uninstaller running after the game is installed uninstalling the new game. I've tried modding and had to re-install a few times and noticed this issue. Last night the game crashed my laptop.
Last edited by labgnome on Mon Jan 30, 2017 6:17 pm, edited 1 time in total.
All of my contributions should be considered released under creative commons attribution share-alike license, CC-BY-SA 3.0 for use in, by and with the Free Orion project.
- Geoff the Medio
- Programming, Design, Admin
- Posts: 13603
- Joined: Wed Oct 08, 2003 1:33 am
- Location: Munich
Re: Issues with Late4st Build
This is useless without details of when it happens/happened, steps to reproduce, or saves, log files, etc.labgnome wrote:Last night the game crashed my laptop.
Re: Issues with Latest Build
Here is what I can manage here. It keeps telling me everything else is too big.
- Attachments
-
- config.xml
- here is the config file.
- (25.81 KiB) Downloaded 140 times
All of my contributions should be considered released under creative commons attribution share-alike license, CC-BY-SA 3.0 for use in, by and with the Free Orion project.
- Geoff the Medio
- Programming, Design, Admin
- Posts: 13603
- Joined: Wed Oct 08, 2003 1:33 am
- Location: Munich
Re: Issues with Latest Build
config.xml alone is not helpful. Try zipping the logs, or posting them at pastebin or a similar site. Or link to a dropbox document. Or cut out part of the log (the start probably) so just the end is left. Or describe in a post what you did to get a crash.
-
- Programmer
- Posts: 389
- Joined: Sun Feb 14, 2016 12:08 am
Re: Issues with Latest Build
Please clarify this, it almost sounds like the uninstaller starts up and completes on its own.issues with the uninstaller running after the game is installed
If that is not the case, knowing the issues you have with the windows installer/uninstaller would be very helpful.
Any content posted should be considered licensed GNU GPL 2.0 and/or CC-BY-SA 3.0 as appropriate.
Re: Issues with Latest Build
I'll try to give more details. Full disclosure: this is also an "I should have payed closer attention" kind of thing.dbenage-cx wrote:Please clarify this, it almost sounds like the uninstaller starts up and completes on its own.issues with the uninstaller running after the game is installed
If that is not the case, knowing the issues you have with the windows installer/uninstaller would be very helpful.
Here is the sequence of events:
- I try to install the file
- It recommends I uninstall previous versions & I click "yes"
- The uninstall program begins
- The installation program window pops up & I start installation
- Installation completes.
- Uninstall completes, uninstalling the new build I had just tried to install.
All of my contributions should be considered released under creative commons attribution share-alike license, CC-BY-SA 3.0 for use in, by and with the Free Orion project.
Re: Issues with Latest Build
Um, you must not start the installation (step 4) before the uninstall process has completed. Otherwise you might end up with a botched installation. So, when installing a new version: start the installer; when it detects an old version and asks if you want to uninstall that old version click "Yes", then wait until the uninstall process has completed. Only then continue with the installation of the new version.labgnome wrote:Here is the sequence of events:
- I try to install the file
- It recommends I uninstall previous versions & I click "yes"
- The uninstall program begins
- The installation program window pops up & I start installation
- Installation completes.
- Uninstall completes, uninstalling the new build I had just tried to install.
I don't understand, what happened while you had a game up and running? I assume you didn't try to do an install/uninstall with the game up and running, did you...?This even happened one time while I had the game up and running
Re: Issues with Latest Build
I've just never had it prompt me/pop-up to install the new version before the uninstall was complete before. It wasn't something I had to look out for until now. So I thought the issues might be connected.Vezzra wrote:Um, you must not start the installation (step 4) before the uninstall process has completed. Otherwise you might end up with a botched installation. So, when installing a new version: start the installer; when it detects an old version and asks if you want to uninstall that old version click "Yes", then wait until the uninstall process has completed. Only then continue with the installation of the new version.
uninstalling the game. The uninstall completed while the game was running.Vezzra wrote:I don't understand, what happened while you had a game up and running? I assume you didn't try to do an install/uninstall with the game up and running, did you...?This even happened one time while I had the game up and running
All of my contributions should be considered released under creative commons attribution share-alike license, CC-BY-SA 3.0 for use in, by and with the Free Orion project.
Re: Issues with Latest Build
Oh... ok, that means, you started the install, then confirmed the message box that asked if you wanted to uninstall the previous version, continued with the installation, which completed, then started a game, and the uninstall completed only after you had already been playing for a while...?labgnome wrote:The uninstall completed while the game was running.
- adrian_broher
- Programmer
- Posts: 1156
- Joined: Fri Mar 01, 2013 9:52 am
- Location: Germany
Re: Issues with Latest Build
It is certainly not optimal to run both branches (uninstaller + installer) at the same time. We should prevent this by blocking the installer until the uninstaller is finished.
http://nsis.sourceforge.net/When_I_use_ ... ninstaller
Should help here.
http://nsis.sourceforge.net/When_I_use_ ... ninstaller
Should help here.
Resident code gremlin
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz
Attached patches are released under GPL 2.0 or later.
Git author: Marcel Metz
Re: Issues with Latest Build
Yep, definitely agree.
-
- Programmer
- Posts: 389
- Joined: Sun Feb 14, 2016 12:08 am
Re: Issues with Latest Build
Thanks to https://nsis-dev.github.io/NSIS-Forums/ ... 79035.html this works:
Anyone know a way to separate the filename from a registry string($R0) in this context?
Using the filename from registry would help in case of later changes (e.g. using a batch file)
Code: Select all
uninst_onInit:
ClearErrors
InitPluginsDir
CopyFiles "$R0" "$pluginsdir"
ExecWait '$pluginsdir\Uninstall.exe _?=$pluginsdir'
fin_onInit:
Using the filename from registry would help in case of later changes (e.g. using a batch file)
Any content posted should be considered licensed GNU GPL 2.0 and/or CC-BY-SA 3.0 as appropriate.
Re: Issues with Latest Build
That does not work at all... when I change the NSIS installer script as suggested here, the installer indeed paused until the uninstaller completes, however, apparently other than removing the uninstaller registry key the uninstaller doesn't do anything, it exits practically immediately, and the FO installation remains apparently untouched.dbenage-cx wrote:Code: Select all
uninst_onInit: ClearErrors InitPluginsDir CopyFiles "$R0" "$pluginsdir" ExecWait '$pluginsdir\Uninstall.exe _?=$pluginsdir' fin_onInit:
The solution suggestion Marcel linked to works far better, but still not entirely satisfactorily. The old FO installation is almost completely removed - the FreeOrion folder itself in the Windows programs directory and the uninstall.exe within don't get deleted. Which shouldn't be a big issue since usually the new installation should overwrite these leftovers immediately afterwards, but still, it's not perfect (e.g. when a user decides put the new installation into a different location).
So I put up a PR with a fix that more or less follows that solution with request for reviews/opinions/objections:
https://github.com/freeorion/freeorion/pull/1299
-
- Programmer
- Posts: 389
- Joined: Sun Feb 14, 2016 12:08 am
Re: Issues with Latest Build
Doh :/
"_?=" Is an argument to the uninstaller and should be the installation directory, not $pluginsdir.
The issue with this approach is separating the filename from the directory name, as the previous versions stored the one value.
"_?=" Is an argument to the uninstaller and should be the installation directory, not $pluginsdir.
The issue with this approach is separating the filename from the directory name, as the previous versions stored the one value.
Re: Issues with Latest Build
As the filename of the uninstaller executable hasn't been changed since the dawn of time, I consider this issue a very minor one. Certainly less serious than the problem with the installer continuing before the uninstaller completes.dbenage-cx wrote:The issue with this approach is separating the filename from the directory name, as the previous versions stored the one value.
So I updated my PR with the approach you suggested here, rebased and merged it. Once someone comes up with a proper solution for separating filename from directory name, we can commit that fix then.
@labgnome, things should work smoothly for you now.