HP Forums
48G MTH (math) key not working? - Printable Version

+- HP Forums (https://www.hpmuseum.org/forum)
+-- Forum: HP Calculators (and very old HP Computers) (/forum-3.html)
+--- Forum: General Forum (/forum-4.html)
+--- Thread: 48G MTH (math) key not working? (/thread-13853.html)

48G MTH (math) key not working? - lemontea - 10-24-2019 01:05 AM

It's been ages since I used the 48G and I'm not sure if it's the hardware or what?

How do I use the MTH key again?

I press it and nothing happens.

RE: 48G MTH (math) key not working? - Joe Horn - 10-24-2019 01:19 AM

(10-24-2019 01:05 AM)lemontea Wrote:  It's been ages since I used the 48G and I'm not sure if it's the hardware or what?

How do I use the MTH key again?

I press it and nothing happens.

It displays the "Math Menu" in the softkey area, beginning with "VECTR" and ending (after pressing the NXT key) with "CONST". If the Math Menu is already displayed, pressing the MTH key will seem to do nothing.

If it doesn't display the Math Menu, it might be tied to a key assignment. Exit USER mode (left-shift alpha) and try again. If that doesn't help, then I'd suspect a hardware problem, although a conflicting library could also be the problem.

RE: 48G MTH (math) key not working? - lemontea - 10-24-2019 01:22 AM

Thanks Joe!

You’re right! I didn’t realize the Math menu was ALREADY displayed. Now I remember how it works. It goes back to the top Math menu, if another Menu or another Menu Level is displayed.



(10-24-2019 01:19 AM)Joe Horn Wrote:  
(10-24-2019 01:05 AM)lemontea Wrote:  It's been ages since I used the 48G and I'm not sure if it's the hardware or what?

How do I use the MTH key again?

I press it and nothing happens.

It displays the "Math Menu" in the softkey area, beginning with "VECTR" and ending (after pressing the NXT key) with "CONST". If the Math Menu is already displayed, pressing the MTH key will seem to do nothing.

If it doesn't display the Math Menu, it might be tied to a key assignment. Exit USER mode (left-shift alpha) and try again. If that doesn't help, then I'd suspect a hardware problem, although a conflicting library could also be the problem.