Orcad Viewer doesn't work

Probably. I've seen it work with 15+ page hierarchical schematics in a fairly recent version.

Best regards, Spehro Pefhany

When I tried it with 15.something, a year ago, it didn't work either.

Sorry guys, Been goofing off and getting work done today while waiting for the solder stencils to get here for the next prototype...

Jeorg, The .DSN file SHOULD contain all the library parts internally. It keeps a local cache of the parts in the design. One of those gotchas when you go and alter the part in the library, and then wonder why all those transistors have the wrong parameters on them...

Can you have the originator try opening the files on a 'virgin' machine? It could be he has been archiving the files after turning off the 'library files' option since, of course, they already HAVE all the library files configured!

Yes, adding the library files to the archive is an option... :-(

Charlie

Oh Boy, so they changed the file format (again!) and didn't update the reader for it! Remind me to tweak Greg the next time I see him... ;-)

Charlie

I'd be curious to hear what's "superior" about the 16.3 format vs. the 16.2 format.

The "what's new" notes for 16.3

On the other hand... TCl/Tk support? In 2010 for a product that's never had it before? Wow. I mean, I've written a few TCl/Tk scripts in my life, and it's a perfectly decent language, but that was some years back... and for tools that had had TCl/Tk for years prior. I.e., I find it hard to believe that anyone writing a *new* ORCAD script is going to choose TCl/Tk over Visual BASIC. They must have had some big corporate customer who wanted it? I mean, if you're going to spend money developing new scripting abilities in ORCAD, I'd think a COM interface would be the way to go.

---Joel

Joel Koltner a écrit :

Lots of CAD packages also have to run on unix systems (where people are used to TclTk).

Good luck with VB on 'nix :-)

my

me

ics

nd

=A0 =A0 =A0...Jim Thompson

possible.

I've had the exact same experience as Joerg--it only sometimes works.

I recently downloaded and installed Myriad Viewer for a project. It worked fine for the original .DSNs from source 'A', but gives Joerg's same error once those files are edited and sent by source 'B'.

Works fine for Allegro (.BRD) files though, so far.

-- Cheers, James Arthur

That makes sense. My 'source B' uses the latest, gratest[sic] also.

-- Cheers, James Arthur

my

me

schematics

and

Which is why I never used it. I only used the schematic editor. That was dongle-less and literally bug-free. I lived and worked in Europe back then and there they seemed to trust people less because the versions there were dongled. And more than double in price. Sooo ... I did the usual and bought it in the US :-)

Layout SW isn't all that important to me and most other design engineers that I know. The layout job is nearly always farmed out because that is less expensive for the client. Same in chip design. Of course, larger companies have employed layouters in house. Unless the design is super critical RF circuitry having the engineer do the layout usually doesn't make business sense.

The major factor here is the word "fairly". Turns out it does work with

Well, we found it out. Myriad does not like the latest Orcad file format, if you move one or more releases back it works. I'd call that a screw-up ;-)

Cadence all my

allowed me

schematics

viewer?

the

libraries and

function

library.

today, it

.DSN

the

pretty

you

that

using

was

of

trust

V6

check

partners

code.

For error - you could use the accessories->library fix utilities (16.3 latest ISR.

For Viewer - 16.3 latest ISR has Intelligent PDF viewer - see

--------------------------------------- Posted through

Yeah, but I don't think ORCAD is one of those packages.

And I can't imagine they'd thinking of porting it -- I suspect few if any people in the market for *new* CAD tools buys ORCAD anyway; their money comes from maintenance contracts and firms already using it that need more licenses due to growth.

Unfortunately, as far as I'm aware, *NIX doesn't have any interprocess communication (well, function call) standard that's widely supported. On Windows, regardless of which language your application is written in, once it supports COM, you can "talk" to it from command prompt scripts, Visual BASIC, Excel, or pretty much any other program you feel like.

---Joel

AFAIK the foot pump was standard just like the starting crank. At least they where on my parent's Lada. Never needed either though.

On unix you use tcp/ip.

A Lada station wagon I saw had a crowbar as standard equipment. Seriously. So if you drove somewhere and had to whack out a tile floor the tool was already right there.

But this is all Western Europe. Whole different story behind the former iron curtain. People had to get in line and sometimes wait more than a decade for a car. Whether you had the money or not didn't make a difference. What I really don't get is that there are still people who believe such an economic system is better.

Actually, I 'sorta' remember them saying something about a new feature that had required a database change in a user group meeting I went to a few weeks ago. The trouble with Capture is that it is a bastardly kludge, with features and interfaces added on top of and around all the existing features and interfaces, so it is very easy to break... ;-)

Charlie

you

Visual

mean,

But once upon a time, around 1990, it was perfect :-)

you

Visual

mean,

I know you keep saying that Joerg, but it drove me crazy! I was using it on a windows machine, and wanted to run in 1024x760, and couldn't see any text on the symbols! The inability to zoom in beyond native resolution made it a major posterial pain to use, since I had to change resolutions just to use it!

Charlie