• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 55 subscribers
  • Views 2147 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Loading a project in CCS 3.3 requires Admin privileges?

Kevin Kaster
Prodigy 25 points

Other Parts Discussed in Thread: CCSTUDIO

Hello,

I am using CCS 3.3.82.13 with normal User privileges on Windows XP SP2. When I load a Project, I get the following warnings in pop-up windows:

"CRegistryInfo::GetSABiosRegKey() could not find BIOS registry entries."

and

"Incorrect %BIOS_INSTALL_DIR% variable setting detected."

I do not get these warnings when running as an Administrator.

My TI Apps engineer told me to use regedt32 to modify some registry entries to give "User" "Full Permission". But modifying HKEY_CLASSES_ROOT in this way, causes irrepairable damage to my computers. Specifically, many of my machine services cannot run including my wireless application. The only way to "fix" these problems is to restore the registry, just changing the permissions back is not enough.

My local IT person said:

"Modifying permissions at the root level of the Registry (HKCR) will overwrite other special permissions that are assigned down level.  The vendor should provide you a listing of the specific keys their application needs permissions to and I bet you won’t have the other side effects."

But so far my TI Apps engineer has been unable to get any information on the specific keys.

Can anyone help me out?

Thanks!

Kevin Kaster

 

  • 0
    TI__Guru**** 480451 points

    Hi Kevin,

    Yes, the registry keys of interest are HKEY_LOCAL_MACHINE\SOFTWARE\GODSP, HKEY_LOCAL_MACHINE\Software\Texas Instruments and HKEY_CLASSES_ROOT. AFAIK, tweaking those registry entries are the only workaround to get CCS running on a user account...

    ki


  • 0 in reply to Ki
    TI__Guru**** 480451 points

    As for which specific keys in HKEY_CLASSES_ROOT... there are a lot of them, hence the recommendation to change them all. I don't think is a comprehensive list of them, making it difficult to modify the specific ones individually.

  • 0 in reply to Ki
    Prodigy 25 points

    Thanks for the quick replies!

    Yes, what you say is exactly what I was told to do. And it does work. Unfortunately it messes up other things on my computer. I have tried this on two desktop PC's and a laptop PC, so it' s not just a problem with a specific computer.

    Has TI had any other complaints about this? I can't believe I'm the only one...

    Maybe I did it wrong. The problem appears to be that changing permissions at a higher level, the way I did it, apparently *overwrites* any other permissions further down the tree. Is there a way to change the permissions so that it *adds* them instead of overwriting them?

    I also tried using the SysInternals tools to log all registry accesses. I thought maybe I could track down the specific keys. Unfortunately, during the few seconds it took me to open the project, there were gazillions of registry accesses - probably literally tens of thousands. So that wasn't very productive :-).

    Thanks,

    Kevin

  • 0 in reply to Kevin Kaster
    TI__Guru**** 480451 points

    People have complained about the workaround being less than elegant. But otherwise I have not hear too many complaints about the workaround breaking their PC environment.

    I don't know if you saw the exact instructions in the release notes. Here they are in case:

    -----------------

    Windows XP

    With Windows XP the registry and the file-system is read-only. Files created by an Administrator are read-only to "Users". Also with WinXP, the tool "regedt32" had been replaced by "regedit". The procedure to edit the registry permissions is as follows:

    a) Log in as an administrator.
    b) Choose "Start->Run" from the Windows XP Start menu.
    c) Type "regedit" to bring up the Registry Editor.
    d) Expand the key "HKEY_LOCAL_MACHINE\SOFTWARE\GODSP".
    e) Right-Click on the "GODSP" key and choose "Permissions..."
    f) From the "Group or user names:" list, select the group or user (if they are not in the list, you may need to add them)
    g) In the "Permissions" box, locate the item "Full Control" and check the corresponding box under "Allow".
    h) Repeat steps "d" through "g" for "HKEY_LOCAL_MACHINE\Software\Texas Instruments" and "HKEY_CLASSES_ROOT"

    Next, once CCStudio is installed, you will also need to edit the permissions of the individual files.

    a) Log in as an administrator.
    b) Browse to the CCStudio installation folder using Explorer
    c) Right-click on the installation directory (i.e. ) and select "Properties"
    d) Select the "Security" tab.
    e) From the "Group or user names:" list, select the group or user (if they are not in the list, you may need to add them)
    f) In the "Permissions:" box, locate the item "Full Control" and check the corresponding box under "Allow".

    --------------

    On a related note, might I interest you in trying out our latest version of CCS? Version 4 is the latest. One good thing is that is not as dependent on the windows registry as previous versions. However the v4 for environment is very different and there is a sizable learning curve if you are very familiar with 3.3

  • 0 in reply to Ki
    TI__Expert 7155 points

    Kevin,

    After looking at Ki Soo's proposed solution it looks the same as what I provided you originally with the exception of the steps a-f where the permissions of the individual files are edited. Probably due to my cut & paste, these steps were chopped off. Don't know if this is the culprit that caused the problems.

    Mark Utter

  • 0 in reply to Ki
    Intellectual 765 points

    Hello,

    I followed the intructions exactly with my local IT person. It's demolish my whole Windows XP account, we were not able to repair it. In the end, we must reinstall the whole OS.

    This was very annoying!

    Joachim