You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to see the possibility of connecting/mounting/mapping the NAS or remote drives as a local (static harddrive) hard disk so
the picky software such as AcronisTrueImage2019 should not find out the mapped drive as a network drive otherwise it will ask for non
existing credentials which hinders the user to use the mapped mountainduck drive as a Target Harddisk for the purpose of disk image backup.
In addition there are many software out there that are very picky on the type of the mapped (such as B:,E:,...) drive in windows and they do not work on those drive if they find out those drive are network mapped drive.
The feature that I would like to see is the mapped drive in the mountain duck should act as a local harddisk drive
The text was updated successfully, but these errors were encountered:
Please write to [support@mountainduck.io]. Currently we do not support mounting as a local disk but are looking into adding this option in a future version.
I would like to see the possibility of connecting/mounting/mapping the NAS or remote drives as a local (static harddrive) hard disk so
the picky software such as AcronisTrueImage2019 should not find out the mapped drive as a network drive otherwise it will ask for non
existing credentials which hinders the user to use the mapped mountainduck drive as a Target Harddisk for the purpose of disk image backup.
In addition there are many software out there that are very picky on the type of the mapped (such as B:,E:,...) drive in windows and they do not work on those drive if they find out those drive are network mapped drive.
The feature that I would like to see is the mapped drive in the mountain duck should act as a local harddisk drive
The text was updated successfully, but these errors were encountered: