Enabling QVCS-Pro IDE integration for non-Admin users.

I don't have admin rights on my machine. How do I get QVCS-Pro's IDE integration to work correctly?

Microsoft's SCC API makes use of several registry keys that non-admin users are not allowed to define or modify. This makes it impossible for a non-admin user of QVCS-Pro to make the registry changes that are required.

The solution is to ask someone who does have admin rights on your machine to make several changes to your registry. Here are the steps they need to follow:

• Login to your machine as the local administrator (or as a user who has those rights).
• Run the regedit utility.
• In RegEdit, you will need to add the following 2 registry keys:

  HKEY_LOCAL_MACHINE\SOFTWARE\QumaSoftware
HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider

• Next, you will need to alter the permissions for these registry keys so that a non-admin user will have the rights needed to make changes to them. To do that, select the registry key, right click to get the context menu, and from the context menu, select the 'Permissions...' menu option.
• On the permissions dialog, click on the 'Add...' button

  

• On the Select Users or Groups dialog, click in the 'Enter the object names to select' edit box, and type 'Everyone' (no quotes). Then click the 'Check Names' button. The 'Everyone' string should now be underlined. Click the 'OK' button.

  

• On the permissions dialog, select the 'Everyone' group, and then enable the 'Full Control' and 'Read' permissions in the 'Allow' column. Then click the OK button.

  

• Repeat these same steps for the

  HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider

  registry key.

• Exit RegEdit. The admin user can now logoff.
• Login as the non-admin user.
• Start QWin3.exe. Select the Admin/IDE Integration menu, and choose the 'Make QVCS the default Version Control tool' menu option.

  

  When you select this menu option, QWin attempts to modify the registry so that a Microsoft SCC compliant IDE will recognize that QVCS is the default version control provider.

• That should do it. You can verify that you are able to make the necessary changes to the registry by running regedit to see if you were able to make changes to the

  HKEY_LOCAL_MACHINE\SOFTWARE\QumaSoftware
HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider

  registry keys.