Stats

  • Locked Locked
  • Replies 29
  • Subscribers 168
  • Views 32529
  • Members are here 0
More Content
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

Orcad Capture - Slow Graphics response on windows 10

excellon1

Hi,

I have an issue with capture 17.2 base release and current ISR 031 running on windows 10 pro. What is going on is the screen refresh is slow when
capture is running. When capture loads it seems like you can see the tool bar icons getting drawn on the window, then they refresh and appear.

Moving Capture tool bar Icons across the screen has the effect of huge mouse trails on the canvas. The PCB editor works fine, Display is very fast.
I tested capture v17.2 on windows server 2008 R2 and it works well.

Things I tried.

Re-Install
Checked Licensing - No issues found
Verified graphics card drivers were fine - Checked ok PCB editor is really fast.
Checked windows logging etc - Nothing found.
Ran capture as an admin - Made no difference.
Disabled Firewall and anti virus software - Made no difference.

The issue seems to be related to win 10 Pro as things work fine on winserver 2008. I will do some more checking but in the mean time
if anyone has any pointers, that would be a big help.

Thanks Paul.

Parents
  • FormerMember
    FormerMember

    Is there no fix for this issue yet? The toolbar icons refreshing every now and then is annoying -- I have all toolbars from View > Toolbar checked.

    Working on Windows 10 version 1903 (OS Build 18362.356) with all the latest drivers. ORCAD version 17.2-2016.

  • cstocci
    in reply to FormerMember

    Hi,

    Have  SPB 17.20.061 and Windows 10 Pro (1903) and have those big sluggish Capture screens.  As mentioned, no issues with Allegro or most other programs.

    Chris

  • RFinley
    in reply to excellon1

    Glad you found a solution.  But, Win Server 2008 R2 is EOL ..next week...  No more patches from MSFT.

  • cstocci
    in reply to RFinley

    Folks,

    SPB 17.20.060 ran plenty fast on Windows 7 Pro, but even 17.20.061 runs like a dog (slow) on Windows 10 Pro.  I can create a Virtual Windows 7 with my VMWare Workstation Pro and reinstall on that environment.  Sound like a possible to all?  I have a virtual Windows 10 running SPB 17.4.001 and it seems to run faster there than my 17.20 does on the host Windows 10 pro.

    My question is this...Is Cadence Design aware that most/all people running their tool are on Windows 10 within a week or so?  Why are they being so ridiculous about rotten performance on 98% of their product's ability to run on the new standard OS? Cannot believe they have not heard of Microsoft Windows!!

    Chris

  • cstocci
    in reply to cstocci

    Folks,

    One other business impassibility...Cadence is well aware of the performance issue with Windows 10 on 17.20 but they also know that Windows 7 ends very shortly this month.  Therefore, this confluence of events forces all of us to go to 17.40 (big plus for Cadence) and insures that most of us will be forced to go to 17.40 after enough performance aggravation of 17.2 on Windows 10.

    Thoughts...?

  • cstocci
    in reply to cstocci

    Folks,

    I loaded the SPB 17.2 on my VMware Workstation Pro (version 15.5.1) virtual machine and everything is very fast again on Windows 7 Pro (64-bit).  So, perhaps what RFinley was saying is true.  Version 17.2 will work on Windows 10, but not well and no where near as clean and fast as in Windows 7 Professional.  Version 17.4 and beyond is working much better on Windows 10 Professional and that was probably always the intention (accidental or not!) as I mentioned earlier about Cadence's business model attitude toward version 17.2 with the newer version 17.4 already out since November 2019.

    The good news is most antivirus/anti-malware programs will continue to work within Windows 7 for sometime to come, so while I need version 17.2 (up to hotfix 17.20.062) due to it's maturity and the fact that going from version 17.4 back to 17.2 will be somewhat problematic (by design, maybe?), as long as I have a virtual machine in Windows 7, I am OK.  This means, for me at least, I will uninstall 17.2 in my Windows 10 host and replace it with version 17.4 and go forward from this standpoint with two versions.  Version 17.4 on the host Windows 10 and version 17.2 on the guest Windows 7 virtual machine.

    Thoughts, people...

    Chris

Reply
  • cstocci
    in reply to cstocci

    Folks,

    I loaded the SPB 17.2 on my VMware Workstation Pro (version 15.5.1) virtual machine and everything is very fast again on Windows 7 Pro (64-bit).  So, perhaps what RFinley was saying is true.  Version 17.2 will work on Windows 10, but not well and no where near as clean and fast as in Windows 7 Professional.  Version 17.4 and beyond is working much better on Windows 10 Professional and that was probably always the intention (accidental or not!) as I mentioned earlier about Cadence's business model attitude toward version 17.2 with the newer version 17.4 already out since November 2019.

    The good news is most antivirus/anti-malware programs will continue to work within Windows 7 for sometime to come, so while I need version 17.2 (up to hotfix 17.20.062) due to it's maturity and the fact that going from version 17.4 back to 17.2 will be somewhat problematic (by design, maybe?), as long as I have a virtual machine in Windows 7, I am OK.  This means, for me at least, I will uninstall 17.2 in my Windows 10 host and replace it with version 17.4 and go forward from this standpoint with two versions.  Version 17.4 on the host Windows 10 and version 17.2 on the guest Windows 7 virtual machine.

    Thoughts, people...

    Chris

Children
  • RFinley
    in reply to cstocci

    Back in the early 90's Harris Scicards abandoned their NeWS/Open UI (yeah, I'm old) for Solaris OS to share more code between Solaris and HP-UX, which uses Motif.  With this change, they still couldn't add crossprobing to Viewlogic schematics, so everything was replaced where I worked and soon I'm hating Boardstation even more.  O_o

    Cadence has to offer Allegro for both Windows and Linux.  It helps if they look and feel the same.  Tier-1 companies use Linux.  Cadence has to invest in separate code bases and developer staff for two flavors of the same tool.   

    In the end, 17.4 is an improvement over previous, and includes (limited) P-SPICE in the base product.  Love the dark mode.  Hope the edit-boundary function is fixed to match 17.2 soon.

    Meanwhile, someone needs to encourage MGC to update their Allegro to P*DS translator as MGC support won't talk to you unless you're running 6.3, which requires Windows 7.   The MGC Translator to P*DS/Exp*dition doesn't handle the padstack changes with 17.2.  Have to stick with 16.6 (latest sp) for projects that have to collaborate with P*DS.

    thanks.

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.