+- Antwise community forums (https://forums.antwise.com)
+-- Forum: General Info and Questions (https://forums.antwise.com/forumdisplay.php?fid=3)
+--- Forum: Updates (https://forums.antwise.com/forumdisplay.php?fid=6)
+--- Thread: Vimalin for Fusion 2.5.481 update (/showthread.php?tid=50)
Vimalin for Fusion 2.5.481 update - wila - 2020-10-01
Vimalin for Fusion 2.5.481 update
This is a bugfix update for a few issues in the user interface.
https://www.vimalin.com/download/Vimalin-2.5.481.dmg
(or use the Vimalin -> "Check for Updates" menu option)
Please note that the update recommendation is to first uninstall your existing Vimalin application by dragging it to the Trash (or for our English users, drag it to the Bin).
Only after the old Vimalin is uninstalled run the installer to update to Vimalin 2.5.481.
Here's the list of changes since version 2.5.474:
New
- VMware Fusion 12.0 support
- Both Fusion Professional as well as Fusion Player are supported.
General changes
- The screen to guide you through enabling Full Disk Access via the apple Security Preferences screen now has a button to immediately open the "Security & Privacy" panel on the privacy pane.
- The new resize logic caused the application to start in the top left of the screen instead of in the middle. This has been fixed.
- If the backup process gets interrupted, for example by a reboot of the host, then a backup snapshot might not be removed. When trying to run a new backup this would then result in a slightly confusing error 'Failed it already has a backup snapshot'. If this problem happens now then Vimalin will first try to automatically remove that old backup snapshot and continue with the backup if that was successful.
- If the worker could not connect to a network drive then it would not register the backup. This is now properly saved and handled in the backup archive.
Backup Archive:
- When a job gets scheduled it now changes the status for that archive immediately to "queued". That way the user knows that their action was registered by Vimalin.
- There was a timing issue with jobs that completed before the screen was updated and as a result some jobs would never display on the backup archive as being busy processing. The timing logic has been tweaked a bit so that it would be much harder for this to happen.
More information about Vimalin is available at the main website: https://www.vimalin.com