thank you for your efforts.
this command does not return anything on Win7 and Win10.
not at vDisk nor on real disk.
downloaded version number still is 126.96.36.199
Setting a (vitual) disk state to readonly, I noticed the following:
Create a new text-file -> obviously OK
Writing to this file and save changes -> obviously OK
Copy this text-file -> obviously OK
Copy files from another drive to the readonly vDisk -> Up to a certain number OK - then stating readonly
After detaching and re- attaching the vDisk, all created files are gone.
So the windows explorer simulated the creation of files.
how can vMount do this too?
Version 188.8.131.52 out.
-NOTE : about getstoragedependencyinfo, note that this is lowercase and vmount is (shame on me) case sensitive.
-NOTE : you can type vmount whatevertypo and vmount will silently run - not ideal and will do something about later.
-FIXED : getstoragedependencyinfo will now return an error in most situations (including if you run it against a non vdisk)
-NEW : attributes will now return the readonly flag if the vdisk was mounted in readonly mode
-NEW : attachvhd will now accept a RO parameter
-NOTE : ro and rw will still report OK even on readonly vdisk (when it should ideally report not ok)
-FIXED : detachvhd should work fine on win7 (and that bug was fixed in clonedisk win32 as well)
If you are playing with disk attributes (i.e not attaching your vdisk in RO mode), it is worth reading Misty's post above as you may hit some strange behaviors.
Also, for now it is safe to consider that setting RO attributes on a disk is not like attaching a vdisk in RO mode even if the end result may appear the same.
Note the '*' indicating this readonly is inherited from the vdisk.
The logic is the following : when checking the disk attributes, i will also check if it is a vdisk in readonly mode and if so will report it.
Writing that I just realise Normal should not be reported then if Read-Only ... oh well, next version will fix this minor issue...
>vmount-win32 attributes 2
Note the flag=5 (permanent + ro)
You may have thought that the developper could just have reported Read-Only instead of a cryptic Flag 5? Well it is without knowing the perverted mind of a developper
>vmount-win32 attachvhd e:\test.vhd RO
Note that DependentVolumeName will always be empty.
Interesting that vdisk api takes either a devicename or a volumename as input.
Could be handy thus later on to retrieve vdisk details based on a volume/drive letter.
>vmount-win32 getstoragedependencyinfo 2