The Sinclair QL Forum

On QPC and my QLs, I'm using TRAP #15 instructions with beacon strings to trap into QMON. This works nicely: When QMON sees a TRAP 15, it will break the program at the current PC (I'm using macros to create a TRAP #15 and strings to show me where I am). This, unfortunately, does not work on my Q68 (...

just as experiment..... For anyone who wants to give it a try.... Arduino code + Superbasic file please ignore the weather tningy.... I am not ready for HTTPS yet :) Would like to see if anyone can add nice things as well... It works perfect on a Q68 I don`t have a cable for my old ql so I couldn't...

Indeed. I have been using that one for a long time, until I moved all my QLs to SMSQ/E. It basically behaves the same as the history device in the newer OS (some marginal differences that you need to get used to). Recommended. These are indeed "must haves" for non-SMS systems, as long as ...

QJump have always sold their RAM disk as a separate product, "ramprt" (Also includes a print spooler). It just got mixed up with Toolkit 2 over time because many disk interfaces simply included both. If anyone wants to use ramprt (as the most "original" RAM disk), it is included ...

Could you provide a link, please? I see PTH on Dilwyn's site ( https://dilwyn.qlforum.co.uk/tk/pth.zip ) but it does not seem to include a commandline history extension. Nope! The "history device" is not from Phil Borman but from Boris Jaubith, Berlin (friend of mine). You will find it on...

There seem to be simple I2C-to-RS232 adapters that allow you to connect I2C devices to RS232 serial interfaces. Here's a link to such an adapter kit: https://www.horter-shop.de/de/i2c-pc-adapter/41-bausatz-i2c-rs232-koppler-4260404260547.html (Note I haven't tried wether that works with the QL, but ...

Sometimes, apparently, problems need to sink in deeply for a while until they collide with something else in my memory that happens to be the solution. Same case here, I totally forgot about NASERVE until a small LED went blinking in my brain: With regards to the MEM device and security concerns (ov...

What could be of interest in this context is the mem_ device driver which is part of the DIY toolkit (in the v_n section) - That allows you (amongst some really "magic" (or is it dubious?) other stuff) to PEEK and POKE into a remote machine's memory over QLAN (George Gwilt's NET_PEEK does...

What could be of interest in this context is the mem_ device driver which is part of the DIY toolkit (in the v_n section) - That allows you (amongst some really "magic" (or is it dubious?) other stuff) to PEEK and POKE into a remote machine's memory over QLAN (George Gwilt's NET_PEEK does ...

<> This is the simple program that run on Q68: 110 ch=FOP_IN ("tcp_time.nist.gov:13") <> I just get Not found. What driver do you load? That happens to me as well, sporadically. That's when the driver couldn't resolve a hostname in time. I tend to do that resolving by hand then and insert...