Open Dobby233Liu opened 1 year ago
To reproduce this issue:
Then observe that in games.js, the paths to the game executables in your network folder are written in the form of //host/path, e.g.:
games.js
//host/path
{ "th08": "//vmware-host/Shared Folders/beast/Touhou 8 - Imperishable Night/vpatch.exe", "th08_custom": "//vmware-host/Shared Folders/beast/Touhou 8 - Imperishable Night/custom.exe" }
But the host part in the paths should really be written in the form of \\host, and without editing games.js to something like the below:
\\host
{ "th08": "\\\\vmware-host/Shared Folders/beast/Touhou 8 - Imperishable Night/vpatch.exe", "th08_custom": "\\\\vmware-host/Shared Folders/beast/Touhou 8 - Imperishable Night/custom.exe" }
thcrap_loader will fail to start the executables with bad paths, with the following error:
Failed to start <thcrap path>\<executable path> The system cannot find the path specified.
A possible fix would be to add a special case in str_slash_normalize ensuring that network paths start with \\ instead of //
As a temporary workaround you can map the network drive to give it a drive letter.
To reproduce this issue:
Then observe that in
games.js
, the paths to the game executables in your network folder are written in the form of//host/path
, e.g.:But the host part in the paths should really be written in the form of
\\host
, and without editinggames.js
to something like the below:thcrap_loader will fail to start the executables with bad paths, with the following error:![image](https://user-images.githubusercontent.com/28653235/235288770-651c578c-e459-48b8-9edb-03e190fb83b9.png)