What do you mean with "The folders are read only and the files are not read only"?
We have to distinguish 3 reasons for files being not writable:
- A file has read-only attribute set. This cause for a write protection of a file can be easily detected by applications and UltraCompare recognize the read-only file attribute. Applications can also easily remove the read-only attribute from a file, modify it and set read-only attribute again. And copying a file over an existing file with read-only attribute is also easily possible.
- NTFS file permissions prevent applications modifying a file. This cause for a write protection of a file cannot be easily detected by applications. Normally applications can detect a deny on overwriting a file caused by NTFS permissions only when the application starts modifying the file. The permission to modify a file depends on current user privileges and the entire NTFS permissions heritage tree from drive down to the file. For example it is possible with NTFS permissions that a user can create a file and write to it in a directory, but cannot append something to an existing file in that directory, or modify the contents of an existing file in that directory. Yes, really, such fine differences in write access can be set up with NTFS permissions.
- Another application has a file currently open with file open respectively access flag shareDenyWrite set on opening the file. In this case any other application can read the contents of the file without any problem, but when it tries to modify the file, the write access is denied by the operating system. If you work with UEStudio without using temporary files, UEStudio opens all files with open flag shareDenyWrite. For more information about open flags see for example MSDN article about CFile::CFile.
I suggest to use free tool Process Monitor
(Microsoft) to find out the reason for write protection on files when you are working with UltraCompare. You have to start this tool as administrator as it needs administrator privileges to capture and log all file system accesses. On start of this tool a filter configuration dialog opens. I suggest to define Path contains directory name containing the write protected files then Include
as filter option. After pressing button OK, you see main window of Process Monitor. On the toolbar on right side uncheck from the 5 symbols all except the second one being a filing cabinet with a magnifying glass. Then only file system activity is displayed in the log below. Start your work with UC and UES and when UltraCompare displays the error message, look on the log if you can see the reason.