The Sinclair QL Forum

It's most probably not possible to port a C++ Compiler, because even for standard headers and libraries the pathname length from QDOS (36 chars [device name is not counted :‑)] is too low, to compile a C++ Compiler A compiler can be cross-compiled on a system without that limitation. I think there ...

I wonder if someone's written a stand-alone program to generate a WIN image file, rather than having to require people to get an emulator working. That would be far easier to explain too. I don't know. Maybe as part of the QXL software? Since empty images are short when zipped, the easiest way is p...

P.P.S. The manual should be explicit that if you boot from another device then you HAVE to use WIN_USE every time, not often, always. The manual can not state that in general, as the behaviour depends on the the other device. Depending on the timing of the "MDV renaming magic" of the othe...

QDOS-gcc is somewhat different. I tend to read everywhere "it's miles better than C68". Well, in my opinion and experience, it isn't. It might be (significantly) faster for some benchmarks, but in reality it isn't really worth the hassle. For example, the sound player for QIMSI is too slo...

My workflow does often include non-QDOS file systems as well. But I only keep my source files there and edit them using modern IDEs. Compilation and linking is done natively [...] But if you compile natively, your IDE won't be able to parse the compiler output for errors and jump there. Or did you ...

You normally shouldn't need to reboot a multitasking system. Of course. I was just referring to the task of getting the file length for setting an executable's dataspace once, on a 128K machine, if the file is too large to coexist with a Toolkit . (TK2 could almost be considered part of the OS...)

lliont wrote: ↑Thu Dec 07, 2023 5:42 pm I got a true dual bus internal video ram that fpga accesses at 16bit words totally independent of the cpu that can simultaneously read and write at it.

So you are using FPGA block RAM for the whole video memory? How large is it?

lliont wrote: ↑Thu Dec 07, 2023 4:40 pm Bandwidth is not a problem for the QL up-scaled to 1024x768 resolution.

Of course. I did not mean that, but actual 1024x768 @ 4 bpp.
Are you using FPGA block RAM, async. SRAM oder SDRAM?

I may be wrong, but I think Leon is describing the VGA output res/timing as opposed to the actual QL screen res as seen from software... It must be that way. On the screenshots, I see at least 4 bpp. And 1024 x 768 @ 4 bpp means 384 KB of screen memory. Filling that would crawl with a 68008 - even ...

On an unexpanded (no Toolkits) QL there is (if I remember correctly) no way to determine the length of a file :‑( Isn't this a pretty academic problem? The reason for the lost dataspace info was that the file came from a PC, where you easily see the length. And in the worst case of no PC involved a...