Fixing dokan support discussion... #256

apocalypse2012 · 2016-07-15T01:45:41Z

Python 2.7.9 64 bit and 32 bit
Dokan 0.7.4
FS 0.5.4
Windows 8.1

from fs.memoryfs import MemoryFS
from fs.expose import dokan
fs = MemoryFS()
mp = dokan.mount(fs,"Q")
Traceback (most recent call last):
File "", line 1, in
File "C:\Python27\lib\site-packages\fs\expose\dokan__init__.py", line 936, in mount
check_ready(mp)
File "C:\Python27\lib\site-packages\fs\expose\dokan__init__.py", line 913, in check_ready
raise OSError("dokan mount process seems to be hung")
OSError: dokan mount process seems to be hung

dokan.mount(fs,"Q",foreground=True)
Traceback (most recent call last):
File "", line 1, in
File "C:\Python27\lib\site-packages\fs\expose\dokan__init__.py", line 929, in mount
raise OSError("Dokan failed with error: %d" % (res,))
OSError: Dokan failed with error: -5

I tried the newer versions before I realized that 8.0 was API breaking. I've read through all the message boards I can find with no apparent 'fix'. Dokan 0.6.0 no longer appears to be available on the Dokan project page at Github. I

lurch · 2016-07-15T08:36:28Z

Somebody started working on updated Dokan support (#241 and #236) but I dunno if they ever got any further :-/
Ping @zommuter

See also https://github.com/PyFilesystem/pyfilesystem/search?q=dokan&state=open&type=Issues

zommuter · 2016-07-15T19:23:26Z

Thanks for the ping, @lurch. Unfortunately that is currently at the very bottom of my TODO list, and lacking more experience with Dokan I doubt I can fix this on my own :(

Liryna · 2016-07-27T12:52:11Z

👍 I am willing to help on this !
@arekbulski I seen you forked pyfilesystem, did you plan to update dokan implentation ?

I will try to take a look at it in the next days and see what changes should be made.
Dokan 1.0.0 should be implemented since it is near to be release stable.

lurch · 2016-07-27T13:43:32Z

It would be great to see working Dokan support in pyfilesystem again :-)

arekbulski · 2016-07-27T14:13:30Z

I am willing to review pyfilesystem, especially documentation. But I am also looking forward to seeing Dokan working with pyfilesystem, tell me how can I help. @Liryna

Liryna · 2016-07-27T19:31:59Z

@arekbulski Ok, I just wanted to know if you planned to update the wrapper yourself.

I began to update most of the natives commandes https://github.com/Liryna/pyfilesystem without implementing it

from ctypes import *

try:
    DokanMain = windll.Dokan.DokanMain
    DokanVersion = windll.Dokan.DokanVersion
except AttributeError:
    raise ImportError("Dokan DLL not found")

Where does the dllimport happen ? How to set library name ?

arekbulski · 2016-07-27T20:36:36Z

You import windll from ctypes, which is a library loader. Member name is used as library name that is DLL name to be loaded. And for the library object, member name is used as function name. Simple example:

In [13]: ctypes.windll
Out[13]: <ctypes.LibraryLoader at 0x247b7dcdc88>
In [11]: ctypes.windll.msvcrt
Out[11]: <WinDLL 'msvcrt', handle 7ff829220000 at 0x247b8359f98>
In [12]: ctypes.windll.msvcrt.memset
Out[12]: <_FuncPtr object at 0x00000247B829FEE8>

In your code Dokan is the library name, DokanMain/DokanVersion are imported functions. You might limit it to from ctypes import windll if you choose.

Liryna · 2016-07-27T20:44:25Z

Thank you for your answer @arekbulski ❤️
So windll.dokan1 should load dokan1.dll ?

arekbulski · 2016-07-27T20:45:48Z

I think so, one way to know for sure.

Liryna · 2016-07-27T20:47:45Z

Yes I will make the test 😃
I don't have access to my dev environment so I am just reviewing the code for now.

Liryna · 2016-07-28T19:21:54Z

I am currently able to start the mount of a dokan device with my last changes https://github.com/Liryna/pyfilesystem
I see that Mounted operation is called, the python is correctly called but I get the error run-time check failure the value of ESP directly when the function return here: https://github.com/Liryna/pyfilesystem/blob/master/fs/expose/dokan/__init__.py#L805
I understood that this error means that the mapping python <-> C is not correct but I am unable to find what I did wrong. :( (first time I do this 😄 )

If someone could guide me, it would be nice !

https://github.com/dokan-dev/dokany/blob/master/dokan/dokan.h#L111
https://github.com/Liryna/pyfilesystem/blob/master/fs/expose/dokan/libdokan.py#L112

arekbulski · 2016-07-28T19:27:04Z

Throw it at Stack Overflow. I am not familiar enough with it.

I do not understand why USHORT is not taken from c_ushort.

Liryna · 2016-07-28T20:41:08Z

Probably in case USHORT was not define in earliest version of ctypes.
I removed it and forced c_ushort, same behaviour 😢
@lurch @zommuter are you familiar with ctypes ?

arekbulski · 2016-07-28T20:59:52Z

Not surprised. There is no point in supporting dinosaur-old versions of Python.

Liryna · 2016-07-30T09:51:36Z

My bad, I found that all call work with dokan1.dll in Release mode and not in Debug as I was doing.
Now I get proper call from dokan.

CreateFile fail here https://github.com/Liryna/pyfilesystem/blob/master/fs/expose/dokan/__init__.py#L453 when \ directory is requested

execpt Path contains invalid characters: \

I am not familiar with fs api and the code seems to not have been updated since 3 years (dokan part). It there one of the pyfilesystem that could help me to review fs api calls ?

arekbulski · 2016-07-30T11:03:22Z

Here is the isdir() from MemoryFS and normpath() that it uses. From what I read in these methods, fs objects require/expect paths formatted in their way. Notice that normpath does not recognize backslash at all. It is not recognized as one of ('..', '.', '') so it gets passed as a component, normpath('') should give '/' right? isdir('') will give False which will lead to further problems.

https://github.com/Liryna/pyfilesystem/blob/master/fs/memoryfs.py#L321
https://github.com/Liryna/pyfilesystem/blob/master/fs/path.py#L20
https://github.com/Liryna/pyfilesystem/blob/master/fs/path.py#L66

Liryna · 2016-07-30T12:04:06Z

👍 @arekbulski You are exactly right
normpath('') is giving '' 😢

I had to add in all functions:
path = path.replace('', '/')

I don't know if this is the best way but I am now able to run the test.

I am just not able to write the test file and will look into this.

Liryna · 2016-07-30T12:46:11Z

Pull request created: #258

I am able to Create/Delete/List/Rename/Read/Write files without issues.
As an example, Word 2016 successfully open a file, read/write and save it.

arekbulski · 2016-07-30T12:46:36Z

Well, it is you who is doing all the hard work. I am just good at code analysis. 😃

Liryna · 2016-07-30T13:03:16Z

A pleasure 👍 I always wanted dokan being compatible with python.

lurch · 2016-08-01T11:34:38Z

normpath('') is giving ''

That's correct - as far as pyfilesystem is concerned, a file named \ is totally fine. 'input paths' to pyfilesystem should always be separated only by / characters ( http://docs.pyfilesystem.org/en/latest/concepts.html#paths ), and any conversion to/from backslashes (to handle the underlying OS / API calls) should be done inside the FS code. Have a look at OSFS to see if that helps?

Liryna · 2016-08-01T11:47:18Z

You are right self.fs.isdir (OSFS) does raise the error at some point with \ as input path.
Does that mean OSFS should be fixed to handle such case ?
I will remove the replace if thats the case.

lurch · 2016-08-01T12:09:10Z

Does that mean OSFS should be fixed to handle such case ?

No. As I already tried to explain, pyfilesystem has the concept of (abstract) "pyfilesystem paths", and (concrete) "system paths".
A pyfilesystem path might be something like /some/dir/file.txt and on Linux this might map to a (OSFS) system path of /home/lurch/testing/some/dir/file.txt, and on Windows it might map to a (OSFS) system path of C:\Users\Andrew\Documents\testing\some\dir\file.txt.
The user-code talking to pyfilesystem should only ever use forward-slashes to separate directories, and it's up to the library-code inside pyfilesystem to do any necessary manipulations to convert the pyfilesystem-paths to and from system-paths as necessary.

It's kinda difficult to explain clearly, but it means that user-code making use of pyfilesystem is always identical, no matter what platform it's running on, and what the backend filesystem is. (and this is also why pyfilesystem has no 'current directory' concept, because some of the backend filesystems don't support that)

Liryna · 2016-08-01T12:20:56Z

All right 👍 , so If I understand correctly
my wait to convert path coming from Dokan CreateFile/Cleanup/Close operation like \, \folder, \folder\file.txt to "pyfilesystem paths" with path.replace('\\', '/') is correct ?

If not, I have no idea what to do since dokan directly send the path like that and there is no way to change it.

arekbulski · 2016-08-01T12:21:18Z

I totally understand and agree with the concept behind abstract paths. However on Windows backslashes must be converted to a recognized separator or path splitting will lead to incorrect results. Remeber Dokan is Windows only. Btw windows syscalls work with slashes just as well as far I was told.

lurch · 2016-08-01T12:46:18Z

I'm afraid I've never looked at any of the 'expose' classes in pyfilesystem, so maybe I'm getting confused between which paths are pyfilesystem-paths, and which paths are system-paths? :-S

But anyway, IMHO it'd be much cleaner to have just a couple of functions that convert Dokan-paths to and from pyfilesystem-paths, and use those in each of the other functions; rather than sprinkling path.replace calls everywhere ;)

Given that you've updated all the docstrings to say that the Dokan class now supports mounting to an arbitrary path, rather than (just) a drive-letter, have you tested that? Does there need to be any code adding and removing this extra path-info from the Dokan-paths? (apologies if that's a stupid question, but I've never looked at dokan code)

Liryna · 2016-08-01T17:33:56Z

I have added the extract method to convert paths.

JokerQyou · 2016-08-18T08:00:16Z

I gave it a try just now, with a Python 2.7.11 (32 bit) on Windows 10 64 bit, and the mounting subprocess went wrong, Windows shows a dialog saying python.exe has stopped working. And the traceback is as follows:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "fs\expose\dokan\__init__.py", line 973, in mount
    check_ready(mp)
  File "fs\expose\dokan\__init__.py", line 943, in check_ready
    check_alive(mp)
  File "fs\expose\dokan\__init__.py", line 931, in check_alive
    raise OSError("dokan mount process exited prematurely")
OSError: dokan mount process exited prematurely

The code I tried is:

import fs.memoryfs
import fs.expose.dokan
fs.memoryfs.__file__
s = fs.memoryfs.MemoryFS()
mp = fs.expose.dokan.mount(s, 'Q:\\')

My dokan installation is Dokoan Library 1.0.0.4000 Bundle as shown in Windows control panel.

I'm not sure whether it's a problem with my dokan installation or with your code. If I get a chance to reboot my computer I'll test again and let you know the result.

Liryna · 2016-08-29T19:44:05Z

Hi @JokerQyou ,

Did you copy the dokan1.dll from x86 folder (C:\Program Files\Dokan\x86) ?
It has to be in the same folder as your code.

JokerQyou · 2016-08-31T03:34:44Z

I tested again with dokan1.dll copied to the pyfilesystem project root folder, and it did not work as well.

>>> import fs.memoryfs
>>> import fs.expose
>>> s = fs.memoryfs.MemoryFS()
>>> mp = fs.expose.
>>> from fs.expose import dokan
>>> mp = dokan.mount(s, 'Q:')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "fs\expose\dokan\__init__.py", line 923, in mount
    _check_path_string(path)
  File "fs\expose\dokan\__init__.py", line 896, in _check_path_string
    raise ValueError("invalid path: %r" % (path,))
ValueError: invalid path: 'Q:'
invalid path: 'Q:'
>>> mp = dokan.mount(s, 'Q:\\')
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "fs\expose\dokan\__init__.py", line 1061, in _do_mount
    mount(fs, path, **opts)
  File "fs\expose\dokan\__init__.py", line 964, in mount
    res = libdokan.DokanMain(ctypes.byref(opts), ctypes.byref(opstruct))
WindowsError: exception: access violation reading 0x00DF0000
KeyboardInterrupt

And I tested again with no mistake typing letters.

>>> import fs.memoryfs
>>> from fs.expose import dokan
>>> s = fs.memoryfs.MemoryFS()
>>> mp = dokan.mount(s, 'Z:\\')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "fs\expose\dokan\__init__.py", line 973, in mount
    check_ready(mp)
  File "fs\expose\dokan\__init__.py", line 940, in check_ready
    check_alive(mp)
  File "fs\expose\dokan\__init__.py", line 931, in check_alive
    raise OSError("dokan mount process exited prematurely")
OSError: dokan mount process exited prematurely
dokan mount process exited prematurely

And this time the dokan.mount() takes very long to finish (with an error though), and the drive Z: did appear in explorer, but it says drive disconnected when I try to open it.

I was testing within an interactive shell, does that affect anything?

Liryna · 2016-08-31T05:39:16Z

>>> mp = dokan.mount(s, 'Q:\\')
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "fs\expose\dokan\__init__.py", line 1061, in _do_mount
    mount(fs, path, **opts)
  File "fs\expose\dokan\__init__.py", line 964, in mount
    res = libdokan.DokanMain(ctypes.byref(opts), ctypes.byref(opstruct))
WindowsError: exception: access violation reading 0x00DF0000

That's very strange

Can you try to run the mirror.exe in C:\Program Files\Dokan\sample ? (you need to enable developement files option during dokan installation)
mirror.exe /r C:\Users /l m

I was testing within an interactive shell, does that affect anything?

This should not affect dokan.

If I understood correctly it mount the device but something is making it umount.
I have not been able to reproduce this so we should first look on your side if it come from the python or the library (by runing the mirror)

Liryna · 2016-09-06T20:07:01Z

@lurch have you been able to test it ?

lurch · 2016-09-07T09:42:36Z

@lurch have you been able to test it ?

Unfortunately not yet, been far too busy with other stuff :-(
It's still on my TODO list though...

Liryna · 2016-09-20T20:39:13Z

Dokan 1.0.0 has been released https://github.com/dokan-dev/dokany/releases/tag/v1.0.0
and can be used with my PR 😉

Liryna · 2016-09-22T05:32:11Z

@JokerQyou I made a change on the pull request, do you think can you clone again and try to test it ?

apocalypse2012 · 2016-09-22T05:51:43Z

Sorry for not having followed up on this. I've been impacted by a layoff that has taken me offline from my original motivation. Still interested in this library and will Follow up as soon as I can... Raymond

JokerQyou · 2016-09-22T06:23:06Z

I'd like to give it a try but I've been too busy... And I cannot afford a system restart (I reinstalled dokan with development files but have not restarted my computer) now. I'll test it if I got time tonight (GMT+8).

arekbulski · 2016-09-22T11:29:48Z

I moved on to Construct. Unsubscribing from this thread. Ping me if needed. 👋

lurch · 2016-10-10T22:35:34Z

Moving this comment to here to try to separate 'general discussion' from 'code comments'...

@lurch After 2 month, It would be nice if you could clone the PR and make your own opinion.

Sorry, I'm not sure what you're asking me for?

I do appreciate all the hard work you and others have been putting into getting this working 👍 I've never written Win32 API code myself, but I understand how 'murky' it can be.
Unfortunately, if even Windows Explorer or Notepad are currently unable to save files into a dokan-exposed filesystem (which AFAICT is the whole reason for the 'expose' interface in the first place - right @willmcgugan ?) then IMHO #258 has limited usefulness for typical users. People would only complain when it doesn't work the way they expect it to.

OTOH if you wanted to modify the PR so that it can only be used to expose ReadOnly filesystems (see e.g. http://docs.pyfilesystem.org/en/latest/base.html#fs.base.FS.getmeta and http://docs.pyfilesystem.org/en/latest/wrapfs/readonlyfs.html ), and documented it as such, then that could probably be merged. (Which will then hopefully be 'upgraded' later on to allow full dokan read/write access when this security issue gets fixed)
It would be limited functionality (no modification to the exposed FS), but at least it would be consistent behaviour for the end-user.

I hope that doesn't sound too harsh, I hope you can see where I'm coming from. I'm afraid I don't get as much time to look at pyfilesystem as I'd like, and from their lack of input I assume @willmcgugan and @rfk are even busier than I am :-/

willmcgugan · 2016-10-11T14:04:21Z

Thanks @lurch. Sorry I haven't been keeping up with the work here.

Not being a massive Windows user I'll need a little guidance here. If we're talking about fixes then I'm all for it. But I'm guessing its not as clear cut?

JokerQyou · 2017-06-06T07:11:57Z

I've managed to test directly with the whole repo cloned from @Liryna 's remote, and here's the result with memory fs.

λ ptpython                                                                       
>>> import fs.memoryfs                                                           
>>> import fs.expose                                                             
>>> fs                                                                           
<module 'fs' from 'fs\__init__.py'>                                              
>>> s = fs.memoryfs.MemoryFS()                                                   
>>> from fs.expose import dokan                                                  
>>> mp = dokan.mount(s, 'Q:')                                                    
Traceback (most recent call last):                                               
  File "<stdin>", line 1, in <module>                                            
  File "fs\expose\dokan\__init__.py", line 957, in mount                         
    _check_path_string(path)                                                     
  File "fs\expose\dokan\__init__.py", line 929, in _check_path_string            
    raise ValueError("invalid path: %r" % (path,))                               
ValueError: invalid path: 'Q:'                                                   
invalid path: 'Q:'                                                               
>>> mp = dokan.mount(s, 'Q:\\')                                                  
>>> mp                                                                           
<fs.expose.dokan.MountProcess object at 0x050FEBB0>                              
>>> s                                                                            
MemoryFS()                                                                       
>>> s.listdir()                                                                  
[]                                                                               
>>> s.listdirinfo()                                                              
[]

At this time Q: is mounted successfully and can is visible through explorer, and I've created a folder in it (using explorer's context menu), but the created folder does not show up with s.listdir().

And I've also tried to created a new folder with s.makedir('a'), this folder showed up with s.listdir(), but not in explorer. The mounted drive in explorer does not sync up with the memory fs in python.

And I used the following code to unmount the drive:

>>> dokan.unmount('Q:\\')
>>> Traceback (most recent call last):
  File "<string>", line 3, in <module>
  File "fs\expose\dokan\__init__.py", line 1096, in _do_mount
    mount(fs, path, **opts)
  File "fs\expose\dokan\__init__.py", line 998, in mount
    res = libdokan.DokanMain(ctypes.byref(opts), ctypes.byref(opstruct))
WindowsError: exception: access violation reading 0x00000010

This error was not raised right after my command returned. Actually the unmount method returned very fast, but it was after several more seconds did the error come up. I suspect it was the background process which crashed.

For pyfilesystem it was a fresh clone from https://github.com/Liryna/pyfilesystem.git , as for Dokan it was 1.0.0.4000 (version of dokan1.dll). I'll try the newer version of Dokan some time later.

Rondom · 2017-06-06T12:30:56Z

Current master in this repo should have all necessary changes.

BiatuAutMiahn · 2019-08-31T21:09:34Z

I can't get this to work, Dokany v1.3.0.1000

Output:

>>> from fs.memoryfs import MemoryFS
>>> from fs.expose import dokan
>>> fs = MemoryFS()
>>> # Mount device mount point
... mp = dokan.mount(fs, "Q:\\")
Traceback (most recent call last):
  File "<string>", line 3, in <module>
  File "C:\ProgramData\Miniconda3\lib\site-packages\fs\expose\dokan\__init__.py", line 1107, in _do_mount
    mount(fs, path, **opts)
  File "C:\ProgramData\Miniconda3\lib\site-packages\fs\expose\dokan\__init__.py", line 1011, in mount
    raise OSError("Dokan failed with error: %d" % (res,))
OSError: Dokan failed with error: -7
Traceback (most recent call last):
  File "C:\ProgramData\Miniconda3\lib\site-packages\fs\expose\dokan\__init__.py", line 983, in check_ready
    os.stat(path)
FileNotFoundError: [WinError 3] The system cannot find the path specified: 'Q:\\'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 2, in <module>
  File "C:\ProgramData\Miniconda3\lib\site-packages\fs\expose\dokan\__init__.py", line 1018, in mount
    check_ready(mp)
  File "C:\ProgramData\Miniconda3\lib\site-packages\fs\expose\dokan\__init__.py", line 985, in check_ready
    check_alive(mp)
  File "C:\ProgramData\Miniconda3\lib\site-packages\fs\expose\dokan\__init__.py", line 976, in check_alive
    raise OSError("dokan mount process exited prematurely")
OSError: dokan mount process exited prematurely

Liryna · 2019-08-31T21:58:52Z

Will take a look when I can. Otherwise are you sure to use same 32/64 platform for dokan dll and python? Le sam. 31 août 2019 à 23:09, BiatuAutMiahn <notifications@github.com> a écrit :

…

I can't get this to work, Dokany v1.3.0.1000 Output: >>> from fs.memoryfs import MemoryFS >>> from fs.expose import dokan >>> fs = MemoryFS() >>> # Mount device mount point ... mp = dokan.mount(fs, "Q:\\") Traceback (most recent call last): File "<string>", line 3, in <module> File "C:\ProgramData\Miniconda3\lib\site-packages\fs\expose\dokan\__init__.py", line 1107, in _do_mount mount(fs, path, **opts) File "C:\ProgramData\Miniconda3\lib\site-packages\fs\expose\dokan\__init__.py", line 1011, in mount raise OSError("Dokan failed with error: %d" % (res,)) OSError: Dokan failed with error: -7 Traceback (most recent call last): File "C:\ProgramData\Miniconda3\lib\site-packages\fs\expose\dokan\__init__.py", line 983, in check_ready os.stat(path) FileNotFoundError: [WinError 3] The system cannot find the path specified: 'Q:\\' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<stdin>", line 2, in <module> File "C:\ProgramData\Miniconda3\lib\site-packages\fs\expose\dokan\__init__.py", line 1018, in mount check_ready(mp) File "C:\ProgramData\Miniconda3\lib\site-packages\fs\expose\dokan\__init__.py", line 985, in check_ready check_alive(mp) File "C:\ProgramData\Miniconda3\lib\site-packages\fs\expose\dokan\__init__.py", line 976, in check_alive raise OSError("dokan mount process exited prematurely") OSError: dokan mount process exited prematurely — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#256?email_source=notifications&email_token=ABA4S65LOCPF4HSSOJ3YJQTQHLMY7A5CNFSM4CJUAUMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5TVIEY#issuecomment-526865427>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABA4S642QUVFWBZSHNCQ3SLQHLMY7ANCNFSM4CJUAUMA> .

BiatuAutMiahn · 2019-09-06T19:23:59Z

Tried both, CWD was in the dokany dll folder

BiatuAutMiahn · 2019-09-06T19:42:45Z

I ran dokanctl to see options, enabled debug then found DebugView, tried to run mp = dokan.mount(fs, "Q:\\") again and I found this...

Liryna · 2019-09-06T20:00:59Z

Oh this is helpful! There is a version number in dokan py file normal. You would need to update the value but this also mean probably something in the python wrapper need to be updated also. Will try to take a look in the next weeks if you want. Best regards Adrien JUND Le ven. 6 sept. 2019 à 21:42, BiatuAutMiahn <notifications@github.com> a écrit :

…

I ran dokanctl to see options, enabled debug then found DebugView, tried to run mp = dokan.mount(fs, "Q:\\") again and I found this... [image: image] <https://user-images.githubusercontent.com/6149596/64455944-f6874500-d0bc-11e9-8c6a-3526448b86be.png> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#256?email_source=notifications&email_token=ABA4S62BCHHIX75RJ5Z76FTQIKXDNA5CNFSM4CJUAUMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6D3W2Y#issuecomment-528989035>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABA4S66HDVLUWVTKTTAXZ5DQIKXDNANCNFSM4CJUAUMA> .

BiatuAutMiahn · 2019-09-06T22:25:34Z

Changed:
DOKAN_MINIMUM_COMPATIBLE_VERSION = 100 # this is release 1.0.0
to
DOKAN_MINIMUM_COMPATIBLE_VERSION = 110 # this is release 1.0.0

and Q:\ has mounted!

Rondom · 2019-09-17T16:17:51Z

There is a version number in dokan py file normal. You would need to update
the value but this also mean probably something in the python wrapper need
to be updated also.

You need to a diff between dokan.h of 1.0.0 and latest Dokan and adapt the Python code accordingly. Otherwise you will get random crashes (which is why there are those version checks).

vpuhoff · 2019-12-04T01:22:58Z

https://github.com/nznaza/pyfilesystem_dokan

Liryna · 2020-02-14T10:21:12Z

If anyone would be interested, dokan-dev is still looking for an official dokan python wrapper!
There is already some code base available here and there, it might not be much work to put everything together and make it available to the community 👍

Ping @nznaza

nznaza · 2020-04-28T21:30:01Z

I have finally decided to look back into my repo. (When I first uploaded it I got burned out, and studies and whatnot got in the way)

Creating, Deleting and Renaming Folders work.
Copying Files works.
Creating, Deleting and Modifying files works too,
Moving files to another drive works too.
Moving/renaming files it's the only major bug that I noticed. I'm looking into it.
I have tested it with MemoryFS, but since it relies in PyFilesystem any should work.

If people test and report bugs I will happily look into them.

hugo-hur · 2022-08-20T04:47:00Z

Hi!

Any updates on this? Looking to use this to mount ramfs on Windows to display decrypted files using Python3.

hugo-hur · 2022-08-20T04:55:28Z

Could be willing to help with this, but would it be better suited here or the Dokany repo? Imho would be simpler to write an intermediate wrapper using C/C++ and then create python bindings to that intermediate wrapper optimized to use with Python?
@Liryna

hugo-hur · 2022-08-20T05:00:03Z

And then most of the work would be associated with updating the C/C++ intermediate binding interface?

Liryna · 2022-08-23T11:42:18Z

@hugo-hur
@kdschlosser Started a new python wrapper for Dokan https://github.com/kdschlosser/py_dokany
From his last comment dokan-dev/dokany#964 (comment) it looks like it is working and probably need to be finished / polished. Unfortunately, there was no update after that so we would need someone else to take over 💪

kdschlosser · 2022-08-25T23:51:08Z

No matter what I did it would not enumerate a directory properly. .. the sheer number duplicate requests was also an issue and made it not visible to use for what I had wanted to use it for.

Liryna mentioned this issue Aug 1, 2016

Update Dokan wrapper to 1.0.0 #258

Merged

arekbulski mentioned this issue Aug 1, 2016

Dokan failed with error -7 for dokany 0.8.0 and -5 for 0.7.4 #236

Closed

lurch mentioned this issue Aug 1, 2016

Dokany 0.8.0 #241

Closed

Fixing dokan support discussion... #256

Fixing dokan support discussion... #256

Comments

apocalypse2012 commented Jul 15, 2016

lurch commented Jul 15, 2016

zommuter commented Jul 15, 2016

Liryna commented Jul 27, 2016 • edited Loading

lurch commented Jul 27, 2016

arekbulski commented Jul 27, 2016

Liryna commented Jul 27, 2016 • edited Loading

arekbulski commented Jul 27, 2016 • edited Loading

Liryna commented Jul 27, 2016 • edited Loading

arekbulski commented Jul 27, 2016

Liryna commented Jul 27, 2016

Liryna commented Jul 28, 2016 • edited Loading

arekbulski commented Jul 28, 2016 • edited Loading

Liryna commented Jul 28, 2016

arekbulski commented Jul 28, 2016

Liryna commented Jul 30, 2016 • edited Loading

arekbulski commented Jul 30, 2016 • edited Loading

Liryna commented Jul 30, 2016

Liryna commented Jul 30, 2016 • edited Loading

arekbulski commented Jul 30, 2016

Liryna commented Jul 30, 2016

lurch commented Aug 1, 2016

Liryna commented Aug 1, 2016 • edited Loading

lurch commented Aug 1, 2016

Liryna commented Aug 1, 2016 • edited Loading

arekbulski commented Aug 1, 2016 • edited Loading

lurch commented Aug 1, 2016

Liryna commented Aug 1, 2016

JokerQyou commented Aug 18, 2016

Liryna commented Aug 29, 2016 • edited Loading

JokerQyou commented Aug 31, 2016

Liryna commented Aug 31, 2016

Liryna commented Sep 6, 2016

lurch commented Sep 7, 2016

Liryna commented Sep 20, 2016

Liryna commented Sep 22, 2016

apocalypse2012 commented Sep 22, 2016 via email

JokerQyou commented Sep 22, 2016

arekbulski commented Sep 22, 2016

lurch commented Oct 10, 2016

willmcgugan commented Oct 11, 2016

JokerQyou commented Jun 6, 2017 • edited Loading

Rondom commented Jun 6, 2017 • edited Loading

BiatuAutMiahn commented Aug 31, 2019

Liryna commented Aug 31, 2019 via email

BiatuAutMiahn commented Sep 6, 2019

BiatuAutMiahn commented Sep 6, 2019

Liryna commented Sep 6, 2019 via email

BiatuAutMiahn commented Sep 6, 2019

Rondom commented Sep 17, 2019

vpuhoff commented Dec 4, 2019

Liryna commented Feb 14, 2020

nznaza commented Apr 28, 2020

hugo-hur commented Aug 20, 2022

hugo-hur commented Aug 20, 2022

hugo-hur commented Aug 20, 2022

Liryna commented Aug 23, 2022 • edited Loading

kdschlosser commented Aug 25, 2022

Liryna commented Jul 27, 2016 •

edited

Loading

Liryna commented Jul 27, 2016 •

edited

Loading

arekbulski commented Jul 27, 2016 •

edited

Loading

Liryna commented Jul 27, 2016 •

edited

Loading

Liryna commented Jul 28, 2016 •

edited

Loading

arekbulski commented Jul 28, 2016 •

edited

Loading

Liryna commented Jul 30, 2016 •

edited

Loading

arekbulski commented Jul 30, 2016 •

edited

Loading

Liryna commented Jul 30, 2016 •

edited

Loading

Liryna commented Aug 1, 2016 •

edited

Loading

Liryna commented Aug 1, 2016 •

edited

Loading

arekbulski commented Aug 1, 2016 •

edited

Loading

Liryna commented Aug 29, 2016 •

edited

Loading

JokerQyou commented Jun 6, 2017 •

edited

Loading

Rondom commented Jun 6, 2017 •

edited

Loading

Liryna commented Aug 23, 2022 •

edited

Loading