• 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. READONLY Issue with private LIBRARY1.OLD with Capture 17...

Stats

  • State Suggested Answer
  • Replies 3
  • Answers 1
  • Subscribers 44
  • Views 8493
  • Members are here 0
More Content

READONLY Issue with private LIBRARY1.OLD with Capture 17.2-2016 SO83 only on first open of Project

CseaTec
CseaTec over 3 years ago

Someone had posted about this before in 2017, but the question got locked before anyone answered it. I am now having the same issue with the latest Capture 17.2. It would seem that whenever I launch Capture and open a previous project that uses my LIBRARY1.OLB that I made a while ago, I get prompted with an alert that asks if I want to open it readonly.  If I click No, the library is not always accessible from within the project hierarchy.  If I then close the project and reopen it, the prompt does not occur and everything is fine.  I can then close & open multiple projects without this prompt reoccurring. But if I totally close out Capture and restart it, the prompt reoccurs (one time again) when I re-open a project that uses this library.

Can anyone explain this?  Thank you.

  • Cancel
  • Sign in to reply
Parents
  • CseaTec
    0 CseaTec over 1 year ago

    Well, after well over 1 year since I posted this question that no one could answer, I finally figured it out myself.

    I found that something was corrupted in my LIBARY1.OLB file.  The way I resolved it was by doing the following:

    1. In OrCAD Capture, open LIBRARY1.OLB, choose File-->Export-->Library XML...

    2. Rename the library1.xml to something new (e.g. library_mycompany.xml)

    3. Edit mycompany_library.xml with a text editor and change the line near the top from:
      <Defn name="c:\users\<myfolder>\library1.olb"/>
      to
      <Defn name="c:\users\<myfolder>\library_mycompany.olb"/>

    4. Open OrCAD Capture again and choose File-->Import-->Library XML...

    5. Save the newly created library and project thereafter and close it.

    6. The next time you open your schematic projects that used the old and problematic LIBRARY1.OLB file, add in the duplicate new library, LIBRARY_MYCOMPANY.OLB and delete LIBRARY1.OLB from the schematic project, save it and close it.

    7. Completely close OrCAD Capture

    8. Reopen OrCAD Capture for a true test of the issue.

    9. Open your Schematic project again with the new library attached and viola, no more READONLY error upon first opening!

    Hopefully this helps someone else since I've suffered with it now for almost 5 years.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
Reply
  • CseaTec
    0 CseaTec over 1 year ago

    Well, after well over 1 year since I posted this question that no one could answer, I finally figured it out myself.

    I found that something was corrupted in my LIBARY1.OLB file.  The way I resolved it was by doing the following:

    1. In OrCAD Capture, open LIBRARY1.OLB, choose File-->Export-->Library XML...

    2. Rename the library1.xml to something new (e.g. library_mycompany.xml)

    3. Edit mycompany_library.xml with a text editor and change the line near the top from:
      <Defn name="c:\users\<myfolder>\library1.olb"/>
      to
      <Defn name="c:\users\<myfolder>\library_mycompany.olb"/>

    4. Open OrCAD Capture again and choose File-->Import-->Library XML...

    5. Save the newly created library and project thereafter and close it.

    6. The next time you open your schematic projects that used the old and problematic LIBRARY1.OLB file, add in the duplicate new library, LIBRARY_MYCOMPANY.OLB and delete LIBRARY1.OLB from the schematic project, save it and close it.

    7. Completely close OrCAD Capture

    8. Reopen OrCAD Capture for a true test of the issue.

    9. Open your Schematic project again with the new library attached and viola, no more READONLY error upon first opening!

    Hopefully this helps someone else since I've suffered with it now for almost 5 years.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
Children
  • MikeO EE
    0 MikeO EE 10 months ago in reply to CseaTec

    Thanks for your effort in finding AND posting the solution!  I had the same problem and submitted problem reports but no one was able to solve it. Your steps above appear to have fixed the problem for me.  THANKS!

    • 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