- Sep
- 34
- 0
I'm sure I'm as confused as others with the forced use of JUNCTION'd directories.
It began when I mistakenly ran TC and other programs in non-admin mode though I was an admin. Programs showed filesaves were succesful to the 'C:\' root.
BUT a DIR from TC did not show the files?! Tried several times, several programs, same results. Those other programs could 'see' those files on the 'C:\' directory, but DIR from the TC command line did not?!!!
How am I supposed to find a file that was MICROSOFT-misdirected to a different directory than I was told it DID go to?
How should I run DIR to 'find' those files in the JUNCTIONed mis-direct(ory)?
DIR Help (in TC) implies that DIR /T:J C:\ should work. It doesn't, it shows 'incorrect use'
And what is '@Junction' in TC help? If I enter it at the cmd line, it's invalid..
It began when I mistakenly ran TC and other programs in non-admin mode though I was an admin. Programs showed filesaves were succesful to the 'C:\' root.
BUT a DIR from TC did not show the files?! Tried several times, several programs, same results. Those other programs could 'see' those files on the 'C:\' directory, but DIR from the TC command line did not?!!!
How am I supposed to find a file that was MICROSOFT-misdirected to a different directory than I was told it DID go to?
How should I run DIR to 'find' those files in the JUNCTIONed mis-direct(ory)?
DIR Help (in TC) implies that DIR /T:J C:\ should work. It doesn't, it shows 'incorrect use'
And what is '@Junction' in TC help? If I enter it at the cmd line, it's invalid..