Mister E's Multi-Calc on WIN10

Been away from PICs for a while and needed one for a project. During that time I had to grudgingly upgrade to a WIN10 machine. Not pleased, but I pushed it as long as I could. Spent way too much time getting everything lined up again and I can finally do something on the new laptop.
Went back to try and use all my favorite tools and couldn't find comparable ones and haven't figured out how to use the old ones in XP mode. Mister E's Multi-Calc is a big one (1.3.1). Another is the PIC HWPWM calculator. Saved me tons of time in the past.

The searches that I have done aren't getting me any closer. If there are no suggestions, I may just fire up the old XP machine along side of the new one just to use the tools.

Anyone have some insight on how to make it play well?

Thanks
bo

For some reason, PIC HWPWM calculator is now deciding to work.

I did find this thread but it was concerned with getting MSSTDFMT.DLL into the SysWoW64 folder, my Multi-Calc install is looking for TABCTL32.OCX. I'm not familiar enough WIN10 to just poke it somewhere and hope for the best.

Thanks
bo

Isn't that the way, now I got a bit further and it in fact DOES want MSSTDFMT.DLL. I'll see if I can get through Henric's process...

I got everything but the ASCii stuff working on my Win10 using Henric's process, but that's covered in that thread as well. Good luck.

Does everything have to have an APP? What happened to the lone CALCULATOR and a piece of paper? The time spent trying to get the application to run on your platform you could have had it figured out already. It's NOT rocket science. IMHO....

Come on, Dave, you know in the heat of battle with one of these little suckers, it's nice to just pop up the purpose built "calculator" and keep moving. Yes, I can do it, but it sure was nice to just pop in a few requirements and move on.
bo

HPWM is an unfortunate wrapper for about 4 pic registers. It would pay to move on from that.

http://www.micro-examples.com/public...alculator.html

To close the loop, Henrik's suggestion and implementation solved the problem for me.
bo