I think I noticed this, but then found the QPC2 was sat in the notifications bar in bottom right... Not seen it recently though... Looks like somehow my QPC2 had changed its "Show QPC in..." setting to Task/Tray somehow without me noticing - now reverted it back to "Taskbar". I ...

mk79 wrote:

XorA wrote:uQlx adds the number of bytes received to A1

aReg[1] = qaddr+res;

where qaddr was the value of A1 on entry to routine!

Oh well, that might make sense in some context but is contrary to the spec the uQLx author himself wrote...

An easy fix for someone though

uQlx adds the number of bytes received to A1

aReg[1] = qaddr+res;

where qaddr was the value of A1 on entry to routine!

stephen_usher wrote:

XorA wrote:So party 28 days after launch day

But only in a location where you can have a tent outside to hold half the attendees.

The rest arrive later on a bus that parks at back of tent? But they are not allowed off bus!

I think I have got my network driver working in uqlx2017. uqlxNETdriver4_cde.zip I had to make some changes to the routine that reads data packets. I have done a quick test between two copies of uqlx2017 running on the same PC. And a test between uqlx2017 on a Linux machine, and QPC2 on a Windows X...

No time for all of that at the moment, so if the OSSC would not collect dust inside and act as a jamming transmitter, I'd be tempted. It's interesting you mention that you think that it'll act as an RF "jammer". I've not seen any interference with any systems or analog & digital radio...

So party 28 days after launch day

Even called a patch, the binaries are much different from the official 2017 version. Look at the file sizes

Eh? I am not seeing any massive difference in size there. Probably just the differences due to better/worse optimization of different gcc versions!

Running opcode AAAA will as you say do the same but call DrvIo() C function!

Running the opcode AAAC causes uQlx to break out of 68k emulation and call the C function DrvClose().