[EDIT: Tomos posted much of what I said below before I got a chance -- however one note is that the "read-only" that FARR is talking about is just its internal decision, and has nothing to do with read-only flags that windows puts on files, so no point looking at those]
FARR treats its built-in alias files as read-only because they would get overwritten on an update.. But the myaliases.alias file should not be in the same place and so should not be treated that way.
I wonder if perhaps your "myaliases.alias" file was put by you in the same folder path as the built-in aliases?
In general, assuming a non-portable install, the built-in aliases will be in C:\Program Files (x86)\FindAndRunRobot\AliasGroups\Installed\
And your custom alias file(s) will be in: C:\Users\USERNAME\Documents\DonationCoder\FindAndRunRobot\AliasGroups\MyCustom\
Check to see if they aren't where they should be. You can exit farr and move them if not.
If that's not the problem, make sure that you aren't trying to run FARR portably (by editing the configdir.ini file) from a directory where that would be illegal (like C:\Program Files..).. One of the ways people get into trouble is by copying a portable install to the normal program files directory..
Let me know if you get it solved.
I think perhaps one thing I could add to FARR is have it show the absolute directory where an alias file is located when it's selected, and maybe check for the cases where the myalias file is where it shouldn't be.. Maybe a hint for people to explain WHY an alias file is being treated as read-only and how to deal with that if they want to modify such an alias.