Stats

  • Locked Locked
  • Replies 6
  • Subscribers 165
  • Views 16964
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How can I switch SPB between versions 16.6 and 17.2 without interfering in the environment variables?

Gustpcb

Hello all,

I have installed both 16.6 and 17.2 versions of SPB in my machine and I need to switch between them, and I'm facing problems in the environment variables of each version as they are interfering one in each other's version.

Usually it's not a problem to the environment variables of each version, since the variables are also switched as the software version is switched - environment variables of one version don't interfere in the variables of the other version if there's no special env variable setup.

However, my SPB 16.6 installation has a different setup - All of it's environment variables point to network folders which contain files and libraries of this 16.6 version. And when I install SPB 17.2, all of it's 17.2 environment variables point to the same folders (network directories) as do the correspondent variables of the 16.6 version, in addition to the default installation directories of the 17.2 version.

Well, one the problems that I'm facing is in the following env variables: MENUPATH - I have to switch between the priorities of the directories of each version everytime I switch between the SPB version, since this variable is related to menu icons - If I don't switch between the priorities of the directories, the 16.6 version shows some menu icons of the 17.2 version and vice-versa; FORMPATH - I have to do the same for this variable, although I'm not sure if it causes the same problem as the MENUPATH environment variable does if I don't switch between the directories priorities.

Another problem that I'm facing is that some default installation directories, previously added to some env variables, are getting lost in these env variables.

Does anyone have an idea on how to separate the environment variables of each version when I switch between them even if I have a previous env variable setup for one version?

Basically, the env variable setup previoulsy made to the 16.6 version was done through the CDS_SITE system variable.

I'm attaching a picture as a reference.

Any help will be appreciated.

Gustavo

Parents
  • mcatramb91

    Hi,

    In general, this is what I have done in the past:

    • Setup a separate 17.2 CDS_SITE folder and update the CDS_SITE System variable to point that folder when running 17.2
    • If everything is being stored in your local PCBENV folder than you could setup a separate 17.2 PCBENV folder and use the System Variable ALLEGRO_PCBENV to point the 17.2 PCBENV folder when running 17.2

    Hope this helps,

    Mike

  • Gustpcb
    in reply to mcatramb91

    Hi Mike,

    How can I set the system variable ALLEGRO_PCBENV? Shall I set it just the way I set the CDS_SITE variable?

    Gustavo

  • Gustpcb
    in reply to Gustpcb

    Just adding:

    Regarding the updating of the CDS_SITE variable required everytime I switch from SPB 16.6 to 17.2: I guess I have to manually edit the directory of the CDS_SITE variable, right? Or do you use some command to do that more automatically?

  • mcatramb91
    in reply to Gustpcb

    The ALLEGRO_PCBENV is a Windows System Variable.   Yes, you would need to manually change CDS_SITE or ALLEGRO_PCBENV to the different location.

    In the past I setup a BAT file to run the SETX command to make the changes.  One line in the file and save the file with a .BAT extension and run it.  You will need to run it as Administrator because you are changing System variables, check with your IT Group as they may be able to help you to automate this as well. .  Normally, Right Mouse Button over the .BAT file and select Run As Administrator will do the trick.

    Here is tow example files - just change your path.

    172.bat

    setx CDS_SITE "C:\CDS_SITE_17.2" /M

    166.bat

    setx CDS_SITE "C:\CDS_SITE_16.6" /M

  • Gustpcb
    in reply to mcatramb91

    This way is much better - It automates the CDS_SITE variable updating process when I run the .bat file.

    Thanks a lot for your help!!!

Reply
  • Gustpcb
    in reply to mcatramb91

    This way is much better - It automates the CDS_SITE variable updating process when I run the .bat file.

    Thanks a lot for your help!!!

Children
No Data
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.