The Sinclair QL Forum

So people paying attention would have noticed that under Minerva sQLux did have some screen corruption (it only exists on screen not in memory)

I believe with my latest set of changes this is now all fixed. I think now all writes from the VM are now arriving correctly on screen. And even better it does not seem to have affected performance negatively on slow devices like Pi0.

Interesting question is on a BBQL are the pixels always square? (also this goes for the clones).

Hi,

I updated the Github files for sQLux and compiled the emulator easily first time.

I like the move to cmake and the updated commad line options.

Nice work.

XorA wrote:Interesting question is on a BBQL are the pixels always square? (also this goes for the clones).

No they are not. In 512x256 QL MODE 4, I double horizontally and triple vertically for VESA standard 1024x768 on 4:3 monitor.
That roughly provides the QL aspect ratio seen on CRT historically.

Peter wrote:

XorA wrote:Interesting question is on a BBQL are the pixels always square? (also this goes for the clones).

No they are not. In 512x256 QL MODE 4, I double horizontally and triple vertically for VESA standard 1024x768 on 4:3 monitor.
That roughly provides the QL aspect ratio seen on CRT historically.

Thanks, Ill give that a go in the GFX options and see how it looks. (Ill leave it as an option)

Hi,

I am using sQLux *** QL Emulator v0.99-rc1 *** release 2021-04-14

I am not sure about some of the command line options:

-v num : set verbosity

What are the levels of verbosity?

-d 'boot_dev' : device where BOOT should be read eg. 'mdv1'

I can not find any information in the documentation about the -d option.

I would appreciate help.

Derek_Stewart wrote:Hi,

I am using sQLux *** QL Emulator v0.99-rc1 *** release 2021-04-14

I am not sure about some of the command line options:

-v num : set verbosity
What are the levels of verbosity?

I have not changed this since uqlx, and I actually have no idea.

-d 'boot_dev' : device where BOOT should be read eg. 'mdv1'

I can not find any information in the documentation about the -d option.

I would appreciate help.

So that basically edits the rom to change the device it looks for BOOT file.

-d WIN1 would change it to WIN1_BOOT
-d FLP1 would change it to FLP1_BOOT

etc

For those awkward cases where BOOT files hardcode their device in them.

Hi,

Thankyou for the information.

I wanted a quiet option when the emulator starts up. Hence -v 0

The reason for asking, is that I sometimes write Superbasic in vim or nano, then load the programme into sQLux, to run.

I hope that I vould write a BASH script to exrcute sQLux with the comand line pointing to the saved Superbasic programme, with the the -b option.

But the Superbasic programme has to be saved in a specific place defined in the config file foe MDV1/FLP1/WIN1 etc...

Since I can not define the QDOS drive folder in the command line, the answer maybe to get the BASH script to write a custom config file, defining MDV1 and specfying the custom config file with the -f in the command line.

This is an attempt at a development system, like Swift on the BBC...

Since I can not define the QDOS drive folder in the command line, the answer maybe to get the BASH script to write a custom config file, defining MDV1 and specfying the custom config file with the -f in the command line.

Id have to have a think on that, but should be relatively easy to add, fancy adding an issue on github so I dont forget?

XorA wrote:

Since I can not define the QDOS drive folder in the command line, the answer maybe to get the BASH script to write a custom config file, defining MDV1 and specfying the custom config file with the -f in the command line.

Id have to have a think on that, but should be relatively easy to add, fancy adding an issue on github so I dont forget?

I have added a Github Issue.

Two things that I have done is to have a couple of pre-built configuration files. When I run one of the shell scripts, it just copies one of the pre-defined config files to the main config file and then fires up sQLux. I think have a desktop link to the script so I have an item on my desktop that I just click on.

There is another way of doing this by using Zenity (formerly I used Xdialog but I could not get it to work on a newer version of Lubuntu). Zenity gives you a little GUI popup so you can select which config file to run. So one desktop item calls up a bash/zenity script that provides a menu.

I can't find my zenity examples, but if someone is interested, I can dig them up.

Tim