Bulk Rename Utility

Could you please help.

Though BRC has the option /Clearr, which "clear the Read-only attribute", "take place after any renaming operation"

But the renaming operation (in any read-only file) never works in the first place.
If the folder/pattern-match contains only read-only files, no file is processed.
If the folder/pattern-match contains read-only files and few normal files, only the later are process, so the file is mix-up.

So anytime I perform BRC, though there is any read-only file or not, I always need to clear read-only manually (or using CMD) first to make sure BRC works correctly.

The Read-only attribute means locking file contents on editing, don't know why BRC treats it as locking filename change.

That problem happened to me since many year ago, in every time I use BRC, even run CMD in Admin doesn't help.

Could you please help?
______________________________________________________
UPDATE

Finally, it was documented, /inclr option is needed. Don't know why I never read it in BRC Manual. Thank you for your reading time.

Code: Select all

/INCLR - Include read-only files/folders. [b]By default, these are excluded.[/b]

I've searched more and see "Truth" said

truth wrote:...
The only exception is that read-only/hidden/system-files are auto-filtered before /pattern starts filtering

Actually, the read-only files are auto-filtered out of renaming process, whether /pattern is used or not.

Is there any way to fix it?

Finally, it was documented, /inclr option is needed. Don't know why I never read it in BRC Manual. Thank you for your reading time.

Code: Select all

/INCLR - Include read-only files/folders. [b]By default, these are excluded.[/b]

https://www.bulkrenameutility.co.uk/forum/viewtopic.php?f=8&t=2051

truth wrote...
If a filename meets /pattern's requirements, append will try to rename it (but can fail to permission issues)
The only exception is that read-only/hidden/system-files are auto-filtered before /pattern starts filtering.

prolinkerx wrote...
Actually, read-only files are auto-filtered out of renaming process, whether /pattern is used or not.

Noone implied /pattern causes the auto-filter.
Auto simply refers to a default behavior, which can sometimes be overridden.

BRC auto-filters Read-only/Hidden/System-files before any /switch.
Fortunately, we have InclR, InclH, & InclS to override this default behavior.
Also, the /clear & /set commands will only process after a successful rename.