I couldn't install beta 4 and now cannot install beta 5. I keep getting an error writing to file:
I guarantee that I can access, and write in the directory. I have full permissions for admin as well as for my username. http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/78/7752.Logos-Log-Files.zip
I have full permissions for admin as well as for my username.
Do you have ownership? - http://wiki.logos.com/Fixing_Logos_4_folder_Ownership
I have full permissions for admin as well as for my username. Do you have ownership? - http://wiki.logos.com/Fixing_Logos_4_folder_Ownership
Yes I do/and did. But I went ahead and "re-applied" ownership as per the wiki and that cured the problem. It's rather odd really. I have no idea how ownership ever would have changed, I am the only person who touches this computer.
I have no idea how ownership ever would have changed, I am the only person who touches this computer.
Maybe a Windows update?? Just a guess[:^)]
I've had this randomly happen to me too. That's why I went and figured out how to change the folder ownership. I wonder if it's a Windows 7 bug or a Logos bug.
I wonder if it's a Windows 7 bug or a Logos bug.
It could be a combination of both. Logos does a lot of checking for permissions and Windows supplies the answers...
I no longer remember if Windows keeps a log somewhere of file permission changes. (I believe it can be done in Linux) That said it would be interesting to log this behavior over time on the Logos directory and see what's happening.
Personally I suspect it was a Logos bug since Windows update would never have a reason to write to that directory or any of it's subs. More than likely it's occuring when administrative permission is needed to do something and the change is not reversed before continuing.
Of course I'm speaking only from very vague memories of what it's like to program anything.
Personally I suspect it was a Logos bug since Windows update would never have a reason to write to that directory or any of it's subs.
The particular \en-US folder that brought up the error did not exist prior to this 4.5 beta!
