I was just curious if anybody has run into this yet. I installed the 16.6 upgrade last week, and it seemed to work just fine. This morning, when I tried to double-click a board (.brd) file to make some edits, I got an error message that says "The program can't start because cdn_xerces-c_2_7.dll is missing from your computer. Try reinstalling the program to fix this problem." But, if I open up OrCAD PCB Editor and then click "File" and "Open" and then browse to the file it will open it that way. It didn't do this to me last week when I first installed the upgrade. Right now, all of my existing board files were generated using the previous 16.5 version of software.
Has anybody else had this problem?
Sounds like your Windows path for the .brd extension is still pointing to the 16.5 application.
In reply to TH Designs:
In reply to David Yackman:
You need to find the Windows configuration settings for file association. In older versions of Windows it was under Control Panle, File / Folder settings I believe. The extension ".brd" would have a path associated to it which is probably still pointing to the 16.5 executable.
Update: Look here: Control Panel, Default Programs - Set Associations
You may have assigned the brd to program association manually.
You should use the switchversion program (in the Cadence Start menu) to assign the association. This way as you switch between releases the association will automatically also switch
In reply to fxffxf:
You can switch between 16.5 and 16.6?
I thought the switch release was only to go back to 16.2.
The switchversion tool allows you to toggle between any installed Cadence Allegro or OrCAD release.
As of some 16.x, release it also supports the option of associating Cadence programs with file extensions. Unlike doing the file associations via the manual method, it assigns the associations using the Cadence <cdsroot> variable. This means as you switch between releases the file associations will launch the correct version of the Cadence programs and you won't see dll errors.
Good to know.
Looks like the Phils will win a game before the Eagles do......................... This was true back in October also.
Yeah, now that it's 4 PM, I'll quit playing IT guy and start editing some boards! LOL
In reply to oldmouldy:
It would've been great for the 16.6 upgrade to configure itself to just work properly without its end users having to go through all of the hocus pocus. I don't really understand the need to switch between versions, either. Ideally, all of the new versions should be backwards-compatible. I know from my limited experience with OrCAD that this probably isn't the case, hence the need to switch versions. Since my company started using OrCAD recently starting with v16.5, hopefully, I won't run into the need to switch versions often.
I have learned never to download an ISR or upgrade of any kind while I have current projects that I'm working on, because the chances are pretty good that the new software will cause an error that will stop my work in its tracks. I waited until the day before new year's weekend to install the 16.6 upgrade for just this reason. I figured that if I ran into a problem with it on Friday afternoon, I'd have the long weekend to fix it. As it turned out, it worked just fine on Friday. I was relieved! But, Wednesday morning, I started gettting the *.dll error, which led me here. Tech support didn't have the answer. I figured out to delete the registry data for brd files myself. It might have been the "dirty" way to get it done, but it worked. This time. Next time, I may have to download one of those "unassociate" utilities that oldmouldy suggested.
I know that many of my problems with OrCAD are due to my position on the learning curve; I have a lot to learn. However, I think that much can be done to make the installation and implementation of ISRs and upgrades more seamless and user-friendly.
I have been using Orcad products for over 25 years and have had installation issues with just about every release / upgrade. But I muddle through, figure it out, gripe, complain and move on........
I have not installed 16.6 at my home office yet because I'm in the middle of a big job there and can't afford any down time. But, that being said, I have migrated to 16.6 at a different work location and I did not have any issues other then one environment issue that I was able to quickly resolve.
I do like some of the new 16.6 features and I'm actually looking forward to upgrading at my office once I get some down time.