Hi get101,
The checkbox actually inserts the following code into your script:
Get System Setting Administrator Rights into CHECKSYSTEM
if Variable CHECKSYSTEM not Equals TRUE
MessageBox: $TITLE$ Setup Error, This product requires at least Administrator Privileges.$NEWLINE$$NEWLINE$Setup cannot continue.
Terminate Installation
end
Unless I'm entirely sure that the Install doesn't need admin rights, I check that box to require admin rights.
User rights can be different on any Pc. So if you don't want to require admin rights, you have to check the installing user's rights on every resource, you want to modify.
I started writing a dll that can check the access rights for Registry Keys, Filesystem Objects and so on. A relatively easy starting point is at:
http://smsoft.ru/en/checkfileaccess.htm
So with that I can start without admin rights, but as soon as I find out that the currently logged on user doesn't have some rights to modify a resource that I need to modify, I present the dialog to require admin rights. Technically it would be more appropriate to state what rights the user is missing that the installer requires. But if the user sees this technical stuff he doesn't understand, he thinks something's wrong with your application.
Registering a library writes to the HKLM Registry key, to which regular users usually don't have write access.
You could tell the administrator to give your users all the rights they need, but usually it's easier to require admin rights for the install.
Rgds
Richard
