Dokan library 0.5.2 released
I released Dokan library 0.5.2. It has been only one month since last release, yeah!. There are a lot of stability improvements, bug fixes and new feature.
From this version, DOKAN_OPTION_REMOVABLE is supported. If you set this parameter in DOKAN_OPTIONS when you call DokanMain, you drive can be removed by right click context menu.
Dokan supports Windows Server 2008 and 2008R2 from this version, and now supports Windows XP, 2003, Vista, 2008, 7 x86 and Windows 2003, Vista, 7, 2008R2 x64.
Changes from 0.5.1
- supports Windows 2008 and 2008R2
- fixed BSOD in Vista x64 while filter manager operations
- fixed unmount after timeout
- fixed potential BSOD in IPR_MJ_CREATE
- added DOKAN_OPTION_REMOVABLE
- fixed BSOD while cache manager operations in Windows 2003.
- improved supprot for network filesystem
- fixed office 2007 issues.
Can you please merge fuse4win (it’s dokan-based FUSE API implementation) from http://fuse4win.4host.ru/ in the further releases?
It will help porting a lot of useful FS’ses from unix world.
Thanks for your great project!
Hi can you please update dokan.net library as dokan.net library is written in c++ and the people who uses .net library may not know c++ properly thank you.
One thing I noticed that I like about 0.5.2 is that if my program crashes without calling DokanUnmount, the drive letter soon disappears from “My Computer”
In 0.5.1, the drive letter would remain, and attempts to unmount it with dokanctl would hang.
Brian
“dokanctl /u c ” this command lead to partion partition C unusable
Hi,
Can’t run on Vista 64 bits, wondering is it’s my windows problem.
Thanks
Never mind, it was Comodo’s glitch, installed ok now.
Still testing with 0.5.2…. So far, I’ve had no blue screens, even with continuous heavy debugging!!! With 0.5.1, I had blue screens fairly regularly.
Good job!
I found a bug in this version. It has been documented in “Issues” on Google Code. http://code.google.com/p/dokan/issues/detail?id=145 . When will it be fixed as it is functionally breaking (TortoiseSVN can’t do a checkout on the VFS because of that).
I’m not able to run this on W2K8 64 bit. Based off of other reported issues, I assume their is a problem with this release and 64 bit platforms.
Using JDokan and MemoryFS sample.
When checking for processId, I always get the same process-id, meaning it won’t change while the VFS is mounted, will change at every re-mount, but once the VFS is mounted, i get the same processID for any application that tries to read a file from the VFS (e.f: text editing or opening in word a DOC file will result in the same processId).
Is that the expected behavior or there is a fix for that?
As a replay to my own previous comment, the issues was with the dokan.h from the driver and the one used by the JDokan (meaning the differences from the Dokan Options). Now I have a working copy of the JDokan returning valid processIDs.
GREAT WORK!!!!
Im ready for an exciting new release soon
Thank you very much for you hard work! Excellent Library!
So glad this is working on x64 now. Thanks!
I want to know how to add format to Dokan.
Any clues?
Thanks
Wouldn’t it be a good idea to support WinXP x64 since there are so many users compared to Vista x64?!?!