The Sinclair QL Forum

PS: Needless to say, devising such a scheme is one thing, implementing it would be quite something else! That would require a good understanding of how Qlib works. The good news is that Martin has gone to quite some trouble to analyse and annotate all the toolkits that form part of Qlib!

Im ...

Great work Martin!

It seems a pity no one could lend you a suitable system to try on. Im sure that would have been so much easier! Supposedly Tony Tebby once debugged a hard disk driver in Germany while he was situated in England! I cant remember the details but it sounded equally impressive ...

I havent been able to follow this in great detail recently, but do I understand correctly that the new QERR file is patched with code to flush the cache before or after certain operations? If so, will the patched QERR still work on non-Qx0 platforms? Or do we need to compile separately, or use a ...

Artificer wrote: Sat Jul 12, 2025 11:54 am QERRON.JPG

I have tweaked and compiled the snippet of code Dilwyn Jones supplied. The image shows the code and the outcome indicating that the program
hangs after Q_ERR_ON was set and when error trapping OPEN_IN.

Q_ERR_xxx figures largely in the Qlib compiler itself..

<>
To remove a Hokey and leave the Thing present, use: ERT HOT_REMV (<key>)

Where <key> is the definition of the HOTKEY setup with on boot up to load the application as a Thing, which when the ALT <key> is removed, the Thing can be loaded with EXEP
<>
But note: To do that you have to load the ...

<>
As for your extension not working, it's generally not recommended to load extensions in SBASIC child jobs, especially not when they contain system extensions such as device drivers and interrupt servers. They will be destroyed when you quit the child job but the system will still have hooks to ...

On a practical level I agree with everything you wrote Peter (and tofro)! The multi GHz CPU was about a revival of 68k systems in general.

Im off to the wilds again for the next month or so, so no time to be more specific.

<>

I guess we're talking slightly at cross purposes (or my friend and you, rather). I suppose she was thinking rather in terms of hardware platforms for a next gen "QL". The speed of QPC and SMSQmulator is good enough for any of the stuff we use on those systems today. (And no, Im not dissing ...

<>
1. Say a multi-GHz MC680x0 compatible CPU magically appeared. Would that make a difference do you think?

2. Emulators work like code interpreters during runtime, something that creates a lot of continuous overhead. Might it be possible that the 68k assembly language were to be considered just ...

Really nice photo!
Wish Id been there!