Greg,
I talked with the shell team and they are currently checking for NTFS to
determine if the file system supports multiple streams or not.
They have already fixed this for longhorn so that they check the volume
properties.
They are willing to fix this for XP SP3 and for SRV03 SP1. Would that
be sufficient to meet your needs?
Neal Christiansen
Microsoft File System Filter Group Lead
This posting is provided “AS IS” with no warranties, and confers no
rights.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Neal Christiansen
Sent: Monday, July 12, 2004 8:24 PM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] Re:Re:streams - why should I do this?
Greg,
I am seeing if I can track someone down from the shell team who can let
me know what is going on. What OS versions have you tried this on?
Sometimes it is a mystery to the file system group as to why the shell
does what it does.
It is probably a bad idea to have your file system identify itself as
NTFS.
Neal Christiansen
Microsoft File System Filter Group Lead
This posting is provided “AS IS” with no warranties, and confers no
rights.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Greg Pearce
Sent: Monday, July 12, 2004 11:18 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Re:Re:streams - why should I do this?
Thanks Max… that clears that up.
Tony said that I must be missing something still though.
In this attempt to support ADS in my FSD, when my FSD gets an
IRP_MJ_QUERY_VOLUME_INFORMATION, I turn on FILE_NAMED_STREAMS in the
filesystem attributes field of the FILE_FS_ATTRIBUTE_INFORMATION
structure,
and set the FileSystemName field to “NTFS”, and explorer stops whining
about
losing the ADS information. I never get warned that I would lose ADS
info
when doing a copy from the command prompt. I still need to put some
meat in
there to parse the name correctly and some other things, but it looks
like
it would work if all that code were in place.
What am I missing, besides MJ_QUERY_INFORMATION/FileStreamInformation
support?
Getting back to a previous question that I had, is it a problem legally
to
tell callers of QUERY VOLUME that I’m “NTFS”, even though I don’t
support
all the stuff NTFS does? It seems like Explorer should have a better
way to
determine if a file system supports ADS instead of relying on the file
system’s internal “name”. Anyone care to comment? Anyone from
Microsoft?
It is greatly appreciated!
Thanks again and again
Greg
“Maxim S. Shatskih” wrote in message
news:xxxxx@ntfsd…
> Sorry, this is not FSCTL. This is
> MJ_QUERY_INFORMATION/FileStreamInformation, which is also absent in
CDFS.
This
> thing enumerates all attribute streams in the file.
>
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> xxxxx@storagecraft.com
> http://www.storagecraft.com
>
> “Greg Pearce” wrote in message
> news:…
> > Hey Max! You’ve just hit on some information that I would like to
find
out
> > more about; i.e. what FSCTLs are required for ADS? Where can I find
this
> > kind of stuff documented?
> >
> > Thanks,
> >
> > Greg
>
>
—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com