On Thu, Oct 13, 2011 at 3:05 PM, Joe Caverly <> wrote:
> It looks like I am one of the few who are using NTFS File Streams to store more than one file.
> I guess they just never caught on, which is why Microsoft Backup is the only archiving tool than
> can store them.
They never caught on.
> To me, though, they are like a binder, which allows me to have all documents, spreadsheets, etc. for a project in one file.
Microsoft offered Microsoft Binder, which provided functionality like
this, as part of Office 95, 97, and 2000. It was originally intended
as a test host for OLE 2.0, and was discontinued after Office 2000.
(You can still read .OLB files on Office 2003 if you install a free
I've never used the functionality. I use directories, naming
conventions, shortcuts and other things to keep files that are part of
particular projects together. Making a backup is normally a matter of
making an archive of a project directory. I have no need to access or
preserve the alternate file streams.
As an aside, I really prefer using external utilities for such things
to having them as TCC built-ins. I can write scripts and create
aliases to customize things as required (like default options passed
to the programs.) Machines are fast enough that I see no real speed
difference in calling an external command to perform the action
instead of using an internal command (the time required to *perform*
the action will be equivalent), and the external utility may well do
things an internal doesn't.
I'm a little bemused by folks who want Rex to add everything
*including* the kitchen sink to TCC. (But then, I'm an old Unix guy,
where the shell language was intended as glue to tie together external
utilities to do this sort of thing. The idea that the *shell* should
do it might be met by blank incomprehension.)