12/22/2023 0 Comments Xnviewmp selectYou should either get familiar with these new folder structure ( Junction Points in Vista) or fill in a bug report for xnViewMp ( MP - Bug reports). > XnViewMP seems to be to modern for these dusty pre Vista MS-compatibility hacks. Staying in this path, both (TC and Explorer!!!) can't open a jpg with XnViewMP (but both can open a jpg with XnView Classic!!) Neither Explorer nor TC redirects this to "C:\User\\Desktop". One flaw in Explorer (and TC) is when you enter something like "C:\Documents and Settings\\Desktop" as path. TC shows this folder, but when you open this folder you are redirected to the correct path "C:\Users". with "C:\Documents and Settings").Īnd btw. MS created these junction only for old application with hard coded paths (that's why these Folders have hidden system attribute and ACLs to deny Read access to everyone)Įven W10 Explorer does not show this folder and does not allow to open this folder (eg. These Folders ("Documents and Settings" and localized versions like "Dokumente und Einstellung" in german XP) Backup applications must be capable of backing up and restoring junction points. For example, C:\Documents and Settings is now a junction point that points to C:\Users. For backward compatibility, the old locations have junction points that point to the new locations. wrote:For example, user data that was previously stored in the %SystemDrive%\Documents and Settings directory is now stored in the %SystemDrive%\Users directory. But it is hard to say this is a bug of TC or xnview. So that is the key reason for the problerm, TC did not replace the the symlink with real path just like what windows explorer does, this would cause some apps can not open the target file correctlly such as xnview. While it is OK to exec "D:\Softwares\XnViewMP\xnviewmp.exe" "C:\Users\xxx\Desktop\1.jpg" in a command window. I also tried to execute "D:\Softwares\XnViewMP\xnviewmp.exe" "C:\Documents and Settings\xxx\Desktop\1.jpg" in a command window, it also complains "file not found" same as in TC. That means windows explorer replace the symlink with the real path of the file,so it works OK. I found that TC Process Start with a Command Line such as "D:\Softwares\XnViewMP\xnviewmp.exe" "C:\Documents and Settings\xxx\Desktop\1.jpg", while windows explorer Pcocess Start with a Command Line "D:\Softwares\XnViewMP\xnviewmp.exe" "C:\Users\xxx\Desktop\1.jpg". I use Process Monitor to compared the difference of how TC and windows explorer open the file. Sorry I do not know how to check the symlink's permission, I checked the permissions of ""c:\Documents and Settings\xxx\Desktop\pic\1.jpg", the current user has the full controll of the file. Set the filter to the executable of the program showing the error message. If you use only xnviewmp for tagging, with export options enabled, obviously its not necessary to import anything, xnviewmp handles its database automatically. Tip: If you're familiar with Sysinternals Process Monitor, you can use that to find out what's wrong. XnViewMp 'Settings >Metadata > Export options' are used to enable keywords writing into embedded metadata as standard method for saving keywords. If you have another system or virtual machine, you can compare those permissions with it. Check the symlink's permissions whether or not they allow to read its target.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |