pcdmis shut downs

[Marty Schwab]

Ok here goes. What do u belive the problem is with shut downs I know we all get them at 1 time or anuther.
grafics card
memory
virtual memory
my onboard grafics is what i beleve is the problem. its 96meg intel 82865g grafics controller
please list your thoughts and what ever just don't highjack this thread into something different or way off track thanks.

[Matthew D. Hoedeman]

I think Pcdmis just has 'brain-farts' from time to time.

One major 'dumper' in V3.5 was deleting using the DELETE key instead of going through the menu. That is nothing BUT Pcdmis, that could NOT be tacked on to anything OTHER than Pcdmis as the fault of the dump. Not memory, not graphics, nothing. And, since it was fixed in an MR, that means it definately was Pcdmis.

Windoze memory allocation can also be to blame. Too often, windoze does not clear 'old info' in the memory very well, it leaves too much garbage it the memory.

The bigger and stronger video cards are better than wimpy ones, but you can turn down the open gl to help this.

Virtual memory is kind of funny. We all know that we should NOT leave the hard drive fragmented, but when windoze increases the size of virt-memory, it IS fragmented. I have a seperate partition on my hard drive JUST FOR the virt-memory. No fragmentation that way.

On-board graphics cards are good for only one thing: making a computer 'run' as cheaply as possible. I have never seen an on-board graphics card with anywhere near as much oomph as an add-on. However, the 'good' thing about the on-board card is that it is 100% compatable with the rest of the hardware in the PC.

There was also a time when Pcdmis didn't play well with anti-virus software, again, that was a Pcdmis thing.

Other applications that you might be running can also be the cause of a dump. If you are running any other thing that uses lots of graphic power at the same time, you might be a redneck, er, in trouble. (sorry)

[Wes Cisco]

Ok here goes. What do u belive the problem is with shut downs I know we all get them at 1 time or anuther.
grafics card
memory
virtual memory
my onboard grafics is what i beleve is the problem. its 96meg intel 82865g grafics controller
please list your thoughts and what ever just don't highjack this thread into something different or way off track thanks.

Well Marty as an interstellar deputy of the PCDGP I have the authority to hijack this to anyplace I want, but we call that commandeering. So while I could take you to Webster's I won't.

Unofficially I have to say I think the main cause of most of the shutdowns is Pc-Dmis. You do not state which version you are asking about. Some are far far far more stable than others! Then there are the other issues to get into. If you are using large CAD files and you do not have sufficient graphics power or memory or processor power any and/or all of those could shut you down. HTH



P.S. Telling us not to hijack your thread is like a red flag to a bull!

[Marty Schwab]

iamnothebestspellerortyper
but i knew i would get something about highjacking my thread
LOL

[tking]

My experience with v7 mr3 has shown the problem most often encountered is the guy I see when I look in the mirror!

Beer!

TK

[jmgreen]

All of the above.

[#2#]

My experience with v7 mr3 has shown the problem most often encountered is the guy I see when I look in the mirror!

Beer!

TK

Who is that guy! He follows me everywhere! Everytime I look in a mirror he is right there looking back!

I don't know why pc-pain in dmis shuts down for me. I have just learned to ctrl+s often and check the forum while it re-starts.

Did someone say beer?

[Underspec]

Onboard graphics is a problem for any Graphics Intense programs, including games.

I agree with most that it is mostly PCDMIS's bugs that cause crashes. To minimize problems you need to upgrade you Graphics Card & Memory (1GB minimum I think). Also, minimize what other things you install on the CMM computer.

[Shelley Liebman]

After all the testing, and many shut downs to study, we found that we crash 3.7 mr2, and mr3 when ever we tried to use the hyper reporting--in that our hyper reports were/are (soon to be changed) located on the file server.
We are in process of moving programs/hyper reports to the local hard drive, and setting up a remote backup to occur nightly.
From here on out, all future programs I write will NOT use the hyper reporting function at all.
I do love the hyper reports, as we can customize them to our liking--hopefully the new inspection reporting module in 4.0 and beyond will have the same flexibility.

[mchough1]

I've also found in 3.7 MR... that modifying an existing alignment is a demon that causes our system to crash occasionally (or as Matt so aptly put it brain-fart!)

[56flh]

This may be a freak occurrance, but we found that the cooling fan on the graphics card had taken a dump causing an occasional overheat that would boot me off the system.

[tking]

Who is that guy! He follows me everywhere! Everytime I look in a mirror he is right there looking back!

Did someone say beer?

Tricky bugger, huh?

Yup, MORE beer!

TK