HardLinks, Junction Points, Object Ids and ADS   

This is my first post to this forum, you'll probably think my questions naive 
but I haven't found answers forthcoming elsewhere.

How can I find all the hardlinks for a file?  I was told that they were 
maintained in an ADS chain, but I cannot find anything that reveals sets of 
ADS's of that ilk.

Similarly how can I find out (aside from clicking on it) where a junction 
point takes me, and even more importantly how can I determine if a folder is 
the target of a junction point.

What are the rules that determine whether a "file" gets an Object Id.  On my 
XP system if I fie up notepad type some text and save the file as a text file 
- eg myfile.txt, then it gets an ObjectId, 

fsutil objectid query myfile.txt tells me this is so by displaying the 4 
ObjectId components, and ReckonWonders ADS Explorer confirms it is so within 
an objectid ADS - the ones with the network of cubes

I do exactly the same thing except I save the file with the name  
myfile.dat, then it does NOT get an object id

fsutil objectid query myfile.dat tells this is so - the specified file has 
no ObjectId. and ADS Explorer confirms it is so

Who decided that text files should have Object Ids and data files should not

Is this specified somewhere in the Registry, and how can I change it, I know 
 how to manipulate ObjectIds with fsutil, but automatic allocation of them 
would appear to be a function of file type, no matter which program I use - 
notepad, editor2, Zeus, Word, WordPad, OpenOffice or Delphad - text files (ie 
..txt's) get an objectid, whereas data files (ie .dats) do not.  This is the 
only consistent pattern I've found so far, otherwise whether or not a file 
has an object id seems completely arbitary.

When a file is copied from one NTFS volume to another I assumed that the new 
copy would show the volumeid of the volume from which it was copied as the 
BirthVolumeId, and similarly with the BirthObjectId, but this seems not to be 
the case.

Can someone recommend a book that documents the underlying functionality of 
NTFS, not to the extent as to allow one to reverse engineer it onto another 
O/S, but beyond telling one how wonderful it is and how it will transform 
one's life.  

Thanks PhilD

date: Fri, 24 Mar 2006 00:00:04 -0800   author:   Philip