Re: hp 50g broken key hinges

J.Chen wrote:
On Apr 22, 6:09 pm, jobar <n...@xxxxxxxxxxxxxxx> wrote:
drela...@xxxxxxxxx wrote:
I have had my hp50g for about a year now, and use it daily for
calculus, physics, and chemistry. Recently, the row of keys above the
number pad (ie the divide key, EEX key, and +/- key) have started to
develop problems where the key can be pressed a little off center
without the key clicking (and sometimes without the key registering a
press). More recently, my 5 and enter key have started to develop this
same problem. Has anyone else had similar problems? I thought the
50g's keyboard was supposed to be fixed somehow.
Prior to getting my 50g, I have had to 49g+s. The first one was an
earlier model with really stiff keys that missed keystrokes regularly.
Hp quickly replaced it under warranty without question and didn't ask
for the old one back. My second 49g+ developed keyboard problems
similar to my 50g, and eventually the keys became completely loose,
"floating" in place and almost impossible to press. My second 49g+ was
already out of warranty, but after a long time on the phone, hp
replaced it as well and didn't ask for the old one back.
Luckily, my 50g's keyboard has not broken to the point where the keys
are "floating" in place, but I am almost completely sure that it will
eventually become so, as my 49g+ did. I wonder how common problems
with the 50g's keyboard are. I realize that I probably use my
calculator more than most people, but there don't seem to be any
complaints about the 50g's key hinges breaking. Would hp replace my
calculator a third time, or am I out of luck?
PS what change exactly was made to the 50g's keyboard? I remember
reading somewhere that metal domes are used, but was the hinge design
ever actually changed?
I'm still battling with HP to get a replacement calc for the obviously
flawed 49g+. I didn't complain until after the warranty period thinking
somehow HP would make good on it. If still under warranty get it replaced.

could this problem be due to heavy use? or just a bad one out of the
batch?

Exactly the opposite problem. The thing was babied to such a degree that the latent problem didn't manifest until the warranty expired. If I had treated it rough, it would have fallen apart and I would have had it replaced by HP's "award winning support team".

Oh well. Let me tell you about my Fluke 87 or my Tek 453 scope both of which cost me < the HP 49g+ and actually work (after 30 years for the Tek).
.

Relevant Pages

  • Re: HP 49G+ keyboard return
    ... contractor and I shouldn't have keyboard problems any more. ... The difference between 631 and 525 means your calculator was ... As the warranty period obviously started when you bought your HP, ... I called HP to complain and asked for a replacement. ...
    (comp.sys.hp48)
  • Re: HP 49G+ keyboard return
    ... contractor and I shouldn't have keyboard problems any more. ... The difference between 631 and 525 means your calculator was ... As the warranty period obviously started when you bought your HP, ... I called HP to complain and asked for a replacement. ...
    (comp.sys.hp48)
  • Re: HP 49G+ keyboard return
    ... contractor and I shouldn't have keyboard problems any more. ... The difference between 631 and 525 means your calculator was ... As the warranty period obviously started when you bought your HP, ... I called HP to complain and asked for a replacement. ...
    (comp.sys.hp48)
  • Re: hp 50g broken key hinges
    ... 50g's keyboard was supposed to be fixed somehow. ... Hp quickly replaced it under warranty without question and didn't ask ... calculator more than most people, but there don't seem to be any ... I'm still battling with HP to get a replacement calc for the obviously flawed 49g+. ...
    (comp.sys.hp48)
  • Re: hp 50g broken key hinges
    ... 50g's keyboard was supposed to be fixed somehow. ... Hp quickly replaced it under warranty without question and didn't ask ... calculator more than most people, but there don't seem to be any ... I'm still battling with HP to get a replacement calc for the obviously ...
    (comp.sys.hp48)