• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Allegro X Capture CIS
  3. Inheriting CIS configuration (.INI) files from previous...

Stats

  • State Not Answered
  • Replies 5
  • Subscribers 44
  • Views 275
  • Members are here 0
More Content

Inheriting CIS configuration (.INI) files from previous versions?

Ulf K
Ulf K 16 days ago

I recently had to reinstall several versions of OrCAD Professional due to a hardware malfunction.

It took some time...

Is there a "Best practices" on how to copy/transfer the CIS-configuration from a previous OrCAD version into a new release?

I guess that simply copying the .INI-file is not a recommended way. The ideal way would be some sort of configurator

utility that says "Found CIS configuration in version xx.y - Do you want to copy CIS settings to 25.1". Iguess that would

be to much work but at least to gather the search patterns, the library footprint viewer in the CIS canvas, etc under

a common headline so that copy-paste could be made on a manual basis.

The same question applies also to the PCB editor environment but in my case, there were fewer settings that needed

to be modified.

  • Cancel
  • Sign in to reply
Parents
  • Jeet
    0 Jeet 15 days ago

    Ulf,

    Where were your files present was it present locally on your system or on sever and what level of permissions do you have to access the CIS Database? Additionally, what type of database is the CIS Database?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Ulf K
    0 Ulf K 14 days ago in reply to Jeet

    The 25.1 installation is local (where I am administrator) on my workstation.

    The CIS database resides in a server (where I am administrator) with full rights.

    Disks are mapped in the windows environment. Both CIS database and all libraries

    (.OLB, .PSM, .DRA, etc. etc) resides in that server.

    The database is a Microsoft Access type, used and maintained for many years by myself being adminstrator.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Jeet
    0 Jeet 7 days ago in reply to Ulf K

    Thanks for providing insights, If libraries and database(.DBC) is present on the server, users can browse the Database configuration file (.DBC) in OrCAD Capture easily they need to setup the ODBC Driver.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Ulf K
    0 Ulf K 7 days ago in reply to Jeet

    If the .DBC-file lists all configuration settings, that would be fine. But I am also wondering about the library, footprint viewer, search paths that are listed in the .INI-file. If limited to a few paths that would be easy, but not if there are many paths and libraries configured.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • Ulf K
    0 Ulf K 7 days ago in reply to Jeet

    If the .DBC-file lists all configuration settings, that would be fine. But I am also wondering about the library, footprint viewer, search paths that are listed in the .INI-file. If limited to a few paths that would be easy, but not if there are many paths and libraries configured.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
  • Jeet
    0 Jeet 7 days ago in reply to Ulf K

    Yes settings are stored in the 'capture.ini' file. I would recommend you to organize your folders by keeping footprints(.dra) in a single folder and libraries(.OLB) in another folder. 

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information