I'm running 16.6 on Win7, and am having some interesting problems. In my attempts to diagnose exactly what's going on, I stumbled across a posting where someone outlined the command line options for starting allegro. The file:
- suggests launching with the executable with "-product help", but the result of this is shown in a popup that isn't big enough to show all the output, and can't be resized =/
Does anybody know a good online ref for all the command line options that can be fed into allegro at startup?
The crux of what I'm struggling with is that when I get Capture to generate a netlist and spawn allegro, it tries to call Allegro PCB Design XL, and fails. Our licensed versions of Allegro are "Designer" or "Design L", and I typically use the High-Speed option for the former. I've tried hunting through every .ini and .bat file I could find in the CDS directories, to no avail.
Has anyone had to deal with this before, and have any ideas where I should be looking?
Whilst it's true that not all the options are shown, the displayed ones should be enough to get you going. Start a Command Prompt and type:
allegro -product PCB_design_studio<enter>
to start with the "legacy L" option, and:
allegro -product Allegro_performance<enter>
to start with the "Designer" option
You could also try "allegro -safe" on the command line, that will ignore any configuration.
16.6 has license caching on by default, you could try renaming the "pcbenv" directory, defaults to C:\SPB_Data\pcbenv that will get PCB Editor to start a new set of configuration file defaults and clear any past selections, or caching.
See if that leads anywhere.
Select File -> Change Editor
In the Product Choices dialog hit the Help button
Scroll towards the bottom of the resulting window.
In reply to oldmouldy:
Hmmm... I found these two lines in my allegro.ini file (in the pcbenv folder):
It's like this file is not being read at all, and the files show no changes (by timestamp) since the day I built up this workstation and installed Cadence (June 13).
I renamed the folder to WTF_pcbenv to see what would happen. The allegro window during startup still shows the same wrong version before failing, and the behaviour was the same. Interestingly (and also unsurprisingly) no new folder was created to replace the one that I renamed. Using the Change Editor item from the menu results in the same behaviour.
Is there a way to see where allegro is pointing at for the pcbenv folder contents?
In reply to mpfleger:
on Allegro command line type
This reports the location of your config directory. If you don't have a HOME system variable set it defautls to the user directory Microsoft provides. This location differs depending upon the Windows OS you are running.
In reply to fxffxf:
Now that was simultaneously interesting and somewhat infuriating:
This location contains an allegro.ini file, which (surprise surprise) does specify the wrong version of Allegro WRT our license file.
Apparently *somebody* set up GPOs to assign our HOME vars to point to a directory on a server. This would explain why pcbenv installed in one place, and then hasn't been touched, probably since the machine was added to the domain. The fun increases exponentially when I discover that this file requires admin privs to modify or delete, and by that I mean domain admin, rather than the local admin privs I have. Which is why none of the changes I try to make are persistent.
In any case; I would rather have this directory ending up somewhere other than $HOME. Could someone please point out where the definition is established, for the Cadence $localenv? More specifically; how do I point this to a folder of my choice?
oldmouldy and fxffxf:
Nicely done gents! Your suggestions were able to help me nail down what was going on, and finally to deal with the problem. Now when the rest of the office workstations get moved to Win7 and Cadence 16.6 - we have a way of circumventing the GPO fun :D
Thanks a bunch!