SiS Updater and Installer

[zakblood]

today and on last test run

2.jpg (444.23 KiB) Viewed 201738 times

[Chasm]

Updater has been giving me a final line of :

updater\start.lua862: server error: want read

before failing.

I have also had in game bug reports be unable to be filed (playing on old version)

[zakblood]

updater modtime: 2016-12-14 03:55:52.395
running on 2016-12-27 16:43:20.189
loading update options:, ok, nil, true
connecting to update.stars-in-shadow.com:80
did handshake
connection established
gathering file data, 2016-12-27 16:43:50.611
fetching file info for, D:/Stars in Shadow
file fetch done..
file info reformat done..
data gather complete, 2016-12-27 16:43:51.533

[zakblood]

seems i maybe on a different version, so maybe wrong to compare it seems

as if i try again,

updater modtime: 2016-12-14 03:55:52.395
running on 2016-12-27 16:43:20.189
loading update options:, ok, nil, true
connecting to update.stars-in-shadow.com:80
did handshake
connection established
gathering file data, 2016-12-27 16:43:50.611
fetching file info for, D:/Stars in Shadow
file fetch done..
file info reformat done..
data gather complete, 2016-12-27 16:43:51.533
version send failed:, updater\start.lua:862: server error:
wantread
lets try another port...
connecting to update.stars-in-shadow.com:4669
did handshake

but no information to download, so seems i'm either on the latest version, or sites down

[Arioch]

The update server is in some state of deadness. Sven is looking at it.

[sven]

The update server is in some state of deadness. Sven is looking at it.

upgraded and restarted the server. i may have underestimated the amount of load we'd have, now that the server is seeing fairly heavy use from steam-user bug reports.

[bjg]

It should be easy for the updater to "remember" which program called it, and if it was sis64 - start it instead of sis. Is there a reason not to implement it?

[Arioch]

It should be easy for the updater to "remember" which program called it, and if it was sis64 - start it instead of sis. Is there a reason not to implement it?

It's a tool that only used by us, the developers and testers. It's slightly irritating to me as well, but it's really not any significant effort to click on a shortcut instead of the "play" button; I'd prefer that Sven not waste any time on it.

[sven]

It should be easy for the updater to "remember" which program called it, and if it was sis64 - start it instead of sis. Is there a reason not to implement it?

It's a tool that only used by us, the developers and testers. It's slightly irritating to me as well, but it's really not any significant effort to click on a shortcut instead of the "play" button; I'd prefer that Sven not waste any time on it.

That said, I do really appreciate all the help we get from our private-server test group. There's a 5-minute patch I can think of that might address the issue. Rather than attempting to remember which exe triggered the update, I can just add a tiny bit of logic so that the version of the exe that gets called is determined by the bit preference of the OS. I.e., on 64 bit OSs, the updater will *always* execute sis64.exe. That's actually exactly the way Steam handles things, so it's a change that actually puts the private test systems slightly more in line with the Steam distro. (Also, in theory, this new behavior should be in the updater code now -- but it will take a few updates before you'll start to notice it.)

[zakblood]

thanks, while not needed, it would help when i forget which one i've updated then played / tested, not that either make much difference even on the largest maps to me 32/or 64bit

[bjg]

The current is still can't be ran on (my) XP. I understand that this is the toll for testers only, but you officially support XP, and the older versions of the update.exe do run on it (so it's not something crucial).

[sven]

The current is still can't be ran on (my) XP. I understand that this is the toll for testers only, but you officially support XP, and the older versions of the update.exe do run on it (so it's not something crucial).

I just did a little fiddling with the build for update.exe; I think it may now once again be XP compatible (but I don't have a test machine of my own around to test it atm.) If you re-download your installer using your download link, you should get a copy of the Feb 15th build. If you have a moment, I'd be curious to know whether or not it's working.

[bjg]

I just did a little fiddling with the build for update.exe; I think it may now once again be XP compatible (but I don't have a test machine of my own around to test it atm.) If you re-download your installer using your download link, you should get a copy of the Feb 15th build. If you have a moment, I'd be curious to know whether or not it's working.

I've copied the today's update.exe from an another computer instead. Seems to work fine. Thank you.

[bjg]

The "user files mod detected" dialog keeps popping up every update (I click "yes" every time) on the XP. Not a big deal, but something is not quite right.

[bjg]

It seems like the update server doesn't scale well, not being able to provide updates way too often. If you use the same server to receive game uploads you might consider splitting them.