Hi all,
I am writing Metro App and MiniFilter driver to secure File/Folder, I need the following things
1-Metro App should be capable to communicate to MiniFilter Driver.
2-Metro App should be capable to deploy MiniFilter Driver.
Thanks
Is there a question in here? It seems to be a couple of statements.
Are you asking HOW to accomplish this?
If so, go look at FltCreateCommuncationPort in the WDK, it will explain one common method for communicating between a user mode application and a kernel mode driver.
As for how a user mode application can install a driver, there are lots of different ways of accomplishing this. Why don’t you start by looking at the “setup” examples in the WDK, since it shows a variety of ways of installing drivers. Another place to look would be to start with this description of the CreateService function provided by one of the myriad of base windows DLLs: http://msdn.microsoft.com/en-us/library/windows/desktop/ms682450(v=vs.85).aspx. This communicates with the “Service Control Manager” and can be used to dynamically install, uninstall, start and stop specific drivers if you would prefer to do it that way.
Tony
OSR
Its not clear that a ‘metro’/‘modern’/‘windows store’ app can do any of
those things however. If I’m wrong, I’d love to hear about it.
If you have an actual bit of hardware that gets plugged in and enumerated
by an existing bus driver, no problem, you can associate your app with the
hardware id and the app package can be found and deployed from the store.
Otherwise it seems you are out of luck, at least if you are trying to stay
within the pure app model.
t.
On Mon, Sep 17, 2012 at 11:52 AM, Tony Mason wrote:
> Is there a question in here? It seems to be a couple of statements.
>
> Are you asking HOW to accomplish this?
>
> If so, go look at FltCreateCommuncationPort in the WDK, it will explain
> one common method for communicating between a user mode application and a
> kernel mode driver.
>
> As for how a user mode application can install a driver, there are lots of
> different ways of accomplishing this. Why don’t you start by looking at
> the “setup” examples in the WDK, since it shows a variety of ways of
> installing drivers. Another place to look would be to start with this
> description of the CreateService function provided by one of the myriad of
> base windows DLLs:
> http://msdn.microsoft.com/en-us/library/windows/desktop/ms682450(v=vs.85).aspx.
> This communicates with the “Service Control Manager” and can be used to
> dynamically install, uninstall, start and stop specific drivers if you
> would prefer to do it that way.
>
> Tony
> OSR
>
>
> —
> NTFSD is sponsored by OSR
>
> For our schedule of debugging and file system seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
Ah, good to know. So apparently a “metro” app isn’t one that works with the “metro UI” but rather one that has some restrictive subset of the normal Windows interface. That does sound rather limiting if true and would be one more reason to avoid the Windows app store model.
Personally, I’m still trying to figure out how to do almost anything with the new Windows UI (formerly “metro” now known as something else…) I did at least figure out how to get a command prompt up, so I can get most everything done that I need. Now I’m just waiting for my new touchscreen monitors to arrive… 
Tony
OSR
This works until you try and eat lunch and do some work. At some point you
have to stop because you can’t read the screen anymore. Yeah keyboards
aren’t any cleaner, but at least I don’t have to look at/through them.
I think it is best to think of metro apps as being like an OS app in the
NT4 era. It happens to run with the same kernel and file system, but…
thats about it. However to confuse things these apps still use the win32
subsystem and much of the underlying infrastructure of COM is re-used and
some of win32 API will still work, so that you might think that it looks
more familiar than it is. The runtime launch processes with a very
restricted token, and counts on external broker processes to do most i/o on
behalf of applications through tightly contracted RPC interfaces.
Pretty sure software device drivers where right out from the start by
design.
t.
** **
Personally, I?m still trying to figure out how to do almost anything with
the new Windows UI (formerly ?metro? now known as something else?) I did
at least figure out how to get a command prompt up, so I can get most
everything done that I need. Now I?m just waiting for my new touchscreen
monitors to arrive? ;-)****** **
Tony****
OSR****
** **
NTFSD is sponsored by OSR
For our schedule of debugging and file system seminars visit:
http://www.osr.com/seminarsTo unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
On Mon, 17 Sep 2012, Tony Mason wrote:
Personally, I’m still trying to figure out how to do almost anything with the new Windows UI (formerly “metro” now known as something else…) I did at least figure out how to get a command prompt up, so I can get most everything done that I need. Now I’m just waiting for my new touchscreen monitors to arrive…
Since we are talking Metro anyway; is it true that you can’t compile
command line programs with the new Visual Studio 2012? (I like to compile
simple testapps with the WDK but sometimes its more convenient to create a
skeleton project in VS)
Bo Brantén
“Bo Brantén” wrote in message news:xxxxx@ntfsd…
Since we are talking Metro anyway; is it true that you can’t compile
command line programs with the new Visual Studio 2012?
Full versions support console applications. The Express edition was going to
allow Metro only, though it looks like they balked and addressed that with
the, “Express 2012 for Windows Desktop” SKU.
-scott
“Bo Brantén” wrote in message news:xxxxx@ntfsd…
On Mon, 17 Sep 2012, Tony Mason wrote:
Personally, I’m still trying to figure out how to do almost anything with
the new Windows UI (formerly “metro” now known as something else…) I
did at least figure out how to get a command prompt up, so I can get most
everything done that I need. Now I’m just waiting for my new touchscreen
monitors to arrive…
Since we are talking Metro anyway; is it true that you can’t compile
command line programs with the new Visual Studio 2012? (I like to compile
simple testapps with the WDK but sometimes its more convenient to create a
skeleton project in VS)
Bo Brantén
VS2012 has at least the same templates as VS2010. You can compile command
line programs.
Bill Wandel
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bo Brant?n
Sent: Tuesday, September 18, 2012 5:49 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Metro App accessing to driver
On Mon, 17 Sep 2012, Tony Mason wrote:
Personally, I’m still trying to figure out how to do almost anything
with the new Windows UI (formerly “metro” now known as something
else…) I did at least figure out how to get a command prompt up, so
I can get most everything done that I need. Now I’m just waiting for
my new touchscreen monitors to arrive…
Since we are talking Metro anyway; is it true that you can’t compile command
line programs with the new Visual Studio 2012? (I like to compile simple
testapps with the WDK but sometimes its more convenient to create a skeleton
project in VS)
Bo Brant?n
NTFSD is sponsored by OSR
For our schedule of debugging and file system seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer