The Sinclair QL Forum

Nice video! I didn't follow the forum too well lately, so I missed that you actually found a better USB to PS/2 converter. Good! By the way, if games are unplayable, you can use the SLUG command to slow the Q68 down in hardware. And I think you don't have to put hardware in quotation marks for the Q...

Thank you, and sorry for asking the same question only two years later. I notice I'm getting older...

If I remember correctly, QLObi on this forum is expert when it comes to QIMI retrofits. Could make sense to message him.

By the way, which mouse interfaces are supported by the non-SMSQ/E pointer environment?

Hi Martyn, I have an almost complete design for a backwards-compatible enhancement to the Sinclair protocol, that would allow for dynamic/negotiated bit-timings and other capabilities between machines that can support them in a way that is invisible/transparent to any legacy machines also listening,...

Whilst on this (off-) topic and just as a little teaser - an updated version of the ND-Q68 driver that I am still testing can push over 700 kbps (that's bits per second, not bytes) between a pair of Q68s... :-) That's amazing. Roughly guessing about 60KB/s actual file transfer throughput, that's al...

dilwyn wrote:I guess it's a documented feature (QPTR guide etc), so purely in that respect it should be included. But I do take the point that it's rarely if ever been used.

I use it in my email client, and so does QPOP3.

M68008 wrote:I've moved the circuit from the breadboard to a permanent circuit and box:

Fantastic! Except the color

There is and I've added a topic on the Off Topic section to explain the differences. It's at https://qlforum.co.uk/viewtopic.php?f=9&t=3643 if anyone is interessted. Thanks Norman! My question even had an almost on-topic backround. I was starting to have a look if Martyn's code could be ported ...

Hi Norm,
many thanks, that's much more of an answer than I expected or deserved as a non-Arduino user who was just nosy.
All the best
Peter

Another issue is the non-streaming nature of the protocol. Every 255-byte block has to be ACKed before the next can be sent, which degrades throughput to 50% or less of what would theoretically be possible. This even hampers performance when using Ethernet connections between emulated systems. When...