The Sinclair QL Forum

I used the public source smsq/e version and emulated the aurora registers and set the same vram addresses, I managed to make the smsq/e recognize my card as a gold card with aurora, machine=11. The standard modes worked using the aurora vram space. The higher resolution 512x384 didn't seem to ...

I used the public source smsq/e version and emulated the aurora registers and set the same vram addresses, I managed to make the smsq/e recognize my card as a gold card with aurora, machine=11. The standard modes worked using the aurora vram space. The higher resolution 512x384 didn't seem to work ...

I added 2 new screen resolutions
-512x384 256 colours
-1024x384 16 colours
I tried aurora emulation for smsq/e, it works but doesn't support the higher than 512x256 resolutions, no good so I quit trying.
It currently works with a pretty standard version of gold card smsq/e with the standard ...

I think the target was something like a SGC, like it was for the original Aurora. In that case the bandwidth is far lower, not evenb 2Mbytes/sev as it emulates the original 68008, and needs in theory up to 256k of screen RAM, but these days not nearlčy all Aurora resolutions make sense, so 192k is ...

The first 16550 version with working FIFO came in 1987.

I have tubes of later 16550-compatible ICs. I have never seen a QL driver to support them though - just the older and less useful 6850 that has an incompatible register structure.


The problem with even the original 16450 descendants ...

A reel of 500x RP2350B is 80 cents per piece and is available now. This chip is "5v tolerant*" and has enough GPIO to replace any of the QL chips
...
* 5V tolerant if it is powered up before any signals >4V appear n any GPIO pin.


This should be fairly easy to mitigate with a few protection ...

If I recall correctly, the original 68k has 2 16-bit ALUs, one for data and the other for address calculations. It was not before the 68020 was introduced that this was expanded to 32 bits, and then it's core was re-used as the CPU32 which is essentially a 68020 without cache. It has benefitted in ...

I would expect that CPMulator uses the ROM as either part of the code and/or look-up tables for Z80 emulation because the ROM slot access is about 1.8x faster than RAM where the code is normally loaded, which would be a big issue to get the emulation fast enough...
I am not surprised it is not made ...

Hello everyone,
Took some time to collect my thoughts - my journey to the meeting started very early Thursday, drove from my home to Nurmberg, then to Muhlheim and visited some friends that I have not seen for ages, slept over in Muhlheim then got to Dormagen on Friday afternoon.
And from then on ...

An simple internal DIN41612 to ROMport connector board might be useful :idea:

You may have noticed 2 x 2 extra pins in addition to the QL ROM port (the smaller ones near to the edge).
One of them is leading QLNET and one is a "detection" pin.
The other two could be used with such a connector ...