Just some thoughts about latest improvements...
1. In a long MD5 file list, it is impossible now to select information about changed files only.
Suggestion: adding somewhat like "show changed" button.
Better suggestion - to add an appropriate checkbox to the "save list" dialog, somewhat like "include changed only".
2. Pressing Start button (Enter) after verification invokes new check - why?
Taking into consideration that, after file list is shown in a window, it cannot be changed, I think Start button must be blocked upon verification performed.
Or maybe its function must be changed, e.g. to show checksum for file under cursor.
3. Is there any way to return to the full list after Find performed in "as filter" mode? ESC preferred
Otherwise one must scan again and again to make a full list available...
4. Screen is not refreshed upon MD5 file creation - must refresh it manually.
Not convenient at all
5. About Backup.
Seems that added files are not operated
Suggestion: if there is MD5 file created for some directory (or a group of dirs), then all new files at (-1) level must be taken (inside the upper directory/directories).
A "whole disk" MD5 file should be an exclusion, in which case _all_ added files must be added to backup!
Just some thoughts about latest improvements...
1. In a long MD5 file list, it is impossible now to select information about changed files only.
Suggestion: adding somewhat like "show changed" button.
Better suggestion - to add an appropriate checkbox to the "save list" dialog, somewhat like "include changed only".
Hm, Leo! I thought you know V+ better than me :¬)
Why don't you use Find button and just filter "Changed" or anything else
Than you can save that filtered list or even re-verify it again.
Quote:
2. Pressing Start button (Enter) after verification invokes new check - why?
Taking into consideration that, after file list is shown in a window, it cannot be changed, I think Start button must be blocked upon verification performed.
Or maybe its function must be changed, e.g. to show checksum for file under cursor.
It could do whatever you'd like
Maybe showing file's checsum is not a bad idea!
Quote:
3. Is there any way to return to the full list after Find performed in "as filter" mode? ESC preferred
Otherwise one must scan again and again to make a full list available...
Hm! Could be done, but requires additional procs. Also, Esc couldn't be used for restoring list! Let me see!
Quote:
4. Screen is not refreshed upon MD5 file creation - must refresh it manually.
Not convenient at all
Already fixed in current Beta
Quote:
5. About Backup.
Seems that added files are not operated
Suggestion: if there is MD5 file created for some directory (or a group of dirs), then all new files at (-1) level must be taken (inside the upper directory/directories).
A "whole disk" MD5 file should be an exclusion, in which case _all_ added files must be added to backup!
Could you explain this a bit more?
The idea (and realisation) is that only changed files are backuped!
Hm, Leo! I thought you know V+ better than me :¬)
Why don't you use Find button and just filter "Changed" or anything else
Than you can save that filtered list or even re-verify it again.
I know this and have tried it already.
A Find button is general and lets to filter anything using custom criteria.
On the other hand, "Changed" files is a special case.
They can be filtered like any other files of course, but I think that having a special button to save changes only should be definitely more convenient.
Quote:
5. About Backup.
Seems that added files are not operated
Suggestion: if there is MD5 file created for some directory (or a group of dirs), then all new files at (-1) level must be taken (inside the upper directory/directories).
A "whole disk" MD5 file should be an exclusion, in which case _all_ added files must be added to backup!
Could you explain this a bit more?
The idea (and realisation) is that only changed files are backuped!
It is simple: {backup} = {changed files} + {added files} - {deleted files}
But there is a problem - files added/deleted on the (upper) level for which MD5 file had been created should not be processed.
E.g., if we have MD5 for System, all new files within System must be added to backup directory, as well as files deleted from System must dissapear from Backup directory correspondingly.
At the same time any file changes outside System directory should be ignored and must not be reflected to Backup directory.
The other problem is that MD5 file must be refreshed upon backup, otherwise there will be a mess with all next backups!
In other words, if MD5 check discovered some changes, for which a backup been performed, those changes must be reflected in MD5 file immediately.
To provide valid information for future backup
A Find button is general and lets to filter anything using custom criteria.
On the other hand, "Changed" files is a special case.
They can be filtered like any other files of course, but I think that having a special button to save changes only should be definitely more convenient.
The idea was to use V+ general feature services (Find etc...) as much as possible, and so avoid adding a lot of new procedures! Economy
Quote:
5. About Backup.
Seems that added files are not operated
Suggestion: if there is MD5 file created for some directory (or a group of dirs), then all new files at (-1) level must be taken (inside the upper directory/directories).
A "whole disk" MD5 file should be an exclusion, in which case _all_ added files must be added to backup!
It is simple: {backup} = {changed files} + {added files} - {deleted files}
But there is a problem - files added/deleted on the (upper) level for which MD5 file had been created should not be processed.
E.g., if we have MD5 for System, all new files within System must be added to backup directory, as well as files deleted from System must dissapear from Backup directory correspondingly.
At the same time any file changes outside System directory should be ignored and must not be reflected to Backup directory.
Leo, seems that you are leading me, by little steps, to write new Backup app! Hm! What Chris would say on that
I just meant to provide updating Backup with changed files! And probably deleting files from Backup that not exist any more. More than that would really bring me to creating Backup+
Would be more natural, definitely, that MD5 checsum verifying is included in a standard Backup application!!!
Quote:
The other problem is that MD5 file must be refreshed upon backup, otherwise there will be a mess with all next backups!
In other words, if MD5 check discovered some changes, for which a backup been performed, those changes must be reflected in MD5 file immediately.
To provide valid information for future backup
A Find button is general and lets to filter anything using custom criteria.
On the other hand, "Changed" files is a special case.
They can be filtered like any other files of course, but I think that having a special button to save changes only should be definitely more convenient.
The idea was to use V+ general feature services (Find etc...) as much as possible, and so avoid adding a lot of new procedures! Economy
Well, let's open cards: I'm speaking of generating a list of changed files automatically
Quote:
5. About Backup.
Seems that added files are not operated
Suggestion: if there is MD5 file created for some directory (or a group of dirs), then all new files at (-1) level must be taken (inside the upper directory/directories).
A "whole disk" MD5 file should be an exclusion, in which case _all_ added files must be added to backup!
It is simple: {backup} = {changed files} + {added files} - {deleted files}
But there is a problem - files added/deleted on the (upper) level for which MD5 file had been created should not be processed.
E.g., if we have MD5 for System, all new files within System must be added to backup directory, as well as files deleted from System must dissapear from Backup directory correspondingly.
At the same time any file changes outside System directory should be ignored and must not be reflected to Backup directory.
Leo, seems that you are leading me, by little steps, to write new Backup app! Hm! What Chris would say on that
I just meant to provide updating Backup with changed files! And probably deleting files from Backup that not exist any more. More than that would really bring me to creating Backup+
Would be more natural, definitely, that MD5 checsum verifying is included in a standard Backup application!!!
1. I think Chris would be astonished if you devour his new program
Maybe he'd even ask why are you remaining so hungry after consuming all other programs? You are really fleshed in blood
2. If you tend to delete files which does not exist any more, so you must to offset a loss
3. A week ago I've thought that we do not need a new backup program at all (remember my mail about Fast Backup?)...
But now I see it already done within V+...
It is possible to create file scripts for backup (which are MD5 files), it is possible to determine changes...
I see the lack of 2 things only, both discussing here now - adding files and adjusting MD5 files according to backup results.
There is not scheduled backup of course, but I wonder if we need it
1. I think Chris would be astonished if you devour his new program
Maybe he'd even ask why are you remaining so hungry after consuming all other programs? You are really fleshed in blood
2. If you tend to delete files which does not exist any more, so you must to offset a loss
3. A week ago I've thought that we do not need a new backup program at all (remember my mail about Fast Backup?)...
But now I see it already done within V+...
It is possible to create file scripts for backup (which are MD5 files), it is possible to determine changes...
I see the lack of 2 things only, both discussing here now - adding files and adjusting MD5 files according to backup results.
There is not scheduled backup of course, but I wonder if we need it
This is how I see it. Just a rough concept (may differ from realization).
1) There is no need to replace standard Backup programs.
They do very well their main job and that is creating Backup (copying files over to Backup folder).
2) Here is where the Backup+ comes
After you created Backup, you just need to produce MD5 Checksum File-list for your Backup folder.
It will usually take few seconds for C: drive. Then you dismiss your Backup program untill the next major (complete) backup
3) What is Backup+ going to do?
It is verifying/checking/updating your Backup!
First you can produce MD5 Checksum File-lists of your own liking, either for whole drive (usually C) or for complete single folders,
or you can have random lists created on various conditions.
Action 1)
BAckup+ will verify (using MD5 checksums) if files from your File-list have changed and compare them to your Backup Checksum list.
If they changed and different from backuped files, they would be copied over to Backup, updating old files.
Action 2)
Backup+ will check if some files are missing and if so, delete them from your Backup.
Action 3)
Backup+ will check if some new files are created recently and if they don't exist in your Backup, they will be added.
You would be able to check on/off options for all actions, therefore having full control over what is going to happen.
After operation is finished, your both File-lists (checked one and Backup Checksum list) would be updated!
So, your Backup (CF) even wouldn't need to be in the slot while verifying/checking
This is how I see it. Just a rough concept (may differ from realization).
1) There is no need to replace standard Backup programs.
They do very well their main job and that is creating Backup (copying files over to Backup folder).
So, there is no need for standard backup program at all - Shell can do it perfectly via Ctrl-Y
Edo wrote:
3) What is Backup+ going to do?
It is verifying/checking/updating your Backup!
First you can produce MD5 Checksum File-lists of your own liking, either for whole drive (usually C) or for complete single folders,
or you can have random lists created on various conditions.
Action 1)
BAckup+ will verify (using MD5 checksums) if files from your File-list have changed and compare them to your Backup Checksum list.
If they changed and different from backuped files, they would be copied over to Backup, updating old files.
Action 2)
Backup+ will check if some files are missing and if so, delete them from your Backup.
Action 3)
Backup+ will check if some new files are created recently and if they don't exist in your Backup, they will be added.
You would be able to check on/off options for all actions, therefore having full control over what is going to happen.
After operation is finished, your both File-lists (checked one and Backup Checksum list) would be updated!
Addendum: there should be an option to see lists of changed/deleted/added files respectively before performing backup.
Edo wrote:
So, your Backup (CF) even wouldn't need to be in the slot while verifying/checking
Cannot understand this point
MD5 file is created at the same drive where folders/files are, so how can we compare something w/o having access to its MD5?
Addendum: there should be an option to see lists of changed/deleted/added files respectively before performing backup.
No need to mention that at all
Quote:
Edo wrote:
So, your Backup (CF) even wouldn't need to be in the slot while verifying/checking
Cannot understand this point
MD5 file is created at the same drive where folders/files are, so how can we compare something w/o having access to its MD5?
Heh! That's the catch
If you keep (a copy of your) Backup Checksum File-list on C drive, you don't need the real Backup folder to be present!
Only before updating/writing Backup you would be asked to insert it into the CF slot
If you keep (a copy of your) Backup Checksum File-list on C drive, you don't need the real Backup folder to be present!
Only before updating/writing Backup you would be asked to insert it into the CF slot
So, this is some special MD5 file, which is MD5 of backup folder on other drive in fact?
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Memberlist
Usergroups
Join! (free) 
Profile
Log in to check your private messages
Log in
- to add an appropriate checkbox to the "save list" dialog, somewhat like "include changed only".
