dburner / dokan

Automatically exported from code.google.com/p/dokan
0 stars 0 forks source link

Unable to add vmdk file to VMPlayer (using sample Mirror code) #298

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Hi,

I have mapped my local folder as a drive using Dokan Mirror example code, and 
try to add a vmdk file present in the Dokan folder to the VMPlayer. When I 
choose the disk and give 'Finish', VMPlayer throws an error like 'One of the 
parameters supplied is invalid'. I have debug the dokan logs and it seems 
'MirrorOpenDirectory' callback function received for the vmdk file and in the 
mirror code we send -1 as error code. 

In the MirrorCreateFile and MirrorGetFileInformation, 
DokanFIleInfo->IsDirectory seems to be 0 for the vmdk file and in the 
MirrorOpenDirectory callback function, DokanFIleInfo->IsDirectory seems to be 1.

OS - Windows 7
Dokan version - Dokan Library 0.6.0

I suspect this is the reason for the failure. My assumption is, 
MirrorOpenDirectory callback should not be called for files. Can anyone please 
confirm what could be the issue and help me to solve the issue.

Awaiting your update.

Regards,
Ashar.

Original issue reported on code.google.com by asharud...@gmail.com on 4 Jul 2014 at 11:50

GoogleCodeExporter commented 9 years ago
I have further analyzed this issue, and it seems sending as a directory is not 
a issue.  

This issue occurs in Windows, if we set the correct file size in 
HandleFileInformation->nFileSizeLow and HandleFileInformation->nFileSizeHigh. 
If I set these values as 0, I can able to choose the vmdk files without any 
issue. However, further boot process fails. If I set the size values correctly, 
I receive the error, 'One of the parameters supplied is invalid' when saving 
the vmdk disk itself. I receive this error only in Windows OS with VMPlayer. 

Let me know your thoughts.

Original comment by asharud...@gmail.com on 7 Jul 2014 at 6:06

GoogleCodeExporter commented 9 years ago
I have used vmplayer 4.x version and faced this issue. Now I have upgraded to 
vmplayer 6.x version and the issue seems to be not reproduced now.

Regards,
Ashar.

Original comment by asharud...@gmail.com on 7 Jul 2014 at 1:53