The Sinclair QL Forum

Its vital that systems work the same way across the board so pleeease fix if needed and possible!

sQLux doesnt currently seem to suffer!

It is unusual that sQLux is faster than the real iron for the 1st picture (1.88 vs 2.16) but slower for the 12th picture (13.12 vs 12.7). sQLux makes no attempt at accurately emulating CPU speed. @Exile did a good job of using number of instructions emulated hueristic to give you approx speed. But ...

go_key moveq #io.fbyte,d0 trap #3 addq.l #-err.nc,d0 check if timed out beq.s set_mde1 yes, just use what we started with addq.b #8,d1 f5 key = $f8 add.b d1,d3 check if {ctrl+}{shift+}f1-f4 (d3.lsb = $10) bcc.s read_key not f1-f4, read again roxl.b #5,d3 set quick reset bit and dual to extend ror.b...

mk79 wrote:Just tried it on an SGC QL, "CALL 390,$00200004" works as expected, giving me 2MB.

Thanks, must be an unintended side effect somewhere in uQLx code (this has never worked in original code due to missing brackets)

If I set bit 2 Minerva is ignoring the ram limit set, and going ahead and detecting ram. Which means its then putting ramtop the wrong side of the extended screen in uQlx/sQLux! I haven't tried it, but from the code if you set bit 2 the jump to res_a5 will be taken an a5 used as limit (which is der...

mk79 wrote:No, why? Comment and code agree here.

If I set bit 2 Minerva is ignoring the ram limit set, and going ahead and detecting ram. Which means its then putting ramtop the wrong side of the extended screen in uQlx/sQLux!

If I leave bit 2 clear it works as though RAM limit is used!

* The value in d1.l is used to decide what sort of restart is required: * bit(s) value meaning * 0 0 do the full memory test * 1 skip the memory test for a quick reset * 1 0 scan rom slots * 1 skip the rom slots, unexpand the m/c * 2 0 normal establishment of memory size * 1 take the upper memory l...

after 8 years i think it's not a problem bringing this thread to live back again... xD i'm actually trying to run QL emulation on mame/mess - it seems to run close to fine from what i expected in the mame(mess file manager, we find magtape1 (magt1), magtape2 (magt2), and cartridge (cart) - i though...

Is this a QL, TK2, or a Q-Emulator issue? I dont have any real QL hardware to test on, so could someone please oblige and tell me where the problem is? As far as I can see this is a QemuLator bug that only happens when the drive is mapped to a Windows directory and the file is one with a QemuLator ...

Perhaps I should abandon my SGC completely ? But it is usually usable with code that does not use the bad byte area in Ram !

Isnt the SGC ZIP ram? Thats easy to replace, maybe ask a hardware guru like Derek to look at it?

Definitely at current prices worth repairing them!