Silly resistor values

Mainly Windows but you can also get it for Linux.

Frequent crashes are a sure sign of a program _not_ being robust.

What list? Yours?

You have to know a little bit about how print jobs are constructed, and what you are dealing with.

A pdf is a full bit map. Every pixel is defined and stored. That is totally different than how a regular document is formatted for output to a printer. That means that a pdf with a large number of pages makes for a HUGE datagram when printing.

So depending on how you have your spooler set up, you can cause the print job to puke if the datagram is huge.

Even on today's modern boxes.

I never said anything about printing. It does hang there as well once in a while but usually it hangs up just showing a small document. A couple megabytes maybe. That can't be too hard to get right in a software, others have done it a long time ago.

Back-up to an older version. v4 is stable as a rock, though v7 is pretty good.

...Jim Thompson

No. It was firstly and "mainly" written as a Linux app and then eventually got ported to Windows from what I recall.

Grow up and come back when you have some reading comprehension skills.

Others do not have problems opening pdfs, so either you create retarded, non-compliant pdfs, or you have a piece of s*it box.

Why do I not see huge volumes of folks complaining about problems with pdfs and acrobat the way you do?

The finger begins to point back at you, chucko.

Yes, that's what other have said as well. It's like with OS'es where usually it's "older = more stable".

So, have you been on the design team?

First it was written for DOS, then ported to Windows.

Adobe is bloatware spyware crap. Even if it didn't crash, it's amazingly slow. Get Foxit Reader and CutePDF and see the difference.

John

Always Wrong!

John

Adobe hangs up, just viewing files, on every machine I own: Dell, HP, Sony Vaio. Sometines it's so slow it might as well be hung up.

Not me. I don't use Adobe crap any more.

John

What... is he Wrong Again? And so early in the day?

John

switches

understand

how to

of

up the

drawn so

if it

the

That's how

major

No

block

IOW I'd have to chase all over various sheets to see which connector pin is ultimately connected to U12 pin 5.

Progress?

John

If the hierarchical sheets were done "right", the end user/tech wouldn't have to search for anything - all you have to do is put "see sheet n" on the source sheet.

I never had any trouble at all reading military prints, and in the military, EVERYTHING is hierarchcial.

Cheers! Rich

You don't even need that. Usually the connectors are on the top sheet or dedicated sheets. A well drawn set of schematics makes it very clear what goes where. Then there is always the search function.

Oh yeah. Not honoring that rule results in a face about 10" from yours and hollering, plus 20 extra push-ups or an extra round on the tracks in

This is how Pulsonix does it as well, although I have used CAD packages that would generate U1.1, U1.2, U1.3, etc. for each instance of a hierarchical block, which does make things a little nicer, at least if you don't mind your silkscreen also saying U1.!, U1.2, etc. The problem with this is that you're then usually forced to use that package's layout tool as well, since AFAIK there isn't a widely used PCB netlist format that really supports hierarchy. I have heard of a few enterprising individuals who wrote netlist translation tools so that U1.1 would get turned into, e.g., U101, U1.2 becomes U102, etc., though -- and I've known people who did something similar manually for small designs.

I am all for printing everything out at some point, but these days your tech is going to be sitting in front of a computer anyway, so sometimes it's faster if they just pull up the schematic electronically and search for, e.g., R265 and some techs prefer this -- particularly field service guys -- since they're not having to carry all those dead trees around.

---Joel

Usually I can't do that because the layouters all use other systems than I do. When you must backannotate it's all over anyhow, it'll start with U1 in the upper left of the board and so on.

Last year I taught a tech who was populating a prototype the use of a Gerber viewer. That sure made life a lot easier for her.

Did I state any such thing, dumbfuck?

So, you are saying that Linux was an afterthought?

That's odd. I thought it was the initial development platform.