comp.sys.hp48 Google Group

Re: U of H calculator contest

2009-11-08T17:27:01Z

Wes,
Thanks for this pointer. I am always looking for good calculator
problems, and these were good ones. It took me around five hours, but
I wasn't racing, just enjoying. I will compare answers, if you
promise not to laugh.
Regards,
Dan

Re: HHC 2009

2009-11-07T04:30:11Z

I have been following this group since as long as I can remember. I
have even posted in spurts. I can tell you that since the 49G/50G that
I am so disappointed in HP I am disgusted with them. I have a shel
full of 48G(x)'s put up because the 50G is that bad. I still hate that
calculator.
I have always heard great things from the HHC's and almost attended

Re: speedui fonts

2009-11-07T00:33:11Z

Did I mention that I found and fixed the 4th bug a few days ago?
An updated SpeedUI archive will be available at the usual places soon:-)
Raymond

Re: Input form field menu message handler

2009-11-06T21:47:43Z

Hello,
> It generates native ARM code that is WAY faster than any
> SysRPL or assembly.
What you forgot: the code is 100 x bigger, needs a specific loader,
you have to do everything by yourself as you are outside of Saturn
ASM / SYS-RPL and there is no further development of HPGCC, the
website is dead for at least half a year.

Re: Input form field menu message handler

2009-11-06T20:31:16Z

Gurveer,
Rather than taking up assembly language for a processor that doesn't
exist anymore (the Saturn processor is emulated using an ARM
processor), consider learning to use HPGCC, the C/C++ compiler for
the 50G. It generates native ARM code that is WAY faster than any
SysRPL or assembly.
Dave

GUISLV 1.2 Release Candidate

2009-11-06T15:56:38Z

Hello,
Haste makes waste and Rome wasn't built in a day...
Until the GUISLV shows up on my webpage (http://
[link]) you can download the Release Candidate
from HP’s forum at
[link]
Scroll to the end of the messages and download the attachment of the

Re: Input form field menu message handler

2009-11-05T09:32:10Z

Hello,
> I'm an amateur at SysRPL and have no idea
> about how Assembly Language works.
start with
Introduction to System RPL and Assembly Language
[link]
Programming in System RPL (PDF)
[link]
and then move on to Saturn ML
Introduction to Saturn Assembly Language (PDF) Third Edition

Re: Input form field menu message handler

2009-11-05T02:53:40Z

On Nov 4, 4:40 pm, Andreas Möller <andreas_moellerNOS...@gmx.de>
wrote:
Thanks a lot Andreas for providing such a nice insight. I'm an amateur
at SysRPL and have no idea about how Assembly Language works. But your
post fills me with determination to learn and come up with my answer
one day. And I can really feel the joy when I make programs in SysRPL

Re: What to do with extended pointers ?

2009-11-05T00:24:09Z

Thanks again Andreas, as always, your help is very valuable.
Yes, i read some explanation from Khan Dang Nguyen, who's using MASD
conditional compilation.
They work pretty well, but are a bit less "verbose", because using
Flag Numbers (instead of names)
I was unaware of the Debug4x ready-to-use Flags,

Re: What to do with extended pointers ?

2009-11-04T23:50:10Z

Hello,
Look into the sources of HPlanétarium which is using this to create
different software depending on the target machine. It will be much
more use for you than I trying to explain it to you because you are
French ;-)
[link]
I too use it but my explanation for me I wrote once back about

Re: Input form field menu message handler

2009-11-04T23:40:57Z

Hello,
maybe you should start with reading the documentation that comes with
Nosy.
Nosy can follow the program flow and can put the currently viewed
program part on the RPL-Data-Stack. You can use these strings that are
put on the stack to build/create parts of the program that you are
browsing, that way you might get an overview of what is going on.

Re: Input form field menu message handler

2009-11-04T22:40:12Z

Seems to be a really good document. Spanish is hard! :)
After a bit of translation, it's making somewhat sense now. Thanks a
lot.
Thank you for that. Now I know how to use Nosy to find out the
programs evaluated by different keystrokes using OT49. But what about
those which are not directly accessed like the Input forms which run

Re: What to do with extended pointers ?

2009-11-04T21:44:00Z

Good point !
I tried the code on an HP48SX (rev E), and it produced a warm reset.
As i always try to have a code which remains valid for both S/G
series,
i guess in this circumstance, i merely need a conditional assembly
method
to exclude ?ACCPTR> from the HP48 target.
Looking into RPLCOMP, i found nothing

Re: What to do with extended pointers ?

2009-11-04T20:08:26Z

Hello Yann,
This was introduced with the 48GX (and not on the 48SX) as the covered
memory was needed for the 48GX.
Regards,
Andreas

Re: What to do with extended pointers ?

2009-11-04T19:34:05Z

Thanks Andreas
It seems that ?ACCPTR> is doing exactly what i'm looking for.
This entry exists for both HP48 & HP49 systems, but is completely
undocumented.
So your advise is really welcomed.
I'm also surprised that such entry exist for HP48; as i though
"Extended Ptr" object type were only available for HP49.