Hoppi 1.3.2 Release

[Han]

(12-15-2016 12:29 AM)JDW Wrote:  

(12-14-2016 09:23 AM)Han Wrote:  Merge your memory...

I've never done that before because I've never had any cards for my 48GX before, but I can lookup how to do that.

(12-14-2016 09:23 AM)Han Wrote:  ...install it into port 0, then detach it.

When I use Paul's software Hoppi, it allows me to move the file (in this case, the 128k Meta Kernel file) from my Mac into VAR on my 48GX. So what you are saying is that after it is saved in VAR, I need to use File Manager to move it to port 0?? And when you say "detach it" you mean PURGE/DELETE it from VAR?

(12-14-2016 09:23 AM)Han Wrote:  That said, as fast as MetaKernel can be, it is quite unstable. I would not recommend using it. If you just want a faster interface, consider using SpeedUI.

But when I use my 50g and do a warm start, I see that it has Meta Kernel. Even the startup screen is exactly the same as the old 48GX Meta Kernel. As such, if Meta Kernel is so buggy, wouldn't the 50g be buggy too?

Thanks!

In general:

Assuming a blank slate and RAM card in slot 1, you simply type MERGE1. This merges RAM and card slot 1 so that you have approx. 256KB memory. Programs that are near the 128KB limit and (after accounting for the fact that the OS takes approx. 4KB) would result in insufficient memory conditions without merging. With merged memory (256KB) this should not be an issue.

Anyway, after downloading the library:

Recall the library onto the stack, and delete the variable containing that library. Then type 0 STO to store the library into port 0. Note the library number. Then, you can "unmerge" your RAM and RAM card using: { :0:lib_num } FREE1 where the :0: refers to port 0 (where the library is initially stored) and lib_num is the library number. If you have multiple libraries, then you will simply need more library numbers in your list, tagged with appropriate port numbers.

Meta Kernel, however, has its own special installer. You will still need to merge memory, but the installer will take care of the rest (such as moving the library and unmerging the RAM card).

Meta Kernel for the HP50G is a much later revision. I believe the MK version in the HP49G was 3.0 or something close (you can find old posts by Jean-Yves Avenard on comp.sys.hp48 about this). I am not sure what version is on the HP50G. However, the highest version on the HP48GX was 2.29 or so. The buggy behavior had to do with the object compiler/decompiler (i.e. the routines responsible for turning human readable code into binary code and vice versa). It has been too long for me to remember all the issues, but the one I do recall was arrays of numbers (integers in particular) often got corrupted and would result in complete memory wipes. Since practically everything involved the command line and hence the compiler/decompiler, MK was not an option for me.