Thanks for the response - funnily enough I'd just worked it out myself ...

The reason the updater dies is for some reason the current GOG unins000.exe gets a runtime error under wine (Fedora 20 64bit with wine straight from the fedora standard repos) and the updater calls the uninstaller?

The following bash script patched from 1.000 to 1.004 - looking forward to playing tonight (especially after my disastrous first game on my commute this morning)!

cd "${HOME}/.wine/drive_c/GOG Games/The Last Federation"
for i in {1..4}
do
wget -O RuntimeData/updates/100${i}.zip [url=http://lastfed.s3.amazonaws.com/TLF_100${i}.zip]http://lastfed.s3.amazonaws.com/TLF_100${i}.zip[/url]
unzip -o RuntimeData/updates/100${i}.zip
rm -f RuntimeData/updates/100${i}.zip
done
mv DB/Managed/Assembly-CSharp.dll LastFederation_Data/Managed/

Standalone installer for major patchs (for example: from 1.0 to 1.3) will be nice. But for minor patches (1.00001.a - 1.00001.a-1)? I'm don't see any purpose for this.

Haha, well, I guess that's how it goes sometimes :) Glad to hear it worked.

And yea, there was that DB-folder wrinkle that's new to the updating process for this game and that I'd forgotten when posting above. Basically that just holds stuff that needs to be copied to different places depending on the platform (Windows/Mac/Linux). That way we don't have to include 3 separate copies of that dll (which holds practically all the actual game code), etc.

That makes sense ... think I'll make it a little more generic for linux users on wine at gog (ie parse the updates text file to see what needs to be downloaded) ...

At least until GOG have linux releases later on this year ;)

Incidentally I'm curious - why is the updater calling the uninstaller ?

let's say I move to another computer. Can I just grab all of the installed files and slap them onto the new machine, therefore eliminating the need to update from 1.00 all over again?

Yes ,that would work.

Yeah it seemed weird - I haven't tried it on an actual windows desktop yet to see the behaviour...

It was definitely invoking it though as I was stepping through the code with winedbg to see where it was triggering - my plan Z was to use winedbg to set a break and step over that call if I hadn't worked out how to do the manual update ;)

I'd appreciate that - no hurry though :)

Do we have an update on why the updater is calling the uninstaller?

I just asked Chris and he said that our updater was basically replaced by another file for GOG's install, so we don't really know what's going on in there. He said he'll ask GOG about it again.

Alright, thanks for your reply!

Apparently it was GOG induced.