HP Forums

Full Version: WP34S rev. 2668 bug report
You're currently viewing a stripped down version of our content. View the full version with proper formatting.

Stacklift gets disabled by turning the calculator off and back on. For example, 2 Enter 3 x results in 6. After turning the calculator off an back on the 6 is still there. Another calculation, for example 3 Enter 5 * then results in 15. But roll down doesn't get the 6 back as expected.

I am not sure if the problem is still present in the latest revision (sorry, I can't flash since I am on holiday).

Cheers,
Harald

Thanks for reporting. Not observed, however, in emulator build 2758 (the latest revision available) nor on my 30b-based 34S build 1108 (the earliest revision available). Thus, must have happened in between. HTH ;-)

And I hope this one is not be overlooked because it's already moved down a few posts:

http://www.hpmuseum.org/cgi-sys/cgiwrap/hpmuseum/forum.cgi?read=216969#216969

It's a quite serious problem. :(

I cannot reproduce it neither on a real WP34s running the last revision.

IIRC this has been addressed in the later builds.

Quote:
I cannot reproduce it neither on a real WP34s running the last revision.

Sorry, but then you must have done something wrong. It's impossible that this bug happens here for me in both emulators (standard and QtGui, latest versions) but not for you.

So once again, program simplified:

LBL A
1
STOP
3
RTN
LBL 21
2
RTN
Now do exactly the following steps:
1) press [A] and you'll see 1 in X
2) press XEQ STO and you'll see 2 from subroutine LBL 21
3) and now press R/S and you'll still see the 2 from LBL 21 instead of the 3 from the main program


Edited: 7 Apr 2012, 5:20 a.m.

Franz, you were hijacking this thread :-( Pascal's response referred to the OP. Please (!) continue your old thread with that error you refer to, don't mess up things.

Quote:
And I hope this one is not be overlooked because it's already moved down a few posts:

http://www.hpmuseum.org/cgi-sys/cgiwrap/hpmuseum/forum.cgi?read=216969#216969

It's a quite serious problem. :(


Maybe. Please continue your old thread and it will move up again. Don't hijack other threads >:-(

Quote:
Franz, you were hijacking this thread :-( Pascal's response referred to the OP. Please (!) continue your old thread with that error you refer to, don't mess up things.

I'd say you are messing up things, Walter.

I don't know what you mean by OP, but Pascal definitely replied to MY post - have a look again.

And posting a different bug in another bug report is nothing what I would call hijacking.

Quote:
I don't know what you mean by OP, but Pascal definitely replied to MY post - have a look again.

No. I was responding to the bug described in this thread. Sorry if I clicked "respond" not exactly after the exact message.

BTW, I would not answer to your post and talk about your bug in this thread. I would have gone to the original one.

I just re-flashed from 2668 to 2726; the bug was in the earlier version but is fixed in 2726.

Sorry for reporting a bug that has already been fixed again. I will flash with the latest version when I get back.

Cheers,
Harald

Not a problem, it is far better for a bug to be reported a few times than not at all.

- Pauli