![]() I could add an "auto-add-to/remove-from-firewall" INI option (off by default) which handles the drive letter and cleans up. but this would break with a drive letter change (and would be major hassle!). ![]() I'm not sure how much of a problem requiring admin is here, especially with the firewall, which needs admin? OK, so you could log in as admin, add Soulseek to the fiewall, log out, log in as user etc. I can add an admin check that closes the app rather than messing up the configuration by trying (and failing) to move things but launching anyway. I haven't tested this though as I am yet to be able to download a file! I presume this is because I'm still a Soulseek 'n00b' (!) rather than any fault of the app Always stuck in the queue. No crashes though!)Įven using the config files, the recent file list is still in the registry but I can wipe it before launch if the drive letter has changed (better to lose it than for it to point to files that aren't there anymore?). I can replace all drive letters in these files so it's all PAF compatible but no path replacement is possible (similar problem to EAC, the files look good but Soulseek won't recognise them and they are corrupt on exit. Unfortunately, these are stored in "AllUsers\AppData" so admin would be required as I can't see any way to redirect them. Soulseek makes it possible to disable writing the configuration to the registry and use (binary) config files instead. I can convert each *path* to hex and put it straight into the registry no problem but Soulseek won't recognise it without further formatting which I can't figure out. Even if I could do that, I will run into the next hurdle. Maybe I could read from reg, convert to string, write to ini, replace in file, read from ini, convert to hex, write to reg, I don't know (you get the idea!). All the paths in the registry are in hex so updating *drives* will be difficult/impossible.
0 Comments
Leave a Reply. |