A151 Subject: Re: HP 49G+ : Library on SD-Card it will ways be slow. The hash table is a good idea but it requires that the SD card would be rechecked l the time for changes wch would be very slow and is the reason why it is not ready done in the ROM. I believe the gorithm I presented earlier is about the only one viable as as I pointed previously extracting just one program from a library, might not be enough as he could cl an undefinite numbers of programs from witn ts library. Actuly it could cl other associated libraries, wch the gorithm does not catter for, but ts would be quite rare. === Subject: Re: UTPN inverse in SysRPL? Ts is a Frequently Asked Question. If you search Google you should find answers to ts question. If you don't let us know we will search for you. === Subject: Re: UTPN inverse in SysRPL? > Ts is a Frequently Asked Question. If you search Google you should find > answers to ts question. If you don't let us know we will search for you. http://www.engr.uvic.ca/~aschoorl/faq/ -- === Subject: Re: UTPN inverse in SysRPL? > If it is a FAQ he should look here: > http://www.engr.uvic.ca/~aschoorl/faq/ Well I guess someone should update these FAQs but I don't tnk I would do it myself. === Subject: Re: Getting a remplacement in Canada ? I am so in Canada and I emailed HP and described my keyboard problems. Due to customs issues, they spped me a replacement first (received 4 working days after my first email to them) and included a filled-out FedEx spping label for the return. Unfortunately it was the wrong label - a US Air Way and not an Internation Air Way... so I had to make a new one. Hopefully it was l filled in properly... They were very prompt and courteous with l their emails. l in l, a very pleasant experience. About the incorrect way? Oh well, at least they made an effort... > I cled to 1-800-HP-INVENT > and now my is in road to the USA =) Somone ever try to get a remplacement in Canada ?? If so where to cl ? > Look at pages W-2 & W-3 in your user's manu. Telephone numbers for > various countries are listed there. > Hewlett Packard Canada, > Matheson Blvd East in Mississauga > 905-206-4900 === Subject: Re: 49g+: freezes, random power-offs, earthquakes FYI, on my 49g+ when I still had ROM 1.22, I was so experiencing frequent crashes, freezes and random power-offs. I had transferred l of my programs and libraries from my old 49G (many of wch were originly from my 48SX) into the new 49g+. I eventuly discovered that I had a corrupt program object in memory. I actuly emailed ts to at s request and wonder if he ever played with it? It would produce some very interesting crashes when one tried to run it... Once I excised ts evil object from the ulators memory, I completely stopped having freezes and shut-downs, even before I upgraded to ROM 1.23. The funny tng is that I never actuly used ts program or tried to run it - at least until just before I removed it. Its mere presence in main memory seemed to cause l kinds of problems. I would, therefore, suggest that anyone suffering from these symptoms Ts was my own experience and, of course, it may not apply to anyone else's problems... > My 49g+ often freezes - in fact, it froze *every time* I was trying to > write an RPL program for too long (5-20 mins). I was able to define the > function I wanted at the fourth try, with the method used on win****: save > after every added line. After the freeze nothng 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 > FYI, on my 49g+ when I still had ROM 1.22, I was so experiencing > frequent crashes, freezes and random power-offs. I had transferred > l of my programs and libraries from my old 49G (many of wch were > originly from my 48SX) into the new 49g+. I eventuly discovered > that I had a corrupt program object in memory. I actuly emailed > ts to at s request and wonder if he ever played with it? It > would produce some very interesting crashes when one tried to run > it... > Once I excised ts evil object from the ulators memory, I > completely stopped having freezes and shut-downs, even before I > upgraded to ROM 1.23. The funny tng is that I never actuly used > ts program or tried to run it - at least until just before I removed > it. Its mere presence in main memory seemed to cause l kinds of > problems. > I would, therefore, suggest that anyone suffering from these symptoms > Ts was my own experience and, of course, it may not apply to anyone > else's problems... > > My 49g+ often freezes - in fact, it froze *every time* I was trying to > write an RPL program for too long (5-20 mins). I was able to define the > function I wanted at the fourth try, with the method used on win****: save > after every 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. > and Peter, I had the same problems with my 49G+, but unlike you guys mine wasn't related to a program that I had loaded. I was still using the ulator in the origin configuration from HP and it just started happening. I am suppose to be getting a new one in the mail at any rate. === Subject: Re: 49g+: freezes, random power-offs, earthquakes guys, I solve my problem by updating the ROM! The 1.23 seems to be ok! ! === > 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 ulator 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 ulator with > another. Same here. Being angry why they are luring customers telling them they are me an email explaining the situation and offering their assistance. Let me see when I receive my . I can only say that, their attitude changed on better, at least. === 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 ulator 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 ulator with >> another. >Same here. Being angry why they are luring customers telling them they are >me an email explaining the situation and offering their assistance. >Let me see when I receive my . I can only say that, their attitude >changed on better, at least. Samson Cables have been straight up with me. I tnk we can lay the blame at Carleys door step. === Subject: some questions about hp49g+ Can anybody tell me how to ulate / n | | k / I don't know how to enter it into the equation writer. Then i would like to know are there some rom updaates out now? Because my runs fast but crashes sometimes. I am not loosing any home memory but l stack elements are gone and ts can be very annoying. Is there a regular expressions libary on it? Or exists any? Where can i download it if there is one? I found out sometng very strange. Try out ts RPL program: << 0 -> KILL << HT >> If you run it the KILL command is overwritten by zero. Everytime when you enter KILL it just outputs 0. Is ts a bug or a feature? To get the HT away: 41.01 MENU and then press F6 === Subject: Re: some questions about hp49g+ > I found out sometng very strange. Try out ts RPL program: > << 0 -> KILL > << HT >> > If you run it the KILL command is overwritten by zero. Everytime when > you enter KILL it just outputs 0. > Is ts a bug or a feature? It's a feature. What happens in that program is that the object 0 is stored in a loc variable named KILL, and then the HT command suspends the program, so the loc variable is still present as long as the program remains suspended, so KILL is treated as the loc name instead of the command. Loc names can be the same as the name of built-in command, library command, glob variable, or even an existing loc variable. Ts lows you to use a loc name without checking that it doesn't conflict with an ready existing name. Of course, it so means that as long as loc name exists, you can't use the name for anytng else. Glob names made with the STO command can't match the name of a built-in command, but you can make an illeg glob name by renaming from the filer or using the S~N command. Of course there are so SysRPL commands that low illeg names. Note that using such names may cause problems. With the SysRPL CREATE command (or the equivent SYSEV sequence), you can even make a glob variable with a name the same as that of an ready existing glob variable in the current directory. Of course, you probably want to be careful to PURGE the duplicate name before the program finishes so that you can again use the pre-existing name. For more on how the compiler determines whether a sequence of non-delimiter/separator characters (outside of a character string, tag, or comment) is a loc name, glob name, library name, or built-in command, see http://groups.google.com/groups?selm=bo63gl%24ch4%241%40newsreader.mailgate. org > To get the HT away: 41.01 MENU > and then press F6 Or press LeftSft [ON] to execute the CONT command. Or #123h DOERR to, in effect, do a KILL. Or #13Eh DOERR to, in effect, do a CONT. -- === Subject: Re: some questions about hp49g+ > Can anybody tell me how to ulate > / n > | | > k / COMB is the command. i never remember the order of the arguments - n k COMB or k n COMB. > If you run it the KILL command is overwritten by zero. Everytime when > you enter KILL it just outputs 0. > Is ts a bug or a feature? A feature. The ulators says 'do what you want, i don't check'. You can so cl a program by any command name, and then your program will be executed instead of the origin command, since the HP looks first in home and then in ROM to execute the command. Xorxar === Subject: Re: some questions about hp49g+ X-ID: rwgpYiZSrebsnDSX0h2Uxp2uPiylEdsa8WEK3Xm6gAzeviAxkC6K > Can anybody tell me how to ulate > / n > | | > k / > COMB is the command. i never remember the order of the arguments - n k COMB > or k n COMB. It's n k COMB. === Subject: Re: some questions about hp49g+ > e, and then your program will be > executed instead of the origin command, since the HP looks first in home > and then in ROM to execute the command. a lot. But how do u do it that he evuates my program? when i do << >> -> KILL << KILL >> It only outputs the program but does not run it. Any to save a program with the name KILL does not work. Or is there a trick? === Subject: Re: some questions about hp49g+ > But how do u do it that he evuates my program? > when i do > << >> -> KILL > << KILL > It only outputs the program but does not run it. Any to save a program > with the name KILL does not work. Or is there a trick? Yes. The problem is to create the name 'KILL', wch is forbidden by the editor. Just type KILL (a string) and then #5B15h SYSEV, and you have 'KILL' on level 1. Then STO works perfectly Xorxar === Subject: Re: some questions about hp49g+ > Yes. The problem is to create the name 'KILL', wch is forbidden by the > editor. Just type KILL (a string) and then #5B15h SYSEV, and you have > 'KILL' on level 1. Then STO works perfectly the command S~N looks less dangerous that your SYSEV. === Subject: Re: some questions about hp49g+ > the command S~N looks less dangerous that your SYSEV. Bc S~N checks the argument ? In ts case, yes. Xorxar === Subject: Re: some questions about hp49g+ cool. thats a great possability to solve some problems i had. what i miss are classes. but perhaps in the next ration. ;) so my last question is there a regexp libary? > the command S~N looks less dangerous that your SYSEV. > Bc S~N checks the argument ? In ts case, yes. > Xorxar === Subject: HP49G HP49G+ saturn & C++ everybody, Does anyone know if a tool exist to write program in C++ for our powerfull HP49G and HP49G+ ? === Subject: Re: Help programming nucleonics and photonics library For references on User RPL programming visit: http://www.engineering.usu.edu/cee/faculty/gurro/Sofare_ulators/HP48_4 9G_Docs/ProgrammingHPs.htm If you want to use your PC to do the programming and then dump your library on the ulator visit: http://www.engineering.usu.edu/cee/faculty/gurro/Sofare_ulators/HP48_4 9G_Docs/ProgrammingInThePC.htm If you want to use the emulator visit: to l! Gilberto Urroz === Subject: Re: Help programming nucleonics and photonics library <9e993670.0402280711.174371d5@posting.google.com> very much, Dr Urroz! I own and like your books very much!! again, > For references on User RPL programming visit: > http://www.engineering.usu.edu/cee/faculty/gurro/Sofare_ulators/HP48_49 G_Docs/ProgrammingHPs.htm > If you want to use your PC to do the programming and then dump your > library on the ulator visit: > http://www.engineering.usu.edu/cee/faculty/gurro/Sofare_ulators/HP48_49 G_Docs/ProgrammingInThePC.htm > If you want to use the emulator visit: === 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. I would not recommend you to do that, because parts of the rest of the ROM depend on the CAS. You would probably not notice it at compilation, but unresolved entries may appear in the ROM (or more precisely flash pointers would point to sometng different or non-existant) and your would warmstart or TTRM. I urge anybody modifying the CAS not to modify flashpointer ordering. You can replace user functions without modifying the order. === Subject: Re: HP49G LGPL CAS release > I would not recommend you to do that, because parts of > the rest of the ROM depend on the CAS. Are there so many parts needing the CAS to work properly ? Xorxar === Subject: Re: HP49G LGPL CAS release > I would not recommend you to do that, because parts of > the rest of the ROM depend on the CAS. > Are there so many parts needing the CAS to work properly ? As far as I understand it the hp49 ROM and the CAS are a bit like MS Windows 98 and IE. It is possible to separate them but it is not trivi. Ts is in order to have a more integrated experience for instance using '+' instead of a function cled 'CAS+' or sometng. I have looked a bit into the ROM and it is not because we have the source of the CAS that we are going to have a great working updated system right away, there are many dependencies and as was posted by @padespam (?) the first one to play with it will certainly get some TTRM or worse, won't see them until it is too late. === Subject: Re: HP49G LGPL CAS release > As far as I understand it the hp49 ROM and the CAS are a bit like MS Windows > 98 and IE. It is possible to separate them but it is not trivi. > Ts is in order to have a more integrated experience for instance using '+' > instead of a function cled 'CAS+' or sometng. It's not just for the user interface. The new types routines (ZINT, symbolic matrices) are sometimes in the CAS. Moreover there are a lot of links beeen non-LGPL CAS code and LGPL CAS code. It is therefore not possible to remove the CAS. > I have looked a bit into the ROM and it is not because we have the source of > the CAS that we are going to have a great working updated system right away, > there are many dependencies and as was posted by @padespam (?) the first one > to play with it will certainly get some TTRM or worse, won't see them until > it is too late. Modifications should not modify the FLASHPTR stack prototypes (you can modify the implementation of course). You can add new flashptr after existing ones and replace some of the reserved ones in cas2user.s to add user words. If these rules are followed, there is no reason to get TTRM. If my recollection is correct, there is around 30K free in the CAS2 bank for additions. If you need more, you can remove part of the help (e.g. the French locization) or improve the CAS implementation in size! === Subject: Re: New HP 49G+ STILL not registering keystrokes! >FYI, I just mailed the ulator back for a refund. I am sorely >disappointed in HP. l three HP-49G+ ulators I purchased were >defective right out of the box. I was stuck paying spping costs five >times (one purchase and o returns, another purchase and return). >problems with the revised model except for my ulator and a few >otheposibly from the same batch. So maybe I rely am just >extraordinarily unlucky. But I don't tnk so, I tnk HP released a >defective product that is STILL not rely fixed, even if it is much >improved from the origin (wch, as you l know, was truly unusable >without the wiggle fix, and in my opinion not even with it). >an Weiss I wish HP would just bite the bullet and fix the damn tng, It might cause them to run in the red now,but if they would just fix it they would have another ulator with a probable ten year plus lifespan, under their belts. Eventuly they would make even more money. === Subject: Re: New HP 49G+ STILL not registering keystrokes! > I wish HP would just bite the bullet and fix the damn tng, It > might cause them to run in the red now,but if they would just fix it > they would have another ulator with a probable ten year plus > lifespan, under their belts. Eventuly they would make even more > money. I agree. Wle ts first effort at fixing the keyboard problems help, I do tnk they should just go l the way and completely fix the keyboards to be like the 48's. Like you said, if they did that, it would be an overwhelming suess. === Subject: Re: What brands of SD cards are you using??? Same here, Costco de too. > I'm using the SanDisk 256M card, bought at a loc Costco. It seems to > work fine on both my origin and replacement 49G+. > I used the 49G+ to format the card before using. >> Lexar SD cards don't seem to work with hp49g+'s >> They did not work with my first and sure don't work in my replacement >> with the redesigned keyboard. >> >I've just had a Lexar card stop working with my hp49g+. >I'm going to buy a Kingston next time > === Subject: Re: What brands of SD cards are you using??? Strange... For the record, I had used a gh-speed 32x 256Mb Lexar SD card for a wle with my CN331 49g+ and had no problems at l. so have used Kingston and SanDisk with no problems. Maybe some larger SD cards are factory fored as FAT32 and that is preventing them from working out of the box...? I now have a CN402 - maybe I'll try to borrow and test a Lexar card again on it... > Lexar SD cards don't seem to work with hp49g+'s > They did not work with my first and sure don't work in my replacement > with the redesigned keyboard. === Subject: Re: What brands of SD cards are you using??? Just purchased a Lexar 256Mb 32X o days ago and to date it is working flawlessly. The big bonus is that it is fast. Writing to the SD is atleast ice as fast as to writing to the built in flash memory. (a 6 sec backup operation now only takes 3 sec) Rick > Strange... For the record, I had used a gh-speed 32x 256Mb Lexar SD > card for a wle with my CN331 49g+ and had no problems at l. so > have used Kingston and SanDisk with no problems. Maybe some larger SD > cards are factory fored as FAT32 and that is preventing them from > working out of the box...? > I now have a CN402 - maybe I'll try to borrow and test a Lexar card > again on it... > > Lexar SD cards don't seem to work with hp49g+'s > They did not work with my first and sure don't work in my replacement > with the redesigned keyboard. === Subject: 49G Libraries on the 49G+? I have just been browsing the libraries on hp.org for my newly acquired 49G+. I presently see very few libraries listed there that explicitly support the 49G+. I have downloaded a couple of libraries, organizer 1.1 and scribe 1.1, and attempted to instl them on ports 0, 1, and 2 (I would prefer 2). There were no errors when I ran STO on the library. However, there were no LIB menus created for them either. Are these libraries compatible with the 49G+? If they are, I suspect that I have an understanding fault. === Subject: Start a program from SystemRPL Can I start a program from a SysRPL program? :: TAG 3 ID FILER6 xEV ; @ work... it starts FILER6 from SD... but I don't like it :o( === Subject: Re: Dare I mention the 49g+ Keyboard? What seri number ? > I just recieved my replacement and it still has the keyboard problem. > 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 very anxious to test my new > replacement. The new ulator 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 very similar. Compared to the old keyboard, the new one is > quieter, softer, and no longer has that hollow sound. I'm sorry about > an's experience, but for me ts has made l the difference...I now > have > a truly great ulator. === Subject: Re: Dare I mention the 49g+ Keyboard? Sorry to hear you are still having problems. Here is my experience to add to the statistics: Had a CN331 since November. The wiggle-fix mostly fixed my keys but I still felt I needed the key-click on for reliable data entry. The keys sounded hollow and had a sharp, plastic sounding click to them with much variation from one part of the keyboard to the next. Just received a CN402 a few days ago and it's a HUGE improvement. Virtuly l the keys now sound the same with a much quieter and smoother thud when pressing them. On my old keyboard, I could very deliberately miss keystrokes by pressing the keys at an angle or pressing very lightly. That is virtuly impossible to do now on the new keyboard. so, l the keys are tight on the new one - on my old one, I could jiggle whole sections of the keyboard around. so, taking the bottom part of the 49g+, lifting it about an inch off my desk and then dropping it would result it a clear rattling sound. Do the same with the new one and it sounds tight with no rattle. so note that my origin one was loose and rattly from the day I got it and did not seem to get any worse wle I had it. In a nutshell, I am very pleased with the keyboard now! I had heard or read somewhere that the new keyboard isn't rely new but early production units were actuly missing some important mechanic components in the keyboard. Obviously not enough to completely prevent it from functioning though. If anyone's new replacement still feels the same as an older (pre CN352) unit, one must begin to believe that maybe a few new ones are so making it past the QA inspectors and are still missing parts... I so own a 48SX and a 41CX. IMHO, even the new keyboard on my 49g+ is still a little too stiff and not quite as nice feeling as my 48SX - though it now seems just as reliable. Maybe it will soften up a little with use and more resemble the 48SX? However, my 41CX still has an awesome keyboard that has, IMO, a perfect feel with just the right pressure and click. The 49g+ doesn't come close - but then, neither does my 48SX... For the record, HP spped me a replacement with no fuss and included a spping label to send my old 49g+ back. > 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 very happy (I've had to > turn key click back on to make sure I wasn't dropping digits - wch saved > me on sever oasions). > 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 very similar to each > other) > Obviously some are finding tngs very 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? > > 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 very anxious to test my new > replacement. The new ulator 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 very similar. Compared to the old keyboard, the new one is > quieter, softer, and no longer has that hollow sound. I'm sorry about > an's experience, but for me ts has made l the difference...I now > have > a truly great ulator. === Subject: Re: Dare I mention the 49g+ Keyboard? Wle I so used a 41c and 48gx in the past, I tnk the 49g+ would be a beter ulator if hp could fix ts keyboard problem. I was taking a test yesterday and I had to constantly check to make sure l the numbers were being entered correctly as well as the arithemetic functions. There were a lot of keys not registering. I do miss the enter key being where it used to be on the 41 and 48. But I could live with that if the rest of the keyboard functioned right. > Sorry to hear you are still having problems. Here is my experience to > add to the statistics: > Had a CN331 since November. The wiggle-fix mostly fixed my keys but > I still felt I needed the key-click on for reliable data entry. The > keys sounded hollow and had a sharp, plastic sounding click to them > with much variation from one part of the keyboard to the next. > Just received a CN402 a few days ago and it's a HUGE improvement. > Virtuly l the keys now sound the same with a much quieter and > smoother thud when pressing them. On my old keyboard, I could very > deliberately miss keystrokes by pressing the keys at an angle or > pressing very lightly. That is virtuly impossible to do now on the > new keyboard. so, l the keys are tight on the new one - on my old > one, I could jiggle whole sections of the keyboard around. so, > taking the bottom part of the 49g+, lifting it about an inch off my > desk and then dropping it would result it a clear rattling sound. Do > the same with the new one and it sounds tight with no rattle. so > note that my origin one was loose and rattly from the day I got it > and did not seem to get any worse wle I had it. In a nutshell, I am > very pleased with the keyboard now! > I had heard or read somewhere that the new keyboard isn't rely new > but early production units were actuly missing some important > mechanic components in the keyboard. Obviously not enough to > completely prevent it from functioning though. If anyone's new > replacement still feels the same as an older (pre CN352) unit, one > must begin to believe that maybe a few new ones are so making it > past the QA inspectors and are still missing parts... > I so own a 48SX and a 41CX. IMHO, even the new keyboard on my 49g+ > is still a little too stiff and not quite as nice feeling as my 48SX - > though it now seems just as reliable. Maybe it will soften up a > little with use and more resemble the 48SX? However, my 41CX still > has an awesome keyboard that has, IMO, a perfect feel with just the > right pressure and click. The 49g+ doesn't come close - but then, > neither does my 48SX... > For the record, HP spped me a replacement with no fuss and included > a spping label to send my old 49g+ back. > 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 very happy (I've had to > turn key click back on to make sure I wasn't dropping digits - wch saved > me on sever oasions). > 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 very similar to each > other) > Obviously some are finding tngs very 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? > > 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 very anxious to test my new > replacement. The new ulator 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 very similar. Compared to the old keyboard, the new one is > quieter, softer, and no longer has that hollow sound. I'm sorry about > an's experience, but for me ts has made l the difference...I now > have > a truly great ulator.