27. December 2022, 23:31:09

#0

apaaQuote

Hi all,

I'm looking to play System Shock 2 for the first time, and I've run into an issue with SS2Tool 6.1.1.8. It's like the installation doesn't complete properly, but there are no error messages at the end of the install.

I'm on Manjaro Linux XFCE. Installed the GOG version of SS2 through Lutris. The game installs and runs without issues. I went through the 3 tutorials and stopped at the role selection crossroads, because I've read that after installing mods I'll need to start a new game.

I then follow the instructions at the "File Archives » SS2 General » SS2Tool v6.1" thread: I download the tool, place it in the same folder as ss2.exe, and use Lutris' option to 'Run exe inside Wine prefix'.

The tool says "The local game content version is unknown. An update is recommended."
It only offers the Perfect Mode option which is fine by me. I leave every component on default and start the install.

Apparently it backs up ss2.exe (along with a few other files) but doesn't replace it with anything, so the game is not startable, even with the shortcuts the Tool places on the Desktop of the Wine prefix.
The log shows rsync errors, even if I turn off the firewall on my system; however, it's able to download ss2bmm.exe and a few other files. The rsync errors show up in a few places in the log but are always the same:
rsync: writefd_unbuffered failed to write 8 bytes to message fd [receiver]: The descriptor is a file, not a socket (108)
rsync error: error in rsync protocol data stream (code 12) at /usr/src/rsync/rsync-3.0.8/io.c(1530) [receiver=3.0.8]
rsync: connection unexpectedly closed (43 bytes received so far) [generator]
rsync error: error in rsync protocol data stream (code 12) at /usr/src/rsync/rsync-3.0.8/io.c(601) [generator=3.0.8]
When I start ss2bmm.exe, and click the "Select game folder" button, the OK button is not active, probably because of the missing ss2.exe file.

I have deleted and reinstalled everything from scratch at least 6 times, to no avail (yes I know the definition of insanity)

I'm sure you guys have seen this a million times. Would someone please offer some advice?

I'm happy to provide any other info you may need.

Thanks!

28. December 2022, 14:49:17

#1

sarge945Quote

This is actually a known issue.

I have a workaround for it in the form of a shell script which I use on my Linux machines, however after talking with Kolya about it, I am not allowed to post it here as it potentially gives access to copyrighted game data by bypassing some of the checks in the original ss2tool, which is technically illegal and I don't want to rock the boat.

I have been meaning to actually properly host both the script and the game data, to fix the Linux install issues, but I haven't gotten around to it. That would move the liability to me rather than this forum, which I am prepared to accept.

I am about to do a MAJOR interstate move, but should be free to do this in the coming weeks. So this should be resolvable. For now, you can run Windows inside QEMU and install it there, then copy the files over (I know that's not a good solution but it will work).

Please PM me if I forget about this at the end of January. If you really can't wait to play until then, and don't have access to a Windows machine, you can use the native rsync binary to do it but I can't tell you the server address/password or how to circumvent other checks, you're on your own. The only clue I can give is that you will need a hex editor.

18. January 2023, 19:04:03

#2

daemonspudguyQuote

I ended up installing the Windows version of Shock 2 in Proton, copying my game folder to a virtual machine running Windows Vista, and running SS2Tool on that. It was annoying, but I couldn't find any other way to get rsync to work because finding the login details for the SS2 rsync server is beyond my abilities.

21. January 2023, 02:24:03

#3

sarge945Quote

I have got SS2 set up on my server, and it can auto-run ss2tool every week or so to stay up to date with the main version. The issue currently is I can't rsync to my desktop from my server, and I can't for the life of me figure out why. I just get random socket errors and such.

I am not a sysadmin, and the rsync daemon seems like dark magic to me.

If someone wants to help me with this, I can have a proper Linux script set up to replace ss2tool ready to go so we don't need any more Windows shenanigans.

I wish Kolya was still around, I assume he set up the ss2tool stuff in the first place.

21. January 2023, 09:01:47

#4

voodoo47Quote

he did, and it's not like he is gone completely, just say @Kolya and he probably will notice in a couple of days.

Acknowledged by: sarge945