You are here

qBittorrentPortable suddenly claims qBittorrentPortable.ini is missing [Launch]:ProgramExecutable

6 posts / 0 new
Last post
hamptito
Offline
Last seen: 2 years 10 months ago
Joined: 2010-09-09 07:25
qBittorrentPortable suddenly claims qBittorrentPortable.ini is missing [Launch]:ProgramExecutable

The file is there (if I copy the path from the error message it is opened up) and the Launch section exists as well as its ProgramExecutable value. So I don't understand where the error comes from?!

Thanks.

hamptito
Offline
Last seen: 2 years 10 months ago
Joined: 2010-09-09 07:25
Ok problem solved.

Ok problem solved. Systemdrive C was full and the error message was simply nonsense. Your chance to improve error message Smile

John T. Haller
John T. Haller's picture
Offline
Last seen: 13 hours 41 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Windows reported

That error will show if Windows says the file isn't there. Odd stuff like that can happen with drive errors.

Sometimes, the impossible can become possible, if you're awesome!

hamptito
Offline
Last seen: 2 years 10 months ago
Joined: 2010-09-09 07:25
Why should Windows say the

Why should Windows say the file is not there? I assume it is copied to C for some reason and this copy operation fails and Instead of write error either Windows or your tool misinterprets this as a read error.

John T. Haller
John T. Haller's picture
Offline
Last seen: 13 hours 41 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
TEMP

The TEMP directory is used by NSIS for runtime components. NSIS is the language our launcher is written in. If TEMP is on C and C is wonky, all kinds of stuff will go a bit nuts, regardless of what drive it's running from.

Sometimes, the impossible can become possible, if you're awesome!

hamptito
Offline
Last seen: 2 years 10 months ago
Joined: 2010-09-09 07:25
Its not only that. I also

Its not only that. I also noticed that this App copies/creates config data in %appdata%, which is (on that system and by default) on C as well.

anyway, "cannot write to C:\something" should not result in "cannot find D:\something-else" error messages.

Log in or register to post comments