|
This is an issue with file permissions, as set by the installer.
DISCLAIMER: Tinker with your system at your OWN risk. Links to Microsoft articles on changing permissions are provided at the bottom of this post
I set up a test folder (c:\test), and gave all users full permissions for this folder.
I installed FSB to this folder. The main FSB Folder (c:\test\FSBuild) inherited the proper permissions. However, every single file (including the sub-folders) had only Administrators and SYSTEM authorized any access at all. Why USERS were not given read and execute (at the minimum) is beyond me. As an aside, other programs installed to c:\test had the appropriate permissions propagated properly.
I found the same problem with the .ocx files installed to \windows\system32. These files also had Administrators and SYSTEM only allowed access. When I changed permissions of the newly installed .ocx files to match the \system32 folder...viola! FSB runs properly on a limited account. I like FSB, but running it as an administrator is an unacceptable work-around for an installation issue.
|
Login
Register
FAQ
Search
