: "Steve Jones" wrote
: > :
: >: "Steve Jones" wrote
: >: Hello
: >: I am posting this on behalf of a friend of mine.
: >: He has recently taken delivery of a new Dell computer with 512Mb of
: >: memory and a 3Ghz P4. The OS is Xp Home.
: >: He wishes to run Pro Engineer Student edition on this machine but
: >: after installing, the program runs but refuses to accept any input and
: >: stops responding to mouse and keyboard.
: >: The same program ran on his much slower machine without any hitches
: >: and the only difference between his old machine and the new one apart
: >: from a faster chip and more memory is that the newer machine has a PCI
: >: express 128 Mb ATI Radeon graphics card rather than an AGP slot in the
: >: slower computer.
: >: Could this be where the problem arises?
: >Easily possible ~ don't know of another program that is as graphically
: >cantankerous as Pro/e, meaning, cards and drivers play an inordinately large
: >in generating problems, including those which do not immediately seem graphics
: >First thing to check is the PTC website for certified/decertified graphics
>If this card is on the decertified list, you can guarantee problems. Also,
: >out the type of card that is certified. For ATI/Radeon, there's only the
: >cards. Not on this list? You've just increased your chances of
: >many of them i/o related.
: >Then, even if your card is on the list of those certified/supported, check the
: >driver this card needs to be compatible with Pro/e. The right card with the
: >driver is just as problematic.
: >This kind of troubleshooting boils down to a process of elimination. If these
: >things check out OK, we'll have to try something else.
: >David Janes
: Tried turning off hardware acceleration. No luck. A manual I managed
: to acquire suggested that I give the network card an IP address with a
: subnet mask added. No luck.
: It is a program called Xtop that is crashing.
Check in any of the working directories you were logged to when it crashed. You
should find there a file called std.err or std.out, quite innocuous looking,
really. These ascii files usually contain 1 line of text that says what error
encountered. I have discovered no other function for these files except to
errors. One is always created when the program crashes, even if no other
indication is given and the program just seems to wink out, poof, it's gone,
with some minutes/hours worth of work. Usually, when it crashes, it will contain
some innocuous message like "Raising signal: 00013". And that little turd in
working directory is all the 'apology' or 'help' you get. Still, you may be able
to find reference to these messages on the PTC website and get some kind of hint
as to what is actually causing the crashes.