March 13, 2002

At some point, I installed the Cadence software on our Windows server. It works ok there, but now it needs to be installed so that it can be run on each windows machine in our domain. Since I forgot to write down my notes from the first installation, I don't remember what the overall setup for the windows machines is supposed to be. But I do seem to recall that I couldn't find a way to just run the software on the clients without reinstalling it. So, the following notes describe the settings I changed on each windows machine to make them able to run the Cadence software that is installed on the server.

Environment Variables

CDSROOT=s:\Cadence\PSD_14.0
CDS_LIC_FILE=5280@impulse
CHDL_LIB_INST_DIR=s:\Cadence\PSD_14.0
CONCEPT_INST_DIR=s:\Cadence\PSD_14.0
Add the following to the PATH:
s:\Cadence\PSD_14.0\tools\libutil\bin
s:\Cadence\PSD_14.0\tools\specctra\bin
s:\Cadence\PSD_14.0\tools\fet\bin
s:\Cadence\PSD_14.0\tools\jre\bin
s:\Cadence\PSD_14.0\tools\bin
s:\Cadence\PSD_14.0\share\pcb\selfstudy\bin
s:\Cadence\PSD_14.0\tools\pcb\bin

Registry Settings

The two links below go to two files that were created by saving the relevant parts of the registry on the server. I simply created all of these keys and values in the registries of each machine that would be running the Cadence software. These subtrees go in the HKEY_LOCAL_MACHINE section of the registry.

Cadence Design Systems subtree
Cadence subtree

Menu Settings

To get the menu settings, I copied the section of the Start Menu from the server to each client machine. I then had to edit each link to change the drive location from f: to s:.

Misc Settings

The only other things that needed to be changed were some of the .ini files. Since the software was originally installed on the server on the f: drive, these locations needed to be changed to s:, which is the drive that all the clients see. I seem to recall that when I first installed the software on the server, I tried to install it to s:. But it wouldn't install to any mapped drive letters and I had to use f:. In the future, if the software can be installed directly to the s: drive, it will save some time in setting things up.

Cadence software is rather difficult to install. One because each piece of software comes on its own cd and requires its own license. And two because the software uses a goofy email message to install, which is a pain to get working properly. But here is a chronicle of my latest Cadence software installation. Read this entire document through to get a feel for what has to be done, before starting anything.

Thirteen cds were delivered for our HP system. Of these, four are labelled as QSRs, which means Quarterly Software Rollups. When you get these, be sure to install from these first. It sounds backwards, but that's how you do it.

The old installation directory was on edg:/mnt/disk4/cad_13.5 and ./cadence and Specctra was on transi in /net/transi/cadence. Since everything should now be on edg and to be able to keep track of the different installations, this installation will be to /net/edg/disk4/. Normally, I would name the directory according to the version of the software, so we have spw45 and psd136 as package names.

-Need to set SPW_HOME=/net/edg/disk4/cad2000 and SPW_SYS_DB=/net/edg/disk4/cad2000
-Run $SPW_HOME/install/bin.hppa/softload
-On the SoftLoad Main Menu, check Load Products and OK
-Device: /cdrom and CD Mounted
-Now it's going to ask to installation information and for the 20 emails that have been sent. This has NEVER worked properly for me when I used my regular email reader, pine. I had to use Netscape to save the attachments from the email messages. Supposedly, then you can use cat to combine them and the install software will be able to figure out where the info for the cd being used is located. This feature did not work for me as my concatenated file was rejected because the software thought it was for the first package listed. So you have to know which file goes with which package, not easily done since they are all named 99124842.?. This part is a royal pain.
-If/When you finally get to the installation, choose Default Installation, only because I have no idea what the custom one will ask.
-Here is a list of which products will be installed:
**SoftShare License Server 0060b018fb5c
**9000: Release Information for System Administrators
**SPWB01: Cierto(TM) SPW university bundle
-Once the installation starts, it takes a few hours to finish. Most of this time is spent copying items off the first cd (QSR).
-Next, need to configure the system. I selected all items, which were:
***Softshare License Server 0060b018fb5c
SPWB01: Cierto(TM) SPW University Bundle
-Got all kinds of errors here, I'm not sure why, but the configuration stuff that they wanted to run didn't work. I don't think it worked last time either, I ended setting it all up by hand.
-Need to get the licensing going. cdslmd is the daemon that takes care of this package (and a bunch of others). It is located in /net/edg/disk4/cad2000/tools.hppa/bin/cdslmd. I edited the license file to reflect this location. Cadence is rather particular about the license and its location must be in /net/edg/disk4/cad2000/share/license. Also here is a file called configure, which should be run to set up a clients file (I'm not sure what this does). I put the license and log file here and called them cdslmd.lic and cdslmd.log.
-Restart softload and run configure again. It will work now that licensing is set up. Configuring takes a long time. I don't know what it's doing, but the messages say things like "Decrypting hds_sigs...."

I think that's it. They have a script that sets the tons of things, like aliases and path additions, in /net/edg/disk4/cad2000/site_data/config/spw.profile. All this did was put a copy of .motifbind in my home directory. It didn't change the path or any other environment variables. I'll have to look into setting those later, when everything is installed.

OK, so I was wrong in thinking that I could install all the Cadence software in a common directory. They don't play well together and all need their own space. So the SPW software is in /net/edg/disk4/spw45 and this software I am installing here is in /net/edg/disk4/psd136. I ran /cdrom/SETUP.SH, which copies the install directory. Then I quit before starting softload and will run it from the directory just created.

-softload
-/cdrom and CD Mounted
-No to viewing readme
-email file cad/99124842.18
-Default installation
-The following list is what will be installed off these three cds:
**Softshare License Server
**9000: Release Information for System Administrators
**PX3000: Concept(R) HDL expert
**PX3100: SPECCTRAQuest(TM) SI expert
**PX3300: PCB mixed-signal expert
**PX3400: digital logic SI library
**PX3410: memory SI library
**PX3420: FPGA SI library
**PX3430: microprocessor SI library
**PX3500: PCB librarian expert
**PX3700: PCB design expert
**PX4000: advanced package engineer expert
**PX4100: advanced package designer expert

-Configure products when installation is finished.
-Top installation directory: /net/edg/disk4/psd136
-Create tools link? Y
-Edit license file? N
-Configure clients file? N
-Edit fozzie's boot script? N
-The configuring will stop at Concept-HDL Libraries, asking which libraries to configure. Choose a for all and continue. It estimates that the time required is 817 minutes.
-Next stop is at SCALD-AWB Libraries, choose all and continue.
-Next stop (which was on the next day) is at AX1100A and/or AX1200A Libraries. Choose all and continue.
-When done, that's it.

LDV2.1-Logic Design and Verfication
Again, this is an older version that we hadn't been using, but that had already been installed. I just moved it to its new location at /net/edg/disk4/ldv21.

Here is what I think I have to set for ICC50, which doesn't have a doc directory:

export CDS_INST_DIR=/net/edg/disk4/icc50--Though maybe not, I'm basing this on past experience.
export HHHOME=/net/edg/disk4/icc50/tools.hppa/iccraft/help
export XAPPLRESDIR=/net/edg/disk4/icc50/tools.hppa/iccraft/help/app-defaults
export PATH=$PATH:/net/edg/disk4/icc50/tools/iccraft/bin

For the SPW software that I finally got running, I need to set:
export SPW_HOME=/net/edg/disk4/spw45
export SPW_SYS_DB=/net/edg/disk4/spw45
. $SPW_SYS_DB/site_data/config/spw.profile--This doesn't work in the edg script, I think I'll just put it aside and tell anyone who wants to run Cadence stuff that they have to manually source this file. If Cadence becomes more popular, I'll incorporate everything into the edg script.
-This last file sets a ton of aliases that will be used to start the software. But I'm not sure their format is correct for bash, I may need to edit this file. Note that the PATH additions are also in this file. There are quite a few, so it is probably better to leave them there.

From the doc that came with the ambit software, I need to set:
export PATH=$PATH:/net/edg/disk4/ambit30/BuildGates/current/bin

To start the command line interface, ac_shell or pks_shell
To start the graphical user interface, navigates -pks or navigates -ac

From the psd136 documents, I get:
export PATH=$PATH:/net/edg/disk4/psd136/tools/bin:/net/edg/disk4/psd136/tools/dfII/bin
I'm very happy to say that I found no mention of CDS_INST_DIR

From ldv21 documents, I get:
export PATH=$PATH:/net/edg/disk4/ldv21/tools/bin:/net/edg/disk4/ldv21/tools/dfII/bin

There had been a CDS_LIC_FILE variable to set, but I haven't set it and everything seems to be working ok. If I do need to set it, it would probably be:
export CDS_LIC_FILE=/net/edg/disk4/spw45/share/license/cdslmd.lic:/net/edg/disk4/ambit30/license/ambitd.lic

Probably more things will get added to these as I install the software that could only be run in HP 11.0.