An interesting registry fix

On 06/02/2017 12:31 PM, Paul wrote:
Fokke Nauta wrote:

I have a lot of rescue cd's that run on Linux. Very useful in case
something gets wrong with Windows.

Fokke

Until you need to work on a reparse point.

There are three standard constructions of reparse points,
for which a Linux developer could write filters in support.

And Windows 10 has at least one *custom* reparse
point, which spells "doom" for a home user. The
idea being, that only Windows will have the filter
for it. The Linux guys simply cannot keep up with
such "non-standard" extensions. This provides a
mechanism for Microsoft to throw a wrench in the
works.

Paul

If anyone is wondering what a "reparse point" is:

https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx

In message , T writes:
[]
If anyone is wondering what a "reparse point" is:

https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx

"A file or directory can contain a reparse point, which is a collection
of user-defined data. The format of this data is understood by the
application which stores the data, and a file system filter, which you
install to interpret the data and process the file."

Now, how about this:

A file or directory can contain a file, which is a collection of data.
The format of this data is understood by the application which writes
that file, and the OS file-association system knows how to select the
right application to interpret the date and process the file."

Now, despite the slip in the first quote (where the last word is "file"
rather than "reparse point"), I'm sure a reparse point _is_ not a file;
however, I don't find the quote explains to _me_ how they differ. (It
does proceed, soon getting well over my head - but, when the _beginning_
of the explanation _doesn't_ immediately explain to me how the two
concepts differ, I tend to think it isn't entirely me that's at fault,
but the quality of the explanation, at least partly.)
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Old soldiers never die - only young ones

J. P. Gilliver (John) wrote:
In message , T writes:
[]
If anyone is wondering what a "reparse point" is:

https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx


"A file or directory can contain a reparse point, which is a collection
of user-defined data. The format of this data is understood by the
application which stores the data, and a file system filter, which you
install to interpret the data and process the file."

Now, how about this:

A file or directory can contain a file, which is a collection of data.
The format of this data is understood by the application which writes
that file, and the OS file-association system knows how to select the
right application to interpret the date and process the file."

Now, despite the slip in the first quote (where the last word is "file"
rather than "reparse point"), I'm sure a reparse point _is_ not a file;
however, I don't find the quote explains to _me_ how they differ. (It
does proceed, soon getting well over my head - but, when the _beginning_
of the explanation _doesn't_ immediately explain to me how the two
concepts differ, I tend to think it isn't entirely me that's at fault,
but the quality of the explanation, at least partly.)

Directories are files.

Use NFI.exe for example, and dump your C: drive. A directory
is a file with a $I30 entry.

A reparse point likely stores information in two places.
There's a $REPARSE or something, for the metadata. And the
filter software reading those, has to interpret any custom
ones. So if you add "VFS" to your C: NFS, then a VFS
filter driver of some sort must be present to read the
VFS-specific data from $REPARSE.

That's without me looking up all the proper terms. That's
how I understand the concept.

It's intended as an extension mechanism, for adding features
to the file system. Which is of course, a bad idea (from a standardized
behavior perspective). For example, imagine mounting a disk
with a VFS on it, on your old Win2K machine. What happens then ?

"Reparse Point" is the general escape mechanism.
"Junction Point" is a specific flavor of Reparse Point, standard
and available in more than one OS. Junction Points can be
manipulated with the "Junction.exe" program on Sysinternals.com .

Paul

In message , Paul
writes:
J. P. Gilliver (John) wrote:
In message , T writes:
[]
If anyone is wondering what a "reparse point" is:


https://msdn.microsoft.com/en-us/lib.../aa365503(v=vs
.85).aspx
"A file or directory can contain a reparse point, which is a
collection of user-defined data. The format of this data is
understood by the application which stores the data, and a file
system filter, which you install to interpret the data and process
the file."
Now, how about this:
A file or directory can contain a file, which is a collection of
data. The format of this data is understood by the application which
writes that file, and the OS file-association system knows how to
select the right application to interpret the date and process the file."
Now, despite the slip in the first quote (where the last word is
"file" rather than "reparse point"), I'm sure a reparse point _is_
not a file; however, I don't find the quote explains to _me_ how they
differ. (It does proceed, soon getting well over my head - but, when
the _beginning_ of the explanation _doesn't_ immediately explain to
me how the two concepts differ, I tend to think it isn't entirely me
that's at fault, but the quality of the explanation, at least partly.)

Directories are files.

Use NFI.exe for example, and dump your C: drive. A directory
is a file with a $I30 entry.

Yes, I'd forgotten that, but very true: I think of a directory as a list
of filenames (with a clever [?] workaround to allow for ones longer than
11 characters - IIRR, uses further 11-character ones with a continuation
bit, in effect) and pointers to start positions on the disc. Plus, these
days, odd extra bits of information such as icons, preferred filetypes,
etc., though those are often in a file _in_ the directory called
desktop.ini, at least under Windows.

So, in one way, _everything_ is a file - but ...

A reparse point likely stores information in two places.
There's a $REPARSE or something, for the metadata. And the
filter software reading those, has to interpret any custom
ones. So if you add "VFS" to your C: NFS, then a VFS
filter driver of some sort must be present to read the
VFS-specific data from $REPARSE.

That's without me looking up all the proper terms. That's
how I understand the concept.

.... which is almost infinitely better than I do. I _hope_ I can get by
for the rest of my computing life without needing to (-:!

It's intended as an extension mechanism, for adding features
to the file system. Which is of course, a bad idea (from a standardized
behavior perspective). For example, imagine mounting a disk
with a VFS on it, on your old Win2K machine. What happens then ?

"Reparse Point" is the general escape mechanism.
"Junction Point" is a specific flavor of Reparse Point, standard
and available in more than one OS. Junction Points can be
manipulated with the "Junction.exe" program on Sysinternals.com .

Paul

I've looked at that in the past, but not _really_ grasped what I'd be
doing with it. I have great respect for most things on Sysinternals,
especially if the name R..ovitch is associated with them; and the fact
that I don't understand much about what this one does does not diminish
my respect for it.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

If it ain't broke, don't download updates.
- Al Drake in alt.windows7.general, 2015-4-4

On Fri, 02 Jun 2017 18:05:47 -0400, Paul wrote:
Use NFI.exe for example, and dump your C: drive. A directory
is a file with a $I30 entry.


I kept trying to understand how "a hundred-and-thirty-dollar entry"
could create a directory from a file. Finally I realized it must be
dollar sign (not used as currency) and then I (eye) thirty.

I think I need to choose a better font for my news client!

--
Stan Brown, Oak Road Systems, Tompkins County, New York, USA
http://BrownMath.com/
http://OakRoadSystems.com/
Shikata ga nai...