Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

HP49 problem (bug?)

0 views
Skip to first unread message

Steindor E. Sigurdsson

unread,
Dec 12, 1999, 3:00:00 AM12/12/99
to
I've been having problems with my 49G, it frequently freezes and corrupts my
Home directory.

The following is an example of a sequence of actions that causes my 49G to
freeze (on both 1.10 and 1.16).

PLOT(X) [ENTER]
[->] [TABLE]
[->] [TBLSET]
|
V (down arrow tvice, to ZOOM)
[F6] (OK)

Could someone try the above and let my know if this is just a bug or if i
might have a damaged calculator.

I don't know wheter it is relevant but when I turned it on for the first
time I got two messages, "Invalid card data" and "Try to recover memory?".

Any ideas?
___
Steindor E. Sigurdsson
ste...@hi.is

Alex Lagor

unread,
Dec 12, 1999, 3:00:00 AM12/12/99
to
I tried a similar manoeuvre on mine just now (to test the calculator)...but
not following exactly your steps (I didn't fully understand what you
meant)...anyhow, suddenly it crashed and stated "Recover Memory"...so, it
might be a bug after all...but again, this might be pure coincidence since I
didn't follow exactly all your steps!


----------------------------------------------------------
A_L_E_X @ Technical University, Budapest
Student of Software Engineering
email : bloody_...@hotmail.com
www : http://driving.virtualave.net

Steindor E. Sigurdsson

unread,
Dec 13, 1999, 3:00:00 AM12/13/99
to
This is what I do to crash my 49G (It didn't quite come out right earlier,
sorry)

Type PLOT(X) and press [ENTER]
Press "left shift" (blue left arrow) and then [TABLE] (F6)
Press "left shift" (blue left arrow) and then [TBLSET] (F5)
Press [F6] (OK)

Like I said earlier, I've been having problems with my HP (halts and memory
corruption) so I'm hoping that some feedback could help me figure out if
this is caused by an unstable operating system or if I just got a faulty
calculator.

Also,
does anyone know what "Invalid card data" means?

aven...@epita.fr

unread,
Dec 13, 1999, 3:00:00 AM12/13/99
to

Hello.

I can't reproduce any problems using your key sequence on any ROM
version (1.05, 1.10 and 1.16)...

What version are you using ?
In order to get rid of the "Invalid Card Data" type the PINIT
sequence...

Jean-Yves

In article <832iso$ocb$1...@gneisti.skima.is>,


Sent via Deja.com http://www.deja.com/
Before you buy.

Steindor E. Sigurdsson

unread,
Dec 13, 1999, 3:00:00 AM12/13/99
to
This happens on both v1.10 and v1.16 (it either hangs, distorts the image on
the screen or responds with "Try to recover memory?").
And this is not the only thing that causes problems, just the only sequence
I've noted exactly and been able to repeat (it has also happened while
running games for example).
Like I noted in my first post, when I turned it on for the first time it
responded with "Try to recover memory?" and "Invalid card data", I was
wondering if that might indicate problems with the machine itself.

My main concern is therefore, could this problem be related to software (and
hence fixable) or hardware?
___
Steindor


<aven...@epita.fr> wrote in message news:832phg$2b8$1...@nnrp1.deja.com...

Joėl Bourquard

unread,
Dec 13, 1999, 3:00:00 AM12/13/99
to
> This happens on both v1.10 and v1.16 (it either hangs, distorts the image
on
> the screen or responds with "Try to recover memory?").
> And this is not the only thing that causes problems, just the only
sequence
> I've noted exactly and been able to repeat (it has also happened while
> running games for example).

You shouldn't swear by games' stability.. Some may crash ! Just run a big
UserRPL program,
or try running some safe Assembly program to check whether it happens..

> Like I noted in my first post, when I turned it on for the first time it
> responded with "Try to recover memory?" and "Invalid card data", I was
> wondering if that might indicate problems with the machine itself.

I don't think so.. I guess it's because the RAM contents were undefined when
you
bought the machine.

> My main concern is therefore, could this problem be related to software
(and
> hence fixable) or hardware?

Maybe your hp's RAM is not reliable.. The TRM never happens with my machine
(rom 1.16),
except when I'm coding and running bad Assembly programs (but that's another
story..).
A garbled screen happened only once, and ON-C did the job.

You should run some test program ! Also, try ON-D to check the RAM ..

Regards,
Joėl

Andrew Cruickshank

unread,
Dec 13, 1999, 3:00:00 AM12/13/99
to

Alex Lagor wrote in message <831cq5$pbo$1...@mail.euroweb.hu>...

> anyhow, suddenly it crashed and stated "Recover Memory"...so, it
>might be a bug after all...but again, this might be pure coincidence since
I
>didn't follow exactly all your steps!
>

It's either a hardware fault or a bug if any user action
causes a crash.

---------------
Andrew.


jcrm...@hotmail.com

unread,
Dec 14, 1999, 3:00:00 AM12/14/99
to
Hello All.
Yes, I tried these keystrokes, and the screen was frozen, and a bit
later, many vertical lines , then the happy message:
Try To Recover Memory? My user memory was not erased, but I have
experienced some different situations with the same result.
There are many bugs which cause memory corruption. Therefore, I have
seen many others which was fixed succesfuly.


"Steindor E. Sigurdsson" <ste...@hi.is> wrote:

> I've been having problems with my 49G, it frequently freezes and
corrupts my
> Home directory.
>
> The following is an example of a sequence of actions that causes my
49G to
> freeze (on both 1.10 and 1.16).
>
> PLOT(X) [ENTER]
> [->] [TABLE]
> [->] [TBLSET]
> |
> V (down arrow tvice, to ZOOM)
> [F6] (OK)
>
> Could someone try the above and let my know if this is just a bug or
if i
> might have a damaged calculator.
>

> I don't know wheter it is relevant but when I turned it on for the
first


> time I got two messages, "Invalid card data" and "Try to recover
memory?".
>
> Any ideas?

hector

unread,
Dec 14, 1999, 3:00:00 AM12/14/99
to
What ROMs where you using?
anyway to avoid the "invalid card data" message type PINIT, it should
go away.

jcrm...@hotmail.com

unread,
Dec 14, 1999, 3:00:00 AM12/14/99
to
I am using ROM 1.16-C. But the problems happened with 1.05, 1.10,
1.14-2, 1.15-5 and 1.14-7. Many bugs in older versions are fixed in
later versions fortunately, but not all.
The problems are not with "invalid card data", but with warm or
coldstarts, depending on situation. For an example, when I was editing
programs in sys-rpl, and press [enter] without compile nor run it, the
editor causes a warmstart. The memory was not corrupted, but the stack,
pict etc. was lost. Many other crashes occur in various situations.
These situations are unpredictables.

Joėl Bourquard

unread,
Dec 14, 1999, 3:00:00 AM12/14/99
to
> I am using ROM 1.16-C. But the problems happened with 1.05, 1.10,
> 1.14-2, 1.15-5 and 1.14-7. Many bugs in older versions are fixed in
> later versions fortunately, but not all.
> The problems are not with "invalid card data", but with warm or
> coldstarts, depending on situation. For an example, when I was editing
> programs in sys-rpl, and press [enter] without compile nor run it, the
> editor causes a warmstart. The memory was not corrupted, but the stack,
> pict etc. was lost. Many other crashes occur in various situations.
> These situations are unpredictables.

I'm using the editor A LOT, and I haven't had any warmboot since 1.14-3.
I think they changed something in the interrupt handler after the 1.14-2,
but I don't know if this is related.

Besides, I couldn't reproduce your keystroke sequence to crash 1.16.. Could
you be more precise ?

Thanks
Joėl

Ivan Cibrario Bertolotti

unread,
Dec 15, 1999, 3:00:00 AM12/15/99
to
Hello,

I could reproduce the bug on both my real machine
and on the emulator, both with ROM 1.16, using the same
key sequence, entered immediately after a full reset,
in *algebraic* mode.

Instead, I was *not* able to crash the calculator
in *RPN* mode, possibly because in RPN mode the left-shift(hold)
TBLSET shortcut does *not* work while TABLE is active, so
I was no able to start TBLSET without exiting TABLE first.

Hope this helps,
Ivan

aven...@epita.fr wrote:
>
> Hello.
>
> I can't reproduce any problems using your key sequence on any ROM
> version (1.05, 1.10 and 1.16)...
>
> What version are you using ?
> In order to get rid of the "Invalid Card Data" type the PINIT
> sequence...
>
> Jean-Yves
>

> In article <832iso$ocb$1...@gneisti.skima.is>,


> "Steindor E. Sigurdsson" <ste...@hi.is> wrote:

> > This is what I do to crash my 49G (It didn't quite come out right
> earlier,
> > sorry)
> >
> > Type PLOT(X) and press [ENTER]
> > Press "left shift" (blue left arrow) and then [TABLE] (F6)
> > Press "left shift" (blue left arrow) and then [TBLSET] (F5)
> > Press [F6] (OK)
> >
> > Like I said earlier, I've been having problems with my HP (halts and
> memory
> > corruption) so I'm hoping that some feedback could help me figure out
> if
> > this is caused by an unstable operating system or if I just got a
> faulty
> > calculator.
> >
> > Also,
> > does anyone know what "Invalid card data" means?
> >
> > ___
> > Steindor E. Sigurdsson
> > ste...@hi.is
> >
> >
>

> Sent via Deja.com http://www.deja.com/
> Before you buy.

--
------------------------------------------------------------------------
Ivan Cibrario Bertolotti | phone: +39-011-3919246
IRITI - National Research Council | fax: +39-011-341882
Turin (Italy) | mailto:cibr...@cstv.to.cnr.it

Steindor E. Sigurdsson

unread,
Dec 15, 1999, 3:00:00 AM12/15/99
to
> I'm using the editor A LOT, and I haven't had any warmboot since 1.14-3.
> I think they changed something in the interrupt handler after the 1.14-2,
> but I don't know if this is related.
>
> Besides, I couldn't reproduce your keystroke sequence to crash 1.16..
Could
> you be more precise ?
>
> Thanks
> Joėl

This is about as precise as I can be:

Type PLOT(X) and press [ENTER]
Press "left shift" (blue left arrow) and then [TABLE] (F6)
Press "left shift" (blue left arrow) and then [TBLSET] (F5)

Press [OK] (F6)

"Works" every time, halts the machine on both ROM 1.10 and 1.16 and on
"ON-C" responds with "Try to recovery memory?"

___
Steindor E. Sigurdsson

Nate Eldredge

unread,
Dec 15, 1999, 3:00:00 AM12/15/99
to

Reproduced here on 1.16. These are my flags (yes that's algebraic mode).

{ # 3080018402A14FF0h
# 1000000000000000h
# 18010442000000h
# 0h }

Note also that:

Plot type FUNCTION is necessary. I had 'X' stored in EQ.

And "halts the machine" means it hangs with the hourglass on.
--

Nate Eldredge
neld...@hmc.edu

Joėl Bourquard

unread,
Dec 15, 1999, 3:00:00 AM12/15/99
to
> This is about as precise as I can be:
>
> Type PLOT(X) and press [ENTER]
> Press "left shift" (blue left arrow) and then [TABLE] (F6)
> Press "left shift" (blue left arrow) and then [TBLSET] (F5)
> Press [OK] (F6)
>
> "Works" every time, halts the machine on both ROM 1.10 and 1.16 and on
> "ON-C" responds with "Try to recovery memory?"

You're right ! Sorry.
If happens on mine (it locks up), but only in algebraic mode.
Thanks, I'll report it to them.

Regards,
Joėl


aven...@epita.fr

unread,
Dec 15, 1999, 3:00:00 AM12/15/99
to
Hello.

Thank you for this interesting mode...

Unfortunately, to fix it I had to disable the TaskSwitch capabilities of
the HP49..
Fortunately, it was not used *yet* :)

Jean-Yves


In article <838qo4$mue$1...@news1.sunrise.ch>,

Keith Farmer

unread,
Dec 15, 1999, 3:00:00 AM12/15/99
to
aven...@epita.fr wrote:
> Unfortunately, to fix it I had to disable the TaskSwitch capabilities of

Task Switch?

Multitask?

Garcia Garcia, Cesar F.

unread,
Dec 16, 1999, 3:00:00 AM12/16/99
to

Like Windows?

and

Without getting blue-screen errors two times out of three?????

Veli-Pekka Nousiainen

unread,
Dec 16, 1999, 3:00:00 AM12/16/99
to
Garcia Garcia, Cesar F. <zz96...@opalo.etsiig.uniovi.es> wrote in message
news:QlANpX...@opalo.etsiig.uniovi.es...
!> In article <385832F7...@pacbell.net>, Keith Farmer
<far...@pacbell.net> writes:
!> > aven...@epita.fr wrote:
!> >> Unfortunately, to fix it I had to disable the TaskSwitch capabilities
of
!> >
!> > Task Switch?
!> >
!> > Multitask?
!>
!> Like Windows?
!>
!> and
!>
!> Without getting blue-screen errors two times out of three?????

The point is to set the display blue! (and be Microsh*t compliant)

This shows the famous HP 49G preproduction "Blue Screen":
http://www.hpcalc.org/temp/dead/

;-) Regards, VPN


0 new messages