NTobject namespace (was: "Interest in ReactOS" / "Drive letters")

[Martin Fuchs]

Hello,

to make visible as a picture what has been discussed in the recent discussion about drive letters, in which way to mount them and eventual extension for new file system standards, I want to post a screenshot of the new ROS Explorer version.

I implemented display of NT object namespace. So you can now see the internals of NTDLL, where and how drive letters are mounted and much more. Even the registry can been seen as an integrated part of NT object namespace.

--
Martin Fuchs
[e-mail]

[Robert K.]

HEy, this looks really nice!
And if these ?... names are taken by apps (which should be) it would 
imply that we may have also other "drive letters". For instance whole words.
At least, I think, there are too many object directorys visible. What 
about reducing it to just ??  ?
On the other hand it's also nice to look into \Devices

Martin Fuchs schrieb:
> Hello,
>
> to make visible as a picture what has been discussed in the recent discussion about drive letters, in which way to mount them and eventual extension for new file system standards, I want to post a screenshot of the new ROS Explorer version.
>
> I implemented display of NT object namespace. So you can now see the internals of NTDLL, where and how drive letters are mounted and much more. Even the registry can been seen as an integrated part of NT object namespace.
>
> --
> Martin Fuchs
> [e-mail]
>
> ros-general mailing list
> [e-mail]
> http://reactos.com/mailman/listinfo/ros-general

[Martin Fuchs]

> Hey, this looks really nice!
> And if these ?... names are taken by apps (which should be) it would 
> imply that we may have also other "drive letters". For instance whole words.

Well, the syntax is a bit more complicated, for example \?\c:\reactos, but it
would be possible to implement longer drive names this way.
Of course there are some limitations. The API function GetLogicalDrive()
is only capable to return a bit mask of existing drive letters. (max. 26 out of 32)
But this is already superseded by GetLogicalDriveStrings(), which would be
compatible to "drive words".

Regards,

Martin