I believe the Converter G3A file has no code in it, just a header with the icon, and that screen that says the file enables the converter function. It may eventually contain some magic key inside which the OS checks for. If that magic inside a Conv.g3a file is found, the OS makes the converter functions available. If not, conversion is not available.
This is what makes me support this theory of mine:
- On the Run-Mat OPTN menu, if the Conv.g3a file is not present, the space for the converter menu is still there, but blank.
- The function key icons for the converter menus are present in the OS itself and not in the add-in (I checked this with the help of INSIGHT). For example, I don't believe the icons "TMPR", "PRESSURE" or "FORCE" are used anywhere in the OS but on the conversion functions, and still, they are present in the ROM: icons 012B, 013F and 0139 respectively.
- There is no delay in accessing the conversion menus, ever (but this can be explained). I'd expect to see a hourglass even for just a fraction of a second when we enter the menu, because if the functions really are on the g3a file, then for executing code from it, it would need to be loaded. To load it, the file would have to be read. And the OS syscalls for file reading all display a hourglass even if the file is very small.
Let's admit the code was cached. It would need to be loaded at least once, at system startup (after reboot), when Run-Mat is run for the first time, or when the conversion menu is entered for the first time after a reboot. But I don't see an hourglass or any different delay the first time any of these are loaded...
If the conversion code was loaded at system startup, and then never get touched after, then deleting the Conv.g3a file in-calc wouldn't make the conversion menu disappear immediately after. If in your Run-Mat history there were any conversion "characters", they will be replaced with @ symbols that return syntax errors when executed (this is probably the only way to insert @ on the Run-Mat
). This kind of defeats my point saying the code isn't in Conv.g3a. But it may just be a clever trick by Casio. Then if the code is in Conv.g3a, how does it get loaded so fast, and without hourglass? I'm so confused now...