> There is an alternate 49g+ rom at hpcalc.org
> http://www.hpcalc.org/details.php?id=6376
> Has anyone updated his/her calc to it?
Yes, I just did. Thanks for alerting us to its existence.
> And did it improve your situation of
> missed or multiple keystrokes, if you
> had a "situation"?
YES YES YES, it helps GREATLY! I can even play MINEHUNT now! I get NO
repeated keystrokes any more! YAY!!!
Hey, people, TRY this ROM version! But beware, it seems to overwrite
things in Port 2 without warning or notice, so be sure to back up Port
2 before upgrading.
It does NOT solve the amazingly-hitherto-unmentioned Busy Bug
introduced with ROM 2.00, namely: IF, at the exact moment that the busy
annunciator turns off, a key is pressed, THEN that key will go into the
key buffer but the calculator will immediately go into idle mode, so
that the key will not be processed until the next interrupt (e.g. next
keystroke). When typing rapidly, this will FEEL like a
garbage-collection delay, but it's not. Next time a key seems to have
been "missed", look at the busy annunciator to make sure it's off and
then press any key (e.g. the SPC key). If BOTH the "missed" key and the
second key are then processed, you just experienced the The Busy Bug.
It also can be easily experienced while browsing up and down the CAT or
strolling through the minefield in MINEHUNT; a press of the cursor key
can SEEM to be "missed" but then the very next press SEEMS to be
"doubled". Truth is, they are neither missed nor doubled; the first one
was merely delayed by The Busy Bug until the next keystroke.
HP: Get Busy!
-jkh-
-Brandon
Chuck Rushton wrote:
> There is an alternate 49g+ rom at hpcalc.org
> http://www.hpcalc.org/details.php?id=6376
>
> Has anyone updated his/her calc to it? And did it improve your situation of
> missed or multiple keystrokes, if you had a "situation"?
>
> I have a CN406xxxxx (external), CN408xxxxx (internal) and thus far none of
> the updates has given me much help with the keyboard.
>
> I suppose it's worth a try....
>
> chuck
> I suppose it's worth a try....
Does it glue the key hinges back together? Thought not...
Regards
Steen
> There is an alternate 49g+ rom at hpcalc.org
> http://www.hpcalc.org/details.php?id=6376
FYI
It seems that we were beta testers with build 80.
With build 80, VERSION returned: "Version HP49-B REVISION #2.01-2"
With build 83, VERSION returns: "Version HP49-C REVISION #2.01"
Back in the "frozen hamster but blue" hp49g days if memory serves correctly
"-B" indicated beta version "-C" comercial release.
Rick
By the way, I still have double keystrokes :(
Best regards.
Many thank's to the developer of this build !
Regards,
Herve
The easiest way for me to discover doubles is to play the minehunt
game. Using the arrows keys instead of the number keys to navigate
the minefield, on the third game I tried, I managed to get doubles
twice, and several missed keypress attempts. (I lost the game since
the last double landed on a mine!) So version 2.01 doesn't appear to
have fixed the arrow key doubles, anyway. It takes awhile to notice
the other key effects ... but if I have any news, I'll be glad to let
you know.
-drd-
On Thu, 01 Dec 2005 16:26:05 GMT, "Chuck Rushton"
It DOES !!!! Amazing....
-drd-
"Rick Neufeld" <rneu...@gmail.com> schrieb im Newsbeitrag
news:l178t0cgamok$.1t1fjks9iw3oj.dlg@40tude.net...
In the FHB (or Rubber Duck) days even the 'C' versions were of beta quality
IMHO;-)
Raymond
<SNIP>
> Hey, people, TRY this ROM version! But beware, it seems to overwrite
> things in Port 2 without warning or notice, so be sure to back up Port
> 2 before upgrading.
>
Oh joy! I'm stoked....not.
> It does NOT solve the amazingly-hitherto-unmentioned Busy Bug
> introduced with ROM 2.00, namely: IF, at the exact moment that the busy
> annunciator turns off, a key is pressed, THEN that key will go into the
> key buffer but the calculator will immediately go into idle mode, so
> that the key will not be processed until the next interrupt (e.g. next
> keystroke). When typing rapidly, this will FEEL like a
> garbage-collection delay, but it's not. Next time a key seems to have
> been "missed", look at the busy annunciator to make sure it's off and
> then press any key (e.g. the SPC key). If BOTH the "missed" key and the
> second key are then processed, you just experienced the The Busy Bug.
> It also can be easily experienced while browsing up and down the CAT or
> strolling through the minefield in MINEHUNT; a press of the cursor key
> can SEEM to be "missed" but then the very next press SEEMS to be
> "doubled". Truth is, they are neither missed nor doubled; the first one
> was merely delayed by The Busy Bug until the next keystroke.
>
Would the "delayed stroke" eventually execute, if you simply wait. If so,
that's what's been bugging me.
Scott Chapin
This ROM version eliminates the missed and double key strokes! Finally,
the keys register reliably, including the arrow, alpha, and shift keys.
I'm glad to have this calculator. It's way faster than the older 48/49.
I haven't gotten any broken keys; the quality maybe worse than the old
48 in some ways, but who cares, as long as you don't abuse the
calculator. The g+ is way faster.
> the quality maybe
> worse than the old 48 in some ways, but who cares, as long as you
> don't abuse the calculator.
I care. And I haven't abused the calculator, but the keys broke anyway.
As did the black plastic strip, but that seems very minor at the moment.
Regards
Steen
> Would the "delayed stroke" eventually execute, if you simply wait.
Two possibilities:
IF it's delayed by a garbage collection, THEN the answer is definitely
yes: the busy annunciator will be ON, nothing will seem to be happening
(during the garbage collection process), and then the delayed
keystrokes (up to 15 of 'em) get executed. During ordinary operations,
garbage collection is extremely fast on the 49g+, but the more
different unreferenced things there are on the stack, the longer it
takes.
IF it's delayed by The Busy Bug, THEN the answer is barely yes: the
busy annunciator will be OFF, nothing will in fact be happening, and
then when the next system interrupt occurs the key will execute. The
next system interrupt would ordinarily be caused by the next keystroke,
but if you don't press another key and just wait, then the next system
interrupt might take a long time to occur (depending on your TOFF
setting, alarms, clock display, and so on).
<SNIP>
> During ordinary operations,
> garbage collection is extremely fast on the 49g+, but the more
> different unreferenced things there are on the stack, the longer it
> takes.
Hmmm. Sometimes when I call the object's name followed by its contents (a
largish matrix) to the stack, modifiy the matrix and swap to store, it will
hang a long time.
I never store using 'LS' 'OBJ' anymore. I have accidentally overwritten
way to many objects that way!
Thanks for the info.
Scott Chapin
It was the 0 key om my first one, and the 2 key followed by the 0 key on my
second one. Maybe these numbers are use more frequently? The 0 doesn't
suprise me as being oft used, but why a 2 over the other non-zero digits?
Scott Chapin
-Brandon
> I never store using 'LS' 'OBJ' anymore. I have
> accidentally overwritten way too many objects that way!
You know about the magical LASTARG rescue in that case, no? If not,
check this out. Because it's so easy to overwrite objects using
LS-softkey, all RPL machines store the OLD contents (instead of the new
contents as would be expected) into LASTARG. That way, if you realize
RIGHT AWAY that you overwrote something, just press LASTARG and *voila*
there on the stack is what you thought you lost! This LASTARG rescue
also works after pressing the STO key on the keyboard, or the soft
PURGE key in the TOOL menu. It even works in the "menu 30" solver [RS+7
ROOT SOLVR] after performing a single-key STO. It does *not* work for
STO or PURGE in a program, nor the STO and PURGE menu keys in the PRG
MEM [DIR] menus.
-jkh-
<SNIP>
ARGH...ARGH...he beats his head on the wall. No, I didn't know that.
Thanks,
Scott Chapin
TED
Did you store the library on a computer and then restore it by any
chance? Or copied from flash to RAM then back to Flash
That's the only explanation I can offer as why you have twice the library
JY
Before I upgrade from v50 to v80-b83 this time. I were not sure if it's
better to remove all the file on port2 in advance. I moved all the
files, from port2 to port3, except L226 and L227. And copied them back
after upgrading v80-b83. This time I did not do anything to these two
files.
Please advise how to do is better. Should I delete one of the
duplicated L227 or clean port2 and reflash it again?
JY
I have reflashed it again.
Thanks for who worked hard for this job. There are many pepole works
silently.
I did not say thanks to HP. The broken keys still cannot be fixed. And
they even never admit this major defect.
> Chuck Rushton writes:
>
>> There is an alternate 49g+ rom at hpcalc.org
>> http://www.hpcalc.org/details.php?id=6376
>> Has anyone updated his/her calc to it?
>
> Yes, I just did. Thanks for alerting us to its existence.
>
>> And did it improve your situation of
>> missed or multiple keystrokes, if you
>> had a "situation"?
Well, I just have to throw in my 0.02€:
My calc has the serial number CN33900342 engraved on the case and CN33928709
as reported by SERIAL, so I guess it's pretty early.
I had no hope that the keyboard would work correctly because no ROM upgrade
has ever fixed missed keystrokes and double keypresses - I'd come to think
that my calc was hardware faulted, but...
ROM 83 FIXED IT ALL!
Great work indeed!!!
Sometimes I've experienced the Busy Bug reported by Joe Horn, and I hope it
will be fixed in the future, but it's definitely a minor flaw... now I can
type as fast as I can and don't miss a key...
--
Stefano Priore | Debian Sarge 3.1r0
--------------------------------+--------------------------------
"Video meliora proboque, | Linux Registered User #210152
autem deteriora sequor..." | Linux Registered Machine #97752
Very true!
JY is the man!
BUT
I would still give thanks to Cyrille & al
[not to the HPQ Co.]
VPN