• 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. Custom IC Design
  3. technology file manager

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 14950
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

technology file manager

skillEater
skillEater over 5 years ago

Hi all,

I am getting an issue when opening technology file manager.

The error is 

techManagerOpenTechToolBox()
*Error* eval: unbound variable - ciwvHelpMenu
ERROR

I am using ICADV12.3-64b.

please help me.

Thanks,

Ganesh Doddipatla.

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    Hi Ganesh,

    This is another symptom of having an old ciw.menus file in your search somewhere, similar to my answer to your post: RE: virtuoso export stream option a couple of weeks ago. An older post where I suggested the same answer (exactly the same as this question here): RE: Library Technology Manager

    You didn't reply to my last response - so presumably you've not yet fixed the underlying issue with a bad ciw.menus file in your setup. Normally the ciw.menus file would come from the installation; if somebody has copied it and customised it, they need to keep it up to date or write it in a way that loads the central file first and then adjusts the contents.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • skillEater
    skillEater over 5 years ago in reply to Andrew Beckett

    Hi Andrew,

    I did as you told in the previous mail.

    the result is /appl/LINUX/ICM_MODEM/ic6/menus/ciw.menus.

    should i point this to new path or What should Ido?

    I opened the fie.the menu commands are related to old version of icfb.

    Please tell me how to,update it.

    Thanks,

    Ganesh Doddipatla.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to skillEater

    Hi Ganesh,

    The right thing to do is to get the owner of that file to either remove it or update it. As a workaround though, you could create a "menus" directory within the directory you launch virtuoso, and then within that directory place a file called "ciw.menus" with the following contents:

    load(prependInstallPath("etc/tools/menus/ciw.menus"))

    That should mean that it finds your ciw.menus file first, which then loads the standard installation menus file and bypasses the erroneous one (hopefully this will work anyway, depending on whether the search order has been messed with).

    Check the working dir that you're running in by typing:

    getWorkingDir()

    in the CIW, just in case your environment messes with the working dir when you start virtuoso.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to skillEater

    Hi Ganesh,

    The right thing to do is to get the owner of that file to either remove it or update it. As a workaround though, you could create a "menus" directory within the directory you launch virtuoso, and then within that directory place a file called "ciw.menus" with the following contents:

    load(prependInstallPath("etc/tools/menus/ciw.menus"))

    That should mean that it finds your ciw.menus file first, which then loads the standard installation menus file and bypasses the erroneous one (hopefully this will work anyway, depending on whether the search order has been messed with).

    Check the working dir that you're running in by typing:

    getWorkingDir()

    in the CIW, just in case your environment messes with the working dir when you start virtuoso.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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