While debugging a win2k pro sp4 system with windbg, I’m getting an assert as
soon as the user-mode part of my system starts. This has been going on for
a while now, and I finally have to time to not “ignore” it. My FSD starts
type=2, then sometime later the user-mode part starts and iosubs.c generates
the following assert:
*** Assertion Failed: !(FileObject->Flags & FO_DIRECT_DEVICE_OPEN)
*** Source file: D:\nt\private\ntos\io\iosubs.c, line 7286
My FSD “sees” a CREATE irp, and the file object has no name, so it’s an open
for the volume, and this flag is infact set in the file object. After I let
the IRP complete in my driver, this assert happens.
Can anyone tell me what is going on here? I suppose that I shouldn’t turn
off this flag in the file object (but when I do, the assert goes away!).
Please advise…
Thanks and regards,
GAP