A162 Subject: Re: Navigation Sofare , IÇm concentrating on offering the same function as the NauticTools (www.nautictools.de - sor, only in German), maybe you have a look at ts program. It doesnÇt need any HO-Tables Çcause evetng is cculated on the fly. By the way: IÇm programming for the 49G/49G+ because IÇm using the new Inputngine. > Sounds interesting. Will your sofare do both sight reductions (HO 229 / HO 249 or even N(x)) and > provide manac information? > I am sure that my HP48 will not mind if the sofare was written in Deutsch or English. > (http://www.worldcruising.com/arc/english.htm) and as backup for GPS > and Laptop IÇm currently writing my own navigation sofare but at the > moment only in German. > So you are ve welcome to provide an Englisch translation. Does anyone know of navigation sofare for the HP48? NavPak was THE navigation sofare for HP cculators prior to the HP48, but it looks like Sparcom is out of business (or at least their website is). I have so seen reviews for Navcom 48, but there does not seem to be any website for ts. I have checked out hpcc as well, but they do not have sofare that will do both sight reductions and give manac information. === Subject: Re: HP49G+ permanent status display area An other tng I noticed is that when you enter of leave the editor, the header moves by one row of pixels. Ts is just a sml annoyance but it would be nice without. === Subject: Re: 49g graysce games on 49g+ >>I am not ve good with the jargon. However what is the bottom line here? > Do gray sce games work or not on the HP 49G+ with rom 1.23? > NO You mean NOt yet ? Well, anyway, the graysce games will have to be modified in order to be run on g+. After finding how to get grays, we will need people to study the sources and convert the displaying routines. === > Well, anyway, the graysce games will have to be modified in order to be Exactly: NO! NOT a single old graysce game could work without a major rewrite > run on g+. After finding how to get grays, we will need people to study the sources and convert the displaying routines. === Subject: Re: 49g graysce games on 49g+ What do mean not yet? Are you telling me there is hope in the near future? That would be wonderfull. Please elaborate . >>I am not ve good with the jargon. However what is the bottom line here? > Do >>gray sce games work or not on the HP 49G+ with rom 1.23? > NO > You mean NOt yet ? > Oh ! I guess ! You had posted your message from the hp49g+ with Usinagaz > and because of the bad keyboard, your message has been cut === Subject: Re: 49g graysce games on 49g+ > What do mean not yet? Are you telling me there is hope in the near future? > That would be wonderfull. Please elaborate . I hope to have a 'proof on concept' by next week... The hardware should support greysce, and I tnk I know enough ARM asm to t it. === Subject: Re: HP 49G+ : Libra on SD-Card > You have to tnk that one command in a libra can cl sever others from > the same libra. I would tnk to solve ts problem you could do: > 1 Copy the libra to port 1 wch I assume is nearly empty. > 2 Attach the libra > 3 Run the command > 4 Detach the libra > 5 Delete the liba from port 1 That would probably be too slow, even on the 49+. A better solution is 1. check whether the input name occurs in the lib as command 2. If yes extract its content. Otherwise abort. 3. Replace recursively occurring rompointers from that lib by their content. 4. Run the command 1 and 2 are easily reized with the commands ->H and H-> from lib 256 just with string-search, in a tiny program < 100 bytes But it is faster to do ts directly in asm, as well as 3. Basicly, the problem was solved in older lib splitters by Pivo wch were running on the libs as tempora objects. Clearly, it is much faster getting l information from intern tables as, e.g., the lib splitter of OT49. === Subject: Re: HP 49G+ : Libra on SD-Card My SD reader being still broken, I tried to make some kind of proof of concept program. I put a list cled ORG containing a 15KB libra ID 1144 in port2: The following program executes a command from ts libra in less than 1.5s << :2:ORG RCL OBJ-> DROP 1 STO :1:1144 ATTACH #478001h LIBEV >> I measured the time to transfer extable to 1.7s So ts may not be so fast but it is not too slow either. Obviously I had knowledge of the libra. To gain ts knowledge a sml bit of ASM would be required after the RCL. My point is that it is doable and I believe not too slow. There might however be a bit of screen flicker when the libra is attached. I may push ts further if you tnk it is useful. === Subject: Re: HP 49G+ : Libra on SD-Card > So ts may not be so fast but it is not too slow either. Obviously I had > knowledge of the libra. To gain ts knowledge a sml bit of ASM would be > required after the RCL. Now that it is apparently possible to run ARM code (unfortunately I do not have a 49G+, so I cannot t it myself), you could t making a hash table of l commands available from SD-resident libraries. That would probably be a lot faster. Or you could write a program that makes wrapper libraries for eve libra on the card, wch would reduce libra size in memo to maybe 20-30 bytes per command. I tnk ts could be done without any ARM programming. - === Subject: Re: HP 49G+ : Libra on SD-Card Addtion to previous mail: How to proceed to find out whether, for instance, ViewP is rely a command of Headman. 1. Put Headman on the card and and delete it from any standard port. Thus, the system does not know anytng about Headman anymore. 2. Recl Headman from the card and apply ->H 3. Put the name ViewP the on the stack and run ->H 4. Remove the first 5 nibbles from the result (type information, not contained in the Hexastring of Headman). 5. Run the user-command POS. Voil.87, ts is 238. Ts proves, ViewP is rely a command in Headman. Now you may procede to extract the content of ViewP. Better read Eric's Programming the Saturn cp before wch contains concise information on the body of a lib === Subject: Re: HP 49G+ : Libra on SD-Card > 2. Recl Headman from the card and apply ->H > 3. Put the name ViewP the on the stack and run ->H > 4. Remove the first 5 nibbles from the result (type information, not > contained in the Hexastring of Headman). > 5. Run the user-command POS. Voil.87, ts is 238. > Ts proves, ViewP is rely a command in Headman. Now you may procede > to extract the content of ViewP. Ts proves exactly *notng*. T making a sml libra with, say, a command named FOO containing :: ViewP === Subject: Re: HP 49G+ : Libra on SD-Card > 2. Recl Headman from the card and apply ->H > 3. Put the name ViewP the on the stack and run ->H > 4. Remove the first 5 nibbles from the result (type information, not > contained in the Hexastring of Headman). > 5. Run the user-command POS. Voil.87, ts is 238. > Ts proves, ViewP is rely a command in Headman. Now you may procede > to extract the content of ViewP. > Ts proves exactly *notng*. T making a sml libra with, say, > a command named FOO containing > :: > ViewP > and see. Well, I'd be happy if my math students were as attentive as As a er of fact, one has to search for the name ViewP just in the area where the visibles of the lib reside. But ts doesn't complicate tngs ve much. It doesn't er whether in a lib exist a name TViewP, say, because the next o nibbles after the 5 type nibbles encode just the length of the name wch was in included in the search. === Subject: Re: HP 49G+ : Libra on SD-Card > Now, the next o > nibbles after the 5 type nibbles encode just the length of the name > and have to be used to verify the search correctness as well That may still give you fse positives since notng prevents a libra creator from putting any nibble sequence you test for in any string-like object etc. The Right Tng is to skip the libra name to access the hash table offset, and use the hash table to find the name, just like the system does. - === Subject: Samson Cables lied to me about the 49G+ I sent Samson Cables an email asking them about their current stock of HP49G+'s and the reply was that they have the newer version of the macne. I so asked about their policy on defective returns. It appears that unless the cc is defective out of the box, they will not accept any returns. as I ordered the 49G+ from them and indeed it is the one with the defective keyboard CN333 s/n. A previous poster has so had ts experience. I will NEVER order from them again. I had to send in my newer cculator for a replacement. HP customer support has been great with the return, sometng that Samson Cables should have been responsible for. === Subject: Re: Samson Cables told the truth as they knew it I received a reply to an email I sent to them and was told that HP informed them they were getting the latest version of the 49G+. To their credit, it is impossible to tell the seri number of the cculator unless the package is opened. They have removed the wording on the web page about spping the latest version and have offered to replace my cculator with another. So I retract my earlier statement about being lied to as Samson Cables was just passing ong the information provided to them. I apologize for my error, De Richmond > I sent Samson Cables an email asking them about their current stock of > HP49G+'s and the reply was that they have the newer version of the > macne. I so asked about their policy on defective returns. It appears > that unless the cc is defective out of the box, they will not accept any > returns. as I ordered the 49G+ from them and indeed it is the one with > the defective keyboard CN333 s/n. A previous poster has so had ts > experience. I will NEVER order from them again. I had to send in my > newer cculator for a replacement. HP customer support has been great > with the return, sometng that Samson Cables should have been responsible > for. === Subject: Re: Samson Cables lied to me about the 49G+ > I sent Samson Cables an email asking them about their current stock of > HP49G+'s and the reply was that they have the newer version of the > macne. I so asked about their policy on defective returns. It > appears that unless the cc is defective out of the box, they will not > accept any returns. as I ordered the 49G+ from them and indeed it is >the one with the defective keyboard CN333 s/n. A previous poster has so > had ts experience. I will NEVER order from them again. I had to send > in my newer cculator for a replacement. HP customer support has been > great with the return, sometng that Samson Cables should have been > responsible for. I so ordered from Samson Cables and received the same reply, so it looks like I could end up with the same old cc. Being from Europe (Croatia) I checked and loc HP does not handle replacement, so can you give me some email where I could contact HP customer support? === Subject: Re: Samson Cables lied to me about the 49G+ I requested an email sent when my replacement cculator was spped. Here is the address: cculatorbus_support@am.exch.hp.com The support guy I tked to was VE helpful. - Origin Message - Subject: Re: Samson Cables lied to me about the 49G+ > I sent Samson Cables an email asking them about their current stock of > HP49G+'s and the reply was that they have the newer version of the > macne. I so asked about their policy on defective returns. It > appears that unless the cc is defective out of the box, they will not > accept any returns. as I ordered the 49G+ from them and indeed it is >the one with the defective keyboard CN333 s/n. A previous poster has so > had ts experience. I will NEVER order from them again. I had to send > in my newer cculator for a replacement. HP customer support has been > great with the return, sometng that Samson Cables should have been > responsible for. > I so ordered from Samson Cables and received the same reply, so it looks > like I could end up with the same old cc. > Being from Europe (Croatia) I checked and loc HP does not handle > replacement, so can you give me some email where I could contact HP > customer support? > I sent Samson Cables an email asking them about their current stock of > HP49G+'s and the reply was that they have the newer version of the > macne. I so asked about their policy on defective returns. It > appears that unless the cc is defective out of the box, they will not > accept any returns. as I ordered the 49G+ from them and indeed it is >the one with the defective keyboard CN333 s/n. A previous poster has so > had ts experience. I will NEVER order from them again. I had to send > in my newer cculator for a replacement. HP customer support has been > great with the return, sometng that Samson Cables should have been > responsible for. > I so ordered from Samson Cables and received the same reply, so it looks > like I could end up with the same old cc. > Being from Europe (Croatia) I checked and loc HP does not handle > replacement, so can you give me some email where I could contact HP > customer support? === Subject: HP49G LGPL CAS release I'm happy to announce the release of my contribution to the HP49G CAS under the LGPL license. It means that evebody is now able to modify the CAS source code (except for the files containing code from G48), or add a new functionnity, compile it, make a new ROM, and use it in s HP49G cculator. For more information, get the arcve (see references below) and look at the README, LICENSE and ABOUT files. Ts release was made possible to may people (see ABOUT file) and especily De Brebisson. Have fun, Web: English http://www-fourier.ujf-grenoble.fr/~parisse/english.html French http://www-fourier.ujf-grenoble.fr/~parisse/ Ftp: ftp://ftp-fourier.ujf-grenoble.fr/xcas/hpcas/casrelease.zip === Subject: Re: HP49G LGPL CAS release I just reised that it so means that we can take the CAS out of the ROM and replace if we want by whatever we fancy. At least ts would please Helen (or maybe not). Well I haven't read the licenses yet so I am not sure what we can actuly do. === Subject: Re: HP49G LGPL CAS release I'm happy to announce the release of my contribution to the HP49G CAS > under the LGPL license. It means that evebody is now able to modify > the CAS source code (except for the files containing code from G48), > or add a new functionnity, compile it, make a new ROM, and use it > in s HP49G cculator. For more information, get the arcve (see > references below) and look at the README, LICENSE and ABOUT files. > Ts release was made possible to may people (see ABOUT file) > and especily De Brebisson. > Have fun, > > Web: English http://www-fourier.ujf-grenoble.fr/~parisse/english.html > French http://www-fourier.ujf-grenoble.fr/~parisse/ > Ftp: ftp://ftp-fourier.ujf-grenoble.fr/xcas/hpcas/casrelease.zip Ts is ve nice of you. Now the CAS development for the 49G(+) can go on (well, at least in principle). for making ts available. . === Subject: Re: HP49G LGPL CAS release > I'm happy to announce the release of my contribution to the HP49G CAS > under the LGPL license. It means that evebody is now able to modify It is such a good idea ! === Subject: Re: HP49G LGPL CAS release >> I'm happy to announce the release of my contribution to the HP49G CAS >> under the LGPL license. It means that evebody is now able to modify > It is such a good idea ! And it would be a good idea too if the ROM of the hp49(+) could be released under a free license. Is it possible ? === Subject: Re: HP49G LGPL CAS release a lot. Does that mean you won't be working on it anymore. I haven't looked at it yet but do we have a list of known bugs? Once again to l those who made ts possible and those who will be working on it. === Subject: Re: HP49G LGPL CAS release Excellent idea !!! But maybe, Bernard, you should keep the control over the next changes on the source code... to avoid some problems like the Linux multi distribution compatibilities :( > a lot. Does that mean you won't be working on it anymore. > I haven't looked at it yet but do we have a list of known bugs? > Once again to l those who made ts possible and those who will be > working on it. > === Subject: Re: Ts is what I need.... should I get a 48GX or 49G+ waiting for a 49g+ with new keyboard from warranty....went back to my 48's keyboard...fell in love l over again... So who is coming up with the protocol to slash and bash a 48 keyboard onto a 49g+? Qfwfq ps it's an *SX baby, and I'm proud.... > I create my custom equations, It would be nice to create them on the > PC, then transfer them to the HP. > I use equation writer l the time. > I need to isolate variables in an expression. > I use standard variable sets, (I am a mechanic engineer) > I am tnking of the hp49G+ === Subject: Re: 49G+ New Keyboard > I want to make sure that it is the flawless latest > series. DOn't let your imagination run away... went1180 AT sover DOT net === Subject: =?ISO-8859-1?Q?What=B4s_wrong_with_GOOGLE_and_l_our_posts_!!!!!!?= Today I open google groups, comp sys hp48 and l I see is 800 tot posts, where are l the 11 000? And the worse, no recent threads; the WhatÇs wrong? === Subject: Re: =?ISO-8859-1?Q?What=B4s_wrong_with_GOOGLE_and_l_?= =?ISO-8859-1?Q?our_posts_!!!!!!?= > Today I open google groups, comp sys hp48 and l I see is 800 tot > posts, where are l the 11 000? And the worse, no recent threads; the > WhatÇs wrong? I'm not sure what you did, but it worked fine for me, I got: Secuencias de la 1 a la 25 de aproximadamente 113,000 en comp.sys.hp48 Translation: Threads from 1 to 25 of aprox. 113,000 in comp.sys.hp48 And I did a search and saw posts from 1992. === Subject: Re: hp49g+ : THE END OF THE QUEST ! > Can anyone recomend a good document that details l of those routines > that have been re-written in arm asm language? I Yoann's post at the top of ts thread is the best I have seen so far. === Subject: Re: hp49g+ : THE END OF THE QUEST ! Sor for being confusing, but I've been lookig for documentation for what those routines ready listed do. I can find some but not l. === Subject: Re: Numeric methods for SIN regression T searcng htpp://support.education.ti.com I found a topic there on sine regression by accident and remembered ts topic. > Well I currently have no programming project to work on and a short > wle back I recieved a message about SIN regression, so I tnk I'll > give it a t. Does anyone know of a website that gives the procedure > one would use to cculate a sinusodi regression? I'd appreciate it > ve much. ! > === Subject: Re: Factoring integers on hp 49g > Does anyone know (if it's available) the gorithm bend DIVIS or > FACTORS on the 49g? > For complete information, get the G48 libra's source code, > available here: http://www.hpcc.org/details.php?id=1322 > In gener, a version of the Pollard-Rho gorithm (optimized for the > HP) is used for factoring, and it uses the Miller-Rabin probabilistic > gorithm to test for primity. > I *tnk* that when the G48 code was ported to the '49, it was only > improved in range (using a bigger pseudo-prime base, I tnk), but the > gorithms are the same. If I'm mistaken about any of the above, I'd > be delighted to be corrected. > How about program/gorithms for those older HPs that don't have these > built-in functions? > Didn't J. Horn write some in the heydays of the 41, 42S, etc...? > Yes, but they merely used brute-force tri division. Not worth a > second look or thought. > for the information Joe. Much appreciated. P.S. In case your wondering, no relation to the actor/comedian. === Subject: Re: Factoring integers on hp 49g > P.S. In case your wondering, no relation to the actor/comedian. Do you mean S.=Steve as in Steve Martin or do you mean S.=Sheen as in Sheen Martin - OT PS: I guess it is S.=Simon as in Simon sayz! === Subject: Help programming nucleonics and photonics libra l, I am looking for a good first step into programing my Hp's. I own both a 48gx and 49 and like the both. That said, my go is to provide the equations for various nuclear engineering problems, and I am not sure what is the most reasonable way to go about ts. I am an experienced programmer in sever languages (C, C++, Pasc, Fortran..) but I am not sure wch would be the right one to use for ts project. I would like to provide a simple user interface to the code with the correct greek variables to evetng. Simple being, in my mind, like the equation solver interface, except that the equations are there for you. Any ideas are welcome. , === Subject: Re: Help programming nucleonics and photonics libra I may not understand you question, but I would t good old URPL first. There are a few examples in the 48 book. URPL follows hand cculations. Often, you hand solve a problem, then work the solution into a program following the same sequence of keystrokes. It's rely fun, fast enough, and compact. Since URPL is old news you don't hear about it much on comp.sys.hp48. However, it is a ve slick environment. You'd be amazed what can be done in a few hundred bytes. === Subject: Re: Help programming nucleonics and photonics libra >>I am an experienced programmer in sever languages (C, C++, Pasc, >>Fortran..) but I am not sure wch would be the right one to use for >>ts project. Sor , I should have said: Of the couple of languages available on the claculator I don't know wch to use. I reize that the above are not, to my knowlege, available. Just that I know my way around programming. , === Subject: 49g+: freezes, random power-offs, earthquakes My 49g+ often freezes - in fact, it froze *eve time* I was ting to write an RPL program for too long (5-20 mins). I was able to define the function I wanted at the fourth t, with the method used on win****: save after eve added line. After the freeze notng helps except the paperclip. There were some random power-offs, but I can't reproduce that. And sometimes I get the tng referred as the earthquake here: the right side of the screen fills with garbage for a few seconds. Is there a hope that ts buggy behavior will be fixed in new ROM versions? (I use 1.23 at the moment) Ts tendency to freeze is extremely annoying. === Subject: Re: 49g+: freezes, random power-offs, earthquakes > My 49g+ often freezes - in fact, it froze *eve time* I was ting to > write an RPL program for too long (5-20 mins). I was able to define the > function I wanted at the fourth t, with the method used on win****: save > after eve added line. After the freeze notng helps except the paperclip. > There were some random power-offs, but I can't reproduce that. > And sometimes I get the tng referred as the earthquake here: the right side > of the screen fills with garbage for a few seconds. > Is there a hope that ts buggy behavior will be fixed in new ROM versions? > (I use 1.23 at the moment) Ts tendency to freeze is extremely annoying. > Perhaps you have the 'older' version of 1.23 - if you got it early from hpcc.org then you probably do. I had it and my cc crashed often too. If you tnk ts might be your problem, download 1.23 again from hpcc.org and it is the new better one. Hope that helps! === Subject: Re: 49g+: freezes, random power-offs, earthquakes > Is there a hope that ts buggy behavior will be fixed in new ROM versions? > (I use 1.23 at the moment) Ts tendency to freeze is extremely annoying. You unfortunately got one of the Not Rely 1.23 ROMs that were proliferating. Download the *re* 1.23 from HP's website and you'll notice that these and many other problems have been resolved. === Subject: Re: 49g+: freezes, random power-offs, earthquakes Go ON-D ... if it's not build 31 then you've got the 'beta' version of the 1.23 ROM (Build 19 off memo) > Is there a hope that ts buggy behavior will be fixed in new ROM versions? > (I use 1.23 at the moment) Ts tendency to freeze is extremely annoying. > You unfortunately got one of the Not Rely 1.23 ROMs that were > proliferating. Download the *re* 1.23 from HP's website and you'll > notice that these and many other problems have been resolved. > === Subject: Re: 49g+: freezes, random power-offs, earthquakes > My 49g+ often freezes - in fact, it froze *eve time* I was ting to > write an RPL program for too long (5-20 mins). I was able to define the > function I wanted at the fourth t, with the method used on win****: save > after eve added line. After the freeze notng helps except the paperclip. > There were some random power-offs, but I can't reproduce that. > And sometimes I get the tng referred as the earthquake here: the right side > of the screen fills with garbage for a few seconds. > Is there a hope that ts buggy behavior will be fixed in new ROM versions? > (I use 1.23 at the moment) Ts tendency to freeze is extremely annoying. > line edit instead of infinite line edit and so flag 40 to don't show clock l the problem disappeared and now I can edit my programs without any freezing or earthquake. Still I tnk it should so work right with these flags on. T it. b. I have seri number cn33900986. === Subject: Re: 49g+: freezes, random power-offs, earthquakes I used to have those problems with ROM 1.22. Not any more! Iam using the ROM from the HP site version 1.23. Make sure you have it right. === Subject: Re: 49g+: freezes, random power-offs, earthquakes > My 49g+ often freezes - in fact, it froze *eve time* I was ting to > write an RPL program for too long (5-20 mins). I was able to define the > function I wanted at the fourth t, with the method used on win****: save > after eve added line. After the freeze notng helps except the paperclip. > There were some random power-offs, but I can't reproduce that. > And sometimes I get the tng referred as the earthquake here: the right side > of the screen fills with garbage for a few seconds. > Is there a hope that ts buggy behavior will be fixed in new ROM versions? > (I use 1.23 at the moment) Ts tendency to freeze is extremely annoying. > I have the same tngs like you: freezes, power-off etc.... and I don't know what to do .... === Subject: Re: freezes, random power-offs, earthquakes > My 49g+ often freezes - in fact, it froze *eve time* I was ting to > write an RPL program for too long (5-20 mins). I was able to define the > function I wanted at the fourth t, with the method used on win****: save > after eve added line. After the freeze notng helps except the paperclip. > There were some random power-offs, but I can't reproduce that. > And sometimes I get the tng referred as the earthquake here: the right side > of the screen fills with garbage for a few seconds. > Is there a hope that ts buggy behavior will be fixed in new ROM versions? > (I use 1.23 at the moment) Ts tendency to freeze is extremely annoying. > What build of ROM 1.23 do you have? What's your seri number? The screen flicker and earthquake went away for me when I upgraded to ROM 1.23 build 31. If you haven't check your build number you can do so by ON [F4], (build number will display) and then ON [F3] to escape out of self-test mode. If you have an early production unit (like my first one with seri no. CN 331....) you might consider cling HP for a replacement Hope ts helps.... === Subject: Re: batteries > I get about 30 days as well on rechargeables. > I'm using ROM 1.23. > Today my 49G+ froze on me. I tried ON + f3 but it would not restart. I > didn't have anytng sml enough to reset the cc so I removed one of > the > batteries and put it back in. Evetng was fine again after that. Will > doing ts harm the cculator? > No, it will not harm the cc and is one standard way of resetting > a HP cculator. There is so the reset pin and [ON]&[C] > and [ON]&[A]&[F] answer |NO| > As far as I know/read here in the past reversing batteries, even for a short wle, will not bring life in to your cc. In other wo , use it only when you have no other way out, has it can possibly damage your cc (memo and other components). === Subject: Re: batteries I get about 30 days as well on rechargeables. I'm using ROM 1.23. Today my 49G+ froze on me. I tried ON + f3 but it would not restart. I didn't have anytng sml enough to reset the cc so I removed one of > the batteries and put it back in. Evetng was fine again after that. Will doing ts harm the cculator? > No, it will not harm the cc and is one standard way of resetting > a HP cculator. There is so the reset pin and [ON]&[C] > and [ON]&[A]&[F] answer |NO| As far as I know/read here in the past reversing batteries, even for a > short wle, will not bring life in to your cc. In other wo , use > it only when you have no other way out, has it can possibly damage > your cc (memo and other components). REVERSING could be dangerous, yes If you are daring enough - leave still one batte the right way and do it quickly - then tell us a sad sto about your fried cc === Subject: Re: batteries X-ID: SSx5x8Zr8e2tknQE6iZyCJEIdCS1W0jUn8UXiDaoDneSXRUhUF3brE My batteries were empty - after a long time of not-usage. (one month ?) Marten Amiel schrieb: >>How long can you work with one new set of batteries with a HP49G+ ? > It depends on your usage and your batteries. Apparently batte life was > further improved in the new ROM 1.23 but before that I was at about 2 months > per batte set with moderate use. > === Subject: Re: Hp 49 g+: vs TI89 and other issues... Please HELP! > I have found the ti89s use of wte space in its pretty printing to be > obnoxious. At the other end I tnk that the 49gs pretty printing > tries to cram too much in. So What I did in my expression writer was > add a user setting that can change the spacing. > By spacing I mean when 'x+y' is pretty printed notice how far the '+' > is from the 'x' or the 'y' > > http://www.nyl.net you send the suggestion to ti-cares@ti.com? I like it the way it is on my V200, though. === Subject: Re: Writing a UserRPL Function > That's -> [Space] g, not ->g. What's the difference? Does a space have a speci meaning in ts context? === Subject: Re: Writing a UserRPL Function That's -> [Space] g, not ->g. > What's the difference? Does a space have a speci meaning in ts context? Yes. Outside of a character string, a space is a separator, so ->g resolves to the glob name '->g', but -> g resolves to the Create loc variables command followed the loc name g. === Subject: Re: Writing a UserRPL Function >>That's -> [Space] g, not ->g. > What's the difference? Does a space have a speci meaning in ts context? It is the same difference with << a2 >> wch is interpreted as << 'a2' >> and << a 2 >> wch is parsed as << 'a' 2 >> === Subject: Re: Writing a UserRPL Function Yes, the space needs to be in beeen the -> and the variable name, g in ts case. The command ->g is not a recognizable command, wch explains the errors he was getting. The -> symbol means take the contents of level 1 stack and assign it to a loc variable, the name of wch is to follow the -> symbol. > That's -> [Space] g, not ->g. > What's the difference? Does a space have a speci meaning in ts context? > , > . === Subject: Re: Writing a UserRPL Function That's -> [Space] g, not ->g. Function g must be previously defined and >>saved in the current directo, or gher in the directo tree. > but that's exactly what I DON'T want - to have to save g separately. > I want to be able to define and use a function l in one source module. I'm not sure that I know exactly what you want, but maybe sometng like one of these? %%HP: T(3)A(R)F(.); @ Results from BYTES command (on 49g+): @ Checksum: # F9A4h @ Size: 73. Bytes << << -> '2*a' >> -> g 'g(5)'>> %%HP: T(3)A(R)F(.); @ Results from BYTES command (on 49g+): @ Checksum: # BC7Bh @ Size: 73. Bytes << << -> a << 2 a * > -> g 'g(5)' >> %%HP: T(3)A(R)F(.); @ Results from BYTES command (on 49g+): @ Checksum: # 8CD0h @ Size: 65.5 Bytes << << -> a '2*a' >> -> g ' << 5 g EV > %%HP: T(3)A(R)F(.); @ Results from BYTES command (on 49g+): @ Checksum: # 7DE4h @ Size: 65.5 Bytes << << -> a << 2 a * > -> g << 5 g EV > Or maybe sometng like ts? %%HP: T(3)A(R)F(.); @ Results from BYTES command (on 49g+): @ Checksum: # 6C4Ah @ Size: 49. Bytes << << 2 * >> -> g << 5 g EV > Maybe see the thread http://groups.google.com/groups?th=bb502cd75df0e4c7 for more comments on functions versus commands and on user-defined functions. so review the topic loc variables. === Subject: Re: Writing a UserRPL Function Oops! > %%HP: T(3)A(R)F(.); > @ Results from BYTES command (on 49g+): > @ Checksum: # F9A4h > @ Size: 73. Bytes > << << -> '2*a' >> -> g 'g(5)'>> Make that: %%HP: T(3)A(R)F(.); @ Results from BYTES command (on 49g+): @ Checksum: # F9A4h @ Size: 73. Bytes << << -> a '2*a' >> -> g 'g(5)'>> === Subject: 49G CAS release guys! look at THAT: I'm happy to announce the release of my contribution to the HP49G CAS > under the LGPL license. It means that evebody is now able to modify > the CAS source code (except for the files containing code from G4, > or add a new functionnity, compile it, make a new ROM, and use it > in s HP49G cculator. For more information, get the arcve (see > references below) and look at the README, LICENSE and ABOUT files. > Ts release was made possible to may people (see ABOUT file) > and especily De Brebisson. > Have fun, > > Web: English http://www-fourier.ujf-grenoble.fr/~parisse/english.html > French http://www-fourier.ujf-grenoble.fr/~parisse/ > Ftp: ftp://ftp-fourier.ujf-grenoble.fr/xcas/hpcas/casrelease.zip Now we have to know what's going to happen in case of an improvement! Especily how will we be able to use ts improvement under the 49G+ as the CAS release doesn't contain the ARM emulator!! I hope De Br.8ebisson (by who ts release was possible) and HP are gonna help us in such a case! === Subject: Re: Dare I mention the 49g+ Keyboard? Ts just isn't adding up :( My replacement is CN402xxxxxx and I'll be damned if I can tell the difference beeen that and my pre-352xxxxx model. Keys are still quite firm (too firm) - same hollow sound - and now that I've had the chance to key numbers into it solidly for 1/2 hour I'm rely not ve happy (I've had to turn key click back on to make sure I wasn't dropping digits - wch saved me on sever occasions). I've got a 48gx and a 41CV and I find they are notng remotely like the 49g+ keyboard - different as chk an cheese (though ve similar to each other) Obviously some are finding tngs ve different to ts with their replacement items, so I rely can't figure out what's going on. Perhaps they've reverted back to the 'origin' keys? Perhaps they've got multiple production lines and they're still using the old technology one some of them? Quite disappointing rely - now I've spend a bit of time with the replacement I've concluded that the one I had before was actuly better, though I haven't tried the wiggle fix with the new one yet. Perhaps someone can get more info out of one of the service centres around the world for us, or an eMail address we can write to? CC > some questions : > 1. did your old 49g+ passed the keyboard test or it passed only > after pressing hard enough ? > 2. Do you find the new keyboard quieter ? or the same hollow, springy > noise ? > I just received my replacement ironicly the door bell rang at the > exact moment I was reading an Weiss's 2/26 posting in New HP 49G+ still > not registering keystrokes! so I was ve anxious to test my new > replacement. The new cculator I got has seri number CN402.... Rom 1.23 > build 31. > (1) My origin 49g+ (CN331) wch had the keypress recognition problem > ways passed the keyboard test. Others have posted and I agree that ts > test is not a good indicator for the keypress recognition problem. > (2) The new keyboard is GREAT. I've owned a 48gx and the 49g+ keyboard > strikes me as ve similar. Compared to the old keyboard, the new one is > quieter, softer, and no longer has that hollow sound. I'm sor about > an's experience, but for me ts has made l the difference...I now have > a truly great cculator. > === Looks like someone screwed up spping the cculator so early. It feels great to actuly get your hands on the 33s more than a month before it's officily released. I just wanted to say to the group for giving the heads up on W-mart because I received mine today, the day they changed the site! === > Looks like someone screwed up spping the cculator so early. It feels > great to actuly get your hands on the 33s more than a month before it's > officily released. I just wanted to say to the group for giving the > heads up on W-mart because I received mine today, the day they changed the > site! That's crazy. It said 3/3 to 3/11 yesterday. :( so beware that WMart charges ses tax to orders. Bo === >> Looks like someone screwed up spping the cculator so early. It feels >> great to actuly get your hands on the 33s more than a month before it's >> officily released. I just wanted to say to the group for giving the >> heads up on W-mart because I received mine today, the day they changed the >> site! > That's crazy. It said 3/3 to 3/11 yesterday. :( > so beware that WMart charges ses tax to orders. Bo Unless you are ordering outside the US, it is hardly bo - it is US law that they charge tax in any state where they have a physic presence. Know of a state without a W-mart you can order from? === Subject: important problem with purchase of g49+ someone knows if is possible to know if a g49+ is the ld versione (with old keyboard) or the new version without open the packaging. The seri number isn't visible from outer packaging? === Subject: Re: New HP 49G+ STILL not registering keystrokes! I like your input, it keeps the focus banced. > Yes, I learned sometng... I learned that you are waiting to jump at > any problem that arises, and enjoy if the 49Gs have any failure. > That is nonsense, of course. But I do notice problems rather than > sweeping them under the rug. I might add that if more users had that > kind of attitude, then maybe HP would get a much clearer idea of how > they cannot take their customers for a ride. > Let me so say ts ve clearly: For a reputable company like HP to > attempt to sell a device with the kind of glaring problems the 49G+ > and, even worse, the 48GII had is more than pathetic. As I said > before, if I go pick up a $5-cculator at the checkout in a groce > store, it will come with a keyboard that is better than what any of > the new HPs sold in the last couple of years have. If you bought > yourself a Lexus, and you find that they have used transparent plastic > film for wind selds in order to save some money, what would you > tnk of Toyota? > Or how about ts: Can you name any cculator in recent sto, > heck, in l of sto, from any company, that has even had a > fraction of the hardware and sofare issues that are plaguing, and > have _consistently_ plagued, the ones from HP? Was there ever a TI > cculator that had to see a tot recl like the 48GII from HP? A > Casio? A Sharp? Finly, do you believe that if another company would > offer similarly powerful RPN cculators, anybody in s right mind > would buy an HP? === Subject: Re: New HP 49G+ STILL not registering keystrokes! > I got your point here: Not quite. Let me t again: Those other companies are successfully selling quity cculators by the millions in stores l over ts count. I haven't yet seen a single store that carries the hf-broken garbage HP tries to pass off as cculators these days. Case closed. === Subject: Re: New HP 49G+ STILL not registering keystrokes! You're not an HP fan, get over it, move on to the TI newsgroups. The rest of us will enjoy our past, present, and future HP cculators. > I got your point here: > Not quite. Let me t again: Those other companies are successfully > selling quity cculators by the millions in stores l over ts > count. I haven't yet seen a single store that carries the > hf-broken garbage HP tries to pass off as cculators these days. > Case closed. === Subject: Re: New HP 49G+ STILL not registering keystrokes! > The keys are less hard to > activate and seldom do they fail to register. WHAT? They seldom fail to register? So, you are saying that you have a cculator with a broken keyboard, but you are happy, because it is broken just a little bit? No further comment... > I don't know if the keyboard is as good as that on a 48 but it is close. Ts is ridiculous. I'll just say that in more than a decade of usage, my 48 has never failed to register a key. If you get yourself $10-Casio, you will get a cculator that will never miss a key, either. A cculator that forces you to ways make sure that the numbers you typed in have actuly been registered is less than useless, in my book. === Subject: Re: New HP 49G+ STILL not registering keystrokes! Helen schrieb > WHAT? They seldom fail to register? So, you are saying that you have > a cculator with a broken keyboard, but you are happy, because it is > broken just a little bit? No further comment... Helen, you get the point. I agree toty to your statements up to now. I used to have cculators wch do not need to take care about key-actions from me. That is one of the *most *important tnks, why I am using HP-cculators. I was disapointed about the HP 49G because of the gh required key-force ( about 3 N on mine). But I am more disapointed about the hp 49g+ CN347... wch SOMETIMES makes a keyreaction when pressing with 2 N (Newton). The keyboard test for the hp 49g+ is insufficiant to identity unreliable key reactions. To get reliable keyreactions on g+ 3 N seem to be required! Ts is even worse compared to the HP 49G in terms of *reliable key-reactions, because the user assumes the key to be registered but it is NOT. > I don't know if the keyboard is as good as that on a 48 but it is close. > Ts is ridiculous. I'll just say that in more than a decade of usage, > my 48 has never failed to register a key. If you get yourself > $10-Casio, you will get a cculator that will never miss a key, ... Yes, I agree 100 %. I do not understand, why HP has introuced new mechanics for the keyboard. I assume a BAD documentation about what has been used for the ccs up to the HP48G-series or did somebody of the new marketing guys found a dollar to save at the *wrong *place? Regardless the insufissant documentation (command-reference is missing), the bugy ROM (see bugreports in ts NG about ROM 1.23), essenti security issues (overwriting write protected SD-ca ), *big MARKETING-display (wch is not applicabel for the user)... but the most important is the keyboard of my g+, wch is *unreliable. info@bandermann-gmbh.de and still waiting for a response. I *hope, they are *only overloaded by the replacement-requests for the hp 49g+ Up to now, the promissed HP-cculator-support gets a double-minus from me. Heiko === Subject: Re: New HP 49G+ STILL not registering keystrokes! > The keys are less hard to > activate and seldom do they fail to register. > WHAT? They seldom fail to register? So, you are saying that you have > a cculator with a broken keyboard, but you are happy, because it is > broken just a little bit? No further comment... He means it's harder for a key to 'miss' a keystroke or register it. A good tng. Read the post... === Subject: Re: New HP 49G+ STILL not registering keystrokes! >>Yes, I learned sometng... I learned that you are waiting to jump at >>any problem that arises, and enjoy if the 49Gs have any failure. > That is nonsense, of course. But I do notice problems rather than > sweeping them under the rug. ... You're missing the point, you repeated your speech l over again. I do agree that there have been quity problems, but now that the keyboard issues has been adressed you saw one post of discomfort against many people finding the new keyboard great, and you started with your agression against the new 49g+ again. Are you going to tell me that your beloved TI cculator indust has never had a faulty unit in the market? === Subject: UTPN inverse in SysRPL? Any bady knwo how to make a inverse UTPN (UTPC,UTPF,UTPT) function on SysRPL?