How to register a custom parse method of my device object ?

Hi,

I am trying to modify the RamDisk.sys KMDF sample to provide some custom
path features for the files.

(For example, I should be able to address the second character in the
"Hello.txt" file on the RamDisk when I speciffy Z:\Hello.txt\2)

I came to know that Object manager takes care of parsing the paths and
dispatching the portions to associated devices.

But I am not sure how I receive this in my RamDisk code.

It seems Object manager would parse upto "z:\" and then would pass the
"hello.txt\2" to my RamDisk driver for parsing. Is that right? And which
function/event (or IOCTL) is responsible for this?

Please provide some information (or sources/links) in this regard.

Thanking you,
Yours,
P.Gopalakrishna.

pavel_a
Wed Nov 15 12:04:02 CST 2006

"P.GopalaKrishna" wrote:
> Hi,
>
> I am trying to modify the RamDisk.sys KMDF sample to provide some custom
> path features for the files.
>
> (For example, I should be able to address the second character in the
> "Hello.txt" file on the RamDisk when I speciffy Z:\Hello.txt\2)

This is quite unusual semantics, could you please explain more on this?
Do you want the users to be able to open the 2nd character,
delete, rename or lock it?

--PA

Don
Wed Nov 15 12:29:06 CST 2006

You cannot do this. The RamDisk sample provides a raw disk, there is a
file system layered on top of this that captures the files and deal with
the type of things you are talking about. At the disk level all you will
see are block operations, nothing with files.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply



"P.GopalaKrishna" <PGopalaKrishna@discussions.microsoft.com> wrote in
message news:B92C3E2F-69E6-42E8-A9A6-20461DF4A231@microsoft.com...
> Hi,
>
> I am trying to modify the RamDisk.sys KMDF sample to provide some custom
> path features for the files.
>
> (For example, I should be able to address the second character in the
> "Hello.txt" file on the RamDisk when I speciffy Z:\Hello.txt\2)
>
> I came to know that Object manager takes care of parsing the paths and
> dispatching the portions to associated devices.
>
> But I am not sure how I receive this in my RamDisk code.
>
> It seems Object manager would parse upto "z:\" and then would pass the
> "hello.txt\2" to my RamDisk driver for parsing. Is that right? And which
> function/event (or IOCTL) is responsible for this?
>
> Please provide some information (or sources/links) in this regard.
>
> Thanking you,
> Yours,
> P.Gopalakrishna.

PGopalaKrishna
Wed Nov 15 23:34:02 CST 2006



"Pavel A." wrote:

>
> This is quite unusual semantics, could you please explain more on this?
> Do you want the users to be able to open the 2nd character,
> delete, rename or lock it?
>
> --PA
>

Dear,

Actually the file system under question is a Record Oriented File System
with the ability to address and operate upon individual records in the file.

Consider the example of html file with internal addressible links, such as
http://www.geocities.com/krishnapg/createmovie.html#Introduction - where the
browser would directly take me to the "Introduction" link.

Similarily, we should have similar functionality but at file system level.
That is the concept.

Now, I am looking for the information on how to parse the extra "record
path" provided as part of the file path. Upto the file name, I would like the
underlying file system to take care of. But from there are on the remaining
"Record path" I would like to my driver to take care of.

Any suggestions on how to progress would be greatly appreciated.

Yours,
P.Gopalakrishna.

PGopalaKrishna
Wed Nov 15 23:35:01 CST 2006



"Don Burn" wrote:

> You cannot do this. The RamDisk sample provides a raw disk, there is a
> file system layered on top of this that captures the files and deal with
> the type of things you are talking about. At the disk level all you will
> see are block operations, nothing with files.
>
>
> --
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> http://www.windrvr.com
> Remove StopSpam from the email to reply
>



Dear Don Burn,

Actually the file system I am trying to conceptualize is a Record Oriented
File System with the ability to address and operate upon individual records
in the file.

I would like to records to placed in the file at the locations determined by
my driver so that I would be able to address and access them (lock, modify
etc..) directly from the user mode applications.

Consider the example of html file with internal addressible links, such as
http://www.geocities.com/krishnapg/createmovie.html#Introduction - where the
browser would directly take me to the "Introduction" link.

Similarily, we should have similar functionality but at file system level.
That is the concept.

Now, I am looking for the information on how to parse the extra "record
path" provided as part of the file path. Upto the file name, I would like the
underlying file system (Say NTFS) to take care of. But from there are on the
remaining "Record path" I would like to my driver to take care of.

Any suggestions on how to progress would be greatly appreciated.

Yours,
P.Gopalakrishna.

David
Thu Nov 16 00:20:14 CST 2006

I believe it is beyond your capabilities, but you have to write a file
system and not a storage device. RamDisk is a storage device driver that
happens to use memory instead of some other type of magnetic media.

"P.GopalaKrishna" <PGopalaKrishna@discussions.microsoft.com> wrote in
message news:C5E97028-D285-4F3A-B59F-F14658263F71@microsoft.com...
>
>
> "Don Burn" wrote:
>
>> You cannot do this. The RamDisk sample provides a raw disk, there is a
>> file system layered on top of this that captures the files and deal with
>> the type of things you are talking about. At the disk level all you will
>> see are block operations, nothing with files.
>>
>>
>> --
>> Don Burn (MVP, Windows DDK)
>> Windows 2k/XP/2k3 Filesystem and Driver Consulting
>> http://www.windrvr.com
>> Remove StopSpam from the email to reply
>>
>
>
>
> Dear Don Burn,
>
> Actually the file system I am trying to conceptualize is a Record Oriented
> File System with the ability to address and operate upon individual
> records
> in the file.
>
> I would like to records to placed in the file at the locations determined
> by
> my driver so that I would be able to address and access them (lock, modify
> etc..) directly from the user mode applications.
>
> Consider the example of html file with internal addressible links, such as
> http://www.geocities.com/krishnapg/createmovie.html#Introduction - where
> the
> browser would directly take me to the "Introduction" link.
>
> Similarily, we should have similar functionality but at file system level.
> That is the concept.
>
> Now, I am looking for the information on how to parse the extra "record
> path" provided as part of the file path. Upto the file name, I would like
> the
> underlying file system (Say NTFS) to take care of. But from there are on
> the
> remaining "Record path" I would like to my driver to take care of.
>
> Any suggestions on how to progress would be greatly appreciated.
>
> Yours,
> P.Gopalakrishna.
>
>
>