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.

Yes, AV are rude with drivers. :( We fixed symantec and another AV during the process. We will look into it !

I am the author of WinFsp. Thanks for mentioning it.

WinFsp properly supports the filter manager, which means that AV filters should work without problems.

Like dokan before it was tested :wink:

I am not sure what that means.

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.

Bill

>expect BSODS

I wrote a (unreleased I believe) filesystem with this a couple years ago and my machine would reliably BSOD every time Windows tried to do the mandatory automatic updates. My friends say you can disable that but I haven't used Windows often enough since then for it to be a problem.

Dokany is a fork of legacy dokan abandonned by the creator. It has a lots of changes and fix since you tested !

Why would a user-space file system driver cause BSOD?

As I understand it, the BSODs happened when virus scanners hit a Dokany FS. Interaction between two different hooks into the kernel's FS layer, I guess.

There's a kernel-mode component here too - Dokan.sys I think. It's the equivalent to fuse.ko. I imagine a bug in FUSE could cause a kernel panic as well.