If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Rate Thread | Display Modes |
#16
|
|||
|
|||
Explorer Duplicate Listings
OK, that yields a very long text file emdimg :
File 269068 \Program Files\Common Files\Microsoft Shared\VS7Debug\vsjitdebuggerps.dll $STANDARD_INFORMATION (resident) $FILE_NAME (resident) $FILE_NAME (resident) $DATA (nonresident) logical sectors 58186736-58186943 (0x377dbf0-0x377dcbf) File 271592 \Windows\MICROS~1.NET\FRAMEW~1\V40~1.303\NGEN_S~1. LOG $DATA (nonresident) logical sectors 132997000-132999919 (0x7ed5f88-0x7ed6aef) What now ? ... |
Ads |
#17
|
|||
|
|||
Explorer Duplicate Listings
SteveGG wrote:
OK, that yields a very long text file emdimg : File 269068 \Program Files\Common Files\Microsoft Shared\VS7Debug\vsjitdebuggerps.dll $STANDARD_INFORMATION (resident) $FILE_NAME (resident) $FILE_NAME (resident) $DATA (nonresident) logical sectors 58186736-58186943 (0x377dbf0-0x377dcbf) File 271592 \Windows\MICROS~1.NET\FRAMEW~1\V40~1.303\NGEN_S~1. LOG $DATA (nonresident) logical sectors 132997000-132999919 (0x7ed5f88-0x7ed6aef) What now ? ... Well, you're looking for the *two* \Program Files entries you claim are somehow in the file system at the same time. If they existed, they may not be right next to one another. And other similar looking paths will come right after them, like your \Program Files\Common Files... example. That's the entry for a filenum which is a folder just below Program Files. ******* Files that are hardlinked, have two or more $FILE_NAME (resident) $FILE_NAME (resident) A file stored in WinSXS can be the same as a file in System32. There can be one set of clusters, and two filenames for the same clusters. Even if one $FILE_NAME is deleted by the user, the second $FILE_NAME continues to exist. So to "erase" the file, requires removing all the pointers to it. It's unfortunate that the NFI program did not print out the value of each of those. As it would make interesting reading. Your problem is *not* related to that mechanism, and I'm just explaining why one of your copied examples has two entries. It happens to be a hardlinked fine that likely exists in WinSXS as well. Since there is no tool to print out hardlinks, I have to resort to Linux and "ls -i" to print out the Linux fake inode number, which is actually filenum from the NTFS file system. That's how I can tell what files are "the same" from a hardlinked point of view. But this isn't something we need to research right now, as it has nothing to do with your problem. I'd hoped Command Prompt and "dir" would show only one "Program Files", as that would be easier to explain. If "dir" sees it too, that means it's "real" and we have to figure out what character set trick is being used to make a fake one possible. I don't hold out a lot of hope for NFI, but it can print almost everything on C: . There are only four entries it refuses to print (and they are likely access denied, even to adminstrator). You might spot this, by virtue of some low filenum values have "gone missing". Somewhere around "filenum 20" or so. That's all I remember about what it won't print. No utility seems to show absolutely everything. But NFI comes close. Paul |
#18
|
|||
|
|||
Explorer Duplicate Listings
SteveGG wrote:
I tried your "solution(s)" and they didn't work, so I said so. Oh, you *said* so. To WHOM? That would be to Paul, not me. Then I see with your next reply to Paul that you are again vague and deliberately so. Paul needs to shake out the hook. |
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|