It's not really clear to me what that return code 256 is coming from, the installer, Wine, or Lutris?

See if you can run the installer manually. If it works, Lutris have a problem with NFS, if not, it's a Wine problem.

Running something like this from the terminal might work:

WINEPREFIX="/home/xxx/Diskstation/SteamLibrary/Lutris/gog/torchlight" /home/xxx/.local/share/lutris/runners/wine/lutris-7.2-2-x86_64/bin/wine /home/xxx/Diskstation/SteamLibrary/Lutris/Cache/torchlight/gog/setup_torchlight_1.15(a)_(23675).exe

Lutris also turn off all Wine messages:
 DEBUG    2023-02-08 17:44:54,251 [command.start:141]:WINEDEBUG="-all"
Kind of idiotic not to enable it if you're running Lutris in debug mode.... anyhow, sounds like you can "enable debugging output in the global wine runner settings".

It should hopefully get you useful logs.

I don't see anything that jumps out at me that makes me think it's related to the NFS mount. I would think that neither Lutris nor Wine should know anything about that if it's mounted correctly (and you have correct ownership/permissions of the directories on the synology station).

A lot of those Lutris game install scripts are b0rken. Search their forums for "return code 256" and it's always some poor soul trying to install something through the Lutris game install scripts.

Yes, try installing it "manually". You can manually create a Wine prefix for it with Lutris. Click the + sign and choose "Locally installed game" and fill out the fields. Leave the game executable out until after you've run the GoG installer archives. Install using "Run Exe in Wine Prefix"

The only errors I see in the log are "unable to load libGLX_nvidia.so" Sorry, I can't copy and paste it using my phone (touchscreen is not in great shape).
Although I'm not sure why that would cause the problem you're experiencing.

That's a weird one. I'd go with the others suggestion and try the manual install. That way if there's a failure, it might be more immediate and apparent.

For gog games i never bother with the installer, just use innoextract. Faster and more convenient than clicking through the installer.

Quoting: whizseIt's not really clear to me what that return code 256 is coming from, the installer, Wine, or Lutris?

See if you can run the installer manually. If it works, Lutris have a problem with NFS, if not, it's a Wine problem.

Running something like this from the terminal might work:

WINEPREFIX="/home/xxx/Diskstation/SteamLibrary/Lutris/gog/torchlight" /home/xxx/.local/share/lutris/runners/wine/lutris-7.2-2-x86_64/bin/wine /home/xxx/Diskstation/SteamLibrary/Lutris/Cache/torchlight/gog/setup_torchlight_1.15(a)_(23675).exe

Thank you Whizse

needed some quotes around the exe path but that worked and I got a pop-up that mono needed to be installed, so did that and the installer opened up, so I figured maybe the mono pop-up is the reason, cancelled the install and did it with Lutris (did not delete the install directory as mono is installed in there now !), and got the same error, so nope not mono pop-up related.

Took Grogan's advice and finished the manual install with the above line and then used the locate game, that works.

I tend to agree with Grogan that Wine and Lutris should not see it's NFS, but the fact remains Lutris has no issue if I do the install locally so not on the NFS. It's not a rights issue else the manual install would fail too.

so yes seems to be Lutris related

well I got a pretty easy workaround so thanks :)
and will look into dvd's suggestion of the inoextract.

thank you for the help and pointing me in the right direction

Not directly related to it being on a NFS mount, but possibly latency/packets needing retransmission. In other words possibly inducing a fault that the front ends can't handle. The result is that it got short or bad data or the chicken came before the egg etc. I don't know how you're configured, but NFS can use TCP/IP or UDP/IP (depending on version and configuration).