Strange behaviour on Read-Only volumes

The behaviour described in the bug report is either by design, or would be far too complex/time-consuming to be changed

Moderators: white, Hacker, petermad, Stefan2

Post Reply
Marlby23
Junior Member
Junior Member
Posts: 22
Joined: 2006-10-21, 17:57 UTC

Strange behaviour on Read-Only volumes

Post by *Marlby23 »

I have noticed that when i try to rename a folder in a read-only volume it gives a somewhat strange error (Error: Cannot read <folder path here>) instead of hinting to remove the write protection for ex. when trying to rename files on the same volume.

Also, when trying to create a new text file on the same read-only volume (via context menu) no error pops up, when hitting OK the dialog just closes as if the file was created (but it gives errors when creating a new folder trough)

Regards!
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48077
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

I guess that what happens is the following: TC tries to rename the file, which fails. Then TC tries to move (copy then delete) the files within the folder, which also fails with the read error you get.
Author of Total Commander
https://www.ghisler.com
Post Reply