Repository navigation
Relative Paths #6
Description
I use a NAS for all of my storage. I find that the updater always errors out because it doesnt like creating paths on the shares. This wouldnt be a problem if the paths were able to be relative to the executable, versus hard coded paths as my solution has been to copy it down to my non-network local drive, and perform the updates (there it works). Problem with that is that I have to go in and change the entire setup each time, to make it point to a not relative path (something more like ".\installed", etc...
Activity
TechnicallyComputers commentedon Sep 9, 2026
I'll look into this at some point soon.
TechnicallyComputers commentedon Sep 18, 2026
In the latest version this should be better supported (it technically was already) and there should be notation about it in Library Settings. Please confirm this works for your use case
trumpetlicks commentedon Sep 19, 2026
I would say that it is partially fixed, as it is still referenceing a RETCOMM_HOME data folder which shows a full path. I think that to fully make it relative, it should be relative to the current executable (RetComM Launcher.exe) path.