John Larkin wrote:> On Thu, 28 Apr 2011 13:25:28 -0700, Joerg <invalid@invalid.invalid> > wrote: > >> John Larkin wrote: >>> On Wed, 27 Apr 2011 22:51:59 -0500, "krw@att.bizzzzzzzzzzzz" >>> <krw@att.bizzzzzzzzzzzz> wrote: >>> >>>> On Wed, 27 Apr 2011 17:06:50 -0700, John Larkin >>>> <jjlarkin@highNOTlandTHIStechnologyPART.com> wrote: >>>> >>>>> On Wed, 27 Apr 2011 18:00:29 -0500, "krw@att.bizzzzzzzzzzzz" >>>>> <krw@att.bizzzzzzzzzzzz> wrote: >>>>> >>>>>> On Wed, 27 Apr 2011 15:22:09 -0700, josephkk <joseph_barrett@sbcglobal.net> >>>>>> wrote: >>>>>> >>>>>>> On Wed, 27 Apr 2011 07:16:51 -0700, Joerg <invalid@invalid.invalid> wrote: >>>>>>> >>>>>>>> josephkk wrote: >>>>>>>> >>>>>>>> [...] >>>>>>>> >>>>>>>>> Looking at this again, i suggest that you have some version of DLL hell. I >>>>>>>>> do not have any problems with Acrobat on any machine, Windoes or Linux. >>>>>>>>> This is often the root cause of Flash problems as well. >>>>>>>> Why is Foxit stable then and Acrobat isn't? And Cadsoft Eagle is rock >>>>>>>> solid and Orcad isn't? No matter how impatient I am (and with software >>>>>>>> and GUIs I am not the most patient guy) I have not managed to bring >>>>>>>> Eagle to crash on me. I can bring Foxit to choke and huff and puff, but >>>>>>>> not really into a CTRL-ALT-DEL situation. >>>>>>> I should think that's obvious. Neither Foxit nor Eagle have DLLs with >>>>>>> conflicts. In fact, this points to conflicts between Orcad and Acrobat. >>>>>> No Acrobat, here, and I can get OrCAD crashes quite consistently. Fewer with >>>>>> 16.3 than 15.7 but it'll still crash. When it does, it's more often without a >>>>>> save, now. >>>>> Does it have periodic autosave? PADS does. >>>> It causes crashes. >>> >>> Oh. >>> >> Yep. Found that out the hard way. Now that I have set auto-backup to 300 >> minutes (essentially meaning never because by then I am on the next >> schematic) the number of crashes is lower. I also learned to smell >> wooziness and do a quick shut-down. For example when placed probes >> refuse to turn from gray to some bonbon color. > > I've heard mostly horror stories about Orcad. The only thing I've ever > used it for, long ago, was schematic entry for FPGA design. It seemed > to me to be a horror. Sometimes wires would actually enter connection > dots but be a few pixels short of completing the connection. They > managed to automate the cold solder joint! > > PADS just doesn't allow unconnected wire ends. Maybe all the > connection-dot whiners here still are using Orcad. Or diazo machines. >Eagle doesn't either as long as stay-on-grid is turned on. If it ain't you can move a part and if the wires tag along it's connected. Orcad also seems fussy about replacing parts. Delete one, pick new part, move over, click to place ... refuses. Same symbol, no dice. First the wires need to be deleted, part placed, then new wires drawn. Probably I didn't use some magic trick but man, that's the opposite of intuitive. -- Regards, Joerg http://www.analogconsultants.com/ "gmail" domain blocked because of excessive spam. Use another domain or send PM.
Stability of older Orcad/PSpice combos?
Started by ●April 24, 2011
Reply by ●April 28, 20112011-04-28
Reply by ●April 28, 20112011-04-28
On Thu, 28 Apr 2011 18:05:45 -0700, Joerg <invalid@invalid.invalid> wrote:>John Larkin wrote: >> On Thu, 28 Apr 2011 13:25:28 -0700, Joerg <invalid@invalid.invalid> >> wrote: >> >>> John Larkin wrote: >>>> On Wed, 27 Apr 2011 22:51:59 -0500, "krw@att.bizzzzzzzzzzzz" >>>> <krw@att.bizzzzzzzzzzzz> wrote: >>>> >>>>> On Wed, 27 Apr 2011 17:06:50 -0700, John Larkin >>>>> <jjlarkin@highNOTlandTHIStechnologyPART.com> wrote: >>>>> >>>>>> On Wed, 27 Apr 2011 18:00:29 -0500, "krw@att.bizzzzzzzzzzzz" >>>>>> <krw@att.bizzzzzzzzzzzz> wrote: >>>>>> >>>>>>> On Wed, 27 Apr 2011 15:22:09 -0700, josephkk <joseph_barrett@sbcglobal.net> >>>>>>> wrote: >>>>>>> >>>>>>>> On Wed, 27 Apr 2011 07:16:51 -0700, Joerg <invalid@invalid.invalid> wrote: >>>>>>>> >>>>>>>>> josephkk wrote: >>>>>>>>> >>>>>>>>> [...] >>>>>>>>> >>>>>>>>>> Looking at this again, i suggest that you have some version of DLL hell. I >>>>>>>>>> do not have any problems with Acrobat on any machine, Windoes or Linux. >>>>>>>>>> This is often the root cause of Flash problems as well. >>>>>>>>> Why is Foxit stable then and Acrobat isn't? And Cadsoft Eagle is rock >>>>>>>>> solid and Orcad isn't? No matter how impatient I am (and with software >>>>>>>>> and GUIs I am not the most patient guy) I have not managed to bring >>>>>>>>> Eagle to crash on me. I can bring Foxit to choke and huff and puff, but >>>>>>>>> not really into a CTRL-ALT-DEL situation. >>>>>>>> I should think that's obvious. Neither Foxit nor Eagle have DLLs with >>>>>>>> conflicts. In fact, this points to conflicts between Orcad and Acrobat. >>>>>>> No Acrobat, here, and I can get OrCAD crashes quite consistently. Fewer with >>>>>>> 16.3 than 15.7 but it'll still crash. When it does, it's more often without a >>>>>>> save, now. >>>>>> Does it have periodic autosave? PADS does. >>>>> It causes crashes. >>>> >>>> Oh. >>>> >>> Yep. Found that out the hard way. Now that I have set auto-backup to 300 >>> minutes (essentially meaning never because by then I am on the next >>> schematic) the number of crashes is lower. I also learned to smell >>> wooziness and do a quick shut-down. For example when placed probes >>> refuse to turn from gray to some bonbon color. >> >> I've heard mostly horror stories about Orcad. The only thing I've ever >> used it for, long ago, was schematic entry for FPGA design. It seemed >> to me to be a horror. Sometimes wires would actually enter connection >> dots but be a few pixels short of completing the connection. They >> managed to automate the cold solder joint! >> >> PADS just doesn't allow unconnected wire ends. Maybe all the >> connection-dot whiners here still are using Orcad. Or diazo machines. >> > >Eagle doesn't either as long as stay-on-grid is turned on. If it ain't >you can move a part and if the wires tag along it's connected. > >Orcad also seems fussy about replacing parts. Delete one, pick new part, >move over, click to place ... refuses. Same symbol, no dice. First the >wires need to be deleted, part placed, then new wires drawn. Probably I >didn't use some magic trick but man, that's the opposite of intuitive.Copying a part over an old part should work. You can't copy it somewhere else and drag it into position, though. OrCAD won't let you move anything that would change a connection (i.e. a move can't cause a change in the netlist); copy can.
Reply by ●April 28, 20112011-04-28
"Joerg" <invalid@invalid.invalid> wrote in message news:91uh7cFuu8U1@mid.individual.net...> Orcad also seems fussy about replacing parts. Delete one, pick new part, > move over, click to place ... refuses. Same symbol, no dice. First the > wires need to be deleted, part placed, then new wires drawn. Probably I > didn't use some magic trick but man, that's the opposite of intuitive.Check that you have Options->Preferences->Miscellaneous->Wire Drag->Allow Component Move With Connectivity Changes checked? (It isn't checked after a default installation.) Also, in case you aren't aware of this... if you Alt-drag a part, it'll purposely *not* drag its wires along with it. (...and Ctrl+dragging a part duplicates it, as happens in most Windows programs.) ---Joel
Reply by ●April 28, 20112011-04-28
Joel Koltner wrote:> "Joerg" <invalid@invalid.invalid> wrote in message > news:91uh7cFuu8U1@mid.individual.net... >> Orcad also seems fussy about replacing parts. Delete one, pick new part, >> move over, click to place ... refuses. Same symbol, no dice. First the >> wires need to be deleted, part placed, then new wires drawn. Probably I >> didn't use some magic trick but man, that's the opposite of intuitive. > > Check that you have Options->Preferences->Miscellaneous->Wire > Drag->Allow Component Move With Connectivity Changes checked? (It isn't > checked after a default installation.) >Just tried it but unchecked it again. It does then accept parts to be scooted into position but when moving them it breaks connections. Not so cool. Cadence should buy a copy of Eagle and see how it's done :-)> Also, in case you aren't aware of this... if you Alt-drag a part, it'll > purposely *not* drag its wires along with it. (...and Ctrl+dragging a > part duplicates it, as happens in most Windows programs.) >Another annoying "feature" of Orcad is that it pushes wires upon block moves. Meaing some cleanup after evey move, including some contortion art. Makes no sense. SDT didn't do that, but that was from the good old times. -- Regards, Joerg http://www.analogconsultants.com/ "gmail" domain blocked because of excessive spam. Use another domain or send PM.
Reply by ●April 28, 20112011-04-28
On Thu, 28 Apr 2011 18:18:41 -0700, "Joel Koltner" <zapwireDASHgroups@yahoo.com> wrote:>"Joerg" <invalid@invalid.invalid> wrote in message >news:91uh7cFuu8U1@mid.individual.net... >> Orcad also seems fussy about replacing parts. Delete one, pick new part, >> move over, click to place ... refuses. Same symbol, no dice. First the >> wires need to be deleted, part placed, then new wires drawn. Probably I >> didn't use some magic trick but man, that's the opposite of intuitive. > >Check that you have Options->Preferences->Miscellaneous->Wire Drag->Allow >Component Move With Connectivity Changes checked? (It isn't checked after a >default installation.)It wasn't in earlier releases but I think it is now. I've never changed that option and no one would have done it for me.>Also, in case you aren't aware of this... if you Alt-drag a part, it'll >purposely *not* drag its wires along with it. (...and Ctrl+dragging a part >duplicates it, as happens in most Windows programs.)...which is stupid because Ctrl+drag is also how you select components in an area. OrCAD likes to confuse the two and you get an area selected and copied on top of itself (and both still selected). Good thing Ctrl-Z is handy.
Reply by ●April 28, 20112011-04-28
On Thu, 28 Apr 2011 18:29:41 -0700, Joerg <invalid@invalid.invalid> wrote:>Joel Koltner wrote: >> "Joerg" <invalid@invalid.invalid> wrote in message >> news:91uh7cFuu8U1@mid.individual.net... >>> Orcad also seems fussy about replacing parts. Delete one, pick new part, >>> move over, click to place ... refuses. Same symbol, no dice. First the >>> wires need to be deleted, part placed, then new wires drawn. Probably I >>> didn't use some magic trick but man, that's the opposite of intuitive. >> >> Check that you have Options->Preferences->Miscellaneous->Wire >> Drag->Allow Component Move With Connectivity Changes checked? (It isn't >> checked after a default installation.) >> > >Just tried it but unchecked it again. It does then accept parts to be >scooted into position but when moving them it breaks connections. Not so >cool. Cadence should buy a copy of Eagle and see how it's done :-) > > >> Also, in case you aren't aware of this... if you Alt-drag a part, it'll >> purposely *not* drag its wires along with it. (...and Ctrl+dragging a >> part duplicates it, as happens in most Windows programs.) >> > >Another annoying "feature" of Orcad is that it pushes wires upon block >moves. Meaing some cleanup after evey move, including some contortion >art. Makes no sense. SDT didn't do that, but that was from the good old >times.You can Cntl-uncheck wires before the move. Uncheck them in the segment *before* the segment you don't want to "push". Also, only push in one direction at a time. It's dumb but not as bad as you indicate. OTOH, bundle (bus) operation is backwards. There, you want to select the segment. ...and taps still get messed up no matter what you do.
Reply by ●April 28, 20112011-04-28
On 4/28/2011 8:01 PM, Jim Thompson wrote:> On Thu, 28 Apr 2011 17:55:56 -0700, Joerg<invalid@invalid.invalid> > wrote: > >> Jim Thompson wrote: >>> On Thu, 28 Apr 2011 13:25:28 -0700, Joerg<invalid@invalid.invalid> >>> wrote: >>> >>>> John Larkin wrote: >>>>> On Wed, 27 Apr 2011 22:51:59 -0500, "krw@att.bizzzzzzzzzzzz" >>>>> <krw@att.bizzzzzzzzzzzz> wrote: >>>>> >>>>>> On Wed, 27 Apr 2011 17:06:50 -0700, John Larkin >>>>>> <jjlarkin@highNOTlandTHIStechnologyPART.com> wrote: >>>>>> >>>>>>> On Wed, 27 Apr 2011 18:00:29 -0500, "krw@att.bizzzzzzzzzzzz" >>>>>>> <krw@att.bizzzzzzzzzzzz> wrote: >>>>>>> >>>>>>>> On Wed, 27 Apr 2011 15:22:09 -0700, josephkk<joseph_barrett@sbcglobal.net> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> On Wed, 27 Apr 2011 07:16:51 -0700, Joerg<invalid@invalid.invalid> wrote: >>>>>>>>> >>>>>>>>>> josephkk wrote: >>>>>>>>>> >>>>>>>>>> [...] >>>>>>>>>> >>>>>>>>>>> Looking at this again, i suggest that you have some version of DLL hell. I >>>>>>>>>>> do not have any problems with Acrobat on any machine, Windoes or Linux. >>>>>>>>>>> This is often the root cause of Flash problems as well. >>>>>>>>>> Why is Foxit stable then and Acrobat isn't? And Cadsoft Eagle is rock >>>>>>>>>> solid and Orcad isn't? No matter how impatient I am (and with software >>>>>>>>>> and GUIs I am not the most patient guy) I have not managed to bring >>>>>>>>>> Eagle to crash on me. I can bring Foxit to choke and huff and puff, but >>>>>>>>>> not really into a CTRL-ALT-DEL situation. >>>>>>>>> I should think that's obvious. Neither Foxit nor Eagle have DLLs with >>>>>>>>> conflicts. In fact, this points to conflicts between Orcad and Acrobat. >>>>>>>> No Acrobat, here, and I can get OrCAD crashes quite consistently. Fewer with >>>>>>>> 16.3 than 15.7 but it'll still crash. When it does, it's more often without a >>>>>>>> save, now. >>>>>>> Does it have periodic autosave? PADS does. >>>>>> It causes crashes. >>>>> >>>>> Oh. >>>>> >>>> Yep. Found that out the hard way. Now that I have set auto-backup to 300 >>>> minutes (essentially meaning never because by then I am on the next >>>> schematic) the number of crashes is lower. I also learned to smell >>>> wooziness and do a quick shut-down. For example when placed probes >>>> refuse to turn from gray to some bonbon color. >>> >>> I hope you're backing up to other media. ... >> >> >> Oh yeah, three different media. With Orcad me no take no chances no more :-) >> >> >>> ... Your ass is about to be grass ;-) >>> >> >> What, you had that turning gray of probe pins happen, too? > > No, Remember I don't use Crapture, but can convert my schematics to > Crapture upon request... without ever opening Crapture ;-) >The word "crapture" has become trite, especially when used three times in one sentence. Please, Jim, tell me you're not developing a feces fetish like your most recent admirer.> ...Jim Thompson
Reply by ●April 29, 20112011-04-29
On Sun, 24 Apr 2011 08:18:01 -0700, Joerg <invalid@invalid.invalid> wrote:> >In your experience, what was a relatively stable (as in "not many >crashes") version I could try to go back to?The older ones are definitely more stable. They got heavy on theft deterrence, and those checks, and that detection engine is part of why the newer versions suck so badly. They suck so bad, they suck at sucking. Anyway, 13 thru 15 are nice. 15 works good on a laptop (hey, if I own the license, I should be able to run it anywhere). We used to buy software dongle replacements from a house in Canada.
Reply by ●April 29, 20112011-04-29
On Mon, 25 Apr 2011 00:24:46 -0400, "Michael A. Terrell" <mike.terrell@earthlink.net> wrote:> >"krw@att.bizzzzzzzzzzzz" wrote: >> >> On Sun, 24 Apr 2011 15:35:21 -0700, Joerg <invalid@invalid.invalid> wrote: >> > >> >Then I must continue the crash -> re-install game. >> >> I've never had to re-install but the binaries are on a server (floating >> licenses and all that). Then again, we don't use P-Spice anymore, either. > > > It sounds like a hardware problem like not enough RAM, or a dying >hard drive. If you don't have enough RAM, the drive is constantly >reading and writing swap files. That pushes the hardware to it's limits >and causes more errors. Also, it may be old enough to have failing >electrolytics on the motherboard. I recently picked up three Acer >Aspire L100 mini desktops with bad capacitors. All three were running >512 MB of RAM. One also had a bad hard drive. There are just over a >year old.That is the most retarded prognosis I have ever seen. I'll bet his box will run blu-ray video stream level stuff, no problem. That is GPU AND CPU intensive decode and render routines, AND reads AND writes to swap AND ALL the RAM. I'll bet his hardware is fine. Your prognosis is pathetic. RAM OR a hard drive? Which is it, boy? What a joke. IF his hard drive was giving errors, they would still be there. He would have said something. I'll bet those machines you have were NEVER cleaned by their owner, and they ran hot most of their life, and even up until failure. (He'll come back and claim that they were 'clean as a whistle'). Good chance that you failed them too. With a garage full of junk, it would appear that what you have is anything but "The Midas Touch".
Reply by ●April 29, 20112011-04-29
