|Re: Running 33S and 35S emulators in Win 8|
Message #8 Posted by fhub on 5 Dec 2012, 9:00 a.m.,
in response to message #7 by Ed Look
Well, you can let the real 33s in its bag - I think I've found (and fixed!) the problem. :-)
I might as well pull out the real 33s or 35s, as I often do, anyway.
I've analyzed the 'HP 33S.exe' and found that more than 400kB (of about 507kB) are just a 'loader' program which loads the true emulator, and this emulator is only 90kB. I saw this because when running the 33s it creates a temporary hidden file with random names (like e.g. 'HP 13C2.exe'), and this hidden file is the true emulator with only 90kB. You can also see this in the taskmanager, because it shows both processes running, the original 33s and the smaller emulator.
And I guess that's exactly the problem: when you close the program, one of these processes is still running (sometimes, at least in Win7/8).
Ok, with this knowledge it wasn't difficult to solve the problem: I've simply extracted this 90kB emulator, and guess what - yes, this small emulator file is running without any problems. :-)
Since I can't reach my own website at the moment, I've uploaded this 'fixed' HP33s emulator here for you:
Just unzip the 'HP 33S.exe' from this file and copy it over your original one (make a backup if you want).
BTW, after removing this 'loader' code there's still another advantage: now the emulator doesn't need a serial number anymore! ;-)
And since the HP-10bII emulator has the same loader program, I've also included the pure emulator file for the 10bII (this one runs without any extra files).
The 35s does not have such a loader, so if you really have the same problem (staying in memory after closing) with the 35s, then it must be something else. But I doubt that the 35s shows this behaviour, because I never had this problem with the 35s (even on my Win7) - so maybe it was just a single failure on your side.
Let me know if my 'fixed' 33s solves your problem on Win8 ...
Edited: 5 Dec 2012, 9:02 a.m.