Shell extension handling for Volm locking

NTFSD
1

I’ve an annoying problem when I was doing some protype work …

Basically I’m trying to block a volume using simple fs filter. So the volm
can be seen within the explorer, but it can not be opened, and since it is
at a volm level, chkdsk, format, etc all are blocked. BUT THE ANNOYING THING
IS THAT BY DEFUALT, EXPLORER HIGHLIGHTS ONE OF THE ICON (SAY A: OR B: OR
WHATEVER UNDER MY COMPUTER ), now if I try to double click say f: that is
under watch, the explorer provides a diaglog box … not accessible …, but
the heading of the box shows that x is not accessible, where x is the
current highlighted (active icon). It is surely in the domain of namespace
shell extension that explorer uses.

Is there anyway we can have the diag shows the right info ( on the title of
the diag window ) ?

-pro

2

Sorry for the typos ( meant to say prototype) …

  1. there is no requirement that the driver has to start at boot time, but
    I’ve not seen if there is any requirement to have a file filter tobe stated
    at boot time, might have missed a subtle point here !!

  2. It is in an early stage, so I need to test different ways, but for now at
    the CREATE dispatch entry, I’m using the IoCancel*() … logic (so
    essentially unrolling the work done by underlying storage stack
    ).

    3) Might have to look at how explorer interact with the shell namespace
    extension !

    -pro

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com]On Behalf Of Prokash Sinha
    Sent: Saturday, May 22, 2004 7:11 PM
    To: Windows File Systems Devs Interest List
    Subject: [ntfsd] Shell extension handling for Volm locking

    I’ve an annoying problem when I was doing some protype work …

    Basically I’m trying to block a volume using simple fs filter. So the volm
    can be seen within the explorer, but it can not be opened, and since it is
    at a volm level, chkdsk, format, etc all are blocked. BUT THE ANNOYING THING
    IS THAT BY DEFUALT, EXPLORER HIGHLIGHTS ONE OF THE ICON (SAY A: OR B: OR
    WHATEVER UNDER MY COMPUTER ), now if I try to double click say f: that is
    under watch, the explorer provides a diaglog box … not accessible …, but
    the heading of the box shows that x is not accessible, where x is the
    current highlighted (active icon). It is surely in the domain of namespace
    shell extension that explorer uses.

    Is there anyway we can have the diag shows the right info ( on the title of
    the diag window ) ?

    -pro

    —
    Questions? First check the IFS FAQ at
    https://www.osronline.com/article.cfm?id=17

    You are currently subscribed to ntfsd as: xxxxx@garlic.com
    To unsubscribe send a blank email to xxxxx@lists.osr.com