Trying to debug what happened to my OrCAD license yet again.
Google searching on the above error message, directed me to this page which does a damn fine job describing the INCLUDE list and other options file parameters:
http://www.ansys.com/products/icemcfd-tech-notes/flexuser/chap5.htm
Further digging shows that this file is just my license.dat file under C:\flexlm
Naturally, there is no "Capture" feature listed because our OrCAD is a site license. There's a bunch of Actel software features listed though, and I bet that when I installed those I somehow messed up the pointer to the OrCAD license server
Showing posts with label OrCAD. Show all posts
Showing posts with label OrCAD. Show all posts
Monday, April 5, 2010
Tuesday, November 17, 2009
Somebody F#@%'d with my path
OrCAD no longer starts. Thank you 560 admins. Was getting an "Application has failed to start because cdsCommon.dll was not found. Re-installing the application may fix this problem"
Found that this dll existed perfectly happily in the tools/bin directory under my CDSROOT directory. Found out how to change the $PATH variable in XP. Added the tools/bin directory to the $PATH and it's up now. My $PATH didn't have anything obviously wrong with it before I edited it though, even though there was no OrCAD paths in it. Either a chunk of the $PATH just got bitten off, or some other variable that OrCAD uses in place of the $PATH was mangled. The $CDSROOT and $CDS_LIC_FILE variables were both there and looked good. A search of recently changed files is what leads me to implicate the admins, as some WBEM stuff changed and the wbemcore.log file seems to indicate that something bad happened on Sunday and there was some kind of restore. Also Patchlink ran on Monday.
To change environment variables, right click on my computer, select properties, go to the Advanced tab, click on Environment Variables. Per: http://www.computerhope.com/issues/ch000549.htm
There's almost nothing on OrCAD environment variables to be found through Google, but the following few OrCAD forum posts were very enlightening, all about customers' struggles to solve the maddening slow start problem that everybody I know is also experiencing:
http://www.orcad.com/forums/ShowPost.aspx?PostID=9172
http://www.orcad.com/forums/ShowPost.aspx?PostID=14748
http://www.orcad.com/forums/ShowPost.aspx?PostID=12819
Found that this dll existed perfectly happily in the tools/bin directory under my CDSROOT directory. Found out how to change the $PATH variable in XP. Added the tools/bin directory to the $PATH and it's up now. My $PATH didn't have anything obviously wrong with it before I edited it though, even though there was no OrCAD paths in it. Either a chunk of the $PATH just got bitten off, or some other variable that OrCAD uses in place of the $PATH was mangled. The $CDSROOT and $CDS_LIC_FILE variables were both there and looked good. A search of recently changed files is what leads me to implicate the admins, as some WBEM stuff changed and the wbemcore.log file seems to indicate that something bad happened on Sunday and there was some kind of restore. Also Patchlink ran on Monday.
To change environment variables, right click on my computer, select properties, go to the Advanced tab, click on Environment Variables. Per: http://www.computerhope.com/issues/ch000549.htm
There's almost nothing on OrCAD environment variables to be found through Google, but the following few OrCAD forum posts were very enlightening, all about customers' struggles to solve the maddening slow start problem that everybody I know is also experiencing:
http://www.orcad.com/forums/ShowPost.aspx?PostID=9172
http://www.orcad.com/forums/ShowPost.aspx?PostID=14748
http://www.orcad.com/forums/ShowPost.aspx?PostID=12819
Thursday, April 16, 2009
Procedure for capturing documents to bitmaps
A method for creating drawings in Word or PPT and then formatting to a bitmap for importing into an OrCAD drawing:
1. Send document to a PDF (for example by using PrimoPDF)
2. Open PDF using Adobe 9, select the image to be exported using the capture tool.
3. With the image still selected after the automatic capture, use the view setting to expand the view as large as feasable to get nice smooth rendering on text and lines (most frequently used setting: 300%). Then hit CTRL-C to copy the image again, this time at the higher resolution.
4. Paste the image in either MS-Paint or IrFanView, manipulate the size and color depth.
5. The maximum size picture that can be imported into OrCAD seems to be dependent on the total number of pixels (approximately 2.5 MPixels). For the front panel that was a width of 2540 pixels but for the top view that limits it to a width of 1700 pixels.
6. The picture resolution when printed is much better than on the screen.
7. Can size the picture based on plain lines drawn in OrCAD for reference.
1. Send document to a PDF (for example by using PrimoPDF)
2. Open PDF using Adobe 9, select the image to be exported using the capture tool.
3. With the image still selected after the automatic capture, use the view setting to expand the view as large as feasable to get nice smooth rendering on text and lines (most frequently used setting: 300%). Then hit CTRL-C to copy the image again, this time at the higher resolution.
4. Paste the image in either MS-Paint or IrFanView, manipulate the size and color depth.
5. The maximum size picture that can be imported into OrCAD seems to be dependent on the total number of pixels (approximately 2.5 MPixels). For the front panel that was a width of 2540 pixels but for the top view that limits it to a width of 1700 pixels.
6. The picture resolution when printed is much better than on the screen.
7. Can size the picture based on plain lines drawn in OrCAD for reference.
Subscribe to:
Posts (Atom)