Windows NT4/2000 and above introduces new security levels for users that can restrict access to the registry and files that applications need to operate successfully.
The latest version of TICK v1.50+ (available soon) has had its setup application upgraded to allow restricted users to run the applications by adjusting the access level of the installation/data folders if required. Using versions of the applications before these versions may cause privileged instruction errors to be displayed at application startup. This problem generally does not affect Sound Control but for TICK you may need to give the restricted user write access to the Logs folder in the TICK installation folder.
If you are installing / uninstalling in a restricted user environment and the setup application is telling you to use an account with Administrator or Power User privileges follow the instructions below to temporarily give users the appropriate access level to install the application. Please note this does not apply to Windows NT4 users which should ensure they continue to run the application with a user with Administrator level privileges.
- Log In using your restricted user account credentials – the account where you want the application to be installed or uninstalled from.
- Click Start – Settings – Control Panel – Users and Passwords. You will need to enter the User Name and Password of an Administrator.
- View Properties on the restricted user you are installing the application for and click the Group Membership tab.
- Select Other – Administrators and click OK twice. You may be prompted to log out and back in again.
- Install the application by double clicking on the downloaded file. You should uncheck the Launch Application option to avoid it interfering with the following step.
- Once installation has completed use the Users and Passwords applet to return the user to their Restricted User access level. Like before you will be prompted to log off and back on again.
- Start – Programs – Application Name will contain shortcuts for starting the application, viewing the readme and displaying the help file.
You should avoid using the Run As command as this can confuse the installation process causing shortcuts to be created in the wrong user accounts.