As an employee of a company that builds an NT file system (that is in no way
a competitor of NTFS, but which people want to use as an NTFS surrogate in
cluster environments), I’d love to see the whole FS information space get
changed to include an API that includes capability bits returned from a
capabilities/getfsinfo API; one bit says I support streams, one says I
support the change journal, one says I support Eas, one says I support
objects and the WinFS query interfaces, one says … you get the idea.
With an API like this, and a clear definition of what it means to turn on
the capability bit, application developers could lose their dependence upon
the name of the FS and just look at making sure that the functionality they
want to do something is available. One could also write apps that degrade
gracefully when, say, the change journal isn’t available.
There is little or no business incentive for Microsoft to create such an API
(if you can make a business case for it that makes sense from Microsoft’s
standpoint, I’d love to hear it), so I doubt we’ll see such an API in the
future. It would have been a great addition to the whole WinFS space if
were going to happen (where there is lots more functionality to be found
that most file systems won’t support), and AFAIK it’s nowhere to be found.
…dave (who has some modicom of understanding of the way MSFT works
internally…)
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tony Mason
Sent: Friday, April 08, 2005 4:30 AM
To: Windows File Systems Devs Interest List
Subject: RE: Re:[ntfsd] Explorer won’t copy named streams to my FS
I dug out what he said: Explorer is using the string NTFS. This has been
fixed for Longhorn, will be fixed for W2K3 SP1, and XP SP3. So it should
work now in W2K3 SP1. Since my understanding is that there won’t be an XP
SP3, I’m not sure what it would mean for XP.
It turns out that the comments indicate that MSDN examples also demonstrate
the technique of using the hard-coded name “NTFS”. It would be ideal to get
the samples in MSDN that show checking for the name to STOP doing that as
well and use the attribute bits instead.
The Exchange team should be similarly engaged and challenged to fix their
product as well - Dave Beaver’s comments are certainly directly applicable.
While I’m sure that this is nothing more than a simple implementation error,
clearly developers at Microsoft would want to correct such behavior because
with recent judicial scrutiny this might appear to be (to the non-technical)
to be a deliberate effort to prevent third party products working with
Windows.
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ladislav Zezula
Sent: Friday, April 08, 2005 2:16 AM
To: ntfsd redirect
Subject: Re: Re:[ntfsd] Explorer won’t copy named streams to my FS
Thanks for the information, although it is certainly not what I had
hoped
to hear, it certainly agrees with what I am seeing. I guess I figured
that
if anything would get it right, it would be the explorer (silly me).
Neal Christiansen once promised that the shell team will fix the hardcoded
“ntfs”, see here:
http://www.osronline.com/lists_archive/ntfsd/thread4946.html
(look at the end of the long thread)
L.
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17
You are currently subscribed to ntfsd as: xxxxx@osr.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: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com