![]() I could use command-line parameter, but I would also have to modify that as well.īy supporting empty portable.dat file in bvckup2.exe folder, and placing both app and service config data folders in same folder, I can keep it on a separate partition, and move the bvckup folder around to my liking, without ever having to worry about specifying where the config folders are/go - it just works, as they are always in the same folder as bvckup2.exe. That is, if the source location is C:Source and the file is C:Sourceabcxyzfile.ext then the app will only be matching abcxyzfile.ext to the pattern. By default, only relative path from the configured location to the file is used for comparison. ![]() Long paths All file system operations are carried out using long path notation, which supports paths of up to 32,767 characters in length. For this pattern to match a file, each part needs to match a part of the file path. This makes for a little miracle when scanning ultra fast local drives and remote shares over slow networks. If I want the config data elsewhere, I have to modify both of these again. When building a list of files at a location, the program processes multiple folders at once. I understand the redirect.ini option, service config registry option, and command line option for specifying different config folder, and that it might be considered "messy" to have config data and exe together, but the problem with the existing solution's, is that a Bvckup folder, with all corresponding config data, cannot be moved around as easily.įor example, suppose I re-install Windows, I have to re-copy over the redirect.ini file, and change the service config registry value again. If found, it will automatically place config folder in same folder as bvckup2.exe. ![]() Kudos to Aram for not only managing to trigger this issue, but also for noticing and reporting it.ĭownload: Bvckup 2 Release 80.8 | 2.4 MB (Free trial, $19.Apr 24, 2023+1 for portable idea - I would also like to see Bvckup2.exe look for an empty file, like portable.dat, in same folder as itself. So the rename went through, but the update didn't, the file ended up looking like is was still in sync with the original.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |