48GX and year 2,000
Ramirez Blandino
Is the HP 48GX avaible to support the y2k bug?, if no, if there's a way to
fix it?
Bellman
I did not know that there was a year 2,000 bug. Here is what I think.
You can set your calculator (using the time functions) to January 1, 2000
by entering a 1 for the month, a 1 for the day, and a 0 for the year. If
you use DATE, the calculator will respond with a 1.012. This is really a
1.012000 but it will only display in this way if you use 6 FIX to force a 6
decimal display.
However, if you enter 1.012 to level 2 and 1.01999 to level 1 and try
DDAYS, the calculator will correctly tell you that the two dates are 365
days apart. Similarly, if you enter 1.012000 and -1.011999 and use DATE+
the calculator will respond with 12.311999, correctly subtracting 1 day.
So, the calculator knows that it is the correct year and it can make day
calculations across the millennium year. Because of this, I don't think
there is a year 2000 hardware/romware issue associated with the 48GX.
However, software is out there that might have a problem with needing the
extra three zeros tacked onto dates during the first year of the new
millennium in order to operate properly. The fix (heh, heh) here is to add
a 6 FIX command prior to making any date calculations and then revert to
whatever format the calculator was in prior to running the program
(typically STD) at the end of the program.
At least, this is how I see it. Any other points of view?
Yours,
Robert Bellman, Jr.
Ramirez Blandino <syste...@geocities.com> wrote in article
<6chmon$9uc$1...@jupiter.tricom.net>...
Soren Hansen
Ramirez Blandino wrote
>Is the HP 48GX avaible to support the y2k bug?, if no, if there's a way to
>fix it?
>
>
In the manuals, HP claims, that the date can be up to year 9999, so the year
2000 problem should not be a problem.
Soren Hansen
sh...@get2net.dk
John H Meyers
There is no "Year 2000 bug" in the HP48 itself, although user-written
applications may or may not have made an oversight in this regard.
See "Re: found a bug in rom timeutils? (HP48)" posted 1997/05/27.
In the G/GX application forms, I believe that "91" thru "99" are
interpreted as 1991-1999, while "00" thru "90" are interpreted as
2000-2190; however, you can EDIT the year value to insert any
exact year you want, subject to the 100-year range over which
the HP48 accepts setting either the current date or alarms.
Functions such as DATE+ and DDAYS accept input and deliver correct results
from Oct 15 1582 thru Dec 31 9999 (they seem pretty confident that no one
will modify the calendar over the next 8000 years, although there
has been quite a lot of juggling during the past 2000 years :)
-----------------------------------------------------------
With best wishes from: John H Meyers <jhme...@mum.edu>
John H Meyers
[minor correction applied]
There is no "Year 2000 bug" in the HP48 itself, although user-written
applications may or may not have made an oversight in this regard.
See "Re: found a bug in rom timeutils? (HP48)" posted 1997/05/27.
In the G/GX application forms, I believe that "91" thru "99" are
interpreted as 1991-1999, while "00" thru "90" are interpreted as
2000-2090; however, you can EDIT the year value to insert any
Elbert S. Liu
Is the HP 48GX avaible to support the y2k bug?, if no, if there's a way to
fix it?
I think HP48S/SX will run into some problem about 12.31 2089 -> 1.1 2090, instead it freezes your screen for 2 seconds (warm start) and jump back to 1.1 1989.
I think HP48G/GX will run into some problem about 12.31 2090 -> 1.1 2091, instead it freezes your screen for 2 seconds (warm start) and jump back to 1.1 1991.
No fun! (unless you are planing to live a century from now)
-- Elbert Liu -------------------------------------- Alcatel Network Systems ASIC Design Engineer Member of Technical Staff Email: liu...@aud.alcatel.com
Kevin Jessup
John H Meyers <jhme...@miu.edu> wrote in article
<6chvlt$k8j$2...@news.iastate.edu>...
> Functions such as DATE+ and DDAYS accept input and deliver correct
results
> from Oct 15 1582 thru Dec 31 9999
Rats! It appears we'll finally have to trash can our 48s
when the year 10,000 hits. ;-)
But perhaps HP will finally get around to again
making fine quality calculators by then.
kje...@nconnect.net
http://www.nconnect.net/~kjessup
Hans Rune Boe
>Ramirez Blandino wrote:
>
>> Is the HP 48GX avaible to support the y2k bug?, if no, if there's a way to
>> fix it?
>
> 2k?
>I think HP48S/SX will run into some problem about 12.31 2089 -> 1.1 2090,
>instead it freezes your screen for 2 seconds (warm start) and jump back to
>1.1 1989.
Mine doesn't. Due to a ROM version difference maybe? I have version P
I use the HPsaucer version 2.2, the clock display is active and I use
DD.MMYYYY format.
>I think HP48G/GX will run into some problem about 12.31 2090 -> 1.1 2091,
>instead it freezes your screen for 2 seconds (warm start) and jump back to
>1.1 1991.
...but this is right...now that is kinda strange!!! Anyone have an
idea of why? Maybe the number of ticks reach some limit value?
>No fun! (unless you are planing to live a century from now)
I doubt I'll live that long, I'm already 1/4 times 100! :-) Well,
maybe I'll put the '48 on my will for my son.....:-D
---
Thanx for your time!
Blake Garretson
"Elbert S. Liu" <liu...@aud.alcatel.com> wrote:
> 2k?
>I think HP48S/SX will run into some problem about 12.31 2089 -> 1.1 2090,
>instead it freezes your screen for 2 seconds (warm start) and jump back to
>1.1 1989.
I recall reading in the manual that it handles up to 9999.
Then again, I might be remembering incorrectly.
-----------------------------------------------------
Blake T. Garretson
bgar...@eng.utoledo.edu
http://eng.utoledo.edu/~bgarrets
-----------------------------------------------------
Eric Gorka
Better be careful, with the reliability of the GX, you may be using it in
the year 2090!!!
I've had mine for 4 or 5 years, and its still going.. (Got it July of 1993
when it first came out..).
Eric
Blake Garretson wrote in message <34ee123d...@news.utoledo.edu>...
John H Meyers
In article <34ed7bef...@news.online.no>,
hrboeR...@writeme.com (Hans Rune Boe) writes:
: I think HP48S/SX will run into some problem about 12.31 2089 -> 1.1 2090,
: instead it freezes your screen for 2 seconds (warm start) and jump back
: to 1.1 1989.
> Mine doesn't. Due to a ROM version difference maybe? I have version P
Well, that's a G/GX; HP moved the "100 year window" ahead
at some point; JKH told me that this actually happened at ROM rev J,
which was the last version of the S/SX, rather than the first G/GX.
> ....but this is right...now that is kinda strange!!! Anyone have an
> idea of why? Maybe the number of ticks reach some limit value?
The internal OS periodically checks the TICKS value for validity
(i.e. being in the "100-year window"), and warmstarts with a
"corrupt system time" (code 4) error in WSLOG if it is out of bounds,
simultaneously re-setting the clock to the lowest valid value.
One of the many discussions about this was posted as
"Re: MC: HP48 Epoch and Doomsday" on 1997/09/19
(consider it corrected by Joe Horn's information above).
The above still has no effect upon the DATE+ or DDAYS functions,
which deal with dates alone, rather than TICKS values, and which
cover the same range in all HP48 models and ROM versions.
Should we accept this "planned obsolescence" in HP calculators?
I mean, whatever happened to the earlier models, which were built
to out-last the next Big Bang (black holes excepted, of course)?
Peter Maage
On Fri, 20 Feb 1998 23:32:34 GMT, bgar...@top.eng.utoledo.edu (Blake
Garretson) wrote:
: > 2k?
: >I think HP48S/SX will run into some problem about 12.31 2089 -> 1.1 2090,
: >instead it freezes your screen for 2 seconds (warm start) and jump back to
: >1.1 1989.
:
: I recall reading in the manual that it handles up to 9999.
: Then again, I might be remembering incorrectly.
You remember half of the truth:
Its date-related functions (day of the week, differences between days,...)
will handle anything up to 31.12.9999. (Stated in the manual)
Its internal clock will show the above (not quite, I think it will jump to
1.1.1990) behaviour, just try it. (Don't know if this is in the manual,
it's certainly in the calc, just try it !)
My .02
Pete
---
Peter Maage
pma...@wiesbaden.netsurf.de
Dylan Greene
In article <6chqef$apt$1...@dalen.get2net.dk>, "Soren Hansen" <sh...@get2net.dk> wrote:
>In the manuals, HP claims, that the date can be up to year 9999, so the year
>2000 problem should not be a problem.
Only up to 9999 - Will HP have a fix for this y1m bug?
BTW - did you know that HP's first product was an automatic urinal flusher?
:-)
--
Dylan Greene (http://active.student.umd.edu)
Dheera Venkatraman
I tested the year 2000 stuff by setting my Hp to December 31, 1999. The next
day it said January 1, 2000, so it handles the year 2000. Actually, we don't
need to have any dates past 2050, since that's the latest a hp48 can
possibly last. (I'm not so sure about 9999)
Dylan Greene wrote in message <6d7rtg$q...@dailyplanet.wam.umd.edu>...
James MacDonald
In article <6cis37$3j8$1...@info1.fnal.gov>, Super-User
<ro...@dcdrjh.fnal.gov> scribbled :
^^^^
Don't put on the magic hat unless it's necessary. It sure feels good,
but it's really A Bad Thing(TM).
[for an explanation, go read Linux HTML documentation!]
--
UNIX - Saving you from the Gates of Hell.