Another issue (eventually)?
C:\Users\Martin\Pictures\NAS Pictures>tclsh
% pwd
C:/Users/Martin//NAS Pictures
% file normalize .
C:/Users/Martin/NAS Pictures
% file exists [file normalize .]
0
% file exists [pwd]
0
% cd ..
% pwd
C:/Users/Martin
% glob NAS*
couldn't read directory "C:/Users/Martin/NAS*": permission denied
% glob -types d -- *
couldn't read directory "C:/Users/Martin/*": permission denied
% glob *
couldn't read directory "C:/Users/Martin/*": permission denied
The current working Directory contains doubled slashes. Which is eventually another issue.
But strange is, that the process tclsh.exe, which is started with the user Martin does not seem to have the rights to list the Contents of my Profile Directory "%userprofile%".
Äähhm - permission denied?
Some thoughts about how I made the Symbolic Link:
1. opeend cmd.exe as Administrator
2. used "cd %USERPROFILE%\Pictures
3. used "mklink ..."
So the created Symbolic Link is inside the "user Profile" of the Administrator account, not inside mine.
So opening a tclsh in the "NAS Pictures" directory as admin causes no, absolutely no Troubles in accessing the directories and files inside this Directory.
Opening the tclsh as other user in the admin's "NAS Pictures" Directory, does not give a sign of insufficient permissions, but strange effects of not existing Contents.
Creating the Symbolic Link in the correct Directory, in "my" user profile, causes no troubles, so that the sort/rename/move tcl script runs without Troubles.
Please take my excuse, that I made my error, my confusing to yours.
The only Thing I would like to see different, is to have concrete error messages, instead of strange results of the file System API.
Best regards and shame on me
Martin