The Sinclair QL Forum

That was a very good idea!

Thanks Martin!
Id be more interested in a utility to entirely remove any built in runtimes..

pjw wrote: Sun Aug 31, 2025 2:01 pm Thanks Martin!
Id be more interested in a utility to entirely remove any built in runtimes..

Me too, although both removal and addition are useful tools.

Martin_Head wrote: Sun Aug 31, 2025 10:42 am I don't know if there is any interest in this, But this program will add the runtimes to a compiled program that does not have them.

At the moment I use only QLib programs which already have a built-in in runtime, but it's good to have, just in case.
Many thanks.

Peter wrote: Sun Aug 31, 2025 9:38 pmAt the moment I use only QLib programs which already have a built-in in runtime

The solution is actually quite simple: simply load "QLib_run" in the boot program, then everything will work....

RalfR wrote: Tue Sep 02, 2025 3:38 am

Peter wrote: Sun Aug 31, 2025 9:38 pmAt the moment I use only QLib programs which already have a built-in in runtime

The solution is actually quite simple: simply load "QLib_run" in the boot program, then everything will work....

A solution is only necessary if you think there is a problem. I have no problems with (rather, I prefer, like Peter) self-contained programs that come with their runtimes. This preference probably depends on how many QLiberated programs you use.

Nice to have the option, I suppose.

I normally load up Qlib_run, Turbo_TK, ptrmen, Qmenu, PHGTK, Dbas, and a bunch of other "standard" toolkits and system extensions in my boot file so I dont have to faff around every time I want to fire up some well-worn - or rarely used - program, or to test anything new. I run the same boot file across all the systems I use for anything other than testing.

It doesnt matter whether the runtimes are included or not, the program will work either way. Its just that niggly feeling about the unnecessary bloatware, so it would be good to have the possibility to get rid of it.

Of course if you only run the same three old programs on your "QL", then theres no need to change. You probably then use some kind of PC to do any "real" work.

Here's a program that will remove the runtimes.

There is also a small update to the previous program. It's functionally the same, it just correctly displays the QLib version number in QLib V3.45

Version 3.45 has a version number of 3.45a. The version number is stored in the compiled program (usually) as a long word, just before the start of the compiled SuperBASIC. But in V3.45a it is stored as a 5 byte string. So in V3.45a the compiled SuperBASIC starts at an odd address, which upset PEEK_L and POKE_L when I tried to move it.

It works a treat, Martin, at least on the program I tried it on. Thank you
The removal program appears to remove 114 bytes more than the size of the Qlib_run I just compiled into it. Is that normal?
Adding it again using your program restores the object to the "correct" size, ie 114 bytes less than the compiler managed.
Either way, the object program worked as it should.