Hi,

HP has released new versions for (almost all) their emulators on their usual emulator sites:

(only a few older financial emulators like the 12c/10bII/17bII are missing)

http://www.hp.com/sbso/product/calculators-emulators/scientific-calculator-emulator.html

http://www.hp.com/sbso/product/calculators-emulators/graphic-calculator-emulators.html

http://www.hp.com/sbso/product/calculators-emulators/finance-calculator-emulators.html

And the good news: these new emulator versions don't need an activation code anymore! :-)

Thanks to HP (and also to Tim Wessman, because I guess it was he who convinced HP to remove this activation code) for making these emulators available.

Franz

Quote:

---

HP has released new versions for (almost all) their emulators on their usual emulator sites:

---

Thanks, Franz, much appreciated.

Best regards from V.

Thanks for sharing!

d:-)

Nope. It was not me. :-)

TW

Thanks HP! Now I will need to learn how to transfer programs between calculator and emulator.

Quote:

---

Nope. It was not me. :-)

---

But there's really something strange going on with these HP-sites:

At the moment when I open any of these 3 websites I'm getting the old pages again (with links for the old emulators with activation code) - it seems HP has changed their mind again and reverted back to the old emulators!?

Edit: Now a few hours later the new (unprotected) emulators are up again - crazy HP ... ;-)

Franz

Edited: 5 Feb 2013, 1:56 p.m.

Quote:

---

Now I will need to learn how to transfer programs between calculator and emulator.

---

d:-/

IIRC a direct connection between Emu48 and a real HP 48 is possible, too, and was possible before a 50g even existed. And don't forget Emu41 and Emu71 from JFG, which can be connected to their real counterparts through HP-IL adapters, using either the ISA card, or better these days, the famous PIL Box.

I stand corrected :-) None of the calculator models contained in HP's emulator package, however, looks like being able to communicate.

d:-)

39gs, 40gs, 39gII.... guess that is none. :-P

TW

Come on, that thread was about the 10s, 300+, 15C, 35s on the scientific side :-b

Tim, I get a severe Windows XP crash (blue screen with auto reboot) when I try to install the virtual COM port driver coming with these emulators. Any hints?

Never heard that one before. If anything, I'd expect XP to work fine and newer OSes to have issues.

TW

Quote:

---

I get a severe Windows XP crash (blue screen with auto reboot) when I try to install the virtual COM port driver coming with these emulators.

---

Me too.

Great. I tried the 15C and 35s emulators - and I wonder why they are so different.

• The 15C version uses a nice photograph of "the real thing". The 35s version offers different skins, but the best you can get is a "stylized product rendering", as the menu calls it. Also, the 15C version allows to hide the title bar so that just the calculator is visible. The 35s version always seems to diplay that annoying window frame provided by the operating system.
  
• The 15C version allows to copy numeric results to the clipboard. The 35s version just copies the two display lines to a graphics file. The result itself cannot be copied (and pasted into another application).
  
• The 35s emulator works significantly slower than its 15C counterpart. Try a simple square root. It takes about half a second on the 35s version, while the 15C returns the result instantly. In general, the 35s emulator seems to work roughly as fast as its hardware counterpart or slower (!), while the 15C emulator runs as fast as the PC hardware allows. Or maybe it's the speed of the 15C LE. ;-)
  
• The 35s emulator offers a lot of options in its Tools menu. I could not find any reference on how to use these. The same is true for the "Macro" function as well as others (e.g. what's the difference between Save/Load and Fast Save/Load?). Or do I miss something and all this is documented somewhere?
  
• What about the keyboard mapping? The 35s simply seems to use the letters on (most of) its keys. "Shift" and "Ctrl" seem to map to yellow and blue shift. On the 15C, "Ctrl" works the same way but "Shift" does not work here. And what about all the other keys?
  

Quite simple actually. The 35s is a totally different codebase.

It was done by Kinpo back in the day way before I joined HP. It matches the 12cp and 17bII+ emulators. The skins are DLL files and require compiling. The emulation is done in a dll we don't have the source code for.

It does have the more advanced macroing stuff built in that allows to save and load key sequences, but it has other things missing. No, you are not missing documentation on those things - it has never been prepared.

The 15C was done by HP and actually is very close to the 20/30b emulators that in part formed the later initial version of the non-QT 34s emulator. It is much quicker and more efficient, but we were never instructed to implement things like the macro recording.

These emulators are really generally created as an offshoot of development. After that there can be a different amount of effort put into them to make them serve as aids for teachers, or possibly for end users.

TW

Tim, thank you very much for your reply. So there actually is no documentation, neither for the 35s nor the 15C emulator? Not even a table with the keyboard mapping? While Ctrl seems to do a blue/g-shift on both emulators, I could not find out how to get a f-shift in the 15C-emulator.

BTW, there seems to be a bug in the "paste number" function. It only works correctly with a dot as the decimal marker, but not with a comma. Try to paste a number like "6,022 E23" and the display shows "6.022 E23" which then translates to 6,022 E26. Even a simple "123,45" is interpreted as 12345.

Finally, it would be nice if copy/paste supported the usual shortcuts Ctrl+C and Ctrl+V. This way they could also be used with a hidden titlebar. ;-)

Dieter

Quote:

---

So there actually is no documentation, neither for the 35s nor the 15C emulator?

---

Quote:

---

Not even a table with the keyboard mapping?

---

The structure is as follows:

key=n,x1,y1,x2,y2,{keycode-list}

'n' is the key-number (0-39) and the following 4 number define the rectangle position of the key.

For the key assignment the last list is important - here you can enter the scancodes of the PC-key which you want to use for this emulator key.

Example: key=0,68,221,132,274,{78,112}

This is key 0 (the top left 'sqrt(x)' key), and the numbers 78 and 112 stand for the PC-keys [N] and [F1].

Quote:

---

While Ctrl seems to do a blue/g-shift on both emulators, I could not find out how to get a f-shift in the 15C-emulator.

---

Franz

On the 30b emulator, how do I hold down the shift key so I can get to the programming functions?

Thanks - at least this means you can get an individual keyboard mapping.

I made some changes to the .skin file - [f] and [g] now are simply f and g on the PC keyboard. #-)

Dieter

I think right click, then left click with both buttons. Could be wrong though...been a while.

TW

Quote:

---

Thanks - at least this means you can get an individual keyboard mapping.

---

Well, with these graphical glitches and now also the key problems I really must say that this is the worst calculator emulator I've ever seen. :-(

BTW, [f] and [g] can also be simulated with a middle and right mouseclick.

Franz

Tim, thanks for mentioning the 34s. The emulator was a direct descendant of the SDK released by HP (mostly Cyrille, I suspect). My contribution was mainly to separate the code from the calculator engine and move it to a DLL. Some 34s specific additions were made but they are minor compared to the work put into the emulator from your side.

I hate emulators. I thought this site was about the "real thing".
There are "emulator fans"?
I feel sorrow for them.

Quote:

---

I hate emulators. I thought this site was about the "real thing".
There are "emulator fans"?
I feel sorrow for them.

---

This forum is about calculators and mathematics, including the "real thing", apps, and emulators.

Now, how do I flash the 30b to become a WP34S? ;)

And why is there such a significant difference in size between the 20b and 30b?

Harald, I know your 'flashing' question is a joke, but nevertheless I can give a serious answer. :)

2nd question first, with the small skin loaded I can see no noticeable difference in size between the 30b and 20b emulators. It should even be possible to transplant the skin(s) of one emulator to the other by copying the *.skin and *.bmp files.

Now back to 'flashing' either emulator to become a 34S. In fact, that's the first thing I did (using the 20b SDK as the target 'machine') when taking my first steps in the 34S project. The GUI part of the original 34S emulator is still mostly HP code...

To make flashing a target ROM image possible would require a totally different emulator architecture than we have now: a complete and faithful ARM/Atmel hardware emulation layer (including write access to flash, and all the peripherals). What we have now is more of a simulator or something between the two extremes: The very same C/C++ code base is compiled for different targets, either by MS Visual Studio or an ARM cross compiler (IAR for HP, GCC for 34S).

Quote:

---

2nd question first, with the small skin loaded I can see no noticeable difference in size between the 30b and 20b emulators.

---

The reason why the 30b package is bigger: it contains twice as many skins as the 20b - for each skin there's also a 'devel' version (development?) for the 30b.

Franz

Quote:

---

Hi,

HP has released new versions for (almost all) their emulators on their usual emulator sites:

(only a few older financial emulators like the 12c/10bII/17bII are missing)

http://www.hp.com/sbso/product/calculators-emulators/scientific-calculator-emulator.html

http://www.hp.com/sbso/product/calculators-emulators/graphic-calculator-emulators.html

http://www.hp.com/sbso/product/calculators-emulators/finance-calculator-emulators.html

And the good news: these new emulator versions don't need an activation code anymore! :-)

Thanks to HP (and also to Tim Wessman, because I guess it was he who convinced HP to remove this activation code) for making these emulators available.

Franz

---

We should be able to use the graphing calculator emulators straight away (without ROMs), correct?

Quote:

---

We should be able to use the graphing calculator emulators straight away (without ROMs), correct?

---

Franz

Quote:

---

Yes, all ROMs are either included or even integrated in the emulators.

Franz

---

Thanks Franz!

Yes, that is what I meant. Thanks Franz!

Quote:

---

Now back to 'flashing' either emulator to become a 34S. In fact, that's the first thing I did (using the 20b SDK as the target 'machine') when taking my first steps in the 34S project. The GUI part of the original 34S emulator is still mostly HP code...

---

Quote:

---

To make flashing a target ROM image possible would require a totally different emulator architecture than we have now: a complete and faithful ARM/Atmel hardware emulation layer (including write access to flash, and all the peripherals). What we have now is more of a simulator or something between the two extremes: The very same C/C++ code base is compiled for different targets, either by MS Visual Studio or an ARM cross compiler (IAR for HP, GCC for 34S).

---

Thanks for the info!
Harald

Quote:

---

I wonder if the 15c emulator does it the other way and emulates the ARM processor.

---

I was previously (probably also) hoping there's the original 30b firmware in the emulator so we have a chance to get a recent firmware with the latest bugfixes. Not so :-/.

There is an emulation layer built into the 15C LE which maps the Nut processor to the ARM hardware. In the Windows version this emulation layer exists too, this time mapping the Nut processor to the Windows PC. There is no ARM layer in the PC version.

It should be possible to extract the original 15C (Nut) ROM code out of the Windows version.

Emulators are the poor man's hardware. I can not afford an IBM 9121 and the needed peripherals and if you feel sorrow for that, well, frankly, it does not help me in no way. But the Hercules emulator does. This and most emulators/simulators of pocket calculators are great fun. My personal joy. :)

Regarding the technology, 'Virtual Machine', what you may translate to 'simulate or emulate hardware' (still up to date in z/VM), is a common tool to set up server clusters. So if you hate emulators, it is your private joy. ;)

Ciao.....Mike

BTW, I could imagine that new calculators are engineered with the help of virtual hardware. So next time you have a real HP at hand, remember, it is the fruit of an emulator - if you hate it or not.

So you hate the HP-50g, HP-15C LE and the newest HP-12C? Because all of them are emulators. Contrary to you I'm glad that there are emulators. It makes writing programs so much easier. And it makes it possible to use different models on the same device like a smart phone. Still I'm fond of the "real thing". But I don't want to cary them with me all the time.

And then I'm amazed that I can boot a Linux System in the browser of my iPhone: Javascript PC Emulator . Now I'm going to download Nonpareil and run the HP-41C emulator in it.

Cheers

Thomas

Quote:

---

So you hate the HP-50g, HP-15C LE and the newest HP-12C?

---

Hi Reth,

I happened to be reading some past comments about other emulators while looking up an unrelated topic. Oddly, I think there seems to be some drift in the tone of your comments over time (posted 9 May 2008, 7:01 a.m.):

Quote:

---

Hi Thomas, first of all I'd like to thank you big time for your brilliant work, absolutely impressive! And please do port your emulator for the iphone/ipod touch (they are identical in that respect as you guessed). I just can't wait to see how your beautiful implementation of one of the greatest calculators ever runs on one of the greatest contemporary platforms. Be good and keep up the good work,
cheers,
reth

---

Possibly this is another person using the handle Reth. If not, then 1) you have commented on emulators in this forum in the past, and 2) you seem to have a soft spot for at least some of them.

Perhaps since that time you have felt wronged or personally let down by an emulator or two and have come to resent and be bitter about them all. Understandable, I once ate a fish that disagreed with me and to this day I cannot look at the ocean the same way. The counselling and therapy are going well, however, I can now at least resume showers again!

I, for one, quite enjoy having emulators available, and though they don't replace the sensual tactile encounter of a real machine, can be quite pleasurable and useful in their own right -- as a previous Reth seems to have also noted.

All the best...

Free42 is not an emulator but a simulator. I stand behind all my words about Thomas Okken's work! And 42S by Byron Foster is my number one choice for iPhone.

Cheers,

why does the blinking stop?

99! ---> 9.9999E99 blinking

f x2 ---> BLANK SCREEN !?

it's not always, but if the keys are pressed fast enough it happens.

The calculator forensic from http://www.rskey.org/~mwsebastian/miscprj/forensics.htm suggest that the original ROM is used or at least the same algorithm as in the HP-15C.

Except the ugly misaligned pressed keys, I like the graphics of the emulation ... but are there some bumps in the bezel??

Some dents and lots of dust indicate perfect emulation of age, too ;-).

The 15C emulator shares the bugs of the 15C LE. The (in)famous PSE bug and other display anomalies have been introduced by a less than perfect optimization of the Nut emulation (to be precise the R2D2 emulation) that is shared by the emulator and the LE.

You did better... :-)

Quote:

---

I'm glad that there are emulators. It makes writing programs so much easier.

---

I agree, I would rather have a bit-perfect emulation running on a virtual machine, which ensures portability of code and reproducibility of results, rather than an optimized simulation that departs in substantial ways from the original such as the precision, solving algorithms etc.

Nick

As long as the emulator is based on the same code base as the original, precision and results should exactly match. No need to emulate on the hardware level. OTH, if only the (old) binary code is available but the original processor no longer is, hardware emulation is the way to go.

HP went both ways: 12C, 15C use hardware emulation; 20b, 30b use the identical code C++ base, compiled for different targets.