ASM Programming with HP50g

[3298]

That's odd, which GitHub repo did you use? The link I posted in this thread leads to Claudio's, which definitely does have the changes for that. Some other repos are stuck at an older version, though those should also be the ones missing fixes for errors with current compilers, i.e. you should have gotten stuck when attempting to use an outdated version. But you mention some SourceForge instructions ... ?!? something like that shouldn't be necessary.
At the time of posting Claudio's was the best repo to use; right now I'm leaning towards another, https://github.com/gwenhael-le-moine/x49gp/ (by another user interested in keeping x49gp going - the name on this forum is gwh, and he's also offering a renovated fork of x48). The difference between the repos is something the average user is unlikely to care about, some license compliance stuff that only affects compiling, installing, and setup on the first run. Claudio's repo has several commits in that direction, gwh's piles on some more. There's room to improve on this (as usual), but if you arrived at a working calculator, you're already past the effects of these changes. (Interested readers: the discussion leading to the commits is over there.

Alternatively, the problem could be one of the "not holding it right" type: the menu appears when right-clicking on the emulated screen, or when pressing the context menu key, which is commonly located next to the right Ctrl key. Some laptop keyboards unfortunately omit it or make it an Fn-combo function of another key.

---

For what it's worth, if I remember correctly the SD emulation itself didn't change since before x49gp arrived on GitHub, I merely made it more accessible.
In older versions it required fiddling with the config: in the section

Code:

[s3c2410-sdi]

you would have to append the filename of the folder or image-file to this line:

Code:

filename=

Absolute paths are preferred (and I believe that's what I made the GUI options retrieve), but relative paths kind of work too: in current versions it'll be interpreted as relative to the config file location; sufficiently old versions might interpret it as relative to the current working directory of the process instead.
If attempting to fix the problem seems like too much trouble for you, this info should let you experiment with the build you already have.