• 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. Default Keyboard Commands Not Working

Stats

  • State Suggested Answer
  • Replies 2
  • Answers 1
  • Subscribers 42
  • Views 929
  • Members are here 0
More Content

Default Keyboard Commands Not Working

anowack
anowack 5 months ago

Hi there,

Recently the keyboard shortcuts (delete part, rotate part, copy, paste, etc.) have stopped working for me in OrCAD X Capture CIS 23.1.

I can still right click and do the command, but it's pretty annoying without the keyboard shortcut. I cannot find any information why keyboard commands would stop working, and I've tried multiple keyboards. It's only OrCAD Capture that has this issue, and it worked at some point in the past.

Any suggestions?

Also, when I right click I cannot close the popup window by left clicking elsewhere. I have to select an option and then exit that option menu.

Thank you

- Aaron

  • Sign in to reply
  • Cancel
Parents
  • Akshay khosla
    0 Akshay khosla 5 months ago

    Hi Aaron,

    You can try deleting workspace (after closing capture). For this, follow the below mentioned steps-

    Step 1: Note the Capture.ini file location

    Open the Capture Command Window (View menu > Command Window) and execute the command `GetIniPath`. This will display the location of the `capture.ini` file.

    Step 2: Close Capture and terminate any remaining processes.

    Close Capture and check the Task Manager to see if any Cadence processes (e.g., `capture.exe`, `cdsMsgServer.exe`, `cdsNameServer.exe`) are still running. If so, manually terminate them.

    Step 3: Delete the Capture Workspace from the Registry.

    Warning: Be cautious when editing the registry. It's recommended to create a backup of your system registry before making any changes.**

    a. Go to Windows Start and type `regedit` to open the Registry Editor.
    b. Locate and delete the `CaptureWorkSpace` key at the following path:
    `HKEY_CURRENT_USER\Software\OrCAD\CaptureWorkSpaceEx\<version>` (where `<version>` is the version of the tool you're using, e.g., `23.1` or `24.1`).

    Step 4: Rename the Capture.ini file

    Rename the `capture.ini` file to `capture_org.ini`. The file is located at the path you noted in Step 1.

    Step 5: Restart Capture and verify

    Launch Capture again to see if the issue is resolved.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • Akshay khosla
    0 Akshay khosla 5 months ago

    Hi Aaron,

    You can try deleting workspace (after closing capture). For this, follow the below mentioned steps-

    Step 1: Note the Capture.ini file location

    Open the Capture Command Window (View menu > Command Window) and execute the command `GetIniPath`. This will display the location of the `capture.ini` file.

    Step 2: Close Capture and terminate any remaining processes.

    Close Capture and check the Task Manager to see if any Cadence processes (e.g., `capture.exe`, `cdsMsgServer.exe`, `cdsNameServer.exe`) are still running. If so, manually terminate them.

    Step 3: Delete the Capture Workspace from the Registry.

    Warning: Be cautious when editing the registry. It's recommended to create a backup of your system registry before making any changes.**

    a. Go to Windows Start and type `regedit` to open the Registry Editor.
    b. Locate and delete the `CaptureWorkSpace` key at the following path:
    `HKEY_CURRENT_USER\Software\OrCAD\CaptureWorkSpaceEx\<version>` (where `<version>` is the version of the tool you're using, e.g., `23.1` or `24.1`).

    Step 4: Rename the Capture.ini file

    Rename the `capture.ini` file to `capture_org.ini`. The file is located at the path you noted in Step 1.

    Step 5: Restart Capture and verify

    Launch Capture again to see if the issue is resolved.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
  • anowack
    0 anowack 5 months ago in reply to Akshay khosla

    Thank you Akshay, since I posted this I uninstalled and upgraded from 22.1 to 24.1 and the issue is resolved, but if this comes up again I'll refer to your answer.

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