Prime crashes upon fsolve

[emax]

Thank you for your answers.

I have now set the Prime to the standard settings, language English and Radians mode - just to get ahead of such suggestions.

This didn't help.

To your suggestions: It is of course a workaround to define a guess. But this is not a real option.

With such a ridiculously simple task like the one showed here, that may be possible. But with more complex problems, those where you really can't guess the answer, that's exactly what the calculator should do: Relieve me of guessing games. That's what I bought it for. And even a TI89/V200, which admittedly needs some seconds for the solution, doesn't need guesses. A year ago I bought one on ebay for 20 Euros for occasional messing around and so could try this out.

On the Prime, there is a setting of "Recursive Evaluation" which could be a cause. This is by default set to 25, and I didn't try other settings. And even if 25 was to small, the calculator should (after having been released seven years ago) never crash. Instead, you should see a message.

But the Prime just rebooted. :-o

For me, this is the equivalent of a windows blue screen. :-|

I had another problem before this happened, but didn't post it here as I could not reproduce it: The Prime (again in CAS mode) all of a sudden showed a totally garbled display completely covered with blueish and whiteish tatters. Keys didn't work, shift-off didn't work, no responses to whatever I did. And the display didn't dim after the dimming time had expired. The only way to get back to operation was a hard reset. I had this just once, but haven't used the Prime much since then.

Another thing came to my attention: When I edited a longer formula (again before the problem occurred which I described in this thread), I got strange error messages which contained unreadable characters. They contained characters like \@\@ or ^@^@ or so, which reminds me of binary zeroes being displayed sometimes in the output of faulty programs. As I am new to the prime, and as I could not reliably reproduce this I was reluctant to post this here.

It seems, that my hardware-version is quite a new one. I don't hope, that this is the reason for the problems.

One thing is certain: I have lost some confidence.

As there wasn't (yet?) an answer from an HP member here, I'd like to know whether there is an official contact at HP to ask for help.

Can anybody point me to the right place?