The Sinclair QL Forum

I just had a short check on it: The driver appears to do some interesting things: In windev_asm (INIT), it seems to copy itself from ROM into allocated RAM and patch the detected hardware addresses directly into the code. Not the most RAM-efficient method, but would make relocating the driver to som...

David,

this should all work from compiled S*Basic.

After all, the programs are simply reading from and writing to channels.

Tobias

What could be done is - if you are willing to free up and dedicate a base address register (instead of PC) in the QubIDE ROM to point to your selected I/O area. This would end up in a major rewrite of the driver, though. You´ll probably need to go that way, as absolute long addressing of I/O (the ot...

Technically, everything is possible on a QL ;) The question is: what is it good for? The QL's memory map is laid out in the expectation that each expansion board is allocated one (or more - but apart from very specific cards like the SuperGold Card, I don't know any that do) 16k address slots for RO...

RWAP wrote:Some of the disk interfaces also used #1 to output file error messages - the original MicroP did this, from memory

Which is actually a severe mis-use of QDOS. The Technical Guide explicitly says you cannot assume #1 to be open. You may do so for #0.

Tobias

The numbers mean (from top to bottom): Memory value (.L) that was written Memory Value read back Affected longword address I'm, however, a bit lost why some of your pictures show read and written value as the same. The addresses seem to be QL internal memory (lower 128k), though. So, you apparently ...

Note you need an ISA bus PC in order to run it.

Increasingly hard to find.

Tobias (happy owner of a QXL 1)

The main difference between a STOP in a compiled program and the same thing under the interpreter is that the former will hand all memory that belonged to the job back to QDOS for re-use, while the latter will not (as you don't terminate the SuperBASIC job, so all memory owned by your program will a...

If you could elaborate a bit on what that program actually does, (like "allocate memory using ALCHP", working with PE, Menue Extensions, whatever) we could maybe help a bit better. Just from a guts feeling, I would vote for the timers as a culprit.

Tobias

pjw wrote: I would have noticed. Perhaps there is a specific version, or software configuration (eg TK2 + Turbo) that behaves in that way? Or perhaps another toolkit containing ALCHP thats overwriting TK2?

Now that you object, I'm not so sure anymore. Was it maybe a re-directed RESPR that did that?

Tobias