I have a bunch of portableapps that I store on a network path so that I don't have to install the same program over on each computer. Most of the programs work fine when accessed via UNC path (\\server\path) but for some reason KVIrc freaks out, tries to load some config from c: and when it can't it is completely unusable. I have to map a network drive and then start KVIrc from the network drive (i.e. x:\portableapps\KVircPortable\kvircportable.exe), at which point it functions perfectly fine.
Why is this, and what can be done to fix it?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
It's likely not supported by the app itself. Many apps either can't run from a UNC path or can't read/write their settings files on a UNC path. We usually lock these out with a setting in the launcher that just shows an error to the user and immediately closes. But we haven't caught every app with the issue and some apps change to either support it or not support it with different releases over the years.
Sometimes, the impossible can become possible, if you're awesome!
You were right. As an experiment I downloaded the non-portable version and installed it to a UNC path. The install SEEMED to go fine, but when I launch it I get the same errors. So is there nothing that can be done to fix this? I can run on a drive letter if I must, but I'd rather not.
You'd need to ask the publisher to add support for it.
Sometimes, the impossible can become possible, if you're awesome!