The Sinclair QL Forum

Thanks to Bob Spelten, an update of the BMP graphics converter is now available from the Graphics page on my website.

Version 1.04 fixes a problem with conversion of Mode 33 images on Q68 (and probably Q40/Q60 too), which could result in incorrect colour conversion due to incorrect interpretation of the I bit.. The Files menu could go wrong when there was only one executable or relocatable file in a directory in the previous version. And the default pixel sizes of the Mode/Size menu defaults to 0 for X and Y, which could cause problems if not manually changed, so now defaults to 512x256.

Download the v1.04 update from http://www.dilwyn.me.uk/graphics/index.html

Hi,

When executing the BMP viewer from command line, the manual and updates are suggesting that I can use:

EX BMP104_OBJ;'%U%\nasa05_pic'

to view a PIC file unscaled

If I use:

EX BMP104_OBJ;"\win1_nasa05_pic'

the program asks for scaling, is there a command line option for Scaling to be enabled?

The Copyright message says v1.03

hello
i get this on QPC2 , sQLux , Qemulator Continue works

Greetings from Switzerland
Markus

desin wrote: ↑Tue Apr 25, 2023 10:31 am hello
i get this "PEEK$ Error" on QPC2 , sQLux , Qemulator
BMP104.png

Continue works

Greetings from Switzerland
Markus

This is most likely a Turbo Toolkit error.
The PEEK$ command in Turbo has a different syntax from the SMSQ version.
On QPC2 or any SMSQ/E system you need the the correct version of TBTK (Turbo_sms).
https://dilwyn.qlforum.co.uk/turbo/index.html

BSJR

Derek_Stewart wrote: ↑Tue Apr 25, 2023 9:17 am Hi,

When executing the BMP viewer from command line, the manual and updates are suggesting that I can use:

EX BMP104_OBJ;'%U%\nasa05_pic'
to view a PIC file unscaled

If I use:
EX BMP104_OBJ;"\win1_nasa05_pic'
the program asks for scaling, is there a command line option for Scaling to be enabled?

The Copyright message says v1.03

The default is to ask for Scaling on the first image, then all selected files will be Scaled.
The "%U%" flag will disable Scaling and skip the Scaling question.
There is no option to automatically Scale everything.
When running BMP in mode 4, Scaling will produce a "not implemented" mesage and continue without Scaling.
When Scaling runs into problems, because of memory or device access errors, Scaling is switched off for the current image and the rest of the selected files.

BSJR

BSJR wrote: ↑Tue Apr 25, 2023 11:49 am

desin wrote: ↑Tue Apr 25, 2023 10:31 am hello
i get this "PEEK$ Error" on QPC2 , sQLux , Qemulator
BMP104.png

Continue works

Greetings from Switzerland
Markus

This is most likely a Turbo Toolkit error.
The PEEK$ command in Turbo has a different syntax from the SMSQ version.
On QPC2 or any SMSQ/E system you need the the correct version of TBTK (Turbo_sms).
https://dilwyn.qlforum.co.uk/turbo/index.html

BSJR

Hi Bob,

BMP works great with SMSQmulator, QPC2, Q68 running SMSQ/E 3.38, which has Turbo_SMS_Code (v3.44)

But with sQLux running Minerva v1.98 and Turbo_TK_Code (v3.44), gives the same error as above.

Derek_Stewart wrote: ↑Tue Apr 25, 2023 3:23 pm
Hi Bob,

BMP works great with SMSQmulator, QPC2, Q68 running SMSQ/E 3.38, which has Turbo_SMS_Code (v3.44)

But with sQLux running Minerva v1.98 and Turbo_TK_Code (v3.44), gives the same error as above.

Thanks Derek for pointing this out.

So far all the BMP updates have been done under SMSQ/E and this PEEK$ is used only once to establish if the program is compiled or running in SBasic for testing.
I never tested it with QDOS or Minerva where this PEEK$ poses a problem.
For now your only option is to execute BMP under SMSQ/E.

The good news is that the soon to be released update v1.05 will have this problem fixed.

BSJR

Hi Bob,

The BMP documentation says nothing about Turo Toolkit.

I would mainly use SMSQ/E, on SMSQmulator, Q68.

I have added the BMP options to Fileinfo2, to view PIC, QL SCR files and converting BMP files.

I must say the software is really good and a nice addition my systems.

I will add it into the software distributed with the Q68.

BSJR wrote: ↑Wed Apr 26, 2023 3:39 pmFor now your only option is to execute BMP under SMSQ/E.

If just PEEK$ ist used from Turbo_TK, why not ectract this with DEA or IDIS SE and link it to the compiled code?

Hi,

I think that it is more likely to be the SMSQ/E PEEK$ and not the Turbo Tookit version.

As the only failure I have with the software is with QDOS, which does not have PEEK$ available and Turbo Toolkit does seem to help.

So alway use SMSQ/E...