yup! No warning either... perhaps there's a design rules check that I'm missing
that would catch this.  The software won't let you connect traces to the wrong
pins, but it doesn't seem to mind traces crossing over others on different
netlists!  I've done many boards with this software, and YES it crashes
constantly.  I've gotten good at saving state to many different filenames...
a,b,c,d, etc.  I've used orcad and viewlogic in the past for schematic capture.
What do you think about this Eagle software?  Any thoughts?
Ron

David VanHorn wrote:

> At 12:16 PM 5/30/01 -0700, Ron Wilder wrote:
> >I use a similar approach.  I call one dGnd and the other zapGnd or aGnd
> >depending on the type of isolation.  Helps when manually routing the board so
> >that you don't accidentally connect parts to the wrong ground.  Then the final
> >step is to "short" the two big traces near the power connector.  Works
> >fine with
> >Ivex PCB.
> >Ron
>
> Do you mean that Ivex will let you short nets while routing manually?? YUK!
>
> Calling them different names makes them different in orcad, (the old dos
> version) and it will not allow tracks from netX to hit netY. The sneaky pad
> trick, or a zero ohm, is the only way I know to get around it.
>
> --
> Dave's Engineering Page: http://www.dvanhorn.org
>
> I would have a link to FINDU here in my signature line, but due to the
> inability of sysadmins at TELOCITY to differentiate a signature line from
> the text of an email, I am forbidden to have it.
>
> --
> http://www.piclist.com#nomail Going offline? Don't AutoReply us!
> email listserv@mitvma.mit.edu with SET PICList DIGEST in the body

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body