I'm going to be looking at the various alternatives to ICE. I was surprised to see so many, but I guess it makes sense since Sinclair didn't provide one. It looks like it became the wild wild west in the early 80s and then eventually settled on a more X-like Pointer Environment that we have today which gives the QL much more modern abilities. But still, the early interfaces were interesting.
I saw this article and these seem to be the first entries into the QL GUI battle:
https://dilwyn.theqlforum.com/frontend/e ... ec1986.pdf
But I decided to start with J.A.M, which also seemed interesting. It doesn't work as a traditional GUI where it treats each file fully as an object (i.e. no double clicking to open things), focusing more on selecting icons and performing menu options on them. Though it's a bit more limited as it only supports 4 hard-coded drives (MDV1, MDV2, FLP1, FLP2) it has some cool features, like the job control providing TK2-like capabilities, and the memory dump, giving you quite a bit of detail. Would have been nice for ICE to add those, but then again, J.A.M. seems to take up twice as much memory at almost 30K. Maybe ICE could have added some auxiliary functionality on MDV, like it did with CHOICE.
So comparing ICE and J.A.M showing system and memory status, it seems that with a 128K QL, they both claim the system takes up about 51K. That would be 32K for screen memory....so where's the other 19K going to?