Jump to content











Photo
- - - - -

vMount

vhd

  • Please log in to reply
78 replies to this topic

#76 ReTokener

ReTokener

    Frequent Member

  • Developer
  • 153 posts

Posted 06 January 2019 - 04:41 PM

Dear Erwan

thanks for the fast reply.

 

 

I suspect that \\?\Volume{26503745-1125-11e9-9e6f-0002a4b2c832}\ will actually have a drive letter already assigned to it.

 

You are right.

 

Maybe I oversaw this fact:

 

if your volume already has a drive letter assigned to it, you may not be able to assign a new drive letter

 

Having no Drive-Letter for the Volume lets vMount assign a letter correctly.

 

Thanks a lot and best wishes for 2019

 

Sincerely   T.

 

 



#77 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14596 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 06 January 2019 - 07:25 PM

Isn't this something that can be implemented in the vmount (at next revision/update)?

I mean checking if the given GUID volume has already a drive letter assigned to it and if this is the case provide an error like:

vmount64_181221.exe assign X:\ \\?\Volume{26503745-1125-11e9-9e6f-0002a4b2c832}\

ERROR: Volume{26503745-1125-11e9-9e6f-0002a4b2c832} is already mounted to drive letter E:

 

Which should be more undestandable than:

vmount64_181221.exe assign X:\ \\?\Volume{26503745-1125-11e9-9e6f-0002a4b2c832}\
X:\ mount failed,87,Falscher Parameter

 

:duff:

Wonko



#78 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2452 posts
  • Location:Nantes - France
  •  
    France

Posted 07 January 2019 - 07:55 PM

Isn't this something that can be implemented in the vmount (at next revision/update)?

I mean checking if the given GUID volume has already a drive letter assigned to it and if this is the case provide an error like:

 

...

 

:duff:

Wonko

 

Absolutely, this is a good idea !

Let me plan this for next release.

 

Cheers,

Erwan



#79 sebus

sebus

    Frequent Member

  • Advanced user
  • 355 posts

Posted 02 February 2019 - 07:53 PM

It seems that VHDSet are not created:

 

vmount v0.9 by erwan2212@gmail.com

 

W:\temp>vmount createdynamic .\trial.vhds 127000
CreateVHD not ok:The parameter is incorrect







Also tagged with one or more of these keywords: vhd

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users