[PCB_FORUM] Re: Moving to V16.01 -- any issues? Plus a related issue....

There is a difference between Windows and UNIX. On UNIX, the shell provides wildcard expansion (*.brd) for free. On Windows, the command window doesn't offer this functionality. Either the tool (dbstat) needs to implement it or you can use a shell (e.g. tcsh.exe or a shell from Cygwin env). Since dbstat currently doesn't offer wildcard expansion, I would 
use download Cygwin and use one of its shells.

Robert Szumowicz wrote:
Thanks for the clarification. We also found it the most practical i.e. to keep a single set of libraries created in 15.7 and use them in 15.7 and 16.01 designs. We have not experienced major issues with that so far. The only problem is that when PAD_DESIGNER is started there is absolutely no information of program version (no about window and the same look) and sometimes a wrong program version is invoked.
I have a question: does DBSTAT *.pad work for you? Manuals for 16.01 and 15.7 say: 
"
Dbstat also accepts the wildcard character *.<ext> for instances when you want to display 
information on all the designs of a particular type in your directory.
"
but in my case (WinXP) DBSTAT comes with a message that multiple files has been found. 


fxf wrote:
You can use symbols and padstacks from any version of Allegro 15.x with 16.x designs. If you have symbols and padstacks that report 14.x when you query them with the "dbstat" program then these must by uprev-ed to at least a 15.x level 
before 16.x software can access them.
The advantages of keeping symbols and padstacks one major release behind your current release is you only need to manage a single set of libraries. This strategy assumes that your users still require access to an older major version of Allegro. The downside of this approach is that you cannot take advantage of any symbol or padstack functionality that was added in 
newer major or dot release.

A major release are 14.0, 15.0, 16.0.




Hi,
 Related question: I'm just starting the Allegro PCB and HDL
migration/validation from 15.5.1 to 16.01 and was told by a AE that we
need to convert the libraries to 15.7 first. Has anyone else done this?
I'd definitely prefer to migrate directly to 16.01. Also -any gotchas? Thanks, 
Lynn

Lynn Isaacson, CID+, CIS
PCB Design & Engineering Services Supervisor Physio-Control, Inc.
Direct: 425-867-4443   Fax: 425-867-4462 lynn.isaacson@xxxxxxxxxxxxx





-----------------------------------------------------------
To subscribe/unsubscribe: Send a message to icu-pcb-forum-request@xxxxxxxxxxxxx 
with a subject of subscribe or unsubscribe
To view the archives of this list go to http://www.freelists.org/archives/icu-pcb-forum/ 

Problems or Questions:
Send an email to icu-pcb-forum-admins@xxxxxxxxxxxxx
-----------------------------------------------------------



-----------------------------------------------------------
To subscribe/unsubscribe: Send a message to icu-pcb-forum-request@xxxxxxxxxxxxx 
with a subject of subscribe or unsubscribe
To view the archives of this list go to http://www.freelists.org/archives/icu-pcb-forum/ 

Problems or Questions:
Send an email to icu-pcb-forum-admins@xxxxxxxxxxxxx
-----------------------------------------------------------

-----------------------------------------------------------
To subscribe/unsubscribe: Send a message to icu-pcb-forum-request@xxxxxxxxxxxxx 
with a subject of subscribe or unsubscribe

To view the archives of this list go to 
http://www.freelists.org/archives/icu-pcb-forum/

Problems or Questions:
Send an email to icu-pcb-forum-admins@xxxxxxxxxxxxx
-----------------------------------------------------------

Other related posts: