### [Ql-Users] Assembly eComic - Issue 11 now available.

```Only 4 months from the last issue and we already have another! In this
issue of the somewhat irregular eMagazine, we have:

Beginners' Corner:

where we discuss simply screen and file handling. Experienced readers
should skip over the excruciating detail that I go into to help beginners.

Sudoku Solver:

yes indeed, a Sudoku solver for 9 by 9 grids. I say "solver" but it's
really a brute force algorithm using recursion and backtracking to guess
which numbers will eventually provide a solution. (Or not!) There's a
demonstration puzzle and a few examples to load and solve. You can make
your own puzzles up and load them too -- the code will let you know if a
puzzle cannot be solved.

Multiplication:

a small but perfectly formed chunk of assembly code to multiply two 32
bit unsigned values to give a 64 bit product. Did you notice unsigned
there? Yes, me too. I convinced myself to add in a bit of extra code and
make it multiply signed numbers as well.

We also have more News and Quickies again in this issue.

As ever, you do not need the source code, that's GitHub's processing of
a release, just grab the PDF from the asset list at the link below.
Click the arrow to open the list if it's not already open.

https://github.com/NormanDunbar/QLAssemblyLanguageMagazine/releases/tag/Issue_11

Cheers,
Norm.

--
Norman Dunbar
Dunbar IT Consultants Ltd

27a Lidget Hill
Pudsey
West Yorkshire
United Kingdom
LS28 7LG

Company Number: 05132767
___
QL-Users Mailing List

```

### Re: [Ql-Users] SMSQE instr_case QLIB

```
On 08/04/2022 14:56, Tobias Fröschle via Ql-Users wrote:

The main reason, I believe, is that INSTR_CASE is a global setting and so
shouldnt be set by a program, but only by the user in the main console

That's actually not the problem: INSTR_CASE seems to work "local" to each
instance of the SBASIC interpreter (I just checked).
Youre right, of course. I dont know where I got that idea. I thought
Id read it somewhere long ago. The stupid thing is that I did some
half-hearted tests myself before I posted but my results were
inconclusive, so I ignored them. Also there is a lack of detail in the
documentation (eg the online Reference Manual) It seems to me that
this is important information, especially since (perhaps) at some time
this may have been documented as a global setting.

Turbo happily compiles programs that contain INSTR_CASE statements,  but does
seem to be using its own INSTR implementation (that will, obviously, not switch
according to INSTR_CASE). So, compiled programs simply don't react on the
INSTR_CASE settings. QLiberator does exactly the same.

Yes, it doesnt work in Turbo nor in Qlib, as I stated. In up to date
versions of Qlib you also get a warning message. It is possible that
it might not be too hard to fix, if anyone wants to have a go. But any
compiled program using it would still only work under SMSQ/E. INSTR is
part of the S*BASIC language and couldnt be altered in Qdos without
creating a new ROM. A workaround might be to add internal INSTR code
to Qlib and Turbo, that is aware of the INSTR_CASE setting, but that
seems to me to be a lot of code and trouble for a rare and minor

Per
___
QL-Users Mailing List
```

### Re: [Ql-Users] SMSQE instr_case QLIB

```

>
> The main reason, I believe, is that INSTR_CASE is a global setting and so
> shouldnt be set by a program, but only by the user in the main console

That's actually not the problem: INSTR_CASE seems to work "local" to each
instance of the SBASIC interpreter (I just checked).

Turbo happily compiles programs that contain INSTR_CASE statements,  but does
seem to be using its own INSTR implementation (that will, obviously, not switch
according to INSTR_CASE). So, compiled programs simply don't react on the
INSTR_CASE settings. QLiberator does exactly the same.

___
QL-Users Mailing List

```

### Re: [Ql-Users] SMSQE instr_case QLIB

```
On 08/04/2022 09:07, desin via Ql-Users wrote:

Hi all

how can we use instr_case in a Qliberated program ?

At present you cant. If you use the latest Qlib (V3.45) youll even get
a warning message. It wont work in Turbo either.

https://www.qlforum.co.uk/viewtopic.php?f=3=3166=instr_case=30)

The main reason, I believe, is that INSTR_CASE is a global setting and
so shouldnt be set by a program, but only by the user in the main console.

You could use a toolkit command instead, such as Knoware's INSTR%()
function in the Str3TK toolkit, which allows for both a case dependent
and case-agnostic INSTR. See www.Knoware.no/htm/toolkits.htm#strings.

100 CLEAR
110 a%= FOPEN ("con")
120 OUTL
130 OUTL  #a%,500,200,0,30
140 WINDOW#a%,500,200,0,30
150 CLS#a%
160 :
170 a\$ = "hello" : b\$ = "Hello": c\$ = "hELLO"
180 :
190 PRINT#a%
200 PRINT#a%,,"instr_case truth table "
210 PRINT#a%
220 :
230 INSTR_CASE 1
240 PRINT#a%,,"instr_case 1"
250 PRINT#a%
260 PRINT#a%,, a\$,a\$,a\$ INSTR a\$
270 PRINT#a%,, b\$,b\$,b\$ INSTR b\$
280 PRINT#a%,, a\$,b\$,a\$ INSTR b\$
290 PRINT#a%,, b\$,a\$,b\$ INSTR a\$
300 PRINT#a%,, b\$,c\$,b\$ INSTR c\$
310 PRINT#a%,, c\$,a\$,c\$ INSTR a\$
320 PAUSE#a%
330 CLS#a%
340 CLOSE#a%

Greetings from Switzerland

Markus

Per
___
QL-Users Mailing List
```

### [Ql-Users] SMSQE instr_case QLIB

```

Hi all

how can we use instr_case in a Qliberated program ?

100 CLEAR
110 a%= FOPEN ("con")
120 OUTL
130 OUTL  #a%,500,200,0,30
140 WINDOW#a%,500,200,0,30
150 CLS#a%
160 :
170 a\$ = "hello" : b\$ = "Hello": c\$ = "hELLO"
180 :
190 PRINT#a%
200 PRINT#a%,,"instr_case truth table "
210 PRINT#a%
220 :
230 INSTR_CASE 1
240 PRINT#a%,,"instr_case 1"
250 PRINT#a%
260 PRINT#a%,, a\$,a\$,a\$ INSTR a\$
270 PRINT#a%,, b\$,b\$,b\$ INSTR b\$
280 PRINT#a%,, a\$,b\$,a\$ INSTR b\$
290 PRINT#a%,, b\$,a\$,b\$ INSTR a\$
300 PRINT#a%,, b\$,c\$,b\$ INSTR c\$
310 PRINT#a%,, c\$,a\$,c\$ INSTR a\$
320 PAUSE#a%
330 CLS#a%
340 CLOSE#a%

Greetings from Switzerland

Markus
___
QL-Users Mailing List

```

### Re: [Ql-Users] Stuart Honeyball

```
Op 19/03/2022 om 18:14 schreef Norman Dunbar via Ql-Users:

One
night in the local pub he redrew the
entire Spectrum Issue 1 PCB from
memory on a napkin, while quite drunk.
I was stupidly impressed by that.

I'd have been seriously impressed by that!

Cheers,
Norm.

Sorry

François Van Emelen

___
QL-Users Mailing List
```

### Re: [Ql-Users] Stuart Honeyball

```> One
> night in the local pub he redrew the
> entire Spectrum Issue 1 PCB from
> memory on a napkin, while quite drunk.

> I was stupidly impressed by that.

I'd have been seriously impressed by that!

Cheers,
Norm.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
QL-Users Mailing List

```

### Re: [Ql-Users] Stuart Honeyball

```I remember him coming to the Irish QL shows I ran in the late 90s.. One
night in the local pub he redrew the entire Spectrum Issue 1 PCB from
memory on a napkin, while quite drunk.

I was stupidly impressed by that.

Miss him dearly.

Darren Branagh

Sent from My iPhone 13 Pro.

On Thu, 17 Mar 2022, 12:44 Marcel Kilgus via Ql-Users, <
ql-users@lists.q-v-d.com> wrote:

> Darren Branagh via Ql-Users wrote:
> > Yes, Stuart passed away several years ago... I posted here the day it
> > happened.
>
> Yes, Ben has resurrected an old thread on QL forum yesterday and added
> his anecdote of getting taught electronics by Stuart, but it's been
> almost 4 years to the day since it happened.
>
> Marcel
>
> ___
> QL-Users Mailing List
>
___
QL-Users Mailing List

```

### Re: [Ql-Users] Stuart Honeyball

```Darren Branagh via Ql-Users wrote:
> Yes, Stuart passed away several years ago... I posted here the day it
> happened.

Yes, Ben has resurrected an old thread on QL forum yesterday and added
his anecdote of getting taught electronics by Stuart, but it's been
almost 4 years to the day since it happened.

Marcel

___
QL-Users Mailing List

```

### Re: [Ql-Users] Stuart Honeyball

```Yes, Stuart passed away several years ago... I posted here the day it
happened.

Darren Branagh

Sent from My Android Phone.

On Thu, 17 Mar 2022, 10:19 RWAP Software via Ql-Users, <
ql-users@lists.q-v-d.com> wrote:

> François,
>
> Correction - I thought he passed away in March 2018 ?
>
> In any case, he is still sorely missed.
>
> Rich Mellor
> RWAP Software
> www.rwapsoftware.co.uk
> www.sellmyretro.com
>
> On 2022-03-17 10:00, François Van Emelen via Ql-Users wrote:
> >  Stuart Honeyball passed away.
> >
> >
> >  Thoughts are with his family and friends.
> >
> > François Van Emelen
> >
> >
> > ___
> > QL-Users Mailing List
> ___
> QL-Users Mailing List
___
QL-Users Mailing List
```

### Re: [Ql-Users] Stuart Honeyball

```
François,

Correction - I thought he passed away in March 2018 ?

In any case, he is still sorely missed.

Rich Mellor
RWAP Software
www.rwapsoftware.co.uk
www.sellmyretro.com

On 2022-03-17 10:00, François Van Emelen via Ql-Users wrote:

Stuart Honeyball passed away.

Thoughts are with his family and friends.

François Van Emelen

___
QL-Users Mailing List

___
QL-Users Mailing List
```

### Re: [Ql-Users] Stuart Honeyball

```
That is indeed sad news - he was one of the great innovators for the QL.

Rich Mellor RWAP Software www.rwapsoftware.co.uk www.sellmyretro.com

On 2022-03-17 10:00, François Van Emelen via Ql-Users wrote:

Stuart Honeyball passed away.

Thoughts are with his family and friends.

François Van Emelen

___
QL-Users Mailing List

___
QL-Users Mailing List
```

### [Ql-Users] Stuart Honeyball

```
Stuart Honeyball passed away.

Thoughts are with his family and friends.

François Van Emelen

___
QL-Users Mailing List
```

### Re: [Ql-Users] QBOX

```
Hi Fabrizio,

It looks like opening a TCP channel for listening doesn't work in these
cases. But which port are you using for listening? Windows allows
privileged ports (below 1024) but Linux doesn't. I don't know about
MacOS but I believe it's more Unix-like and might prevent opening
privileged ports for user space programs.

I'm just following the QDOS TCP specs here so I have no idea what could
otherwise be the cause...

Jan

On 10-03-2022 21:30, Fabrizio Diversi wrote:

Hi,

This is true for QPC2 under MS win10 but not for my main QPC2 system
under MacBook M1 using Crossover where, when Qbox start, I got an
error QSPILTCP: bind socket failed, retrying in 60 msec.

Same using SMSQmulator under MacBook M1(Monterey): QSPILTCP: cannot
set TCP_NODELAY option: not implemented - io.open in sp.wtcall
returned error: not implemented

Quite obvious this is an issue linked with Macbook and Crossover
emulation, not a big issue for me as the Qbox server is on Qpc2 hosted
on Win10 and Qterm client work fine under MacBook/Crossover/Qpc2

Thank you again for your support

fabrizio

--
Jan Bredenbeek | Hilversum, NL | j...@bredenbeek.net

___
QL-Users Mailing List
```

### Re: [Ql-Users] QBOX

```
Hi,

This is true for QPC2 under MS win10 but not for my main QPC2 system
under MacBook M1 using Crossover where, when Qbox start, I got an error
QSPILTCP: bind socket failed, retrying in 60 msec.

Same using SMSQmulator under MacBook M1(Monterey): QSPILTCP: cannot set
TCP_NODELAY option: not implemented - io.open in sp.wtcall returned
error: not implemented

Quite obvious this is an issue linked with Macbook and Crossover
emulation, not a big issue for me as the Qbox server is on Qpc2 hosted
on Win10 and Qterm client work fine under MacBook/Crossover/Qpc2

Thank you again for your support

fabrizio

On 09/03/22 21:17, Jan Bredenbeek wrote:

Hi Fabrizio,

Just start QBOX with the -T option, i.e. EX QBOX;'-T'. This bypasses
the clock check. Then log on and log off, this will correct the time
stamp on the USERS_BBS file. After this, you won't need the -T option
if your clock is set correctly (QBOX only complains when the time
stamp of USERS_BBS is in the future or more than 1 year in the past :)).

Jan

On 09-03-2022 15:13, Fabrizio Diversi via Ql-Users wrote:

Hi,
sorry if this topic was discussed elsewhere, but, after I updated my
Qbox Server system (Raspberry/SMSQmulator) with latest programs/os
etc (SMSQ/E 3.38), Qbox refuse to start with the error "QBOX: wrong
Clock setting" and cannot find why. this happen..either I cannot
find any document that explain QBOX errors messages meaning

Any help will be appreciated :)

Thanks
Fabrizio
___
QL-Users Mailing List

___
QL-Users Mailing List
```

### Re: [Ql-Users] QBOX

```
Hi Fabrizio,

Just start QBOX with the -T option, i.e. EX QBOX;'-T'. This bypasses the
clock check. Then log on and log off, this will correct the time stamp
on the USERS_BBS file. After this, you won't need the -T option if your
clock is set correctly (QBOX only complains when the time stamp of
USERS_BBS is in the future or more than 1 year in the past :)).

Jan

On 09-03-2022 15:13, Fabrizio Diversi via Ql-Users wrote:

Hi,
sorry if this topic was discussed elsewhere, but, after I updated my
Qbox Server system (Raspberry/SMSQmulator) with latest programs/os etc
(SMSQ/E 3.38), Qbox refuse to start with the error "QBOX: wrong Clock
setting" and cannot find why. this happen..either I cannot find
any document that explain QBOX errors messages meaning

Any help will be appreciated :)

Thanks
Fabrizio
___
QL-Users Mailing List

--
Jan Bredenbeek | Hilversum, NL | j...@bredenbeek.net

___
QL-Users Mailing List

```

### Re: [Ql-Users] QBOX

```
Hi Fabrizio,

Just start QBOX with the -T option, i.e. EX QBOX;'-T'. This bypasses the
clock check. Then log on and log off, this will correct the time stamp
on the USERS_BBS file. After this, you won't need the -T option if your
clock is set correctly (QBOX only complains when the time stamp of
USERS_BBS is in the future or more than 1 year in the past :)).

Jan

On 09-03-2022 15:13, Fabrizio Diversi via Ql-Users wrote:

Hi,
sorry if this topic was discussed elsewhere, but, after I updated my
Qbox Server system (Raspberry/SMSQmulator) with latest programs/os etc
(SMSQ/E 3.38), Qbox refuse to start with the error "QBOX: wrong Clock
setting" and cannot find why. this happen..either I cannot find
any document that explain QBOX errors messages meaning

Any help will be appreciated :)

Thanks
Fabrizio
___
QL-Users Mailing List

--
Jan Bredenbeek | Hilversum, NL | j...@bredenbeek.net

___
QL-Users Mailing List

```

### Re: [Ql-Users] QBOX

```
Hi Fabrizio,

Just start QBOX with the -T option, i.e. EX QBOX;'-T'. This bypasses the
clock check. Then log on and log off, this will correct the time stamp
on the USERS_BBS file. After this, you won't need the -T option if your
clock is set correctly (QBOX only complains when the time stamp of
USERS_BBS is in the future or more than 1 year in the past :)).

Jan

On 09-03-2022 15:13, Fabrizio Diversi via Ql-Users wrote:

Hi,
sorry if this topic was discussed elsewhere, but, after I updated my
Qbox Server system (Raspberry/SMSQmulator) with latest programs/os etc
(SMSQ/E 3.38), Qbox refuse to start with the error "QBOX: wrong Clock
setting" and cannot find why. this happen..either I cannot find
any document that explain QBOX errors messages meaning

Any help will be appreciated :)

Thanks
Fabrizio
___
QL-Users Mailing List

--
Jan Bredenbeek | Hilversum, NL | j...@bredenbeek.net

___
QL-Users Mailing List

```

### Re: [Ql-Users] QBOX

```
Hi Fabrizio,

Just start QBOX with the -T option, i.e. EX QBOX;'-T'. This bypasses the
clock check. Then log on and log off, this will correct the time stamp
on the USERS_BBS file. After this, you won't need the -T option if your
clock is set correctly (QBOX only complains when the time stamp of
USERS_BBS is in the future or more than 1 year in the past :)).

Jan

On 09-03-2022 15:13, Fabrizio Diversi via Ql-Users wrote:

Hi,
sorry if this topic was discussed elsewhere, but, after I updated my
Qbox Server system (Raspberry/SMSQmulator) with latest programs/os etc
(SMSQ/E 3.38), Qbox refuse to start with the error "QBOX: wrong Clock
setting" and cannot find why. this happen..either I cannot find
any document that explain QBOX errors messages meaning

Any help will be appreciated :)

Thanks
Fabrizio
___
QL-Users Mailing List

--
Jan Bredenbeek | Hilversum, NL | j...@bredenbeek.net

___
QL-Users Mailing List

```

### [Ql-Users] QBOX

```
Hi,
sorry if this topic was discussed elsewhere, but, after I updated my
Qbox Server system (Raspberry/SMSQmulator) with latest programs/os etc
(SMSQ/E 3.38), Qbox refuse to start with the error "QBOX: wrong Clock
setting" and cannot find why. this happen..either I cannot find any
document that explain QBOX errors messages meaning

Any help will be appreciated :)

Thanks
Fabrizio
___
QL-Users Mailing List

```

### Re: [Ql-Users] Knoware update

```
Op 31/01/2022 om 18:33 schreef pjwitte via Ql-Users:

A small update to Knoware.no

For details go to
https://qlforum.co.uk/viewtopic.php?t=2839=45592#p45592 or more
briefly: www.knoware.no/htm/changes.htm

Per
___
QL-Users Mailing List

Thank you

François Van Emelen

___
QL-Users Mailing List
```

### Re: [Ql-Users] QDOS SMSQE Guide 4.7

```
Op 31/01/2022 om 16:50 schreef Wolfgang Lenerz via Ql-Users:

Hi all,

I have release v. 4.7 of the SMSQE / Qdos manual - it now contains
many of the SBasic (not SuperBasic!) variables, as announced some time
ago.

As usual, you can find it at wlenerz.com/qlstuff

Have Fun!

Wolfgang
___
QL-Users Mailing List

Thank you

François Van Emelen

___
QL-Users Mailing List
```

### [Ql-Users] Knoware update

```
A small update to Knoware.no

For details go to
https://qlforum.co.uk/viewtopic.php?t=2839=45592#p45592 or more
briefly: www.knoware.no/htm/changes.htm

Per
___
QL-Users Mailing List

```

### [Ql-Users] QDOS SMSQE Guide 4.7

```
Hi all,

I have release v. 4.7 of the SMSQE / Qdos manual - it now contains many
of the SBasic (not SuperBasic!) variables, as announced some time ago.

As usual, you can find it at wlenerz.com/qlstuff

Have Fun!

Wolfgang
___
QL-Users Mailing List

```

### [Ql-Users] Assembly Programming Issue 10 now on release!

```A new year, a new issue. Issue 10 of the somewhat irregular eMagazine on
Assembly Programming is now available.

https://github.com/NormanDunbar/QLAssemblyLanguageMagazine/releases/latest

Enjoy!

Cheers,
Norm.

--
Norman Dunbar
Dunbar IT Consultants Ltd

27a Lidget Hill
Pudsey
West Yorkshire
United Kingdom
LS28 7LG

Company Number: 05132767
___
QL-Users Mailing List

```

### Re: [Ql-Users] Illegal (NULL) Instruction \$4b00 at \$105886

```Juraj Lutter via Ql-Users wrote:
> is \$subject a known behavior, please?

No.

Marcel

___
QL-Users Mailing List

```

### Re: [Ql-Users] QL/E v3.21 is out now!

```
Hi Urs,

sounds great as usual!

Wolfgang

On 31/12/2021 13:21, Urs Koenig (QL) via Ql-Users wrote:

﻿Hi QLers,

as the final of a bombatic 2 months firework which brought us new releases of
QPC2, SMSQmulator, SMSQ/E, QemuLator and sQLux, here's the Distribution which
include all free ones!

QL/E v3.21 (Codename "Circle of Life", 2021 edition) is out now!

see message footer.

I wish you all a healthy, prosperous and Happy New Year 2022!

Cheers,
Urs

QL forever!
http://www.sinclairql.net/ - Go and get THE DISTRIBUTION & QL/E!
Sinclair, QL, ATARI, JAGUAR, NUON, APPLE, NeXT, MiST & much more...
Videos, pictures & information

Von meinem iPhone gesendet
___
QL-Users Mailing List

___
QL-Users Mailing List
```

### Re: [Ql-Users] QL/E v3.21 is out now!

``` Thank You Ever Ever So Much For the. New QLE Urs it is Very Very Very Very
GOOD!!! And a Happy New Year to All QL-Users Have a Good One All
the Best
Simon Foster
On Friday, 31 December 2021, 12:21:39 GMT, Urs Koenig (QL) via Ql-Users
wrote:

Hi QLers,

as the final of a bombatic 2 months firework which brought us new releases of
QPC2, SMSQmulator, SMSQ/E, QemuLator and sQLux, here's the Distribution which
include all free ones!

QL/E v3.21 (Codename "Circle of Life", 2021 edition) is out now!

see message footer.

I wish you all a healthy, prosperous and Happy New Year 2022!

Cheers,
Urs

QL forever!
http://www.sinclairql.net/ - Go and get THE DISTRIBUTION & QL/E!
Sinclair, QL, ATARI, JAGUAR, NUON, APPLE, NeXT, MiST & much more...
Videos, pictures & information

Von meinem iPhone gesendet
___
QL-Users Mailing List
___
QL-Users Mailing List
```

### [Ql-Users] QL/E v3.21 is out now!

```﻿Hi QLers,

as the final of a bombatic 2 months firework which brought us new releases of
QPC2, SMSQmulator, SMSQ/E, QemuLator and sQLux, here's the Distribution which
include all free ones!

QL/E v3.21 (Codename "Circle of Life", 2021 edition) is out now!

see message footer.

I wish you all a healthy, prosperous and Happy New Year 2022!

Cheers,
Urs

QL forever!
http://www.sinclairql.net/ - Go and get THE DISTRIBUTION & QL/E!
Sinclair, QL, ATARI, JAGUAR, NUON, APPLE, NeXT, MiST & much more...
Videos, pictures & information

Von meinem iPhone gesendet
___
QL-Users Mailing List
```

### [Ql-Users] Illegal (NULL) Instruction \$4b00 at \$105886

```Hi,

is \$subject a known behavior, please?

thanks
otis

—
Juraj Lutter
XMPP: juraj (at) lutter.sk
GSM: +421907986576

___
QL-Users Mailing List
```

### Re: [Ql-Users] SMSQmulator

```Wolf via Ql-Users wrote:
> I've re-re-upped the version for java 8...

re-thanks!
___
QL-Users Mailing List

```

### [Ql-Users] SMSQmulator

```
Hi,

I've re-re-upped the version for java 8...

Wolfgang
___
QL-Users Mailing List

```

### Re: [Ql-Users] SMSQmulator

```
Hi,

that file seems to have got lost in translation.

I've re-upped everything, it is now there.

Have fun!

Wolfgang

On 29/12/2021 11:14, Massimino Boccardi via Ql-Users wrote:

Hi.
I receive the following error :

Error setting QXL.WIN drives:
..\SMSQmulator.win cannot be found

I’m not able to found SMSQmulator.win on the zip …

Someone could help!?
Max
<>

Il giorno 26 dic 2021, alle ore 10:37, desin via Ql-Users
ha scritto:

﻿Am 26.12.21 um 10:29 schrieb Derek via Ql-Users:

Hi,
I use OpenJDK 11 or 8, version 11 is running on the Linux laptop.
I do not use Windows as I fo not want to pay for the licence. Linux does all I
require, without the constant attension to virus checkers.
I also do not want to buy nee hardware to run Windows 11, whi h maybe as bad as
Windows 10.

i'm using this

Markus
___
QL-Users Mailing List

___
QL-Users Mailing List

___
QL-Users Mailing List
```

### Re: [Ql-Users] SMSQmulator

```Hi.
I receive the following error :

Error setting QXL.WIN drives:
..\SMSQmulator.win cannot be found

I’m not able to found SMSQmulator.win on the zip …

Someone could help!?
Max
<>

> Il giorno 26 dic 2021, alle ore 10:37, desin via Ql-Users
>  ha scritto:
>
> ﻿Am 26.12.21 um 10:29 schrieb Derek via Ql-Users:
>> Hi,
>> I use OpenJDK 11 or 8, version 11 is running on the Linux laptop.
>> I do not use Windows as I fo not want to pay for the licence. Linux does all
>> I require, without the constant attension to virus checkers.
>> I also do not want to buy nee hardware to run Windows 11, whi h maybe as bad
>> as Windows 10.
>
> i'm using this
>
> Markus
> ___
> QL-Users Mailing List
___
QL-Users Mailing List
```

### Re: [Ql-Users] SMSQmulator

```
Am 26.12.21 um 10:29 schrieb Derek via Ql-Users:

Hi,

I use OpenJDK 11 or 8, version 11 is running on the Linux laptop.

I do not use Windows as I fo not want to pay for the licence. Linux does all I
require, without the constant attension to virus checkers.

I also do not want to buy nee hardware to run Windows 11, whi h maybe as bad as
Windows 10.

i'm using this

Markus
___
QL-Users Mailing List

```

### Re: [Ql-Users] SMSQmulator

```Hi,

I use OpenJDK 11 or 8, version 11 is running on the Linux laptop.

I do not use Windows as I fo not want to pay for the licence. Linux does all I
require, without the constant attension to virus checkers.

I also do not want to buy nee hardware to run Windows 11, whi h maybe as bad as
Windows 10.

SMSQmulator rin very smoothely on a Core i7 based computer, only needs 4Gb to
run...
---
Regards,
Derek

On 26 December 2021 05:44:14 GMT, Wolfgang Lenerz via Ql-Users
wrote:
>Hi,
>
>I only use openjdk.
>
>The reason I refer people to the java.com or oracle's site is that they
>have executable files which will do the install for you.
>
>If you want to use openjdk, you need to download the zip file (from
>https://jdk.java.net/17/) and unzip it, set one or two environment
>variables to point to where you unzipped it, and then set the file
>association between .jar files and java
>
>
>Wolfgang
>
>>
>> DId you do any testing with OpenJDK? Oracle’s JDK has had some licensing
>> difficulities over the last 10-15 years.
>>
>> otis
>>
>> —
>> Juraj Lutter
>> XMPP: juraj (at) lutter.sk
>> GSM: +421907986576
>>
>> ___
>> QL-Users Mailing List
>___
>QL-Users Mailing List
___
QL-Users Mailing List
```

### [Ql-Users] SMSQmulator

```
Hi,

I only use openjdk.

The reason I refer people to the java.com or oracle's site is that they
have executable files which will do the install for you.

If you want to use openjdk, you need to download the zip file (from
https://jdk.java.net/17/) and unzip it, set one or two environment
variables to point to where you unzipped it, and then set the file
association between .jar files and java

Wolfgang

DId you do any testing with OpenJDK? Oracle’s JDK has had some licensing
difficulities over the last 10-15 years.

otis

—
Juraj Lutter
XMPP: juraj (at) lutter.sk
GSM: +421907986576

___
QL-Users Mailing List

___
QL-Users Mailing List
```

### Re: [Ql-Users] SMSQmulator

```

> On 25 Dec 2021, at 16:37, Wolfgang Lenerz via Ql-Users
>  wrote:
>
> Hi Per,
>
> Never a dumb question from you.
>
>
> If it doesn't :
>
>
> This will install the full jdk, not just the runtime.
>
> When I go to java.com all I get is this:
> "
> This site https://www.java.com/ is experiencing technical difficulty. We are
> aware of the issue and are working as quick as possible to correct the issue.
>
> We apologize for any inconvenience this may have caused.
>
> To speak with an Oracle sales representative: 1.800.ORACLE1.
>
> To contact Oracle Corporate Headquarters from anywhere in the world:
> 1.650.506.7000.
>
> To get technical support in the United States: 1.800.633.0738.
> "
>

DId you do any testing with OpenJDK? Oracle’s JDK has had some licensing
difficulities over the last 10-15 years.

otis

—
Juraj Lutter
XMPP: juraj (at) lutter.sk
GSM: +421907986576

___
QL-Users Mailing List
```

### Re: [Ql-Users] SMSQmulator

```As my uninspiring maths teacher used to say, "You're right: No
question is too dumb to ask. But you may be too dumb to understand the

I dont know that any version of Java is installed in Windows by
default, but anyway, mine was an "upgrade" from W10 and Java 8 was

I dont want the whole JDK (Im at the end of my month's broadband
quota). So am I to understand that JDK17 includes Java runtime V11? If
so then Oracle's version system is even more screwed up than mine! 8,
11, 17..?

Anyway, I found my way to the V11 runtime, but now they want me to
before. I may revert to V8 if theyll still allow me to download it
without an account. If not, Im not sure what I'll do..

Per

On 25/12/2021 16:37, Wolfgang Lenerz via Ql-Users wrote:

Hi Per,

Never a dumb question from you.

If it doesn't :

This will install the full jdk, not just the runtime.

When I go to java.com all I get is this:
"
This site https://www.java.com/ is experiencing technical
difficulty. We are aware of the issue and are working as quick as
possible to correct the issue.

We apologize for any inconvenience this may have caused.

To speak with an Oracle sales representative: 1.800.ORACLE1.

To contact Oracle Corporate Headquarters from anywhere in the world:
1.650.506.7000.

To get technical support in the United States: 1.800.633.0738.
"

What a crock!

Wolfgang

On 25/12/2021 14:29, Wolf via Ql-Users wrote:

Hi all,

SMSQmulator 2.33 is out now.

Just a small bugfix release, notably for the NFA device, which is
now marked as a format type 4.

http://www.wlenerz.com/smsqmulator/

Season's Greetings to all!

Thank you!

Now for the dumb questions:

update I only ever get shown V8.xx.xx updates. You write on your
website that SMSQmulator V2.33 will be the last for Java 8, so I
want to be ahead of the curve. Also, as you will know from our
correspondence, Im having unresolvable "issues" with SMSQmulator on
Windows 11, so Im hoping these can eventually be resolved by trying
a different Java.

But I cant see Java V11 anywhere on the java.com website.  So I
uninstalled Java V8 and tried again; still only V8 on offer.
Digging a bit further I find there is a Java 17 out there. This is
what Oracle seems to want us to download on starting from scratch now.

So, what do I do?

Per
___
QL-Users Mailing List

___
QL-Users Mailing List

___
QL-Users Mailing List
```

### [Ql-Users] SMSQmulator

```
Hi Per,

Never a dumb question from you.

If it doesn't :

This will install the full jdk, not just the runtime.

When I go to java.com all I get is this:
"
This site https://www.java.com/ is experiencing technical difficulty. We
are aware of the issue and are working as quick as possible to correct
the issue.

We apologize for any inconvenience this may have caused.

To speak with an Oracle sales representative: 1.800.ORACLE1.

To contact Oracle Corporate Headquarters from anywhere in the world:
1.650.506.7000.

To get technical support in the United States: 1.800.633.0738.
"

What a crock!

Wolfgang

On 25/12/2021 14:29, Wolf via Ql-Users wrote:

Hi all,

SMSQmulator 2.33 is out now.

Just a small bugfix release, notably for the NFA device, which is now
marked as a format type 4.

http://www.wlenerz.com/smsqmulator/

Season's Greetings to all!

Thank you!

Now for the dumb questions:

only ever get shown V8.xx.xx updates. You write on your website that
SMSQmulator V2.33 will be the last for Java 8, so I want to be ahead of
the curve. Also, as you will know from our correspondence, Im having
unresolvable "issues" with SMSQmulator on Windows 11, so Im hoping these
can eventually be resolved by trying a different Java.

But I cant see Java V11 anywhere on the java.com website.  So I
uninstalled Java V8 and tried again; still only V8 on offer. Digging a
bit further I find there is a Java 17 out there. This is what Oracle

So, what do I do?

Per
___
QL-Users Mailing List

___
QL-Users Mailing List
```

### Re: [Ql-Users] SMSQmulator

```
On 25/12/2021 14:29, Wolf via Ql-Users wrote:

Hi all,

SMSQmulator 2.33 is out now.

Just a small bugfix release, notably for the NFA device, which is
now marked as a format type 4.

http://www.wlenerz.com/smsqmulator/

Season's Greetings to all!

Thank you!

Now for the dumb questions:

I only ever get shown V8.xx.xx updates. You write on your website that
SMSQmulator V2.33 will be the last for Java 8, so I want to be ahead
of the curve. Also, as you will know from our correspondence, Im
having unresolvable "issues" with SMSQmulator on Windows 11, so Im
hoping these can eventually be resolved by trying a different Java.

But I cant see Java V11 anywhere on the java.com website.  So I
uninstalled Java V8 and tried again; still only V8 on offer. Digging a
bit further I find there is a Java 17 out there. This is what Oracle

So, what do I do?

Per
___
QL-Users Mailing List
```

### [Ql-Users] SMSQmulator

```
Hi all,

SMSQmulator 2.33 is out now.

Just a small bugfix release, notably for the NFA device, which is now
marked as a format type 4.

http://www.wlenerz.com/smsqmulator/

Season's Greetings to all!

Wolfgang
___
QL-Users Mailing List

```

### Re: [Ql-Users] INSTR_CASE

```
Hi,

> INSTR_CASE
> SMSQE works as expected
> but not as Qlib Job

Without checking by actually tracing a call to INSTR from within a Qlib
job, I believe that this probably is one incompatibility between SMSQE
and QDOS/Qlib.

To honour the INSTR_CASE, SMSQE checks a flag, namely the SBasic
variable sb_cinst (=\$b0) (see smsq_sbas_iexpr_asm, label b_instr) which
is set by INSTR_CASE.

However, in QDOS, the SuperBasic variable at \$b0 is "bv_tkpos", which
contains something else entirely, namely "Position of A4 in tklist on
entry to PROC". If Qlib correctly mimicks SuperBasic, it probably
overwrites the flag at \$b0 with the correct value for Superbasic between
the INSTR_CASE keyword and the INSTR.

This difference (and others) between QDOS and SMSQ/E Basic variables is
not documented (yet) in the SMSQ/E reference guide, but can  be seen
form the keys_sbasic file in the SMSQ/E sources. I will include
something in the next version of the reference guide.

Season's greetings to everyone!

Wolfgang
Probably because Qlib doesnt know that there are two different instr
routines in SMSQ/E. The INSTR keyword is part of the S*BASIC language;
it isnt like a toolkit function, so Qlib probably calls this routine
directly which, unlike SBASIC's keyword, doesnt check the sb_cinst flag
before execution.

It could probably easily be fixed, but it still wouldnt work on a Qdos
machine as the underlying code isnt there.

Per
___
QL-Users Mailing List

___
QL-Users Mailing List

```

### Re: [Ql-Users] INSTR_CASE

```
On 23/12/2021 22:31, desin via Ql-Users wrote:

100 OPEN #1,"con_"
110   WINDOW #1,256,256,0,0
120 CLS
130 a\$= "hello" :b\$= "Hello"
140 PRINT#1, a\$,a\$,a\$ INSTR a\$
150 PRINT#1, a\$,b\$,a\$ INSTR b\$
160 PRINT " case 1"
170 INSTR_CASE 1
180 PRINT#1, a\$,a\$,a\$ INSTR a\$
190 PRINT#1, a\$,b\$,a\$ INSTR b\$
200 PRINT " case 0"
210 INSTR_CASE 0
220 PRINT#1, a\$,a\$,a\$ INSTR a\$
230 PRINT#1, a\$,b\$,a\$ INSTR b\$
240 PAUSE #1

SMSQE works as expected
but not as Qlib Job
Any ideas ?

<>

Probably because Qlib doesnt know that there are two different instr
routines in SMSQ/E. The INSTR keyword is part of the S*BASIC language;
it isnt like a toolkit function, so Qlib probably calls this routine
directly which, unlike SBASIC's keyword, doesnt check the sb_cinst
flag before execution.

It could probably easily be fixed, but it still wouldnt work on a Qdos
machine as the underlying code isnt there.

Per
___
QL-Users Mailing List
```

### [Ql-Users] INSTR_CASE

```
100   OPEN #1,"con_"
110   WINDOW #1,256,256,0,0
120 CLS
130 a\$= "hello" :b\$= "Hello"
140 PRINT#1, a\$,a\$,a\$ INSTR a\$
150 PRINT#1, a\$,b\$,a\$ INSTR b\$
160 PRINT " case 1"
170 INSTR_CASE 1
180 PRINT#1, a\$,a\$,a\$ INSTR a\$
190 PRINT#1, a\$,b\$,a\$ INSTR b\$
200 PRINT " case 0"
210 INSTR_CASE 0
220 PRINT#1, a\$,a\$,a\$ INSTR a\$
230 PRINT#1, a\$,b\$,a\$ INSTR b\$
240 PAUSE #1

SMSQE works as expected
but not as Qlib Job
Any ideas ?

Greetings From Switzerland

and happy Christmas too

Makus
___
QL-Users Mailing List

```

### Re: [Ql-Users] More Knoware

```
On 12/12/2021 20:42, Urs Koenig (QL) wrote:

What a repository of nice and handy things! Great work Per.

I'm working on the next release of QL/E and just yesterday, integrated Q2S, to
be loaded as default on non-SMSQ systems.

<>
Good move, Urs! ;o)

For those who dont know what we're talking about, Q2S is a
"compatibility toolkit" that allows for many (SMSQ/E) SBASIC, or
compiled SBASIC, programs to run on a QL. Likewise, programs written
on a QL using these commands have a good chance of being able to run
under SMSQ/E. - And it may even be found genuinely useful in programs
only intended for the QL itself!

At present the commands included are:

SUSJB- Suspend a job
JOBID- Return my job ID
OUTLN- Create a "managed" window (Requires PE!)
QUIT - Quit program with optional error code
ERT  - Terminate program if error
SCR_XLIM - Get screen x-maximum
SCR_YLIM - Get screen y-maximum
SCR_BASE - Get screen base address
SCR_LLEN - Number of bytes between rows on screen
DISP_TYPE- Display type 0, 2, 16, 32, 33
FDEL - Delete a file with error return

(I hope the table above remains readable!)

Only the simplest, most common usage of these commands are
implemented. And some of them are just duds (eg all the SCR_XXX
commands merely return fixed values) as this toolkit is only meant to
be loaded on an actual QL (or exact QL emulator).

It is intended to be compact (presently 732 b), but if anyone has any
suggestions as to whether any important commands have been left out,
Id like to hear. There are some other compatibility toolkits on
Knoware.no/htm/toolkits.htm#compatibility, so check those out first.

Keep your noses to the grinding-wheel, y'all!

Per
___
QL-Users Mailing List

```

### Re: [Ql-Users] More Knoware

```What a repository of nice and handy things! Great work Per.

I'm working on the next release of QL/E and just yesterday, integrated Q2S, to
be loaded as default on non-SMSQ systems.

Cheers,
Urs

QL forever!
http://www.sinclairql.net/ - Go and get THE DISTRIBUTION & QL/E!
Sinclair, QL, ATARI, JAGUAR, NUON, APPLE, NeXT, MIST & much more...

___
QL-Users Mailing List

```

### Re: [Ql-Users] More Knoware

```Fantastic! You are like good wine, getting older better! :-D

Il giorno sab 11 dic 2021 alle ore 11:49 Wolf via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:

> Hi,
>
> as usual, more solid software from Per!
>
> Thanks
>
> Wolfgang
> ___
> QL-Users Mailing List
>
___
QL-Users Mailing List

```

### [Ql-Users] More Knoware

```
Hi,

as usual, more solid software from Per!

Thanks

Wolfgang
___
QL-Users Mailing List

```

### Re: [Ql-Users] More Knoware

```
Op 10/12/2021 om 21:43 schreef pjwitte via Ql-Users:

Ive been clearing out some nooks and crannies and found a few items I
felt were of a shareable quality. Ie they werent written with sharing
in mind, but have worked for me, in some cases for years, without
issue. Many of you will no doubt have produced your own solutions, but
possibly not everyone, or there may be gaps,.. Well, I wrapped mine
up, added some written description, and present them to those who
might want some shiny new toys for Christmas. Yes, it is a bit like
putting lipstick on a pig, but I hope you enjoy them all the same!

Here is the lowdown:

> Updated and expanded Library: Sources now included. Replace old
libraries with this update!
scalar variables. Now with source code included.
> Added Minimize, a minimize button for fullscreen QPC2 and
SMSQmulator.
> Added Bcc, a tool for dyslecix assembler coders(!)
> Added Caps, a Capsloack indicator button.
> Added NoTab, a tool for QD to make compressed files temporarily
> Added LCMP, to compare unsigned long words - and some
eschatological musings on dates and the End of Time..
> Added QLTet, a simple Tetris-like game.
> Added Snowfall, a "screen saver" type program.

See www.Knoware.no/htm/changes.htm for details!

___
QL-Users Mailing List

Hi,

Thanks for rhe info. I'll have a peek and I'll  certainly download the
new version of VLS.

François Van Emelen

___
QL-Users Mailing List
```

### [Ql-Users] More Knoware

```
Ive been clearing out some nooks and crannies and found a few items I
felt were of a shareable quality. Ie they werent written with sharing
in mind, but have worked for me, in some cases for years, without
issue. Many of you will no doubt have produced your own solutions, but
possibly not everyone, or there may be gaps,.. Well, I wrapped mine
up, added some written description, and present them to those who
might want some shiny new toys for Christmas. Yes, it is a bit like
putting lipstick on a pig, but I hope you enjoy them all the same!

Here is the lowdown:

> Updated and expanded Library: Sources now included. Replace old
libraries with this update!
scalar variables. Now with source code included.
> Added Minimize, a minimize button for fullscreen QPC2 and
SMSQmulator.
> Added Bcc, a tool for dyslecix assembler coders(!)
> Added Caps, a Capsloack indicator button.
> Added NoTab, a tool for QD to make compressed files temporarily
> Added LCMP, to compare unsigned long words - and some
eschatological musings on dates and the End of Time..
> Added QLTet, a simple Tetris-like game.
> Added Snowfall, a "screen saver" type program.

See www.Knoware.no/htm/changes.htm for details!

___
QL-Users Mailing List
```

### Re: [Ql-Users] QTImage 1.5

``` The menu you see is my editing "standard" allows you to copy / load the
value to and from the scrap. for example if you have already copied the
value from another point with that menu you can paste it or copy it. Maybe
in that context it is not very useless but it is present in every editable
box in all my programs, I use a generic routine to do it.

Il giorno gio 9 dic 2021 alle ore 17:05 François Van Emelen via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:

> Op 9/12/2021 om 16:03 schreef Giorgio Garabello via Ql-Users:
> > Il giorno gio 9 dic 2021 alle ore 15:49 François Van Emelen via Ql-Users
> <
> > ql-users@lists.q-v-d.com> ha scritto:
> >
> >> Op 8/12/2021 om 17:50 schreef Giorgio Garabello via Ql-Users:
> >>>>
> >>>>
> >>>>
> >>>> About the problems running Qtimage from Ramx_. Just a thought, Why
> don’t
> >>>> you use the HOME-thing, that would make the program more versatile, I
> >>>> think,
> >>>>
> >>> I regularly use THINGS FOR THE HOUSE
> >>> That's not the problem.
> >>>
> >>>> I have merged 3 pic-files (2 large & 1 small) without a problem, It
> took
> >>>> minutes,,, but it worked.
> >>>>
> >>> Unfortunately we are pushing the QPC2 limit.
> >>> Let's not forget that it emulates a 68020
> >>>
> >> This wasn't a negative comment; I only meant that QTimage could do it.
> >>>> Tests
> >>>>
> >>>>
> >>>> Image
> >>>>
> >>>> Zoom OK
> >>>>
> >>>> Resize OK
> >>>>
> >>>> Border OK
> >>>>
> >>>>
> >>>> Colours
> >>>>
> >>>>
> >>>> This is another kettle of fish,
> >>>>
> >> This is another kettle of fish means 'much more difficult, more
> >> complicated'
> >>
> >>> I'm not sure I understand this part. I translated it with google
> >> translate
> >>> but I didn't understand exactly what you mean (in that menu)
> >>> My fault, unfortunately my English sucks
> >>>
> >>>
> >>>> To avoid a new menu popping up, you ought to replace all occurences of
> >>>> scale
> >>>>
> >>>> -256 to +256 with -255 to +255 and keep the loose item ‘ok’
> unavailable
> >>>> until the correct values are entered,
> >>>>
> >>>> Entering wrong values are sometimes corrected by the program but not
> >>>> always. Wrong values allow the popup of a new menu ( see Filter
> →Pixel).
> >>>> But this behaviour seems unpredictable here, at least to me. So make
> it
> >>>> impossible to use values that are out of range .
> >>>>
> >>>> Make it impossible to enter wrong values for all the other colour
> items.
> >>>>
> >> I think I have found the problem: not that difficult after all.
> >>
> >> Try this:
> >>
> >> 1. load an image
> >>
> >> 2. choose Colours
> >>
> >> 3. choose Brightness
> >>
> >> 4. put the mouse pointer over the editable loose item
> >>
> >> 5. Press the right button of the mouse
> >>
> >> 6. a new menu will pop up.
> >>
> >> See attachment
> >>
> >
> >Up to here, everything ok .. then? which attach? I do not understand..
> >
> >
> >
> >> So, make sure the user can't leave the Brightness  with a   DO on an
> >> editable loose item.
> >>
> >> This behaviour is the same for all Colours items.
> >>
> >> There is another problem with Export/Save with name: you should add a
> >> '_' or a '.' before the extension, else the file will be saved without a
> >> valid extension.
> >>
> > Yes this is easy
> > Thanks for your help
> >
> > Giorgio
> > ___
> > QL-Users Mailing List
>
> Sorry, I forgot the attachment
>
> So, If press the right button of the mouse  without editing the loose
> item, you will get a new menu that has nothing to do with Brightness.
> see QTimge.jpg and Qtimge2.jpg
>
>
> ___
> QL-Users Mailing List
___
QL-Users Mailing List
```

### Re: [Ql-Users] QTImage 1.5

```
Op 9/12/2021 om 18:44 schreef Tobias Fröschle via Ql-Users:

François,

the mailing list doesn't forward attachments - You need to put them somewhere
else for us to see or describe textually.

Cheers,
Tobias

Am 09.12.2021 um 17:04 schrieb François Van Emelen via Ql-Users
:

Op 9/12/2021 om 16:03 schreef Giorgio Garabello via Ql-Users:

Il giorno gio 9 dic 2021 alle ore 15:49 François Van Emelen via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:

Op 8/12/2021 om 17:50 schreef Giorgio Garabello via Ql-Users:

About the problems running Qtimage from Ramx_. Just a thought, Why don’t
you use the HOME-thing, that would make the program more versatile, I
think,

I regularly use THINGS FOR THE HOUSE
That's not the problem.

I have merged 3 pic-files (2 large & 1 small) without a problem, It took
minutes,,, but it worked.

Unfortunately we are pushing the QPC2 limit.
Let's not forget that it emulates a 68020

This wasn't a negative comment; I only meant that QTimage could do it.

Tests

Image

Zoom OK

Resize OK

Border OK

Colours

This is another kettle of fish,

This is another kettle of fish means 'much more difficult, more
complicated'

I'm not sure I understand this part. I translated it with google

translate

but I didn't understand exactly what you mean (in that menu)
My fault, unfortunately my English sucks

To avoid a new menu popping up, you ought to replace all occurences of
scale

-256 to +256 with -255 to +255 and keep the loose item ‘ok’ unavailable
until the correct values are entered,

Entering wrong values are sometimes corrected by the program but not
always. Wrong values allow the popup of a new menu ( see Filter →Pixel).
But this behaviour seems unpredictable here, at least to me. So make it
impossible to use values that are out of range .

Make it impossible to enter wrong values for all the other colour items.

I think I have found the problem: not that difficult after all.

Try this:

2. choose Colours

3. choose Brightness

4. put the mouse pointer over the editable loose item

5. Press the right button of the mouse

6. a new menu will pop up.

See attachment

Up to here, everything ok .. then? which attach? I do not understand..

So, make sure the user can't leave the Brightness  with a   DO on an
editable loose item.

This behaviour is the same for all Colours items.

There is another problem with Export/Save with name: you should add a
'_' or a '.' before the extension, else the file will be saved without a
valid extension.

Yes this is easy

Giorgio
___
QL-Users Mailing List

Sorry, I forgot the attachment

So, If press the right button of the mouse  without editing the loose item, you
will get a new menu that has nothing to do with Brightness. see QTimge.jpg and
Qtimge2.jpg

___
QL-Users Mailing List

___
QL-Users Mailing List

François Van Emelen

___
QL-Users Mailing List
```

### Re: [Ql-Users] QTImage 1.5

```François,

the mailing list doesn't forward attachments - You need to put them somewhere
else for us to see or describe textually.

Cheers,
Tobias

> Am 09.12.2021 um 17:04 schrieb François Van Emelen via Ql-Users
> :
>
> Op 9/12/2021 om 16:03 schreef Giorgio Garabello via Ql-Users:
>> Il giorno gio 9 dic 2021 alle ore 15:49 François Van Emelen via Ql-Users <
>> ql-users@lists.q-v-d.com> ha scritto:
>>
>>> Op 8/12/2021 om 17:50 schreef Giorgio Garabello via Ql-Users:
>>>>>
>>>>>
>>>>>
>>>>> About the problems running Qtimage from Ramx_. Just a thought, Why don’t
>>>>> you use the HOME-thing, that would make the program more versatile, I
>>>>> think,
>>>>>
>>>> I regularly use THINGS FOR THE HOUSE
>>>> That's not the problem.
>>>>
>>>>> I have merged 3 pic-files (2 large & 1 small) without a problem, It took
>>>>> minutes,,, but it worked.
>>>>>
>>>> Unfortunately we are pushing the QPC2 limit.
>>>> Let's not forget that it emulates a 68020
>>>>
>>> This wasn't a negative comment; I only meant that QTimage could do it.
>>>>> Tests
>>>>>
>>>>>
>>>>> Image
>>>>>
>>>>> Zoom OK
>>>>>
>>>>> Resize OK
>>>>>
>>>>> Border OK
>>>>>
>>>>>
>>>>> Colours
>>>>>
>>>>>
>>>>> This is another kettle of fish,
>>>>>
>>> This is another kettle of fish means 'much more difficult, more
>>> complicated'
>>>
>>>> I'm not sure I understand this part. I translated it with google
>>> translate
>>>> but I didn't understand exactly what you mean (in that menu)
>>>> My fault, unfortunately my English sucks
>>>>
>>>>
>>>>> To avoid a new menu popping up, you ought to replace all occurences of
>>>>> scale
>>>>>
>>>>> -256 to +256 with -255 to +255 and keep the loose item ‘ok’ unavailable
>>>>> until the correct values are entered,
>>>>>
>>>>> Entering wrong values are sometimes corrected by the program but not
>>>>> always. Wrong values allow the popup of a new menu ( see Filter →Pixel).
>>>>> But this behaviour seems unpredictable here, at least to me. So make it
>>>>> impossible to use values that are out of range .
>>>>>
>>>>> Make it impossible to enter wrong values for all the other colour items.
>>>>>
>>> I think I have found the problem: not that difficult after all.
>>>
>>> Try this:
>>>
>>>
>>> 2. choose Colours
>>>
>>> 3. choose Brightness
>>>
>>> 4. put the mouse pointer over the editable loose item
>>>
>>> 5. Press the right button of the mouse
>>>
>>> 6. a new menu will pop up.
>>>
>>> See attachment
>>>
>>
>>   Up to here, everything ok .. then? which attach? I do not understand..
>>
>>
>>
>>> So, make sure the user can't leave the Brightness  with a   DO on an
>>> editable loose item.
>>>
>>> This behaviour is the same for all Colours items.
>>>
>>> There is another problem with Export/Save with name: you should add a
>>> '_' or a '.' before the extension, else the file will be saved without a
>>> valid extension.
>>>
>> Yes this is easy
>>
>> Giorgio
>> ___
>> QL-Users Mailing List
>
> Sorry, I forgot the attachment
>
> So, If press the right button of the mouse  without editing the loose item,
> you will get a new menu that has nothing to do with Brightness. see
> QTimge.jpg and Qtimge2.jpg
>
>
> ___
> QL-Users Mailing List

___
QL-Users Mailing List
```

### Re: [Ql-Users] QTImage 1.5

```
Op 9/12/2021 om 16:03 schreef Giorgio Garabello via Ql-Users:

Il giorno gio 9 dic 2021 alle ore 15:49 François Van Emelen via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:

Op 8/12/2021 om 17:50 schreef Giorgio Garabello via Ql-Users:

About the problems running Qtimage from Ramx_. Just a thought, Why don’t
you use the HOME-thing, that would make the program more versatile, I
think,

I regularly use THINGS FOR THE HOUSE
That's not the problem.

I have merged 3 pic-files (2 large & 1 small) without a problem, It took
minutes,,, but it worked.

Unfortunately we are pushing the QPC2 limit.
Let's not forget that it emulates a 68020

This wasn't a negative comment; I only meant that QTimage could do it.

Tests

Image

Zoom OK

Resize OK

Border OK

Colours

This is another kettle of fish,

This is another kettle of fish means 'much more difficult, more
complicated'

I'm not sure I understand this part. I translated it with google

translate

but I didn't understand exactly what you mean (in that menu)
My fault, unfortunately my English sucks

To avoid a new menu popping up, you ought to replace all occurences of
scale

-256 to +256 with -255 to +255 and keep the loose item ‘ok’ unavailable
until the correct values are entered,

Entering wrong values are sometimes corrected by the program but not
always. Wrong values allow the popup of a new menu ( see Filter →Pixel).
But this behaviour seems unpredictable here, at least to me. So make it
impossible to use values that are out of range .

Make it impossible to enter wrong values for all the other colour items.

I think I have found the problem: not that difficult after all.

Try this:

2. choose Colours

3. choose Brightness

4. put the mouse pointer over the editable loose item

5. Press the right button of the mouse

6. a new menu will pop up.

See attachment

Up to here, everything ok .. then? which attach? I do not understand..

So, make sure the user can't leave the Brightness  with a   DO on an
editable loose item.

This behaviour is the same for all Colours items.

There is another problem with Export/Save with name: you should add a
'_' or a '.' before the extension, else the file will be saved without a
valid extension.

Yes this is easy

Giorgio
___
QL-Users Mailing List

Sorry, I forgot the attachment

So, If press the right button of the mouse  without editing the loose
item, you will get a new menu that has nothing to do with Brightness.
see QTimge.jpg and Qtimge2.jpg

___
QL-Users Mailing List
```

### Re: [Ql-Users] QTImage 1.5

```Il giorno gio 9 dic 2021 alle ore 15:49 François Van Emelen via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:

> Op 8/12/2021 om 17:50 schreef Giorgio Garabello via Ql-Users:
> >>
> >>
> >>
> >>
> >> About the problems running Qtimage from Ramx_. Just a thought, Why don’t
> >> you use the HOME-thing, that would make the program more versatile, I
> >> think,
> >>
> > I regularly use THINGS FOR THE HOUSE
> > That's not the problem.
> >
> >> I have merged 3 pic-files (2 large & 1 small) without a problem, It took
> >> minutes,,, but it worked.
> >>
> > Unfortunately we are pushing the QPC2 limit.
> > Let's not forget that it emulates a 68020
> >
> This wasn't a negative comment; I only meant that QTimage could do it.
> >>
> >> Tests
> >>
> >>
> >> Image
> >>
> >> Zoom OK
> >>
> >> Resize OK
> >>
> >> Border OK
> >>
> >>
> >> Colours
> >>
> >>
> >> This is another kettle of fish,
> >>
>
> This is another kettle of fish means 'much more difficult, more
> complicated'
>
> > I'm not sure I understand this part. I translated it with google
> translate
> > but I didn't understand exactly what you mean (in that menu)
> > My fault, unfortunately my English sucks
> >
> >
> >> To avoid a new menu popping up, you ought to replace all occurences of
> >> scale
> >>
> >> -256 to +256 with -255 to +255 and keep the loose item ‘ok’ unavailable
> >> until the correct values are entered,
> >>
> >> Entering wrong values are sometimes corrected by the program but not
> >> always. Wrong values allow the popup of a new menu ( see Filter →Pixel).
> >> But this behaviour seems unpredictable here, at least to me. So make it
> >> impossible to use values that are out of range .
> >>
> >> Make it impossible to enter wrong values for all the other colour items.
> >>
> I think I have found the problem: not that difficult after all.
>
> Try this:
>
>
> 2. choose Colours
>
> 3. choose Brightness
>
> 4. put the mouse pointer over the editable loose item
>
> 5. Press the right button of the mouse
>
> 6. a new menu will pop up.
>
> See attachment
>

Up to here, everything ok .. then? which attach? I do not understand..

> So, make sure the user can't leave the Brightness  with a   DO on an
> editable loose item.
>
> This behaviour is the same for all Colours items.
>
> There is another problem with Export/Save with name: you should add a
> '_' or a '.' before the extension, else the file will be saved without a
> valid extension.
>

Yes this is easy

Giorgio
___
QL-Users Mailing List
```

### Re: [Ql-Users] QTImage 1.5

```
Op 8/12/2021 om 17:50 schreef Giorgio Garabello via Ql-Users:

About the problems running Qtimage from Ramx_. Just a thought, Why don’t
you use the HOME-thing, that would make the program more versatile, I
think,

I regularly use THINGS FOR THE HOUSE
That's not the problem.

I have merged 3 pic-files (2 large & 1 small) without a problem, It took
minutes,,, but it worked.

Unfortunately we are pushing the QPC2 limit.
Let's not forget that it emulates a 68020

This wasn't a negative comment; I only meant that QTimage could do it.

Tests

Image

Zoom OK

Resize OK

Border OK

Colours

This is another kettle of fish,

This is another kettle of fish means 'much more difficult, more complicated'

I'm not sure I understand this part. I translated it with google translate
but I didn't understand exactly what you mean (in that menu)
My fault, unfortunately my English sucks

To avoid a new menu popping up, you ought to replace all occurences of
scale

-256 to +256 with -255 to +255 and keep the loose item ‘ok’ unavailable
until the correct values are entered,

Entering wrong values are sometimes corrected by the program but not
always. Wrong values allow the popup of a new menu ( see Filter →Pixel).
But this behaviour seems unpredictable here, at least to me. So make it
impossible to use values that are out of range .

Make it impossible to enter wrong values for all the other colour items.

I think I have found the problem: not that difficult after all.

Try this:

2. choose Colours

3. choose Brightness

4. put the mouse pointer over the editable loose item

5. Press the right button of the mouse

6. a new menu will pop up.

See attachment

So, make sure the user can't leave the Brightness  with a   DO on an
editable loose item.

This behaviour is the same for all Colours items.

There is another problem with Export/Save with name: you should add a
'_' or a '.' before the extension, else the file will be saved without a
valid extension.

Have a fine evening.

François

___
QL-Users Mailing List

___
QL-Users Mailing List

HTH

François

___
QL-Users Mailing List
```

### Re: [Ql-Users] QTImage 1.5

```>
>
>
>
>
> About the problems running Qtimage from Ramx_. Just a thought, Why don’t
> you use the HOME-thing, that would make the program more versatile, I
> think,
>

I regularly use THINGS FOR THE HOUSE
That's not the problem.

>
> I have merged 3 pic-files (2 large & 1 small) without a problem, It took
> minutes,,, but it worked.
>

Unfortunately we are pushing the QPC2 limit.
Let's not forget that it emulates a 68020

>
>
> Tests
>
>
> Image
>
> Zoom OK
>
> Resize OK
>
> Border OK
>
>
> Colours
>
>
> This is another kettle of fish,
>
>
I'm not sure I understand this part. I translated it with google translate
but I didn't understand exactly what you mean (in that menu)
My fault, unfortunately my English sucks

> To avoid a new menu popping up, you ought to replace all occurences of
> scale
>
> -256 to +256 with -255 to +255 and keep the loose item ‘ok’ unavailable
> until the correct values are entered,
>
> Entering wrong values are sometimes corrected by the program but not
> always. Wrong values allow the popup of a new menu ( see Filter →Pixel).
> But this behaviour seems unpredictable here, at least to me. So make it
> impossible to use values that are out of range .
>
> Make it impossible to enter wrong values for all the other colour items.
>
>
> Have a fine evening.
>
> François
>
>
> ___
> QL-Users Mailing List
___
QL-Users Mailing List
```

### Re: [Ql-Users] QTImage 1.5

```
Op 7/12/2021 om 12:26 schreef Giorgio Garabello via Ql-Users:

Fantastic debugging! Extremely accurate! Thank you for your help, these
tests are essential because alone I cannot control everything and after a
while I tend to always try the same options and neglect the others Thanks!

Ciao
Giorgio

Il giorno mar 7 dic 2021 alle ore 12:15 François Van Emelen via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:

Op 4/12/2021 om 22:33 schreef Giorgio Garabello via Ql-Users:

There is some problem with the download permissions on the site :-( I try
to send you the zip

Il giorno sab 4 dic 2021 alle ore 21:48 François Van Emelen via Ql-Users

<

ql-users@lists.q-v-d.com> ha scritto:

Op 4/12/2021 om 18:34 schreef Giorgio Garabello via Ql-Users:

After a year off for personal problems. back to the QL!
Thanks to the fantastic collaboration of Roberto Porro I finally

publish

QTImage 1.5
Thanks also to Armdo Fumero for the Spanish translation

What's new?
Resizing the program in three ways
Added management of the Spanish language
Improved file import management
Improved color management
New feature: invert colors
New X-ray effect
New feature: Quantization

https://www.hunggartorino.it/ql/qtimage-2/
___
QL-Users Mailing List

Hi Gorgio,

There ieems to bea problem with the ZIP-file.

François

___
QL-Users Mailing List

___
QL-Users Mailing List

Hi Giorgio,

I have seen the comments about Qtimage on the QL-forum but I’m not a
member, so you won’t see me there.

1) There seems to be something wrong when launching Qtimage from RAMx_

I suppose there are some data in your dbs-files referring to absolute
PROG_USE?

2) After an error, Qtimage still leave a ‘temp file’. After testing, a
lot of such are left on the Hard Drive.

3) My Qtimage in installed on Win2_ . All my programs run from there
except BP for testing.

I have been testing the Filters in Qtimage and this is what I found:

Smoothing OK

Sharpen OK

Raised OK

Gaussian blur

motion OK

boxed OK

gaussian OK

Dithering

Level 0 to 4 OK

Level 5 to 9 OK but colours disappear

Coarse OK

Medium OK

Feint 0 to 2 OK

Edge 0 to 9 OK

Pixel

dimension 0 no modification but colours change

dimension 2 to 96 OK

dimension 100 : a new menu pops up with Copy, Cut, Paste, Clear field

Mosaic

up to 14 OK

If you enter value 15, it is changed to 16 (which is correct) but no new

Merge

seems to work. I didn’t try to merge a third image. I’ll try that later,

Next time I’ll test other things.

Have a fine day.

François

___
QL-Users Mailing List

___
QL-Users Mailing List

Hi Giorgio,

About the problems running Qtimage from Ramx_. Just a thought, Why don’t
you use the HOME-thing, that would make the program more versatile, I think,

I have merged 3 pic-files (2 large & 1 small) without a problem, It took
minutes,,, but it worked.

Tests

Image

Zoom OK

Resize OK

Border OK

Colours

This is another kettle of fish,

To avoid a new menu popping up, you ought to replace all occurences of
scale

-256 to +256 with -255 to +255 and keep the loose item ‘ok’ unavailable
until the correct values are entered,

Entering wrong values are sometimes corrected by the program but not
always. Wrong values allow the popup of a new menu ( see Filter →Pixel).
But this behaviour seems unpredictable here, at least to me. So make it
impossible to use values that are out of range .

Make it impossible to enter wrong values for all the other colour items.

Have a fine evening.

François

___
QL-Users Mailing List
```

### Re: [Ql-Users] QTImage 1.5

``` Fantastic debugging! Extremely accurate! Thank you for your help, these
tests are essential because alone I cannot control everything and after a
while I tend to always try the same options and neglect the others Thanks!

Ciao
Giorgio

Il giorno mar 7 dic 2021 alle ore 12:15 François Van Emelen via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:

> Op 4/12/2021 om 22:33 schreef Giorgio Garabello via Ql-Users:
> > There is some problem with the download permissions on the site :-( I try
> > to send you the zip
> >
> > Il giorno sab 4 dic 2021 alle ore 21:48 François Van Emelen via Ql-Users
> <
> > ql-users@lists.q-v-d.com> ha scritto:
> >
> >> Op 4/12/2021 om 18:34 schreef Giorgio Garabello via Ql-Users:
> >>>After a year off for personal problems. back to the QL!
> >>> Thanks to the fantastic collaboration of Roberto Porro I finally
> publish
> >>> QTImage 1.5
> >>> Thanks also to Armdo Fumero for the Spanish translation
> >>>
> >>> What's new?
> >>> Resizing the program in three ways
> >>> Added management of the Spanish language
> >>> Improved file import management
> >>> Added new wave effect
> >>> Added new function: image merging
> >>> Improved color management
> >>> New feature: invert colors
> >>> New X-ray effect
> >>> New feature: Quantization
> >>>
> >>> https://www.hunggartorino.it/ql/qtimage-2/
> >>> ___
> >>> QL-Users Mailing List
> >> Hi Gorgio,
> >>
> >> There ieems to bea problem with the ZIP-file.
> >>
> >> François
> >>
> >>
> >> ___
> >> QL-Users Mailing List
> > ___
> > QL-Users Mailing List
>
> Hi Giorgio,
>
>
> I have seen the comments about Qtimage on the QL-forum but I’m not a
> member, so you won’t see me there.
>
>
> 1) There seems to be something wrong when launching Qtimage from RAMx_
>
> I suppose there are some data in your dbs-files referring to absolute
> PROG_USE?
>
>
> 2) After an error, Qtimage still leave a ‘temp file’. After testing, a
> lot of such are left on the Hard Drive.
>
>
> 3) My Qtimage in installed on Win2_ . All my programs run from there
> except BP for testing.
>
> I have been testing the Filters in Qtimage and this is what I found:
>
> Smoothing OK
>
> Sharpen OK
>
> Raised OK
>
> Gaussian blur
>
> motion OK
>
> boxed OK
>
> gaussian OK
>
> Dithering
>
> Level 0 to 4 OK
>
> Level 5 to 9 OK but colours disappear
>
> Coarse OK
>
> Medium OK
>
> Feint 0 to 2 OK
>
> Edge 0 to 9 OK
>
> Pixel
>
> dimension 0 no modification but colours change
>
> dimension 2 to 96 OK
>
> dimension 100 : a new menu pops up with Copy, Cut, Paste, Clear field
>
> I didn’t investiged this menu.
>
> Mosaic
>
> up to 14 OK
>
> 16 a new menu pops up. I didn’t investiged this menu
>
> If you enter value 15, it is changed to 16 (which is correct) but no new
>
> Merge
>
> seems to work. I didn’t try to merge a third image. I’ll try that later,
>
>
>
> Next time I’ll test other things.
>
>
> Have a fine day.
>
> François
>
>
> ___
> QL-Users Mailing List
___
QL-Users Mailing List
```

### Re: [Ql-Users] QTImage 1.5

```
Op 4/12/2021 om 22:33 schreef Giorgio Garabello via Ql-Users:

There is some problem with the download permissions on the site :-( I try
to send you the zip

Il giorno sab 4 dic 2021 alle ore 21:48 François Van Emelen via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:

Op 4/12/2021 om 18:34 schreef Giorgio Garabello via Ql-Users:

After a year off for personal problems. back to the QL!
Thanks to the fantastic collaboration of Roberto Porro I finally publish
QTImage 1.5
Thanks also to Armdo Fumero for the Spanish translation

What's new?
Resizing the program in three ways
Added management of the Spanish language
Improved file import management
Improved color management
New feature: invert colors
New X-ray effect
New feature: Quantization

https://www.hunggartorino.it/ql/qtimage-2/
___
QL-Users Mailing List

Hi Gorgio,

There ieems to bea problem with the ZIP-file.

François

___
QL-Users Mailing List

___
QL-Users Mailing List

Hi Giorgio,

I have seen the comments about Qtimage on the QL-forum but I’m not a
member, so you won’t see me there.

1) There seems to be something wrong when launching Qtimage from RAMx_

I suppose there are some data in your dbs-files referring to absolute
PROG_USE?

2) After an error, Qtimage still leave a ‘temp file’. After testing, a
lot of such are left on the Hard Drive.

3) My Qtimage in installed on Win2_ . All my programs run from there
except BP for testing.

I have been testing the Filters in Qtimage and this is what I found:

Smoothing OK

Sharpen OK

Raised OK

Gaussian blur

motion OK

boxed OK

gaussian OK

Dithering

Level 0 to 4 OK

Level 5 to 9 OK but colours disappear

Coarse OK

Medium OK

Feint 0 to 2 OK

Edge 0 to 9 OK

Pixel

dimension 0 no modification but colours change

dimension 2 to 96 OK

dimension 100 : a new menu pops up with Copy, Cut, Paste, Clear field

Mosaic

up to 14 OK

If you enter value 15, it is changed to 16 (which is correct) but no new

Merge

seems to work. I didn’t try to merge a third image. I’ll try that later,

Next time I’ll test other things.

Have a fine day.

François

___
QL-Users Mailing List
```

### Re: [Ql-Users] Ql-Users Digest, Vol 212, Issue 3

``` I explored the download potential:

Latest Firefox did throw a warning BUT

Will poke around a little later to see If I can find a clue as to why FF threw
a warning

I took the chance because my KungFu is strong! :-)

Paul Holmgren 2 57 300-C's in Indy Hoosier Corps #L6 CPUs run on smoke. I know
this because when the smoke comes out, it stops working.

On Sunday, December 5, 2021, 04:03:36 PM EST,
wrote:

Send Ql-Users mailing list submissions to
ql-users@lists.q-v-d.com

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.q-v-d.com/listinfo.cgi/ql-users-q-v-d.com
or, via email, send a message with subject or body 'help' to
ql-users-requ...@lists.q-v-d.com

You can reach the person managing the list at
ql-users-ow...@lists.q-v-d.com

than "Re: Contents of Ql-Users digest..."

Today's Topics:

1. Re: QTImage 1.5 (Giorgio Garabello)

--

Message: 1
Date: Sat, 4 Dec 2021 22:33:31 +0100
From: Giorgio Garabello
To: ql-users
Subject: Re: [Ql-Users] QTImage 1.5
Message-ID:

Content-Type: text/plain; charset="UTF-8"

There is some problem with the download permissions on the site :-( I try
to send you the zip

Il giorno sab 4 dic 2021 alle ore 21:48 Fran?ois Van Emelen via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:

> Op 4/12/2021 om 18:34 schreef Giorgio Garabello via Ql-Users:
> >  After a year off for personal problems. back to the QL!
> > Thanks to the fantastic collaboration of Roberto Porro I finally publish
> > QTImage 1.5
> > Thanks also to Armdo Fumero for the Spanish translation
> >
> > What's new?
> > Resizing the program in three ways
> > Added management of the Spanish language
> > Improved file import management
> > Added new wave effect
> > Added new function: image merging
> > Improved color management
> > New feature: invert colors
> > New X-ray effect
> > New feature: Quantization
> >
> > https://www.hunggartorino.it/ql/qtimage-2/
> > ___
> > QL-Users Mailing List
>
> Hi Gorgio,
>
> There ieems to bea problem with the ZIP-file.
>
> Fran?ois
>
>
> ___
> QL-Users Mailing List

--

Subject: Digest Footer

___
QL-Users mailing list

--

End of Ql-Users Digest, Vol 212, Issue 3

___
QL-Users Mailing List
```

### Re: [Ql-Users] QTImage 1.5

```There is some problem with the download permissions on the site :-( I try
to send you the zip

Il giorno sab 4 dic 2021 alle ore 21:48 François Van Emelen via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:

> Op 4/12/2021 om 18:34 schreef Giorgio Garabello via Ql-Users:
> >   After a year off for personal problems. back to the QL!
> > Thanks to the fantastic collaboration of Roberto Porro I finally publish
> > QTImage 1.5
> > Thanks also to Armdo Fumero for the Spanish translation
> >
> > What's new?
> > Resizing the program in three ways
> > Added management of the Spanish language
> > Improved file import management
> > Added new wave effect
> > Added new function: image merging
> > Improved color management
> > New feature: invert colors
> > New X-ray effect
> > New feature: Quantization
> >
> > https://www.hunggartorino.it/ql/qtimage-2/
> > ___
> > QL-Users Mailing List
>
> Hi Gorgio,
>
> There ieems to bea problem with the ZIP-file.
>
> François
>
>
> ___
> QL-Users Mailing List
___
QL-Users Mailing List
```

### Re: [Ql-Users] QTImage 1.5

```
Op 4/12/2021 om 18:34 schreef Giorgio Garabello via Ql-Users:

After a year off for personal problems. back to the QL!
Thanks to the fantastic collaboration of Roberto Porro I finally publish
QTImage 1.5
Thanks also to Armdo Fumero for the Spanish translation

What's new?
Resizing the program in three ways
Added management of the Spanish language
Improved file import management
Improved color management
New feature: invert colors
New X-ray effect
New feature: Quantization

https://www.hunggartorino.it/ql/qtimage-2/
___
QL-Users Mailing List

Hi Gorgio,

There ieems to bea problem with the ZIP-file.

François

___
QL-Users Mailing List
```

### [Ql-Users] QTImage 1.5

``` After a year off for personal problems. back to the QL!
Thanks to the fantastic collaboration of Roberto Porro I finally publish
QTImage 1.5
Thanks also to Armdo Fumero for the Spanish translation

What's new?
Resizing the program in three ways
Added management of the Spanish language
Improved file import management
Improved color management
New feature: invert colors
New X-ray effect
New feature: Quantization

https://www.hunggartorino.it/ql/qtimage-2/
___
QL-Users Mailing List

```

### Re: [Ql-Users] Q-Liberator v3.45

```
Op 29/11/2021 om 17:20 schreef Dilwyn Jones via Ql-Users:

Version 3.45 of the Q-Liberator BASIC compiler has been launched.

This version was submitted to me by Per Witte, who has done a fair bit
of work on rationalising the distribution, by splitting the compiler
into a runtime disk (what you need to compile programs) and a sources
disc, for those who like to study the sources of the compiler to see
how it works and who may like to co-operate on future development and
bug fixes.

In this new version 3.45 (or v3.45a as it appears on-screen), there is
a bug fix relating to Externals (compiled external procedures), where
the HISTORY_TXT file says that “A fixed location in Qlib_run was
sought but not found due to change in length of introduction string.”

There is no significant change to the functionality of the compiler
since the previous version.

The compiler is available to download as either floppy disc images or
as regular QL format zipped files for those whose systems don’t
support floppy disc images.

On the runtimes disc, the package is now split into a set of
directories with the documents in one directory, for example, and the
demo files in another directory. While fairly obvious, it does mean it
needs to be used on a system which support level 2 filing system – a
system supporting QL directories.

The runtime compiler disc is a single 720K disc image, while the
sources come on a larger 1.4MB disc image.

Q-Liberator v3.45 may be downloaded free of charge from my website at
http://www.dilwyn.me.uk/qlib/index.html . In case of difficulty, it
http://dilwyn.qlforum.co.uk/qlib/index.html . In both cases, scroll
down to the “QLiberator v3.45” section about halway down the page.

posterity, or in case issues with the current version force you to
revert to using an earlier version. The last full commercial version
of the compiler from publisher Liberation Software was v3.36.

Dilwyn.
___
QL-Users Mailing List

Hi,

Thanks to all who helped to update QLiberate 3.36

François Van Emelen

___
QL-Users Mailing List
```

### Re: [Ql-Users] QPC2 v5.02

```Hi,

>>> Just to chime in, the newest SMSQmulator (hopefully) to come out in a
>>> few days will do the same, i.e. treat NFA/SFA as win type.
>> Hm, I've just seen that Qubide is also another type. How about we
>> simply define our NFS/DOS devices as type "4" for "emulated" or
>> something? This should solve the QD problem, too.
>>
Sounds good to me. That way, no need to change SMSQE I'll just
update the info

> Good idea! But please, whatever you do, do it the same way for the same
> thing! :o)
>
> (Sorry for butting in here..)

That's the whole point of having this discussion here!

Anyway, the more the merrier.

Wolfgang
___
QL-Users Mailing List

```

### Re: [Ql-Users] QPC2 v5.02

```
On 01/12/2021 18:08, Marcel Kilgus via Ql-Users wrote:

Wolfgang Lenerz via Ql-Users wrote:

Hi,
Just to chime in, the newest SMSQmulator (hopefully) to come out in a
few days will do the same, i.e. treat NFA/SFA as win type.

Hm, I've just seen that Qubide is also another type. How about we
simply define our NFS/DOS devices as type "4" for "emulated" or
something? This should solve the QD problem, too.

Marcel

Good idea! But please, whatever you do, do it the same way for the
same thing! :o)

(Sorry for butting in here..)

Per
___
QL-Users Mailing List

```

### Re: [Ql-Users] QPC2 v5.02

```Wolfgang Lenerz via Ql-Users wrote:
> Hi,

> Just to chime in, the newest SMSQmulator (hopefully) to come out in a
> few days will do the same, i.e. treat NFA/SFA as win type.

Hm, I've just seen that Qubide is also another type. How about we
simply define our NFS/DOS devices as type "4" for "emulated" or
something? This should solve the QD problem, too.

Marcel

___
QL-Users Mailing List

```

### Re: [Ql-Users] QPC2 v5.02

```66 / 5000
Sorry for the delay in my reply .. yes, it seems like a great idea

Il giorno mar 30 nov 2021 alle ore 13:34 Wolfgang Lenerz via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:

> Hi,
>
> Just to chime in, the newest SMSQmulator (hopefully) to come out in a
> few days will do the same, i.e. treat NFA/SFA as win type.
>
>
> There is a reason for (at least for me):
>
> I use QD extensively.
> When QD saves data to a file, it first of all checks the device type via
> iof.xinf. If it detects that the drive is registered as a an msdos type
> device, it saves the file with line ending CR+LF, instead of the normal
> LF as used on win devices.
>
> If you now try to use the MacroAssembler to assemble a file that
> contains macros, this will fail (the MA seems to calculate the number of
> bytes it has got, which will be wrong as the NFA driver converts CF+LF
> to LF automagically) The MA then resets the file position to somewhere
> in the file, corresponding to the number of bytes before the macro (I
> suppose to read th emacro again) and that will be wrong, so that it
> reads something other in the file and then fails.
>
>
> That being said, might I make a suggestion?
>
> Giorgio said:
>
> >>>>The old behavior was that DMEDIUM_DRIVE returned -1 when pointing
> >>>> to a dos disk. it was not "correct" but it allowed me to distinguish
> the two
> >>> types.
>
> Indeed, that's not the right way, one should use the DMEDIUM_TYPE
> function for that (returns 1 - qdos, 2 - msdos etc) - but this won't
> help you, as that now returns "qdos" device type for dos and nfa/sfa.
>
> However, the specifications also provide for a device sub-type, which is
> not returned by any function and which, AFAIK is not used. One might
> possibly use that to return 1 or 2 as sub-type also.
>
> I'd be willing to create the new basic keyword for that in SMSQE
> ("DMEDIUM_STYPE").
>
> Would that be agreeable to all?
>
>
> Have fun!
>
> Wolfgang
>
>
>
> >>>> what do i need it for?
> >>>> I use it in a couple of programs .. in particular the new file manager
> >>> that
> >>>> I have created and which I think I will be able to publish in a few
> >>>> weeks. Obviously
> >>>> it works the same but in front of each device he placed an icon to be
> >>> able
> >>>> to identify it if cd / ram / win / dos It would be interesting to be
> >>>> able
> >>>> to distinguish all the types but obviously I have no idea of the work
> >>> this
> >>>> entails. Mine is not a criticism, I'm just chatting.
> >>>>
> >>>> Giorgio
> >>>>
> >>>> Il giorno ven 26 nov 2021 alle ore 10:09 Marcel Kilgus via Ql-Users <
> >>>> ql-users@lists.q-v-d.com> ha scritto:
> >>>>
> >>>>> Giorgio Garabello via Ql-Users wrote:
> >>>>>>> I uploaded a small bugfix release QPC2v5.02.
> >>>>>>>
> >>>>>>> Switch DMEDIUM_FORMAT for the DOS device to 1 (QDOS) instead of 2
> >>>>>> I have a doubt, how can I now recognize a DOS disk from a WIN one?
> >>>>> It has been this way for 20 years, I just reverted it back to the
> >>>>> old behavior.
> >>>>>
> >>>>> Why would you want to recognize a DOS disk from a WIN one?
> >>>>>
> >>>>> Marcel
> >>>>>
> >>>>> ___
> >>>>> QL-Users Mailing List
> >>>>>
> >>>> ___
> >>>> QL-Users Mailing List
> >>>> .
> >>> ___
> >>> QL-Users Mailing List
> >>>
> >> ___
> >> QL-Users Mailing List
> >>
> > ___
> > QL-Users Mailing List
> >
> ___
> QL-Users Mailing List
___
QL-Users Mailing List

```

### Re: [Ql-Users] QPC2 v5.02

```
Op 30/11/2021 om 21:14 schreef Wolfgang Lenerz via Ql-Users:

Hi François,

This will be fixed.

Have fun!

Wolfgang

Op 30/11/2021 om 13:34 schreef Wolfgang Lenerz via Ql-Users:

Hi,

Just to chime in, the newest SMSQmulator (hopefully) to come out in a
few days will do the same, i.e. treat NFA/SFA as win type.

There is a reason for (at least for me):

I use QD extensively.
When QD saves data to a file, it first of all checks the device type via
iof.xinf. If it detects that the drive is registered as a an msdos type
device, it saves the file with line ending CR+LF, instead of the normal
LF as used on win devices.

If you now try to use the MacroAssembler to assemble a file that
contains macros, this will fail (the MA seems to calculate the number of
bytes it has got, which will be wrong as the NFA driver converts CF+LF
to LF automagically) The MA then resets the file position to somewhere
in the file, corresponding to the number of bytes before the macro (I
suppose to read th emacro again) and that will be wrong, so that it
reads something other in the file and then fails.

That being said, might I make a suggestion?

Giorgio said:

The old behavior was that DMEDIUM_DRIVE returned -1 when pointing
to a dos disk. it was not "correct" but it allowed me to
distinguish the two

types.

Indeed, that's not the right way, one should use the DMEDIUM_TYPE
function for that (returns 1 - qdos, 2 - msdos etc) - but this won't
help you, as that now returns "qdos" device type for dos and nfa/sfa.

However, the specifications also provide for a device sub-type, which is
not returned by any function and which, AFAIK is not used. One might
possibly use that to return 1 or 2 as sub-type also.

I'd be willing to create the new basic keyword for that in SMSQE
("DMEDIUM_STYPE").

Would that be agreeable to all?

Have fun!

Wolfgang

Hi Wolfgang,

While working on the next version of SMSQmulator could you verify if
LBYTES works correctly on your  system?

LBYTES  Filename_scr,SCR_SCR_BASE seems to lock SMSQmulator: SO TAKE CARE

100 WINDOW SCR_XLIM,SCR_YLIM,0,0
105 REMark
110 REMark OPEN_IN#3,dev1_bckgrnd_wallpaper_def:INPUT#3,p\$:CLOSE#3
120 :
125 SBYTES_O dev1_dump_scr,SCR_BASE,SCR_LLEN*SCR_YLIM
130 :
135 REMark  dev1_dump_scr  can be displayed correctly in QPC2
140 REMark with LBYTES dev1_dump_scr,scr_base
145 :
150 REMark but locks SMSQmulator
155 REMark dump_scr is 4147200 long
160 REMark Screen size 1920x1080
165 REMark window mode fullscreen

Thanks

François Van Emelen

___
QL-Users Mailing List

___
QL-Users Mailing List

thank you

François Van Emelen

___
QL-Users Mailing List
```

### Re: [Ql-Users] QPC2 v5.02

```Hi François,

This will be fixed.

Have fun!

Wolfgang

> Op 30/11/2021 om 13:34 schreef Wolfgang Lenerz via Ql-Users:
>> Hi,
>>
>> Just to chime in, the newest SMSQmulator (hopefully) to come out in a
>> few days will do the same, i.e. treat NFA/SFA as win type.
>>
>>
>> There is a reason for (at least for me):
>>
>> I use QD extensively.
>> When QD saves data to a file, it first of all checks the device type via
>> iof.xinf. If it detects that the drive is registered as a an msdos type
>> device, it saves the file with line ending CR+LF, instead of the normal
>> LF as used on win devices.
>>
>> If you now try to use the MacroAssembler to assemble a file that
>> contains macros, this will fail (the MA seems to calculate the number of
>> bytes it has got, which will be wrong as the NFA driver converts CF+LF
>> to LF automagically) The MA then resets the file position to somewhere
>> in the file, corresponding to the number of bytes before the macro (I
>> suppose to read th emacro again) and that will be wrong, so that it
>> reads something other in the file and then fails.
>>
>>
>> That being said, might I make a suggestion?
>>
>> Giorgio said:
>>
>>>>>>     The old behavior was that DMEDIUM_DRIVE returned -1 when pointing
>>>>>> to a dos disk. it was not "correct" but it allowed me to
>>>>>> distinguish the two
>>>>> types.
>> Indeed, that's not the right way, one should use the DMEDIUM_TYPE
>> function for that (returns 1 - qdos, 2 - msdos etc) - but this won't
>> help you, as that now returns "qdos" device type for dos and nfa/sfa.
>>
>> However, the specifications also provide for a device sub-type, which is
>> not returned by any function and which, AFAIK is not used. One might
>> possibly use that to return 1 or 2 as sub-type also.
>>
>> I'd be willing to create the new basic keyword for that in SMSQE
>> ("DMEDIUM_STYPE").
>>
>> Would that be agreeable to all?
>>
>>
>> Have fun!
>>
>> Wolfgang
>>
>>
>
>
> Hi Wolfgang,
>
> While working on the next version of SMSQmulator could you verify if
> LBYTES works correctly on your  system?
>
> LBYTES  Filename_scr,SCR_SCR_BASE seems to lock SMSQmulator: SO TAKE CARE
>
> 100 WINDOW SCR_XLIM,SCR_YLIM,0,0
> 105 REMark
> 110 REMark OPEN_IN#3,dev1_bckgrnd_wallpaper_def:INPUT#3,p\$:CLOSE#3
> 120 :
> 125 SBYTES_O dev1_dump_scr,SCR_BASE,SCR_LLEN*SCR_YLIM
> 130 :
> 135 REMark  dev1_dump_scr  can be displayed correctly in QPC2
> 140 REMark with LBYTES dev1_dump_scr,scr_base
> 145 :
> 150 REMark but locks SMSQmulator
> 155 REMark dump_scr is 4147200 long
> 160 REMark Screen size 1920x1080
> 165 REMark window mode fullscreen
>
> Thanks
>
> François Van Emelen
>
> ___
> QL-Users Mailing List
___
QL-Users Mailing List
```

### Re: [Ql-Users] QPC2 v5.02

```
Op 30/11/2021 om 13:34 schreef Wolfgang Lenerz via Ql-Users:

Hi,

Just to chime in, the newest SMSQmulator (hopefully) to come out in a
few days will do the same, i.e. treat NFA/SFA as win type.

There is a reason for (at least for me):

I use QD extensively.
When QD saves data to a file, it first of all checks the device type via
iof.xinf. If it detects that the drive is registered as a an msdos type
device, it saves the file with line ending CR+LF, instead of the normal
LF as used on win devices.

If you now try to use the MacroAssembler to assemble a file that
contains macros, this will fail (the MA seems to calculate the number of
bytes it has got, which will be wrong as the NFA driver converts CF+LF
to LF automagically) The MA then resets the file position to somewhere
in the file, corresponding to the number of bytes before the macro (I
suppose to read th emacro again) and that will be wrong, so that it
reads something other in the file and then fails.

That being said, might I make a suggestion?

Giorgio said:

The old behavior was that DMEDIUM_DRIVE returned -1 when pointing
to a dos disk. it was not "correct" but it allowed me to distinguish the two

types.

Indeed, that's not the right way, one should use the DMEDIUM_TYPE
function for that (returns 1 - qdos, 2 - msdos etc) - but this won't
help you, as that now returns "qdos" device type for dos and nfa/sfa.

However, the specifications also provide for a device sub-type, which is
not returned by any function and which, AFAIK is not used. One might
possibly use that to return 1 or 2 as sub-type also.

I'd be willing to create the new basic keyword for that in SMSQE
("DMEDIUM_STYPE").

Would that be agreeable to all?

Have fun!

Wolfgang

Hi Wolfgang,

While working on the next version of SMSQmulator could you verify if
LBYTES works correctly on your  system?

LBYTES  Filename_scr,SCR_SCR_BASE seems to lock SMSQmulator: SO TAKE CARE

100 WINDOW SCR_XLIM,SCR_YLIM,0,0
105 REMark
110 REMark OPEN_IN#3,dev1_bckgrnd_wallpaper_def:INPUT#3,p\$:CLOSE#3
120 :
125 SBYTES_O dev1_dump_scr,SCR_BASE,SCR_LLEN*SCR_YLIM
130 :
135 REMark  dev1_dump_scr  can be displayed correctly in QPC2
140 REMark with LBYTES dev1_dump_scr,scr_base
145 :
150 REMark but locks SMSQmulator
155 REMark dump_scr is 4147200 long
160 REMark Screen size 1920x1080
165 REMark window mode fullscreen

Thanks

François Van Emelen

___
QL-Users Mailing List
```

### Re: [Ql-Users] QPC2 v5.02

```Hi,

Just to chime in, the newest SMSQmulator (hopefully) to come out in a
few days will do the same, i.e. treat NFA/SFA as win type.

There is a reason for (at least for me):

I use QD extensively.
When QD saves data to a file, it first of all checks the device type via
iof.xinf. If it detects that the drive is registered as a an msdos type
device, it saves the file with line ending CR+LF, instead of the normal
LF as used on win devices.

If you now try to use the MacroAssembler to assemble a file that
contains macros, this will fail (the MA seems to calculate the number of
bytes it has got, which will be wrong as the NFA driver converts CF+LF
to LF automagically) The MA then resets the file position to somewhere
in the file, corresponding to the number of bytes before the macro (I
suppose to read th emacro again) and that will be wrong, so that it
reads something other in the file and then fails.

That being said, might I make a suggestion?

Giorgio said:

>>>>    The old behavior was that DMEDIUM_DRIVE returned -1 when pointing
>>>> to a dos disk. it was not "correct" but it allowed me to distinguish the
>>>> two
>>> types.

Indeed, that's not the right way, one should use the DMEDIUM_TYPE
function for that (returns 1 - qdos, 2 - msdos etc) - but this won't
help you, as that now returns "qdos" device type for dos and nfa/sfa.

However, the specifications also provide for a device sub-type, which is
not returned by any function and which, AFAIK is not used. One might
possibly use that to return 1 or 2 as sub-type also.

I'd be willing to create the new basic keyword for that in SMSQE
("DMEDIUM_STYPE").

Would that be agreeable to all?

Have fun!

Wolfgang

>>>> what do i need it for?
>>>> I use it in a couple of programs .. in particular the new file manager
>>> that
>>>> I have created and which I think I will be able to publish in a few
>>>> weeks. Obviously
>>>> it works the same but in front of each device he placed an icon to be
>>> able
>>>> to identify it if cd / ram / win / dos It would be interesting to be
>>>> able
>>>> to distinguish all the types but obviously I have no idea of the work
>>> this
>>>> entails. Mine is not a criticism, I'm just chatting.
>>>>
>>>> Giorgio
>>>>
>>>> Il giorno ven 26 nov 2021 alle ore 10:09 Marcel Kilgus via Ql-Users <
>>>> ql-users@lists.q-v-d.com> ha scritto:
>>>>
>>>>> Giorgio Garabello via Ql-Users wrote:
>>>>>>> I uploaded a small bugfix release QPC2v5.02.
>>>>>>>
>>>>>>> Switch DMEDIUM_FORMAT for the DOS device to 1 (QDOS) instead of 2
>>>>>> I have a doubt, how can I now recognize a DOS disk from a WIN one?
>>>>> It has been this way for 20 years, I just reverted it back to the
>>>>> old behavior.
>>>>>
>>>>> Why would you want to recognize a DOS disk from a WIN one?
>>>>>
>>>>> Marcel
>>>>>
>>>>> ___
>>>>> QL-Users Mailing List
>>>>>
>>>> ___
>>>> QL-Users Mailing List
>>>> .
>>> ___
>>> QL-Users Mailing List
>>>
>> ___
>> QL-Users Mailing List
>>
> ___
> QL-Users Mailing List
>
___
QL-Users Mailing List
```

### [Ql-Users] Q-Liberator v3.45

```Version 3.45 of the Q-Liberator BASIC compiler has been launched.

This version was submitted to me by Per Witte, who has done a fair bit
of work on rationalising the distribution, by splitting the compiler
into a runtime disk (what you need to compile programs) and a sources
disc, for those who like to study the sources of the compiler to see
how it works and who may like to co-operate on future development and
bug fixes.

In this new version 3.45 (or v3.45a as it appears on-screen), there is
a bug fix relating to Externals (compiled external procedures), where
the HISTORY_TXT file says that “A fixed location in Qlib_run was
sought but not found due to change in length of introduction string.”

There is no significant change to the functionality of the compiler
since the previous version.

The compiler is available to download as either floppy disc images or
as regular QL format zipped files for those whose systems don’t
support floppy disc images.

On the runtimes disc, the package is now split into a set of
directories with the documents in one directory, for example, and the
demo files in another directory. While fairly obvious, it does mean it
needs to be used on a system which support level 2 filing system – a
system supporting QL directories.

The runtime compiler disc is a single 720K disc image, while the
sources come on a larger 1.4MB disc image.

Q-Liberator v3.45 may be downloaded free of charge from my website at
http://www.dilwyn.me.uk/qlib/index.html . In case of difficulty, it
http://dilwyn.qlforum.co.uk/qlib/index.html . In both cases, scroll
down to the “QLiberator v3.45” section about halway down the page.

posterity, or in case issues with the current version force you to
revert to using an earlier version. The last full commercial version
of the compiler from publisher Liberation Software was v3.36.

Dilwyn.
___
QL-Users Mailing List
```

### Re: [Ql-Users] QPC2 v5.02

```My DevGet subroutine (www.Knoware.no/htm/basic.htm) demonstrates how
you can always get the real device name.

Per

On 26/11/2021 10:59, Giorgio Garabello via Ql-Users wrote:

It is not a safe method, it can be renamed from DOS_USE

Giorgio

Il giorno ven 26 nov 2021 alle ore 10:49 pjwitte via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:

Giorgio,

Use the device name to make the distinction: If its called DOS, then
its DOS, etc.
Per

On 26/11/2021 10:28, Giorgio Garabello via Ql-Users wrote:

The old behavior was that DMEDIUM_DRIVE returned -1 when pointing to a

dos

disk. it was not "correct" but it allowed me to distinguish the two

types.

what do i need it for?
I use it in a couple of programs .. in particular the new file manager

that

I have created and which I think I will be able to publish in a few
weeks. Obviously
it works the same but in front of each device he placed an icon to be

able

to identify it if cd / ram / win / dos It would be interesting to be able
to distinguish all the types but obviously I have no idea of the work

this

entails. Mine is not a criticism, I'm just chatting.

Giorgio

Il giorno ven 26 nov 2021 alle ore 10:09 Marcel Kilgus via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:

Giorgio Garabello via Ql-Users wrote:

I uploaded a small bugfix release QPC2v5.02.

Switch DMEDIUM_FORMAT for the DOS device to 1 (QDOS) instead of 2

I have a doubt, how can I now recognize a DOS disk from a WIN one?

It has been this way for 20 years, I just reverted it back to the
old behavior.

Why would you want to recognize a DOS disk from a WIN one?

Marcel

___
QL-Users Mailing List

___
QL-Users Mailing List
.

___
QL-Users Mailing List

___
QL-Users Mailing List

___
QL-Users Mailing List

```

### Re: [Ql-Users] QPC2 v5.02

``` It is not a safe method, it can be renamed from DOS_USE

Giorgio

Il giorno ven 26 nov 2021 alle ore 10:49 pjwitte via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:

> Giorgio,
>
> Use the device name to make the distinction: If its called DOS, then
> its DOS, etc.
> Per
>
> On 26/11/2021 10:28, Giorgio Garabello via Ql-Users wrote:
> >   The old behavior was that DMEDIUM_DRIVE returned -1 when pointing to a
> dos
> > disk. it was not "correct" but it allowed me to distinguish the two
> types.
> > what do i need it for?
> > I use it in a couple of programs .. in particular the new file manager
> that
> > I have created and which I think I will be able to publish in a few
> > weeks. Obviously
> > it works the same but in front of each device he placed an icon to be
> able
> > to identify it if cd / ram / win / dos It would be interesting to be able
> > to distinguish all the types but obviously I have no idea of the work
> this
> > entails. Mine is not a criticism, I'm just chatting.
> >
> > Giorgio
> >
> > Il giorno ven 26 nov 2021 alle ore 10:09 Marcel Kilgus via Ql-Users <
> > ql-users@lists.q-v-d.com> ha scritto:
> >
> >> Giorgio Garabello via Ql-Users wrote:
> >>>> I uploaded a small bugfix release QPC2v5.02.
> >>>>
> >>>> Switch DMEDIUM_FORMAT for the DOS device to 1 (QDOS) instead of 2
> >>> I have a doubt, how can I now recognize a DOS disk from a WIN one?
> >> It has been this way for 20 years, I just reverted it back to the
> >> old behavior.
> >>
> >> Why would you want to recognize a DOS disk from a WIN one?
> >>
> >> Marcel
> >>
> >> ___
> >> QL-Users Mailing List
> >>
> > ___
> > QL-Users Mailing List
> > .
>
> ___
> QL-Users Mailing List
>
___
QL-Users Mailing List

```

### Re: [Ql-Users] QPC2 v5.02

```
Giorgio,

Use the device name to make the distinction: If its called DOS, then
its DOS, etc.

Per

On 26/11/2021 10:28, Giorgio Garabello via Ql-Users wrote:

The old behavior was that DMEDIUM_DRIVE returned -1 when pointing to a dos
disk. it was not "correct" but it allowed me to distinguish the two types.
what do i need it for?
I use it in a couple of programs .. in particular the new file manager that
I have created and which I think I will be able to publish in a few
weeks. Obviously
it works the same but in front of each device he placed an icon to be able
to identify it if cd / ram / win / dos It would be interesting to be able
to distinguish all the types but obviously I have no idea of the work this
entails. Mine is not a criticism, I'm just chatting.

Giorgio

Il giorno ven 26 nov 2021 alle ore 10:09 Marcel Kilgus via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:

Giorgio Garabello via Ql-Users wrote:

I uploaded a small bugfix release QPC2v5.02.

Switch DMEDIUM_FORMAT for the DOS device to 1 (QDOS) instead of 2

I have a doubt, how can I now recognize a DOS disk from a WIN one?

It has been this way for 20 years, I just reverted it back to the
old behavior.

Why would you want to recognize a DOS disk from a WIN one?

Marcel

___
QL-Users Mailing List

___
QL-Users Mailing List
.

___
QL-Users Mailing List

```

### Re: [Ql-Users] QPC2 v5.02

``` The old behavior was that DMEDIUM_DRIVE returned -1 when pointing to a dos
disk. it was not "correct" but it allowed me to distinguish the two types.
what do i need it for?
I use it in a couple of programs .. in particular the new file manager that
I have created and which I think I will be able to publish in a few
weeks. Obviously
it works the same but in front of each device he placed an icon to be able
to identify it if cd / ram / win / dos It would be interesting to be able
to distinguish all the types but obviously I have no idea of the work this
entails. Mine is not a criticism, I'm just chatting.

Giorgio

Il giorno ven 26 nov 2021 alle ore 10:09 Marcel Kilgus via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:

> Giorgio Garabello via Ql-Users wrote:
> >> I uploaded a small bugfix release QPC2v5.02.
> >>
> >> Switch DMEDIUM_FORMAT for the DOS device to 1 (QDOS) instead of 2
> > I have a doubt, how can I now recognize a DOS disk from a WIN one?
>
> It has been this way for 20 years, I just reverted it back to the
> old behavior.
>
> Why would you want to recognize a DOS disk from a WIN one?
>
> Marcel
>
> ___
> QL-Users Mailing List
>
___
QL-Users Mailing List

```

### Re: [Ql-Users] QPC2 v5.02

```Giorgio Garabello via Ql-Users wrote:
>> I uploaded a small bugfix release QPC2v5.02.
>>
>> Switch DMEDIUM_FORMAT for the DOS device to 1 (QDOS) instead of 2
> I have a doubt, how can I now recognize a DOS disk from a WIN one?

It has been this way for 20 years, I just reverted it back to the
old behavior.

Why would you want to recognize a DOS disk from a WIN one?

Marcel

___
QL-Users Mailing List

```

### Re: [Ql-Users] QPC2 v5.02

```Il giorno gio 25 nov 2021 alle ore 18:40 Marcel Kilgus via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:

> I uploaded a small bugfix release QPC2v5.02.
>
> Switch DMEDIUM_FORMAT for the DOS device to 1 (QDOS) instead of 2

I have a doubt, how can I now recognize a DOS disk from a WIN one?

Giorgio
___
QL-Users Mailing List

```

### Re: [Ql-Users] QPC2 v5.02

``` Thank You Ever so Much   Marcel for the Update of QPC2
Thanks Again
Simon Foster
On Thursday, 25 November 2021, 17:40:21 GMT, Marcel Kilgus via Ql-Users
wrote:

I uploaded a small bugfix release QPC2v5.02.

Switch DMEDIUM_FORMAT for the DOS device to 1 (QDOS) instead of 2
(MS-DOS) because QD switches to different line endings on MS-DOS
drives and that confuses other applications.

Also fixed direct SBYTES to screen from WIN/FLP/DOS devices.

Enjoy, Marcel

___
QL-Users Mailing List

___
QL-Users Mailing List
```

### [Ql-Users] QPC2 v5.02

```I uploaded a small bugfix release QPC2v5.02.

Switch DMEDIUM_FORMAT for the DOS device to 1 (QDOS) instead of 2
(MS-DOS) because QD switches to different line endings on MS-DOS
drives and that confuses other applications.

Also fixed direct SBYTES to screen from WIN/FLP/DOS devices.

Enjoy, Marcel

___
QL-Users Mailing List

```

### Re: [Ql-Users] SMSQmulator <> LBYTES filename_scr,SCR_BASE

```
Op 24/11/2021 om 15:40 schreef desin via Ql-Users:

Am 24.11.21 um 11:40 schrieb François Van Emelen via Ql-Users:

Hi,

SMSQmulator locks when trying to display a valid SCR-file with LBYTES
filename,SCR_BASE.

set SMSQemulator to :

scr_size 512x256
QL colours
allow Ql Screen emulation

Hope it helps

Markus
___
QL-Users Mailing List

Hi Markus,

Problem solved. Yhank you.

François Van Emelen

___
QL-Users Mailing List
```

### Re: [Ql-Users] SMSQmulator <> LBYTES filename_scr,SCR_BASE

```
Am 24.11.21 um 11:40 schrieb François Van Emelen via Ql-Users:

Hi,

SMSQmulator locks when trying to display a valid SCR-file with LBYTES
filename,SCR_BASE.

set SMSQemulator to :

scr_size 512x256
QL colours
allow Ql Screen emulation

Hope it helps

Markus
___
QL-Users Mailing List
```

### [Ql-Users] SMSQmulator <> LBYTES filename_scr,SCR_BASE

```
Hi,

SMSQmulator locks when trying to display a valid SCR-file with LBYTES
filename,SCR_BASE.

There is no problem with the same file in QPC2.

Can someone confirm this?

Help is welcome.

François Van Emelen

___
QL-Users Mailing List
```

### [Ql-Users] Urs

```Did you ever try and decode the chips I had to mail??

Paul Holmgren
JCI #74145
CPUs run on smoke. I know this because when the smoke comes out, it stops
working.
___
QL-Users Mailing List

```

### Re: [Ql-Users] Knoware

```Thanks to all for positive feedback! Im glad so many of us are still
active and keeping the show on the road in lots of different ways!

Per

On 22/11/2021 19:42, Urs Koenig (QL) via Ql-Users wrote:

Per wrote:

Thereve been some changes to Knoware since the last announced update.

Wow, many 2021 updates. A lot to explore in the cold winter times.

Keep on doing the good work and keep Knoware alive!

I did little QL in summer/autumn due to both family and work reasons, but
recently started working on the next release of QL/E where I consider to
install at least some of your tools.

Cheers,
Urs

QL forever!
http://www.sinclairql.net/  - Go and get THE DISTRIBUTION & QL/E!
Sinclair, QL, ATARI, JAGUAR, NUON, APPLE, NeXT, MIST & much more...

___
QL-Users Mailing List
.

___
QL-Users Mailing List

```

### Re: [Ql-Users] Knoware

```Per wrote:
> Thereve been some changes to Knoware since the last announced update.
Wow, many 2021 updates. A lot to explore in the cold winter times.

Keep on doing the good work and keep Knoware alive!

I did little QL in summer/autumn due to both family and work reasons, but
recently started working on the next release of QL/E where I consider to
install at least some of your tools.

Cheers,
Urs

QL forever!
http://www.sinclairql.net/ - Go and get THE DISTRIBUTION & QL/E!
Sinclair, QL, ATARI, JAGUAR, NUON, APPLE, NeXT, MIST & much more...

___
QL-Users Mailing List

```

### Re: [Ql-Users] Knoware

```Hi,

ooo, lots of new goodies to discover...

Thanks

Wolfgang

On 22/11/2021 11:58, pjwitte via Ql-Users wrote:
> Thereve been some changes to Knoware since the last announced update.
> (https://knoware.no/htm/changes.htm)
>
> Per
> ___
> QL-Users Mailing List
>
___
QL-Users Mailing List

```

### Re: [Ql-Users] Knoware

``` Fantastic! Thanks for what you do for us!
Giorgio

Il giorno lun 22 nov 2021 alle ore 11:58 pjwitte via Ql-Users <
ql-users@lists.q-v-d.com> ha scritto:

> Thereve been some changes to Knoware since the last announced update.
> (https://knoware.no/htm/changes.htm)
>
> Per
> ___
> QL-Users Mailing List
>
___
QL-Users Mailing List

```

### [Ql-Users] Knoware

```
Thereve been some changes to Knoware since the last announced update.
(https://knoware.no/htm/changes.htm)

Per
___
QL-Users Mailing List

```

### [Ql-Users] Assembly eComic - Issue 9, Now available

```Well, I managed to get two issues into 2021! This is the latest and
probably the final one for this year. What can we find in Issue 9? Well:

QL2WIN - a utility to convert from QL line ends to Windows line ends
when transferring text files between systems. This is one I wrote for
myself, but these days, many Windows editors are happy to load and save
in Linux format -- similar to what the QL uses.

WIN2QL - a utility to go the other way!

Circular Buffers - a fairly long chapter explaining how circular buffers
work and some code to enable them to be used on the QL. Are they useful?
You tell me!

As ever, if you only want to read the issue, grab the PDF and the code
file if necessary. If you want to checkout the LaTeX and LyX source code
used to build each issue, then grab the zip or bz2 file. The PDF and
Code.zip files will be included so you don;t have to download them
separately.

This is the link to the release:
https://github.com/NormanDunbar/QLAssemblyLanguageMagazine/releases/tag/Issue_9

Cheers,
Norm.
--
Norman Dunbar
Dunbar IT Consultants Ltd

27a Lidget Hill
Pudsey
West Yorkshire
United Kingdom
LS28 7LG

Company Number: 05132767
___
QL-Users Mailing List

```

### Re: [Ql-Users] Windows 11 and emulators

```
Sorted!
Thanks to all who tried to help!
Some details here, if youre interested:
https://qlforum.co.uk/viewtopic.php?f=19=3965=44294#p44292

Per
On 08/11/2021 23:53, pjwitte via Ql-Users wrote:

I'll post one on the forum
Per

On 08/11/2021 23:07, Marcel Kilgus via Ql-Users wrote:

pjwitte via Ql-Users wrote:
Thanks, Marcel. I arrived there by a different route, but no, it
doesnt work for me.

OK. I'll ask if there is a Windows 11 VM I can use at work to see it
myself. I can't even find many pictures of it online.

Marcel

___
QL-Users Mailing List

___
QL-Users Mailing List

___
QL-Users Mailing List

```

### Re: [Ql-Users] Windows 11 and emulators

```
I'll post one on the forum
Per

On 08/11/2021 23:07, Marcel Kilgus via Ql-Users wrote:

pjwitte via Ql-Users wrote:

Thanks, Marcel. I arrived there by a different route, but no, it doesnt work
for me.

OK. I'll ask if there is a Windows 11 VM I can use at work to see it
myself. I can't even find many pictures of it online.

Marcel

___
QL-Users Mailing List

___
QL-Users Mailing List

```

### Re: [Ql-Users] Windows 11 and emulators

```pjwitte via Ql-Users wrote:
> Thanks, Marcel. I arrived there by a different route, but no, it doesnt work
> for me.

OK. I'll ask if there is a Windows 11 VM I can use at work to see it
myself. I can't even find many pictures of it online.

Marcel

___
QL-Users Mailing List

```

### Re: [Ql-Users] Windows 11 and emulators

```Hi Per

I tried to updgrade Windows 10 Pro on a Intel Core i5 PC, but it seems the CPU
is not supported. I guess that I need a new PC, but I really do want to buy any
more hardware.

I only use Winfows 10 for use of Altium Designer, however, KiCad  gEDA does the
same, without licencing.

So I will get rid of Microsoft and use a Linux.

Apple ... no thanks, just another UNIX system, that you have to pay throught
the nose more than Microsoft.
---
Regards,
Derek

On 8 November 2021 17:52:35 GMT, pjwitte via Ql-Users
wrote:
>Hi Derek,
>
>On 08/11/2021 16:14, Derek via Ql-Users wrote:
>> Hi
>>
>> I used repair Windows software problems, so I can maybe help.
>So did I back in the heady days of W95 and NT4 ;o)
>> Can the service not be disabled, or msybe removed.
>I dont particularly want it removed. I need to see whats going on or
>Id have to test the keyboard every time before, say, typing a password.
>> I have a Windows 10 Pro PC, which I could upgrade to see if Ican solve your
>> problem.
>
>I wouldnt wish that on you ;o) But thanks for the offer. I see plenty
>of other people are complaining, so perhaps it may get fixed without
>extortion.
>
>I guess its going to get harder and harder to workaround the
>encroachment of the worst kinds of futures.. I dont see QLing on an
>iPhone as a viable option..
>
>Per
>
>> ---
>> Regards,
>> Derek
>>
>> On 8 November 2021 13:39:36 GMT, pjwitte via
>> Ql-Users  wrote:
>>> On 08/11/2021 14:11, Marcel Kilgus via Ql-Users wrote:
>>>> pjwitte via Ql-Users wrote:
>>>>>> I don't have Windows 11 and I find very little on the subject online.
>>>>>> I have no idea how I could hide the blob, but as far as I can see the
>>>>>> feature can be disabled, can it not?
>>>>>>
>>>>> Sure you can turn it off, but then 50% of the time I'll be typing
>>>>> half sentences and passwords in the wrong character set! (Not for
>>>>> nothing do people go retro-fitting caps lock LEDs to their QLs.. But this
>>>>> is worse..)
>>>> As far as I understood the posting was that the behaviour can be
>>>> reverted to the "old" one and not the floating thingie.
>>>>
>>>> Marcel
>>>>
>>> Thanks, Marcel. I arrived there by a different route, but no, it
>>> doesnt work for me.
>>>
>>> Im now looking for the small print, where it no doubt says something
>>> along the lines of "This feature is brought to you sponsored by the
>>> WannaCry software team.."  :oD
>>>
>>> Per
>>> ___
>>> QL-Users Mailing List
>> ___
>> QL-Users Mailing List
>
>___
>QL-Users Mailing List
___
QL-Users Mailing List
```

### Re: [Ql-Users] Windows 11 and emulators

```
Hi Derek,

On 08/11/2021 16:14, Derek via Ql-Users wrote:

Hi

I used repair Windows software problems, so I can maybe help.

So did I back in the heady days of W95 and NT4 ;o)

Can the service not be disabled, or msybe removed.
I dont particularly want it removed. I need to see whats going on or
Id have to test the keyboard every time before, say, typing a password.

I have a Windows 10 Pro PC, which I could upgrade to see if Ican solve your
problem.

I wouldnt wish that on you ;o) But thanks for the offer. I see plenty
of other people are complaining, so perhaps it may get fixed without
extortion.

I guess its going to get harder and harder to workaround the
encroachment of the worst kinds of futures.. I dont see QLing on an
iPhone as a viable option..

Per

---
Regards,
Derek

On 8 November 2021 13:39:36 GMT, pjwitte via Ql-Users
wrote:

On 08/11/2021 14:11, Marcel Kilgus via Ql-Users wrote:

pjwitte via Ql-Users wrote:

I don't have Windows 11 and I find very little on the subject online.
I have no idea how I could hide the blob, but as far as I can see the
feature can be disabled, can it not?

Sure you can turn it off, but then 50% of the time I'll be typing
half sentences and passwords in the wrong character set! (Not for
nothing do people go retro-fitting caps lock LEDs to their QLs.. But this is
worse..)

As far as I understood the posting was that the behaviour can be
reverted to the "old" one and not the floating thingie.

Marcel

Thanks, Marcel. I arrived there by a different route, but no, it
doesnt work for me.

Im now looking for the small print, where it no doubt says something
along the lines of "This feature is brought to you sponsored by the
WannaCry software team.."  :oD

Per
___
QL-Users Mailing List

___
QL-Users Mailing List

___
QL-Users Mailing List
```

### Re: [Ql-Users] Windows 11 and emulators

```Hi

I used repair Windows software problems, so I can maybe help.

Can the service not be disabled, or msybe removed.

I have a Windows 10 Pro PC, which I could upgrade to see if Ican solve your
problem.

---
Regards,
Derek

On 8 November 2021 13:39:36 GMT, pjwitte via Ql-Users
wrote:
>On 08/11/2021 14:11, Marcel Kilgus via Ql-Users wrote:
>> pjwitte via Ql-Users wrote:
>>>> I don't have Windows 11 and I find very little on the subject online.
>>>> I have no idea how I could hide the blob, but as far as I can see the
>>>> feature can be disabled, can it not?
>>>>
>>> Sure you can turn it off, but then 50% of the time I'll be typing
>>> half sentences and passwords in the wrong character set! (Not for
>>> nothing do people go retro-fitting caps lock LEDs to their QLs.. But this
>>> is worse..)
>> As far as I understood the posting was that the behaviour can be
>> reverted to the "old" one and not the floating thingie.
>>
>> Marcel
>>
>Thanks, Marcel. I arrived there by a different route, but no, it
>doesnt work for me.
>
>Im now looking for the small print, where it no doubt says something
>along the lines of "This feature is brought to you sponsored by the
>WannaCry software team.."  :oD
>
>Per
>___
>QL-Users Mailing List
___
QL-Users Mailing List
```

### Re: [Ql-Users] Windows 11 and emulators

```
On 08/11/2021 14:11, Marcel Kilgus via Ql-Users wrote:

pjwitte via Ql-Users wrote:

I don't have Windows 11 and I find very little on the subject online.
I have no idea how I could hide the blob, but as far as I can see the
feature can be disabled, can it not?

Sure you can turn it off, but then 50% of the time I'll be typing
half sentences and passwords in the wrong character set! (Not for
nothing do people go retro-fitting caps lock LEDs to their QLs.. But this is
worse..)

As far as I understood the posting was that the behaviour can be
reverted to the "old" one and not the floating thingie.

Marcel

Thanks, Marcel. I arrived there by a different route, but no, it
doesnt work for me.

Im now looking for the small print, where it no doubt says something
along the lines of "This feature is brought to you sponsored by the
WannaCry software team.."  :oD

Per
___
QL-Users Mailing List
```