Dokan calls IoRegisterFileSystem on disk file systems, but does not appear to do so on network file systems. FsRtlRegisterUncProvider is the pre-Vista MUP and does not do it for you.
WinFsp has multiple integrated test suites, some of which Dokany uses (with tests missing/disabled). It also has hundreds of users at this point.
"WinFsp has multiple integrated test suites, some of which Dokany uses (with tests missing/disabled)." > really? I'm generally quiet and let Liryna talking but your thread hijacking to promote your product each time there is an official Dokan publication start to be annoying. This test suite was one of your contribution on Dokany before you stopped being involved on the project so of course we are... (it will soon be replaced by another test suite btw). Anyway, let's stop the argument here...
Maxhy, I understand that you are annoyed. Please recall that:
1. The only Dokany thread that I have explicitly mentioned WinFsp is this one (and only after someone else mentioned it). I avoided doing so on your Reddit thread, for example. You may consider that my original message to the Dokany mailing list was promotion, but from my perspective at least it was simply a message to like minded people.
2. That until Lyrina's message(s) in cygwin-apps, where she effectively sabotaged my ITP submission, I was willing to work with Dokany and I said so in a message to the Dokany list.
The truth is that until that ITP submission point I was not bothering anyone and was just working on my project. The only two times that I made comments on Dokany vs WinFsp was when I was explicitly asked: one time by you on the Dokany list and one time on Reddit in WinFsp's own promotion thread.
So I agree with you: let's stop the arguments here. I am willing to stop hijacking threads or trying to sabotage your project's progress. However I also want Dokany to stop insinuating that WinFsp is not being tested (where my argument about the test suites stems from) or sabotage WinFsp's progress.
All issue BSOD reported during the 9 months of testing of this version has been fixed (4 release candidate was made). Latest release candidate was already used on products. But it is still recommended using virtual machine when developing your file system in case of.
I don't doubt you've made lots of fixes, but what about the issue I linked above? That's probably a case of an AV filter driver doing something silly, but still.
I used to use https://liquesce.codeplex.com/ which I believe was based on Dokan prior to being silently abandoned by the developer.
Is Dokan the appropriate library to build a disk pooling solution on top of? If so, can you recommend any such projects?
TLDR - Create a "Dokan" folder on each of my 5 physical drives, present a drive to my OS that shows all files from these 5 drives as if they were one physical drive.
Yes Dokan is able to do what you describe.
There is a mirror example in the repository that mirror a device or folder.
With a little of changes based to the mirror, you can create a sub directory for each of your devices in on folder.
(Create a fake main directory that list all directories of your device and after reroute all file opening request to the right device)
