The Sinclair QL Forum

Something I'm still trying to get my head around is the reason behind why, if I compile as file type 2 so that I can use RESPR/Lbytes/Call the QL crashes but if I compile as file type 1 and EXEC or EXEC_w it works fine Is there a particular reason for this please? Many thanks The reason is that whe...

Inside of timerTick, you cannot use a6 to update your variable (it has another value in the polling interrupt routine than in your code and will actually point to the system variables). Instead, you get a pointer in a3, not in a6, to 8 bytes before timerLinkage(a6) - That's because the polling routi...

The QL's RTC is only progressing in 1s intervals. You could use it, but it would make your program crawl The polling interrupt is really the only way you get a suitably fast tick rate.

If you pack your sources and put them here I could have a look at it.

The dev_ device us built in SMSQ/E. There is a loadable device driver for the standard QL, that you probably haven't loaded. You'll find that in the Toolkit section on Dilwyyn's site.

That might have been my fault, sorry. Try adding an "OFFSET 0" after "SECTION data"

Unless there's here's little nasty gremlins changing the wiring every now and then.

I think "terminal program" is a good keyword here. And preferably something that uses checksumed blocks for data transfer, like X-Modem or Kermit. Standard QL serial comms is so unreliable that without that you'll likely become desparate.

Speaking of keyboard, what keyboard settings are supported with the latest release? Where to set the keyboard? In sqlux.ini? Documentation? Remember Tim's manual initially stated: sQLux uses the keyboard mapping from SDL2, which is a US Keyboard. Even with international ROMS, the keyboard will stil...

Well I've implemented all of the suggestions/recommendations and got it working great, many thanks But now I've started to add more sprite data it now won't assemble as it says the LEA is "value out of range" (with more failing as I add more sprite data & workspace) I'm assuming this ...

Or is the dataspace strictly required before loading? Of course it is. The first thing EX does is allocate memory in one piece for the program plus the data space (done by MT.CREAT, which wants both the program size and the needed data space). Then load the binary into the beginning of the allocate...