Lloyd Dupont
11/3/2003 2:16:00 AM
Well, reading all of you writing a file system driver seems to be quite a
daunting task.
this being a personnal project I plan to release commercially one day, I
think I will postpone the "hard-drive" back end.
2 question remaining though:
- about this shell extension, could you give me one function name, I could
start search for ?
- How could it be that writting a driver is so hard ?
I just want to provide a bunch of function, I would guess about ten ?
the 4 basic C file IO function (open(), close(), read() write()) and maybe a
a few others ...
integrate won't be hard, I could always having 2 process which talk through
socket/pipe/shared memory ...
"Kirk Ferdmann" <kirk_ferdmann@nospam.hotmail.com> wrote in message
news:0bidnffH1skZLDiiRVn-sA@comcast.com...
> "Lloyd Dupont" <net.galador@ld> wrote in message
> news:u27CkSaoDHA.1632@TK2MSFTNGP10.phx.gbl...
> > I'm writting a C# network application, which could expose its data as a
> file
> > system.
> > I was thinking to have one back-end which would install itself as a
> > hard-drive on the client's computer, I would host the .NET runtime in my
> > driver, which has to be written in C, I suppose ?
>
> It don't think it's feasible given all the dependencies on things that are
> not available in kernel mode.
>
> > could some one gives me some direction on how to implement the driver ?
>
> Since you're talking about FS driver you will have to start by getting
> yourself a copy of IFS kit (cost about $1000). Documentation is included
in
> the kit. This will take you a few man-years to get implemented.
>
> Alternatively consider using shell namespace extensions. They are
documented
> in MSDN. And being completely user-mode beast they should integrate with
> .NET fairly easy. Not to mention that they are much easier to implement.
>
> -Kirk
>
>