32SII Programming (General?) Question


Actually, because of the length of time I have owned and used it, I am much more familiar with programming a 34C than the 32SII. I find the 32SII very similar except I don't see an "i" or "I" register (used for indirect addressing in the 34C). What is the equivalent or the work around in the 32SII?

Thanks in advance to anyone who has any ideas. (I know, I ought to look in the manual, but as of right now, even though it is by my elbow, I'm in the middle of something else [so what am I doing here, right?].)


It should be the same as my 32s: There's a lowercase "i" on the "." key, and one in parentheses "(i)" on the "R/S" key. Use the former to STO & RCL to/from the register itself, use the latter to STO & RCL indirectly.


Holy smoke!!

It must be more than simple blindness! I can't believe I didn't see it (all these years)! I have been avoiding writing routines that would have required the indirection.

Maybe I just still love my very worn out 34C way too much. I am hoping that the 49G+ will blow me away so I can begin to look at my bab... uh, 34C as you guys do, a virtual museum piece, or as Norm Hill put it, "an heirloom" (like my GameBoy oriented kids would want a RPN machine; I fear when they get old enough, and that's soon, their teachers will indoctrinate them with TIism, though admittedly as a parent, they are more affordable [so to speak; my 34C is now with me for close to thirty years, essentially very usable all that time!] and if the little tykes break one, I [emphasis on me] won't feel so bad.) Sorry for the rant.


Hi Ed,

If the 48GX did not blow you away, and the 49G did not either, then I daresay the 49G+ won't. Maybe the 33s will?;-0




Well, I actually have the 48G (no +, no X), and the major irritation there was that, here I have this incredibly powerful calculator and no memory to run it on! It's like having some hulking, nasty battleship that has to stay in port because it guzzles too much diesel (or, tanks too low).

So, I'm guessing that I would have had a much more positive experience if I had a GX. I never got the 49G. I only have an emulator that I downloaded right before the real unit was released, the emulator that came in connection with some contest HP had back then to publicize the 49G. And an emulator is not a hard piece of plastic studded with cool buttons.


If you're handy with a drill and a soldering iron, it's EASY to upgrade to 128K (basically, a 48g+), and only somewhat more difficult to go to 256K. Theoretically, I guess, it's possible to go to something like 1-and-a-half Mb, but that's with an extra board and several decoding chips.

There are a number of links on the Web describing this process.

I did a couple 48g's to 256K, but backed 'em down to 128k when some of the solder joints didn't hold. (You have to piggy-back two 128K memory chips, and I didn't do something right, as the pins didn't stay soldered together very well.) But the 128K versions seem to be fine.

FYI . . .


I'm not too bad with the ol' soldering iron; it's the drilling part that spooks me. I don't own a Dremel or any such thing. Even so, if I were to do it manually with some small tool bit or screwdriver or some such implement, I'd fear damaging the surrounding plastic around the rivets; neither do I believe I can find a chunk of time to concentrate so delicate a surgery- kids, etc. I think I'll entrust the upgrade to Randy Sloyer.

But as to soldering on two RAM chips piggybacked, would there be the slightest risk of excessive heat during operation if it did work? And as to the actual connecting- were the pins long enough for this sort of thing or could you connect them using some fine wire and do sort of an early Spice-type clamp down of the unsoldered chip to the soldered one? Anyhow, just daydreaming out loud.


I must say, both of my units had some slight scratches on the face from separating the case halves. (The drilling went fine, and doesn't show -- it was the act of pushing some internal spring tabs aside to separate the front from the back that I didn't handle as well as I might have . . . ) I believe that, with the right tool and a unit to practice on, all cosmetic damage can be avoided. But my two 48G's were my "practice units".

On the piggybacking of memory chips, the plan was to bend the upper chip's surface-mount tabs straight down, and then solder almost all of them to the leads of the chip below. In fact, there was something like a ~.5 mm gap between the ends of the upper pins and the tops of the lower, and I bridged that with solder. Apparently, some of those bridges broke loose over time. (The units worked fine for several weeks, then started exhibiting intermittent failure.)

I suppose some sort of tie-up with thin copper wire would work. I envision a loop or figure-eight around each pair of pins to be connected, and temporary connections across the top to the next pair of pins to be joined. After soldering, all the superfluous connections would be cut away.

But before I got to that point, I realized that I don't really fill up my 48's with programs -- I just wanted to upgrade 'em because it could be done ... I resisted the urge to make it work, and satisfied myself with 128K.


I understand the feeling. It's nice to be able to reach up and pull up another level higher... but usually this costs, in terms of sweat (and sometimes tears).

But I really need the extra memory, though I suppose 128K is sufficient... <fingers crossed>.


There's something to be said about using a trusted model with a red LED display! I'm not surprised you subconscously found a way to justify it.

I wouldn't count the 48Gii/49G+ out just yet. It looks as if many of the 49G's problems have been addressed, and if "early production quirks" does indeed explain the few keyboard problems we've heard about, it should be even better than the 48's.


I especially like the display resolution and the lightning speed of downloading to the 49G+. Programs that took upwards 5 mins to download on the GX takes only less than 5 seconds on my G+. The only thing I can really say I dislike on the G+ apart from the loud keyboard [ try typing when the wife is trying to sleep ], is the fact that you must watch everything you type, cause you might miss a character.


You don't say! 5 seconds?! I don't think my PC moves files to a Zip drive or jump drive that fast! Well, that too is something to look forward to. Hmmm... maybe HP is angling to regain some sort of dominance in calculators.


Well, my 48G FEELS as solid as a brick, as solid as my Old Spice ;) ... and actually, the 32SII feels rather solid, too, but you know, and here's where I show my real geeky side, the 34C is like TOS Star Trek, you know, Captain Kirk's ship with all the buttons sticking out from all the consoles, etc., and did the job well. The 32SII is like the Next Generation Trek: slicker, streamlined, rounder corners, and LCDs instead of LEDs, but still does the job well (even better, really, if I'd admit to it), but somehow feels a little less substantial nevertheless.

I preordered a 49G+ and am sort expecting it to blow me away! (You know, allows use of SD chips, and like that... that one feature impresses me the most, that HP would allow the user to do that rather than buying some prohibitively expensive memory plug ins proprietary to HP!)

Possibly Related Threads...
Thread Author Replies Views Last Post
  A good general mathematics reference book? Chris Smith 11 1,507 04-29-2013, 09:44 AM
Last Post: Chris Smith
  Simple? programming question [WP34S] Shawn Gibson 3 645 03-15-2013, 11:56 AM
Last Post: Didier Lachieze
  [43s] General questions fhub 7 928 01-31-2013, 11:04 AM
Last Post: Walter B
  General remark about the 43S polls Walter B 2 516 12-07-2012, 01:02 PM
Last Post: Walter B
  WP-34S Programming Question Matt Agajanian 2 559 08-04-2012, 02:04 PM
Last Post: Matt Agajanian
  WP 34S programming question Nigel J Dowrick 35 3,140 04-10-2012, 02:23 AM
Last Post: Walter B
  15C programming question Eric Zoob 7 848 03-28-2012, 03:14 PM
Last Post: C.Ret
  Question about programming the HP-71B Namir 27 2,516 11-28-2010, 01:50 PM
Last Post: Egan Ford
  General Electric CE 93 RPN calculator - and more... Joerg Woerner 0 293 11-09-2009, 03:16 PM
Last Post: Joerg Woerner
  question on 12c programming Don Shepherd 2 481 12-24-2008, 06:33 PM
Last Post: Egan Ford

Forum Jump: