HP35s BASE-n data entry
in [HP48]
|
Prev: New to the group-who is this phsycotic that is posting in all the newsgroups? Can he be stopped?
Next: Need help compiling SysRPL/ASM on 50g
From: roy_ccwchan on 28 Dec 2007 10:11 Hi there, I am really frustrated using HP35s for BASE-n calculation. I am never seen such kind of long step for data entry. For example. When in HEX mode I want to put ABCh on stack, I need to type A,B,C & BASE key, and then scroll down for small h, otherwise I got error. How come? Suppose anything input should be HEX data under HEX mode but rather than default DEC data input whatever which mode is. I tried to write a program for shorten input step but no success. Does any body have an idea how to overcome this silly input procedure. I prefer using HP20S regarding BASE-n calculation because it is so simple and direct. Other than this I have no complain. Roy
From: Monte Dalrymple on 28 Dec 2007 11:18 <roy_ccwchan(a)sinaman.com> wrote in message news:c610e40a-241d-44be-a39f-326fe3f53875(a)a35g2000prf.googlegroups.com... > Hi there, > > I am really frustrated using HP35s for BASE-n calculation. I am never > seen such kind of long step for data entry. > > For example. When in HEX mode I want to put ABCh on stack, I need to > type A,B,C & BASE key, and then scroll down for small h, otherwise I > got error. How come? Suppose anything input should be HEX data under > HEX mode but rather than default DEC data input whatever which mode > is. > > I tried to write a program for shorten input step but no success. Does > any body have an idea how to overcome this silly input procedure. > I prefer using HP20S regarding BASE-n calculation because it is so > simple and direct. Other than this I have no complain. > > > Roy Entering the "h" is blue shift-"1"-"6". Three keystrokes to do something that should be completely automatic. A royal PITA, with no way around it that anyone has discovered. I use hex regularly and if I had a penny for every time I've swore under my breath the return on investment for the 35s would be incredible. Monte
From: cappy2112 on 29 Dec 2007 13:21 A simple code update to allow data entry in all hex, decimal, or any base mode would fix this easily. But since there's no way to plug the darn thing into a computer, this wont happen. I guess if enough people complained about the problem, they might do a recall and replace the units in the field with updated firmware. On Dec 28, 8:18 am, "Monte Dalrymple" <mon...(a)systemyde.com> wrote: > <roy_ccwc...(a)sinaman.com> wrote in message > > news:c610e40a-241d-44be-a39f-326fe3f53875(a)a35g2000prf.googlegroups.com... > > > > > Hi there, > > > I am really frustrated using HP35s for BASE-n calculation. I am never > > seen such kind of long step for data entry. > > > For example. When in HEX mode I want to put ABCh on stack, I need to > > type A,B,C & BASE key, and then scroll down for small h, otherwise I > > got error. How come? Suppose anything input should be HEX data under > > HEX mode but rather than default DEC data input whatever which mode > > is. > > > I tried to write a program for shorten input step but no success. Does > > any body have an idea how to overcome this silly input procedure. > > I prefer using HP20S regarding BASE-n calculation because it is so > > simple and direct. Other than this I have no complain. > > > Roy > > Entering the "h" is blue shift-"1"-"6". Three keystrokes to do something > that should be completely automatic. A royal PITA, with no way > around it that anyone has discovered. I use hex regularly and if I had a > penny for every time I've swore under my breath the return on > investment for the 35s would be incredible. > > Monte
From: Joel Koltner on 30 Dec 2007 15:28 The base-n data entry issue is just poor design... whereas the 35s does have some pretty nasty bugs, as detailed here: http://www.hpmuseum.org/cgi-sys/cgiwrap/hpmuseum/articles.cgi?read=735 . All of those are, IMO, a good reason that HP ought to offer to recall & replace the units in the field... yet, like most big companies today, HP doesn't even publically acknowledge any of those bugs. Oh well.
From: Harold A Climer on 25 Jan 2008 20:08
On Sun, 30 Dec 2007 12:28:20 -0800, "Joel Koltner" <zapwireDASHgroups(a)yahoo.com> wrote: >The base-n data entry issue is just poor design... whereas the 35s does have >some pretty nasty bugs, as detailed here: >http://www.hpmuseum.org/cgi-sys/cgiwrap/hpmuseum/articles.cgi?read=735 . All >of those are, IMO, a good reason that HP ought to offer to recall & replace >the units in the field... yet, like most big companies today, HP doesn't even >publically acknowledge any of those bugs. > >Oh well. > > As said many times before, Mr. Hewlett and Mr. Packard are probably rolling over in their graves. I had two SX's and one GX replaced free, because of bugs, by HP in the early 90's. The "Golden Age". Of course I paid $350.00 a piece for them too. I guess it is a bit harder for a $60.00 calculator. I am talking a bit in the dark though,because I have no idea as to what HP's margin was for the SX and GX and is for the 35s. Harold A. Climer Dept. Of Physics, Geology, and Astronomy University of Tennessee at Chattanooga 309 Grote Hall 423-425-4546 Harold-Climer(a)utc.edu |