Vimalin for Windows 2.6.517 update

[wila]

Vimalin for Windows 2.6.517 update

You can download the update for Vimalin from:

https://www.vimalin.com/download/Vimalin....6.517.exe
(or use the Vimalin -> "Check for Updates" menu option)

How-to update
First uninstall the old version from the Add/Remove programs or in Windows 10 the Settings -> Apps & Features screen. If you keep defaults you are fine and nothing changes.
Only after the old Vimalin is uninstalled run the installer to update to Vimalin 2.5

Here's the list of changes since version 2.5.487:

General fixes

• Fixed a bug where a backup would fail because the previous backup of that same VM was interrupted.
  The interrupted backup ended up leaving a backup snapshot. On start of the new backup the old snapshot backup is removed before creating a new backup snapshot, but the filelist was not refreshed. This would cause the 2nd backup to fail as well.[/*]
  
• If your backup failed due to lack of free disk space, it would still create an empty folder at the backup target. Deleting the failed backup did not remove the empty folder. Fixed.
  
• In the last version we already changed file checking logic about specific log files as it triggered false warnings, because the log files still change while they are being copied (which is fine for log files). Turns out there are more log files (d'oh), so this changed logic now applies for all .log files thereby curing a lot of failed backups due to the "could not copy all files" error.
  

Backup Archive

• Defined the Delete key as short cut key for deleting a VM.
  
• Introduced search logic. You can search the list of VMs for patterns in VM name and back target. The search is case insensitive.
  
• Any column is now sortable by clicking on the header. You can sort ascending or descending and the rest of the list will adjust to the selected sort.
  

Backup Archive Details

• The list of files is now sorted by file name.
  

Activity Log

• Fixed an optimisation that caused the log not to reload on opening the screen the 2nd time. You had to change from normal view to detailed view to force a reload.
  
• Improved logging details by quite a bit, by providing more exact details on why something went wrong. Eg. if not enough space, then tell how much free space was actually needed. Another example would be that if file size of the copied file is different then state the details. Basically the logging logic has been overhauled, so that you less often have to go down to the text only logs in order to figure out the reason for a problem.
  

More information about Vimalin is available at the main website: https://www.vimalin.com