But it's also the case that it sometimes takes a few tries to find one that works for one firewall, without confidence that it will work for another. Since it is a firewall's job to block things like that, the folks who run firewalls prefer that firewalls not be too easy to bypass. That's the sort of detective work that's needed. directory at the beginning of the PATH, so it would find it right away. But of course, that discovery suggested appending the. The fact that the file was right there in the same folder as the executable made that exercise seem bizarre. I saw a program going through a list of different folders that way, and it only took a few moments to realize it was looking at each folder on the PATH in turn. Sometimes ProcessMonitor from Sysinternals can give you a clue. So try different things and see what you come up with. HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell FoldersĪnd ignores the environment variable completely - which would make things harder, but not impossible. The USERPROFILE would be a more likely place to look than ALLUSERSPROFILE, but it's possible. Unless you poke around inside the source code, the only way to tell for sure where it is looking to find APPDATA is experiment. (LIMEWIRE_PREFS_DIR vs FROSTWIRE_PREFS_DIR) The launcher now sets up both (the program only notices the one it is looking for) in case a future version reverts to using the Frostwire name for the variable.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |