Re: [Ql-Users] Save problems with QPC2, QD, QPAC2 or SMSQm8

[Bob Spelten via Ql-Users]

Derek via Ql-Users wrote:

Hi,

I usually limit my QWA files to a maximum of 512MB, which usually suits my 
needs.

What recommended size of a QWA file?
---
Regards,
Derek


Thanks all for the advice given.
The fresh backup WIN2 has room enough to continue working on for now.
I limit my WINs to 256MB, which has a more efficient block size for the 
usually smaller QL files and is quicker when making a backup WIN.

Besides one can always mount an extra WIN.

Bob


___
QL-Users Mailing List




--
Dit e-mailbericht is met AVG-antivirussoftware gecontroleerd op virussen.
www.avg.com
___
QL-Users Mailing List

Re: [Ql-Users] Save problems with QPC2, QD, QPAC2 or SMSQm8

[Bob Spelten via Ql-Users]

Oops, i forgot about your QLWARZ. I did it the hard way.
Cueshell did not report any Backup errors but behaved strangely on one 
main directory it should copy. Instead it started Deleting files from 
another directory.
I could restore both from an older win2_ backup as nothing had recently 
been changed in both dirs.


Still the question remains why both emulators behaved so differently.

Bob

pjw via Ql-Users wrote:
If you write a lot of programs you will occasionally corrupt your hard 
disk etc. Occupational hazard!


On the occasions its happened to me Ive tried various things, including 
the two Tebby hard disk tools. My problems didnt, perhaps, fit with what 
theyre supposed to fix, as they never seemed to make any difference..


What did make a difference in my case was QLWARZ, or rather what lead me 
to stitching it together in the first place. When it gets to corrupts 
files or directories the program crashes (yes!) Then I just keep typing 
CONTINUE until it picks itself up and runs again. At the end of the 
process, everything that can be saved is copied. Some damaged files 
remain damaged, but at least they are "legal" and dont mess with your 
system.


Clearly, if you need to retrieve irreplaceable material after that you 
will need to go back to the original win drive (QLWARZ doesnt fiddle 
with it other than renaming it) and set to work with a file editor, such 
as Wolfgang Lenerz'es Wined (https://www.wlenerz.com/qlstuff/#wined)!


HTH, Per

On 24/11/2023 15:10, Bob Spelten via Ql-Users wrote:
That's what I did. A larger win2_ was formatted and dirs/files were 
copied with Cueshell from the old win2_.

I only hope any corruption was not migrated with it.
Are there any tools available to examine a suspect win drive?

Bob

Fabrizio Diversi via Ql-Users wrote:

Hi,

no issue here, same with QPC and SMSQmulator.

I suspect your  win2 is corrupted in some way, it happened to me with 
the same error of "drive full",  try to use the tool QLWARZ from Per 
Witte to check if something change.


Fabrizio


On 24/11/23 14:21, Bob Spelten via Ql-Users wrote:

I experienced a strange problem with Saving a text from QD.
Under QPC2 the Overwrite from QD to win2_ froze the emulator.
The same file under SMSQmulator8 to the same win2_ gave no problem.
The text file is about 250KB in size.

Saving to ram2_ from QD went OK on both emulators.
Backup of the ram2_ text to win2_ by QPAC2 froze QPC2 again, not 
under SMSQm8.
Copy with QPAC2 now reported 'drive full' while it claimed 28MB free 
on win2_.
Then I found that the same Copy from SMSQm8 had saved only 10% of 
the text - QPAC2 reported the full size - thus avoiding the 'drive 
full' error.


The emulators, SMSQ/E & QD are the latest versions running under W$7.
I also tried older versions with the same result.
So why is the free MB size wrong?
Why does QPC2 freeze and not report an error from QD?
Why does SMSQm8 deceive me into thinking it all went OK?

Bob



___
QL-Users Mailing List




___
QL-Users Mailing List



--
Dit e-mailbericht is met AVG-antivirussoftware gecontroleerd op virussen.
www.avg.com
___
QL-Users Mailing List

Re: [Ql-Users] Save problems with QPC2, QD, QPAC2 or SMSQm8

[Bob Spelten via Ql-Users]

That's what I did. A larger win2_ was formatted and dirs/files were 
copied with Cueshell from the old win2_.

I only hope any corruption was not migrated with it.
Are there any tools available to examine a suspect win drive?

Bob

Fabrizio Diversi via Ql-Users wrote:

Hi,

no issue here, same with QPC and SMSQmulator.

I suspect your  win2 is corrupted in some way, it happened to me with 
the same error of "drive full",  try to use the tool QLWARZ from Per 
Witte to check if something change.


Fabrizio


On 24/11/23 14:21, Bob Spelten via Ql-Users wrote:

I experienced a strange problem with Saving a text from QD.
Under QPC2 the Overwrite from QD to win2_ froze the emulator.
The same file under SMSQmulator8 to the same win2_ gave no problem.
The text file is about 250KB in size.

Saving to ram2_ from QD went OK on both emulators.
Backup of the ram2_ text to win2_ by QPAC2 froze QPC2 again, not under 
SMSQm8.
Copy with QPAC2 now reported 'drive full' while it claimed 28MB free 
on win2_.
Then I found that the same Copy from SMSQm8 had saved only 10% of the 
text - QPAC2 reported the full size - thus avoiding the 'drive full' 
error.


The emulators, SMSQ/E & QD are the latest versions running under W$7.
I also tried older versions with the same result.
So why is the free MB size wrong?
Why does QPC2 freeze and not report an error from QD?
Why does SMSQm8 deceive me into thinking it all went OK?

Bob



___
QL-Users Mailing List



--
Dit e-mailbericht is met AVG-antivirussoftware gecontroleerd op virussen.
www.avg.com
___
QL-Users Mailing List

[Ql-Users] Save problems with QPC2, QD, QPAC2 or SMSQm8

[Bob Spelten via Ql-Users]

I experienced a strange problem with Saving a text from QD.
Under QPC2 the Overwrite from QD to win2_ froze the emulator.
The same file under SMSQmulator8 to the same win2_ gave no problem.
The text file is about 250KB in size.

Saving to ram2_ from QD went OK on both emulators.
Backup of the ram2_ text to win2_ by QPAC2 froze QPC2 again, not under 
SMSQm8.
Copy with QPAC2 now reported 'drive full' while it claimed 28MB free on 
win2_.
Then I found that the same Copy from SMSQm8 had saved only 10% of the 
text - QPAC2 reported the full size - thus avoiding the 'drive full' error.


The emulators, SMSQ/E & QD are the latest versions running under W$7.
I also tried older versions with the same result.
So why is the free MB size wrong?
Why does QPC2 freeze and not report an error from QD?
Why does SMSQm8 deceive me into thinking it all went OK?

Bob


--
Dit e-mailbericht is met AVG-antivirussoftware gecontroleerd op virussen.
www.avg.com
___
QL-Users Mailing List

[Ql-Users] BMP update 1.05

[Bob Spelten via Ql-Users]

A worthwhile message on the Forum from Dilwyn.

Bob Spelten jr. has released version 1.05 of the BMP graphics viewer and 
converter, available from the Graphics page on my website at 
https://dilwyn.qlforum.co.uk/graphics/index.html


Convert BMP graphics (from 24-bit to 1-bit types) to QL graphics files - 
screens, PIC files, PSA/PAC files, or Page Designer pages. Convert from 
QL graphics files to BMP (16-bit or 24-bit) for transfer to other 
systems. View files, convert QL file types and convert between screen modes.


The QL files can now be RLE compressed as PAC files, using similar 
compression to compressed GD2 sprites, thanks to routines from Per 
Witte. RLE compression under the operating system is normally only used 
for GD2 sprites.


There is a 'scaling' option to allow a picture being viewed to be resize 
to fit the window. And some support for Mode 12 (Thor XVI) screens and 
QDesign compressed _Pgn and mode 2 mono files.


--
Dit e-mailbericht is met AVG-antivirussoftware gecontroleerd op virussen.
www.avg.com
___
QL-Users Mailing List

Re: [Ql-Users] loopy bug

[Bob Spelten via Ql-Users]

pjwitte via Ql-Users wrote:
I dont know if this has been documented anywhere, but Im putting it out 
here as it caused me some grief.


It appears that Q-Liberator zeroes the loop variable on entry to a loop. 
The following demo, which is acceptable (although perhaps not very 
elegant) S*BASIC, will not work in the same way once compiled with Qlib.


100 loop = 3
110 cnt = 0
120 PRINT 'Start:'! loop, cnt
130 REPeat loop
140  PRINT loop, cnt
150  cnt = cnt + 1
160  IF cnt >= loop: EXIT loop
170 END REPeat loop
180 PRINT 'End:'! loop, cnt
190 PAUSE: QUIT

In the Qlib-compiled version the loop is exited after a single run as 
the condition cnt >= loop is met immediately, to wit 1 >= 0


The worrying part of this is that while I was figuring out what was 
wrong, running an embedded routine like this many times, the system 
crashed due to memory corruption. Whether this was due to the SBASIC or 
Qlib compiled version I cant say right now. So just beware and keep on 
progging!


NB: This works, though. As long as you start out with loop = 0

100 loop = 0
110 cnt = 3
120 PRINT 'Start:'! loop, cnt
130 REPeat loop
140  PRINT loop, cnt
150  loop = loop + 1
160  IF loop >= cnt: EXIT loop
170 END REPeat loop
180 PRINT 'End:'! loop, cnt
190 PAUSE: QUIT



Not that I have ever had this problem but when using a REPeat variable 
as a value I've always made sure it was only used within the Loop.


In the Name Table a simple variable is marked differently ($0202) from a 
REPeat index ($0602), the question is who is doing it right?
When Qlib encounters the 2nd 'loop' it probably sets up a new zero entry 
with the same name.


In your second example the first 'loop = 0' is most likely not relevant.

Bob


--
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] "RETurn not in procedure or function"

[Bob Spelten via Ql-Users]

Wolfgang Lenerz via Ql-Users wrote:

Hi,

in my experience, this is often caused by a Basic extension not
resetting the stack correctly. This generally seems to be the case
either when a keyword changes the value of an entry parameter, to make
it into a return parameter, or when a function returns a value (very
often a string).

But without having a complete program to test, this will be difficult to
find out.

Regards

Wolfgang

"RETurn not in procedure or function"

What is causing this error in my Basic?
The error has bugged me for weeks now.
It even seems able to move around (see below).
I have checked for the obvious and didn't find any mismatches.
Also XREF, BasicLinker or QLIB did not report any.

Below a summary of the program section from where the error occurs.

   DEF FN GetScreen(..)
    :...
    IF hd =10
     MC_ProcA parms..
    ELSE
     er%= MC_FnB(..)
     :...
    END IF
    :...
    IF NOT rn% : er%= SetDBS(..)
    REM > rn% is set if the screen file is in the database
    :...
    RETurn 0
   END DEF
   :...
   DEF FN SetDBS(..)
    :...
    er= FDB_SET(..)
    :...
    PRINT er
    REturn er
   END DEF
   :

The program is numberless and testrun from QD with the F10 Sbas/qd thing.
The code for the MC_ProcA and MC_FnB keywords has also successfully been
tested in other Basics.

MC_FnB nicely returns zero in er% and not one of the possible negative
values.
SetDBS does some DBAS handling and doesn't return an error in er, as
tested just before the RETurn line which produces the "RETurn not..."
error. Checking the database confirms that SetDBS works properly.

Strangely when I REM the SetDBS call, the same error is given in another
FN when GetScreen has long been left by its own RETurn.

Also the MC_ProcA route does not generate the error when doing the
SetDBS call or in the other Sbas FN if skipping SetDBS.

When I compile the Basic with QLIB v3.36 there are no errors reported
and the compiled _obj executes without producing this error.

Of course the Sbas version differs slightly from the _obj but this has
mainly to do with reporting variable values. Also the Basic extensions
as for the MC_xxx ones above are LRESPR'd in the Sbas run and $$asmb'd
by Qlib.

The numbered Basic as generated by BasicLinker and then run from job 0
produces the same error as run from QD.

So what could be messing up my RETurns?


As expected it was stack problem with my MC_FnB.
Not being an expert I had looked at some examples and ended up using a mix.
It has now been sorted and I can go on with testing the rest of the program.

I agree with Francois, using LOOKUP% as alternative for EXISTS.
I use it a lot. It returns the place in the name table which can also be 
used to test for conflicting keywords if found out of place.


Bob



--
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] "RETurn not in procedure or function"

[Bob Spelten via Ql-Users]

Wolfgang Lenerz via Ql-Users wrote:

Hi,

in my experience, this is often caused by a Basic extension not
resetting the stack correctly. This generally seems to be the case
either when a keyword changes the value of an entry parameter, to make
it into a return parameter, or when a function returns a value (very
often a string).

But without having a complete program to test, this will be difficult to
find out.


Thanks for the suggestions.

My function does not change any of the entry parameters, only sets the 
return value. I have written other functions that do the same but 
without this anomaly, also with 8 chr names.
Anyway I will check the exit section to see what I did differently from 
previous and consult the Assembly Language PDFs to get it right.


Thanks,
Bob



--
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

[Ql-Users] "RETurn not in procedure or function"

[Bob Spelten via Ql-Users]

"RETurn not in procedure or function"

What is causing this error in my Basic?
The error has bugged me for weeks now.
It even seems able to move around (see below).
I have checked for the obvious and didn't find any mismatches.
Also XREF, BasicLinker or QLIB did not report any.

Below a summary of the program section from where the error occurs.

  DEF FN GetScreen(..)
   :...
   IF hd =10
MC_ProcA parms..
   ELSE
er%= MC_FnB(..)
:...
   END IF
   :...
   IF NOT rn% : er%= SetDBS(..)
   REM > rn% is set if the screen file is in the database
   :...
   RETurn 0
  END DEF
  :...
  DEF FN SetDBS(..)
   :...
   er= FDB_SET(..)
   :...
   PRINT er
   REturn er
  END DEF
  :

The program is numberless and testrun from QD with the F10 Sbas/qd thing.
The code for the MC_ProcA and MC_FnB keywords has also successfully been
tested in other Basics.

MC_FnB nicely returns zero in er% and not one of the possible negative 
values.
SetDBS does some DBAS handling and doesn't return an error in er, as 
tested just before the RETurn line which produces the "RETurn not..." 
error. Checking the database confirms that SetDBS works properly.


Strangely when I REM the SetDBS call, the same error is given in another 
FN when GetScreen has long been left by its own RETurn.


Also the MC_ProcA route does not generate the error when doing the 
SetDBS call or in the other Sbas FN if skipping SetDBS.


When I compile the Basic with QLIB v3.36 there are no errors reported 
and the compiled _obj executes without producing this error.


Of course the Sbas version differs slightly from the _obj but this has 
mainly to do with reporting variable values. Also the Basic extensions 
as for the MC_xxx ones above are LRESPR'd in the Sbas run and $$asmb'd 
by Qlib.


The numbered Basic as generated by BasicLinker and then run from job 0
produces the same error as run from QD.

So what could be messing up my RETurns?

Bob

--
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] The INSTR function?

[Bob Spelten via Ql-Users]

Wolf via Ql-Users wrote:

Hi,

actually functions are present in EXTRAS.

Things like AND, OR, NOT (and, yes INSTR) are considered to be operators 
(like + or -), and thus will not show up with EXTRAS.


These keywords (and variations thereof) are all included in the the 
Basic Keywords Index on the official SMSQ site and most are marked 'O' 
for operator, unless I was unsure about their use or syntax.


Bob


--
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] Select on

[Bob Spelten via Ql-Users]

Op Sun, 21 Jun 2020 09:46:23 +0200 schreef Norman Dunbar via Ql-Users  
:


I have a vague recollection that Simon N Goodwin did something similar,  
maybe, in the DIY Toolkit.


I think it was passed a variable and a list of strings, and returned the  
position of the variable in the list. Something like that.


Maybe useful?


That would then be the PICK$ function.
It's on DIY disk 1, sub E, found on Dilwyn's site, where else?

Bob

--
The BSJR QL software site at: "http://home.hccnet.nl/b.spelten/ql/;

--
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] SMSQmulator 2.29

[Bob Spelten via Ql-Users]

Op Sun, 19 Apr 2020 18:04:04 +0200 schreef Wolfgang Lenerz via Ql-Users  
:



Hi,


Thanks again. I reloaded the re-upped version.

But under W$7 with most recent Java 8.251 (updated today) nothing
happens, not even the black screen or an error message.



Strange. Just to be sure, I downloaded the file and used it under win7
in a VM where it runs OK with java 8.



Under an old Lubuntu and likely an old Java8 it will start.
Also under W$10 with Java 8.241 there seems to be no problem.


Using a commad line,

java --version
will tell you what java you're running .


The Lubutu reports 1.8.0_66, running SQm8229 OK.
On my Pi3 it's even 1.8.0_65, still running SQm8224 OK.

Trying "java -version" on my W$7(1), I get:  
"java.lang.ExeptionInInitializerError" and a whole page of other messages.


Then I unzipped the same file on another W$7 machine (2), also having Java  
1.8.0_251. There it runs as expected.


So SQm8229 seems OK while there is something wrong with the Java on  
machine (1) since the last update. Also a cold reset did not cure that.

I probably need to uninstall it and try again.

BTW, -showversion works too but also shows a list of command options.

Thanks,
Bob

--
The BSJR QL software site at: "http://home.hccnet.nl/b.spelten/ql/;

--
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] SMSQmulator 2.29

[Bob Spelten via Ql-Users]

Op Sun, 19 Apr 2020 15:38:27 +0200 schreef Wolfgang Lenerz via Ql-Users  
:



Hi Bob, Per, François, Derek,

thanks for letting me know.

It seems the version for java 11 is ok, not the one for java 8, though
both work ok here.

I re-upped the version for java 8 (also changing the version number).


Thanks again. I reloaded the re-upped version.

But under W$7 with most recent Java 8.251 (updated today) nothing happens,  
not even the black screen or an error message.


Under an old Lubuntu and likely an old Java8 it will start.
Also under W$10 with Java 8.241 there seems to be no problem.

What's happening here?
Bob

--
The BSJR QL software site at: "http://home.hccnet.nl/b.spelten/ql/;

--
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] SMSQmulator 2.29

[Bob Spelten via Ql-Users]

Op Sun, 19 Apr 2020 07:56:30 +0200 schreef Wolfgang Lenerz via Ql-Users  
:



Hi all,

hot on the heels of SMSQE 3.36 comes SMSQmulator 2.29.

Win drives can be made removable.
NFA drives can handle (exec, save and load) files with an XTcc footer,
so that QL files can be  EXEC'd directly from a native drive.

wlenerz.com/smsqmulator.


Thanks Wolfgang for the final 2.29.
But it seems something has gone wrong when making the zip.
The unpacked SMSQm8229 only opens it's W$ window, the content is black, no  
QL windows.

When viewing the supplied SMSQE bin file I see sections of SBasic(?).

Then I copied SMSQE (also 308.5K) from the 3.36 binaries, which looked  
alright although it said there @h01E0: "<>SMSQXq3.350002..".

The result was the same, no booting into my usual .WIN.
BTW The SMSQE 3.36 announcement was too hot for me and never reached my  
mailbox.


Bob

--
The BSJR QL software site at: "http://home.hccnet.nl/b.spelten/ql/;

--
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

[Ql-Users] Website move

[Bob Spelten via Ql-Users]

Hi All,

As of 1 April 2020 space for my current website,
 will no longer be available.
So anyone with links or bookmarks to this site for SuQcess, SQRview, QCP,  
QCoCo and more, should change that to the new address below.


Bob

--
The BSJR QL software site at: "http://home.hccnet.nl/b.spelten/ql/;

--
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] WM_move_mode and Easyptr menu

[Bob Spelten via Ql-Users]

Op Sat, 19 Oct 2019 17:05:12 +0200 schreef François Van Emelen via  
Ql-Users :



Op 18/10/2019 om 13:01 schreef Bob Spelten via Ql-Users:
op Fri, 18 Oct 2019 11:34:46 +0200 schreef pjwitte via Ql-Users  
:



On 18/10/2019 11:17, François Van Emelen via Ql-Users wrote:

(...)


(...)

According to the EP manual (p71) a -1 parameter should also give the  
WM_MOVEMODE options to WMOVE.


Bob


Hi Bob,

EP manual (p71)? Are you referring to the Easyptr manual ?


Yes, it's there on my original printed manual from 2005.
In a later PDF (dated Oct.2012) it's on page 74.

Bob

--
The BSJR QL software site at: "http://home.hccnet.nl/b.spelten/ql/;

--
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] WM_move_mode and Easyptr menu

[Bob Spelten via Ql-Users]

op Fri, 18 Oct 2019 11:34:46 +0200 schreef pjwitte via Ql-Users  
:



On 18/10/2019 11:17, François Van Emelen via Ql-Users wrote:

Hi,


Can someone confirm what happens in line 220?

In a menu created with Easaymenu (Easyptr) there is a Loose Item to  
allow the menu to be moved.


Configuration A: the key for that Loose Item is CRTL E, seems to be the  
default value.


Configuration B: I replaced the default key with value 77 (‘M’) for  
Move.


….

200 SELect on ObjectHit

205 = -1:Remark do something

210 = -2:Remark do something

215 =- 3:Remark this is the move Loose Item

220 :Remark do something

….


With Configuration A, WM_movemode 0,1,2,3 can be used but line 220 is  
never executed. Why?


With Configuration B, line 220 is executed but only WM_movemode 0 (the  
old way, using the “move window” sprite) is available. Why?


Is this a feature, a bug or am I missing something?

Help and explanation are welcome.


François Van Emelen


In A. the Move window call is trapped by the system, so it never reaches  
line 220. In B. you need to add the instruction to move the window, for  
example WMOV. This gives you the opportunity to carry out other stuff  
before and after the the move instruction. The standard key for this is  
CF4, tho'.


WMOV has evolved over the years, so make sure youre using the latest  
version of ptrmen_cde to get the best. Get it directly from Marcel's.


On my Knoware.no site, for example, there are a number of PE programs  
with source code included. They show a variety of ways you can do this.


Per

According to the EP manual (p71) a -1 parameter should also give the  
WM_MOVEMODE options to WMOVE.


Bob

--
The BSJR QL software site at: "http://home.hccnet.nl/b.spelten/ql/;

--
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] DISK MATE 5

[Bob Spelten via Ql-Users]

Op Tue, 26 Feb 2019 12:29:17 +0100 schreef simon629--- via Ql-Users  
:


Hi There This morning I installed Disk Mate 5 on MY Version of  
LaunchPad2 it Runs OK But When you Launch it it comes up with a Red Box  
with RAC when I Press C key on my Keyboard   Runs Like A dream  can any  
on help me Fix That Tiny Error



There are two known problems with DM5.
When started it complains about the date.
Use ESC to ignore it. Don't try to fix the date, it will produce an error.

It also uses some FileInfo2 keywords: FEX, FEX_W, FEXF, FEX_W(), FEXF(),  
FEX$.
These conflict with SMSQ/E and are possibly switched off in your FI2 and  
while the replacements FI2_CALL can be used.

So if DM5 tries to use FEX it cannot be found.

My way around this was to patch the keywords to FFX in both DM5 and FI2  
and switch them on again. Hopefully no other tool uses the old keywords  
and no tool uses this new keyword.
Sadly the FI2 database is part of the same _bin so this patch needs to be  
done to the current _bin or the whole extensions database needs to be done  
again.


Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] Wallpaper program

[Bob Spelten via Ql-Users]

Op Tue, 19 Feb 2019 11:19:19 +0100 schreef Dilwyn Jones via Ql-Users  
:



Wallpaper Program

Recent versionsof SMSQ/E from about version 3.00 feature high colour and  
high resolution screens along with the new Window Manager. This makes  
them very suitable for displaying colourful and attractive background  
images behind your program windows.

(...)
The downside of using wallpaper on a high-colour system is the amount of  
memory it takes. (...)



Thanks Dilwyn for automating the wallpaper process.

Just a word about memory and compressed images.
As other programs or other OSes appear to put compressed images straight  
to the screen, I suspect they all need to keep a final uncompressed  
version in memory to work.
The space demands may go unnoticed as other systems have more RAM to play  
with.

This is also true for compressed sprites that WMAN2 processes directly.
Compressing _pic or _scr files is feasible but it's mostly WIN space that  
is won.


Bob

Download the Wallpaper software and a few example graphic files from  
http://www.dilwyn.me.uk/graphics/index.html




--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

[Ql-Users] Updates SuQcess2 & QCoCo

[Bob Spelten via Ql-Users]

Hi All,

I have updated some programs on my site.

SuQcess2 is now version 2.07.
Not many new features but lots of internal improvements.
The Sort Key can be set from the DATA menu.
Bug in locating the edited and sorted record from View is fixed.
Better detection of Read-Only media.
Updated ReadMe and Help files.

QCoCo is now version 1.63.
Supports the new binary _thb files next to the ascii _thm theme files.
APPLY needs a Confirm or Undo action.
RESET can reset the current theme or to the startup theme.
A new Theme Viewer (by PJW) is included showing the colours and hex  
numbers.
Incomplete themes should not crash the program and are automatically  
completed through the SYNCHRO option.

Invalid, referenced and 3D items are marked when Viewing the colours.
Can be started with a theme as CMD$ which overrides the config item.
Updated ReadMe file.

Happy QLing,
Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] PWfile and SMSQmulator

[Bob Spelten via Ql-Users]

Op Thu, 06 Dec 2018 15:26:04 +0100 schreef Wolf via Ql-Users  
:



Hi,


You are right, there is a problem. But it seems to be PWFile itself.
Renaming the device is not recognised, it sticks to the original name.
Renaming DOS to NFA under QPC2 presents the same problem.
The same is true for renaming WIN to MDV.




Do you mean that PWFile does not honour a device's usage name, but  
always insists on using its "true" name (a little bit like the menu  
extensions which normally don't show the "dev" device)?



That's exactly what happens.
When I edit the changed name by hand in the "directory" window, it changes  
back to the original name when Enter is pressed.


Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] PWfile and SMSQmulator

[Bob Spelten via Ql-Users]

Op Tue, 04 Dec 2018 13:18:37 +0100 schreef François Van Emelen via  
Ql-Users :



Op 4/12/2018 om 11:59 schreef Bob Spelten via Ql-Users:
Op Tue, 04 Dec 2018 11:20:58 +0100 schreef François Van Emelen via  
Ql-Users :






1. Launch PWfile (smsqumatator)

2.go to 'directory' and replace 'winx_ 'with ''nfax_'

All files in that device  should be visible now. My question is :Can  
you see them?


I don't see anything in SMSQmulator but I do see them in QPC2.

I hope this clarifies my question.

Thank you for your reply

Have a fine day,

François Van Emelen


Hi Francois,

I have just tried PWFile on SMSQm8 but I can see the files and can open  
them.

Are you sure you have a valid NFAx device and not renamed NFA to DOS?
By default PWFile selects only those directories that are configured in  
ProWess else you must edit the device by hand.


Bob


Hi Bob,

You're right, replacing 'dos' with 'nfa' followed by a reset solves the  
problem.

But then my next question is : why is 'nfa' OK  and  'dos' is not OK?
Sorry for the delay,  problems with my mailing server.

Have a fine day.

François


You are right, there is a problem. But it seems to be PWFile itself.
Renaming the device is not recognised, it sticks to the original name.
Renaming DOS to NFA under QPC2 presents the same problem.
The same is true for renaming WIN to MDV.

Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] PWfile and SMSQmulator

[Bob Spelten via Ql-Users]

Op Tue, 04 Dec 2018 11:20:58 +0100 schreef François Van Emelen via  
Ql-Users :






1. Launch PWfile (smsqumatator)

2.go to 'directory' and replace 'winx_ 'with ''nfax_'

All files in that device  should be visible now. My question is :Can you  
see them?


I don't see anything in SMSQmulator but I do see them in QPC2.

I hope this clarifies my question.

Thank you for your reply

Have a fine day,

François Van Emelen


Hi Francois,

I have just tried PWFile on SMSQm8 but I can see the files and can open  
them.

Are you sure you have a valid NFAx device and not renamed NFA to DOS?
By default PWFile selects only those directories that are configured in  
ProWess else you must edit the device by hand.


Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] QD 2018

[Bob Spelten via Ql-Users]

Op Sun, 16 Sep 2018 00:55:45 +0200 schreef Marcel Kilgus via Ql-Users  
:



I have just updated QD 2018 to version B.05:

; B.05  Implemented per-extension editor-usage (configurable) (MK)
;   Fixed BASIC usage for DEFine FuNction (MK)
;   Fixed colours in replacement confirmation dialog (MK)
;   Fixed DO on resize to keep the x window size (MK)
;   Bottom right corner stays where it is on normal resize (MK)
;   Allow CTRL+Z (mark current line) in read-only mode (MK)

As previously with the tab settings the editor-usage can now be
configured per extension, so you can say all "_bas" (or "_bsl" ;) )
files automatically invoke the "BASIC" editor usage, for example.

The rest is the stuff we've already talked about here.

https://www.kilgus.net/smsqe/qd/

Cheers, Marcel


Thanks Marcel for Being So Laborious.

Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] QD 2018 colours

[Bob Spelten via Ql-Users]

Op Wed, 29 Aug 2018 00:48:26 +0200 schreef Marcel Kilgus via Ql-Users  
:



Bob Spelten via Ql-Users wrote:

But setting a custom width, moving the "size" to the left, is where the
right side also moves left.


OK, now I see what you mean.

The size is incremented in 20 character steps. There is no explanation
in the code why that is, but as this is the same amount that is used
when the edit window is panned I guess that this is the reason. I
tried removing the restriction and most things seemed to work, but I
found at least a minor bug, so I'm not comfortable lifting that
restriction.

I can make the bottom right corner stay in place, though. The downside
is that now when you resize less than 20 characters more basically
nothing happens at all, this might be confusing for some users.


Jochen once explained that size grows in
discrete steps but I would expect the right side to be anchored, now  
full screen can never be reached.


Ususally it cannot be reached because the maximum line length is
exhausted before the maximum screen width.


OK, this is indeed the case when set to 160 characters on a 1024 display.
Leaving it anchored right and restricting left movement would then be  
preferable.



My numberless Basic is named xxx_bsl so would not benefit.
Usually I start QD through FI2 where the right command flag is added to
take care of this.


I start 100 QDs when working on stuff like this, 10% by hotkey and 90%
by FiFi ;)

Just one more. It sometimes happens when a line is longer than the  
window and I use ALT-right to jump to the end of the line, the text
pans less  than needed but the cursor/arrow lands on the right spot, 
outside the window.

This seems more likely to happen when the cursor is already at position
80+.


Can't reproduce right now. And in any case, this is a problem with the
editor core, which I'm not touching with a 10 feet pole.


Last one? Opening QD in read-only mode (\P) lets me pick a block for the
scrap but using ^Z to hot-buffer one line is not working. A bug or a
missed feature?


Apparently you have to thank me that CTRL+X works in this mode:
cmp.b   #24,d1  ; CTRL X => Quit
beq.s   not_protected   ; yes, so do it (Marcel wants it !!)

I added
cmp.b   #26,d1  ; CTRL Z => Mark current line
beq.s   not_protected   ; yes, so do it (Bob wants it !!)



Thanks again Marcel for looking into these points and for including my  
name in the source. Now I have no choice in calling it my favourite editor.


Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] QD 2018 colours

[Bob Spelten via Ql-Users]

Op Tue, 28 Aug 2018 15:26:22 +0200 schreef Marcel Kilgus via Ql-Users  
:



Bob Spelten via Ql-Users wrote:

Per already mentions the jumpy resize behaviour.


I frankly don't quite see what's jumpy about it?

My default QD size is 80 columns by 40 lines, and I like that a size DO   
makes it maximize the height.
But setting a custom width, moving the "size" to the left, is where the  
right side also moves left. Jochen once explained that size grows in  
discrete steps but I would expect the right side to be anchored, now full  
screen can never be reached.
It seems that the bigger the move to the left, the more the right moved  
along with it.



One point I would like to add now, as a Basic programmer, is the DEFine
highlight that is not working for FN or FuNction sections.


Again a feature I didn't even know about. And quite obviously this has
never worked but is not too difficult to fix.

I'd prefer if the editor usage would switch automatically to BASIC if
a file with the extension "_bas" was loaded (correspondingly for
"_asm"), but I must check how difficult that would be.


My numberless Basic is named xxx_bsl so would not benefit.
Usually I start QD through FI2 where the right command flag is added to  
take care of this.



For other points I need to check my notes and test them against this
version.

Can do, but as a general matter I must stress that me releasing some
software does not mean that all outstanding 20 years old bugs will get
fixed :-o


One can only hope.;-)
Just one more. It sometimes happens when a line is longer than the window  
and I use ALT-right to jump to the end of the line, the text pans less  
than needed but the cursor/arrow lands on the right spot, outside the  
window.
This seems more likely to happen when the cursor is already at position  
80+.


Last one? Opening QD in read-only mode (\P) lets me pick a block for the  
scrap but using ^Z to hot-buffer one line is not working. A bug or a  
missed feature?


Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] QD 2018 colours

[Bob Spelten via Ql-Users]

Op Sat, 25 Aug 2018 18:45:31 +0200 schreef pjwitte via Ql-Users  
:


Im having a problem with the latest QD (2018). The 'Replace confirmation  
sub menu' seems to have its colours mixed up. I cant read that menu in  
any palette!


Since no one else has complained, and I recently made some changes, I  
was wondering if Im just being confused (again!) But then an older  
version of QD (2003) seems unaffected, although it too uses the old  
colourways settings for part of that menu.


If "someone" ;) is going to delve into the innards of QD again to sort  
this out, could they also tweak the 'resize to full screen' option (DO  
resize icon) to perhaps leave the current x-size of the window unchanged  
(as it was in the earlier version)?


Great that this program is now freely available!

First of all, thanks Jochen & Marcel for setting it free. I have enjoyed  
using QD since '91 and it's the first program I added to QLE, Black  
Phoenix or my Q68 boot when exploring or customising them.


Like Per I found something changed in this "Replace" confirmation window.  
Apart from the mixed m4/HC colours, the text to replace is no longer  
visible in any theme, m4 or HC, I tried. My HC QDvB always uses m4 colours  
here but at least I can see the text to be replaced.


There are a few more small issues that should be addressed when "someone"  
updates the code.

Per already mentions the jumpy resize behaviour.
One point I would like to add now, as a Basic programmer, is the DEFine  
highlight that is not working for FN or FuNction sections.
For other points I need to check my notes and test them against this  
version.


Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] colour confusion

[Bob Spelten via Ql-Users]

Op Sat, 25 Aug 2018 12:03:03 +0200 schreef pjwitte via Ql-Users  
:




Thank you, guys. The confusion, it appears, was entirely mine. I'll  
spare you my various excuses; one of the many clues that should have  
alerted me to the error of my ways was in sp_titletextbg! :) I do wish,  
however, that there had been some "safe" way to put text on a stippled  
or striped background in other cases too. But thats ok.
Im very glad of the palette system as it is. It has stood up well to the  
test of time!



I can understand the "middleground" confusion.
When you open a theme in QCoCo and click the INFO WINDOW item there is  
"ink_1" and "ink_2". The manual explains that ink_2 stands for  
middleground, probably called this way to avoid just this confusion.
Not all themes that are around will fully exploit this, nor do many  
programs, I never did.
So if some text seems missing or vague it's worth checking your theme in  
QCoCo to see if the ink_2 item is actually visible or different enough.


QCoCo's "SYNCHRO" section will take the Outline ink & paper and copy this  
to other sections to quickly build a theme but syncing middleground with  
ink_1 is missing and I will add this to v1.63. Thanks Per for making this  
point.


"sp_titletextbg" is also tricky.
In some themes Title-ink and -paper are the same, using this as a  
contrast. But SuQcess doesn't use it so the title (database name) could  
become invisible with such a theme. For the current version a test has  
been added to make sure ink and paper are different.
Text background is not featured in EasyPTR and should be created with  
overlapping Info Windows.


Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] SuQcess update

[Bob Spelten via Ql-Users]

Oops.
If anyone had a problem understanding the config prompts of SuQcess 2.06,  
he/she should get a new copy of the zip from my site.

The English & German prompts have been restored.

Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

[Ql-Users] SuQcess update

[Bob Spelten via Ql-Users]

Hi All,

There are three program updates on my site.

1) A new version 2.06 of the SuQcess database program.
The viewing order of fields can be set without changing the database.
Date display can be set for individual columns instead of global.
More update info on the site's page and in the Readme file.

2) SQRview has a bug fixed that came to light when running it on my Q68,  
where images larger than the screen could cause an error.

No further changes so the version number is kept at 1.02.

3) The QWatch2 clock too is now Q68 aware and adjusts better to its  
resolutions.


4) The links on the site have also been updated.

Have Fun
Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

[Ql-Users] Q68 & QD

[Bob Spelten via Ql-Users]

There seems to be a problem with QD on my Q68.
When running Q68 in high resolution 1024x768 and the QD window is set at  
80 characters, editing is fine as long as I stay within this 80 chrs  
margin.
I can move the cursor beyond that but when a character is inserted the  
whole machine freezes.


Also with a wider QD window, typing beyond the 80 chrs margin locks up  
SMSQ.
Setting the right margin at 100 seems to fix the problem but only moves it  
to position 101.


This was tested with QD's v9 and vB.01 and has never been a problem on  
QPC2 or SMSQmulator so seems limited to QD interacting with SMSQ/E on the  
Q68.


Any ideas?
Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] Stuart Honeyball

[Bob Spelten via Ql-Users]

Op Sun, 17 Jun 2018 14:32:21 +0200 schreef Urs Koenig (QL) via Ql-Users  
:



Derek wrote:

I totally agree with Tony, Stuart was a very nice person to know.
I talked with him alot when I organised 2 QL workshops in the North  
East.

His product line was excellent quality and I must of bought everything
Miracle Systems produced It does seem a loss to the QL community.


The last couple of weeks I re-viewed all the DVDs from the Italian QL  
community and compiled this playlist for the QL community:


Stuart Honeyball / Miracle Systems
https://www.youtube.com/playlist?list=PLQHAWWG2O0e1rLysASEw-8zRe0rojueA_
In memoriam of the miraculous Stuart Honeyball. R.I.P. my friend.

Thanks to Antonio Gareffa (ANT Videoproductions) and other Italian QL  
friends there’s video footage of many 1990s QL shows. Published with  
their permission. Thank you very much for this great work. Grazie mille!


QL forever!


Thanks Urs,

I especially like the one that was made in Eindhoven.
I remember the Italians filming there and always wondered what they made  
of it. It was a well visited meeting with many famous faces which shall  
not be named in view of the GDPR, so check it out yourself.


Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] SMSQ/E 3.33

[Bob Spelten via Ql-Users]

Op Sat, 12 May 2018 06:48:27 +0200 schreef Wolf via Ql-Users  
:



Hi all,

I re-upped the binaries zip file for SMSQ/E, the Aurora & QXL problems  
should be gone now.


I also used this occasion to correct a bug in the Q68 version due to  
which the card_create command could corrupt the directory of a card.  
This bugfix doesn't merit a whole new version, but you should upgrade.




Thanks Wolfgang.
I can now report a successful boot on all 3 mentioned platforms.

Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] SMSQ/E 3.33

[Bob Spelten via Ql-Users]

Op Fri, 11 May 2018 07:01:33 +0200 schreef Daniele Terdina via Ql-Users  
:


I decided to give a try to the Aurora version on Q-emuLator, but it  
stops when it encounters some "jsr $FE83" instructions... anybody  
knows what those are supposed to do?



My attempt to run v3.33 on the Aurora/SGC also failed.
I made sure it was configured the same as the previous 3.32 but the screen  
stayed black and nothing else happened.


Also the QXL version failed to run.
"The QXL at IO address 02B0h is not responding" is all I got.
The last working version I tried here was 3.26, with the same address.

Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] SMSQ/E 3.33

[Bob Spelten via Ql-Users]

Op Tue, 01 May 2018 12:06:00 +0200 schreef Bob Spelten :

Op Mon, 30 Apr 2018 20:38:27 +0200 schreef Wolfgang Lenerz via Ql-Users  
:



Hi,

I just re-upped the binary file.


Thanks again Wolfgang, but...
The FAT_xxx range of keywords still seem to be missing ...


Oops, my mistake.
This v333 is configured differently then the previous one that came with  
the machine, FAT_ was disabled.


Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] SMSQ/E 3.33

[Bob Spelten via Ql-Users]

Op Mon, 30 Apr 2018 20:38:27 +0200 schreef Wolfgang Lenerz via Ql-Users  
:



Hi,

I just re-upped the binary file.


Thanks again Wolfgang, but...
The FAT_xxx range of keywords still seem to be missing and thus produces  
an "unknown procedure" error on FAT_DRIVE in the BOOT file.


Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] SMSQ/E 3.33

[Bob Spelten via Ql-Users]

Op Sun, 29 Apr 2018 11:40:57 +0200 schreef Wolf via Ql-Users  
:



Hi all,

SMSQ/E 3.33 is out, get it as usual from
www.wlenerz.com/smsqe


Thanks Wolfgang for the update.
But there are some confusing aspects about the Q68 files.
Both count 350.000 bytes, one .SYS and one .WIN.
When Viewed they look the same. Should the .WIN not be a valid QLWA file  
containing the .sys?


I've copied the .sys to the existing Q68_SMSQ.WIN on my SD using QPC2,  
replacing the previous SMSQ. The existing BOOT was used to start the Q68.

The boot file now gave an error on FAT_DRIVE 'unknown procedure'.
Looking at the list of commands with HyperHelp showed no FAT_ keywords  
were found.


Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] QPC2 4.04 BUG

[Bob Spelten via Ql-Users]

Op Sun, 22 Apr 2018 18:00:20 +0200 schreef RWAP Software via Ql-Users  
:



Does anyone know why the following in QPC2 reports "Invalid Channel ID"

WINDOW 448,200,32,16
PAPER #1,3

In fact, any attempt to change #1 after the WINDOW command reports an  
invalid channel.



Tested on a bare QPC2v404, this could happen if channel #1 is closed.
The WINDOW command does then not produce an error on the default channel,  
which will be #0 now, but the PAPER #1 command does.


Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] Graphic objects and padding

[Bob Spelten via Ql-Users]

Op Sat, 14 Apr 2018 11:23:04 +0200 schreef pjwitte via Ql-Users  
:




(...)
Thanks for your replies, most of which agree with my understanding but,  
unfortunately, not with my recent experience. (Eg see my post on the  
Forum for one example:  
http://www.qlforum.co.uk/viewtopic.php?f=3=2272=40#p22823)


And that is the crux of the matter: Without a definitive description its  
each to his own interpretation. This is bad for those of us trying to  
produce fun or useful stuff. And the number of offerings out there that  
dont really work, or work inconsistently, dont exactly evoke the sense  
that "The QL" is a serious or relieable machine. It certainly putsme off  
at times (my own failings in this regard notwithstanding ;)


If those who "wrote the book" on these matters arent able/willing to  
pipe up, then we'll have to waste some time R-ingTFBs and doing the  
tests ourselves. I'll be back.



I must admit having missed your Forum entry.
Without running your program I know that WSASV (EP4) and PSAVE (QPTR) will  
add padding, sometimes even 1 Long more than needed.
They were written in QL mode days and clearly never changed for High  
Colour times.
The same is probably true for the "Books", this padding is not mentioned  
there. That's why SQRview tests for any padding.


When saving such a PIC as SPR the padding is already there and needs not  
to be added but too much padding may result in a slanted sprite if lines  
are not cut properly as it relies on x-width and not on line increment as  
PICs do.


Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] Graphic objects and padding

[Bob Spelten via Ql-Users]

Op Fri, 13 Apr 2018 12:12:56 +0200 schreef pjwitte via Ql-Users  
:



Could someone please explain the rules to me regarding the padding of
graphics objects for the two main formats: Sprites and Pics/PSA?

I thought Id worked it all out, at least for some modes, but my rule-
book does not appear to be complete, nor provide stable answers in all
cases. Also, there are some  formats Im not able to test.. So now Im
confused and would like to get a "definitive" take on the matter.

(...)


As I understand it,
Sprites must always be padded to Longs for all modes QL or GD2.

PIC/PSA must be padded for modes 4 & 8.
The GD2 modes 16 to 33 should/need not be padded and some viewers may have  
problems if they are.

SQRview will detect excess padding and not show it.

Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] Hermes or SuperHermes, this is the problem! :-D

[Bob Spelten via Ql-Users]

Op Thu, 05 Apr 2018 00:04:19 +0200 schreef Giorgio Garabello via Ql-Users  
:



so:
IPCVER$  0  NON HERMES
IPCVER$  1  HERMES
IPCVER$  3 SUPERHERMES

Correct?


Almost.
0= non Hermes, 1 or 2= Hermes, 3= SuperHermes.
My Hermes is 2.20, my SHermes is 3.5.

Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] FiFi

[Bob Spelten via Ql-Users]

Op Fri, 30 Mar 2018 06:48:09 +0200 schreef Wolf via Ql-Users  
:



Hi all,

FiFi, my formerly commercial file finder can now be downloaded from my  
site.


www.wlenerz.com/qlstuff


Thanks Wolfgang for the update.
One small bug seems to be present though.
When I set the colours to be copied from Qmenu, FiFi will start as a  
2x1a0x0 window, which is not very practical.


I checked with my previous v4.31 which was not set up for Qmenu but it  
behaves exactly in the same way when done so.

The bug must have been asleep for some time.

Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] Hermes or SuperHermes, this is the problem! :-D

[Bob Spelten via Ql-Users]

Op Wed, 04 Apr 2018 10:55:59 +0200 schreef Giorgio Garabello via Ql-Users  
:



SMSQ / E with the MACHINE command can detect if Hermes / Superhermes is
present. Is there a way to distinguish via software if it is hermes or
superhermes in order to automatically load the correct drivers?


The method I use is to test the Hermes version:
: LRESPR dev1_IPCexts_bin
: mouse%= IPCVER$()
: IF mouse% =3 : LRESPR dev1_IPCextKB_bin : REM it's SuperH!

The IPCexts are part of the Hermes package, only 356 bytes.
Its Function IPCVER$() returns a string as "1.nn" but we only need the  
first digit. No Hermes would give "0.00".
The IPCextKB_bin is the proper SHermes keyboard driver where KB could be  
IT in your case.


Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;

---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

___
QL-Users Mailing List

Re: [Ql-Users] Menu_rext_english

[Bob Spelten via Ql-Users]

Op Sun, 11 Mar 2018 10:25:26 +0100 schreef simon629--- via Ql-Users  
:


Hi Everyone does Menu_rext_english does it work on LaunchPad OK  
Thankssimon629Simon Foster


Menu_rext is not a required extension needed for Launchpad, according to  
its page on Dilwyn's site.
Launchpad is/has its own file manager and probably doesn't use anything  
from Menu_rext.


Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;
___
QL-Users Mailing List

[Ql-Users] Sjef vd Molengraaf

[Bob Spelten via Ql-Users]

I am sad to inform you all that Sjef van de Molengraaf passed away earlier  
this week at the age of 73.
As long time secretary of the Dutch SIN_QL_AIR foundation he will be  
remembered by many international QL'ers. He was the driving force behind  
many great Eindhoven meetings during the 90's and later, until they ended  
in October 2008.
He seldom posted on this list but it kept him informed of what was going  
on in the QL community.


Our thoughts are with his family.

Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;
___
QL-Users Mailing List

Re: [Ql-Users] Merry Christmas with SMSQ/E

[Bob Spelten via Ql-Users]

Op Thu, 28 Dec 2017 07:43:13 +0100 schreef Wolf via Ql-Users  
:



Hi,
yes that's a bug.
Somehow the return stack gets confused/overwitten (stack overflow!),  
causing a jump to a strange address where you then will get an illegal  
instruction error.
I've checcked that, under SMSQmulator this isn't due to the replacemnt  
FP routines, which it isn't.



It looks like it's an old bug.
On my SGC/AUR (SMSQ/E v3.26) the Kaboom is modest.
No error is reported, it just freezes after one howl from Sysmon.
No keyboard or mouse response anymore.

Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;
___
QL-Users Mailing List

Re: [Ql-Users] Strange channel bugs?

[Bob Spelten via Ql-Users]

Op Sun, 12 Nov 2017 18:11:57 +0100 schreef Per Witte via Ql-Users  
<ql-users@lists.q-v-d.com>:



Is this the sort of issue you mean?

100 CLS
110 FOR i = 0 TO 4
120  FOR j = 0 TO 4
130   AT i * 2, j * 6: PRINT i; ','; j;
140  END FOR
150 END FOR
160 :
170 PRINT
180 PAUSE

RUNs fine under SMSQ/E, displays only the first line if compiled as a  
Qlib job (but no errors or warnings are given - either at compile time
or when executing). Turbo, even under SMSQ/E, kicks up a fuss at parse  
time, and if

you load it in SuperBASIC under Qdos or Minerva lines 140 and 150 show up
as MISTake's. So its normally a good idea to try out problematic code in
different environments. It doesnt necessarily have to work 100% before
certain mistakes reveal themselves.


That's exactly what I mean.
Once fixed the compiler bug was gone and the compiled program did no  
longer freeze and produced it's windows.


The call to my procedure with the END FOR line was even REM'd out but  
still QLIB got in trouble and messed up the _obj and SMSQE.



On 12 November 2017 at 13:54, Bob Spelten via Ql-Users <
ql-users@lists.q-v-d.com> wrote:

Op Tue, 12 Sep 2017 18:47:35 +0200 schreef Bob Spelten  
<b...@upcmail.nl>:


What's happening?


I have successfully compiled a new version of my program.
That's to say, there were no errors reported by BasicLinker or  
Qlibeator.
But when the _obj is executed nothing seems to happen, no menu to act  
on.

It's there in the JOBS list but no channels were opened for it.
When I then kill this job it has the effect that the QD with the
programs  _bas can no longer produce lists of my Procs and FNs from the
C-F6 to C-F8 buttons or keys.

(...)

It's been 2 month since I reported this problem.

After many attempts to locate the problem Wolfgang Lenerz finally found
the culprit.
It was one missing index variable on an END FOR line.

"Unnamed NEXT, EXIT and END statements" is a feature of SMSQ/E.
Normally I am no fan of this as it can make the program more difficult  
to read, especially when start and end of the loop are far apart.

This one (actually two) had escaped my proof reading.

Now it turned out Q_Liberator also cannot deal with it and can, as was  
the case here, corrupt SMSQ/E in a sneaky way without a Sysmon alarm.

So be warned, don't use this "feature" with Qlib!


Bob



--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;
___
QL-Users Mailing List

Re: [Ql-Users] Strange channel bugs?

[Bob Spelten via Ql-Users]

Op Tue, 12 Sep 2017 18:47:35 +0200 schreef Bob Spelten :


What's happening?

I have successfully compiled a new version of my program.
That's to say, there were no errors reported by BasicLinker or Qlibeator.
But when the _obj is executed nothing seems to happen, no menu to act on.
It's there in the JOBS list but no channels were opened for it.
When I then kill this job it has the effect that the QD with the  
programs  _bas can no longer produce lists of my Procs and FNs from the  
C-F6 to C-F8 buttons or keys.


(...)


It's been 2 month since I reported this problem.
After many attempts to locate the problem Wolfgang Lenerz finally found  
the culprit.

It was one missing index variable on an END FOR line.

"Unnamed NEXT, EXIT and END statements" is a feature of SMSQ/E.
Normally I am no fan of this as it can make the program more difficult to  
read, especially when start and end of the loop are far apart.

This one (actually two) had escaped my proof reading.

Now it turned out Q_Liberator also cannot deal with it and can, as was the  
case here, corrupt SMSQ/E in a sneaky way without a Sysmon alarm.

So be warned, don't use this "feature" with Qlib!

Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;
___
QL-Users Mailing List

Re: [Ql-Users] EXT_PROC

[Bob Spelten via Ql-Users]

Op Wed, 08 Nov 2017 21:05:55 +0100 schreef Per Witte via Ql-Users  
:



I was just made aware of a number of features in Q-Lberator that I havent
seen documented anywhere: EXT_PROC, EXT_FN, GLOBAL, and possibly others.  
I
believe I have a general idea of what theyre about, but should like to  
see

some documentation. Ive been told there is a chapter 14 in some manuals?
The two pdf manuals I found online, one of them claiming to be of V3.36,
dont mention these keywords, and my printed one is altogether of an older
vintage.

Anyone?


A version of the manual is at Dilwyn's download site.
< http://www.dilwyn.me.uk/qlib/Q_Liberator%203.36%20manual.pdf >

I just did a quick check of the .pdf against my original 3.36 printed  
manual and everything including chapter 14 is there.
However chapter 15 (Release 3.3 Enhancements) from my copy is missing from  
the .pdf.

I'll try to scan this asap.

Bob




--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;
___
QL-Users Mailing List

Re: [Ql-Users] QMenu v8

[Bob Spelten via Ql-Users]

Op Thu, 21 Sep 2017 11:00:45 +0200 schreef Giorgio Garabello via Ql-Users  
:



7.64 support GD2?


No, this was the last mode 4 version.
v7.65 is the first attempt at GD2 compatibility.
IN v8.xx the Long Words that hold the palette parameter in the low bytes,  
also use the high bytes for extra options like timeout.
This should not be a problem when used from S*Basic but may be an issue  
when called from machine code when the high bytes are taken for granted.

This could be why in QDT LSEL does not work properly.

Bob


--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;
___
QL-Users Mailing List

[Ql-Users] Strange channel bugs?

[Bob Spelten via Ql-Users]

What's happening?

I have successfully compiled a new version of my program.
That's to say, there were no errors reported by BasicLinker or Qlibeator.
But when the _obj is executed nothing seems to happen, no menu to act on.
It's there in the JOBS list but no channels were opened for it.
When I then kill this job it has the effect that the QD with the programs   
_bas can no longer produce lists of my Procs and FNs from the C-F6 to C-F8  
buttons or keys.


When killing this QD I did get a strange channel error:
 "at line 2430:1 invalid channel ID"
This was from the clock_bas executing in the background.
When SMSQ/E was RESET this produced a similar error in my BOOT file.

These errors were not given every time but after what looked like a proper  
reset, an newly started QD still did not do C-F6/F8.

The QPC2 job has to be restarted before QD behaves normal again.

Under SMSQmulator the _obj also executes without opening any windows but  
the QD anomaly doesn't seem to happen there.


I understand that my source _bas is faulty but what can cause such an  
upset and where do I start looking for a fix?

Executed from QD/Sbas the program runs fine.

Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;
___
QL-Users Mailing List

Re: [Ql-Users] Qbase

[Bob Spelten via Ql-Users]

Op Sun, 10 Sep 2017 20:19:22 +0200 schreef Daniel Baum via Ql-Users  
:



One more thing:

I should add that limiting the number of displayed records to 1000 works
fine, so I could fix the problem by using a paging arrangement.


The test _dbs has 3111 records by 6 fields making 18666 menu items.
That is well within the limit of items (<32K) WMAN2 can handle in the AW.
Records times Fields must be less.
But there is also a limit in S*Basic of 65K for indexing second and third  
dimensions, in this case Fields x Field_length (including length word).
As you used Fields as the first dimension instead, 2nd (Records: 3111)  
times 3rd (length: 20 +2) would be just too much.
As records will in most cases be the highest number, making it the first  
dimension is the best choice.
So checking these limits and using paging is the only option for a large  
database that exceed these limits.


Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;
___
QL-Users Mailing List

Re: [Ql-Users] Qbase

[Bob Spelten via Ql-Users]

Op Sat, 09 Sep 2017 15:06:06 +0200 schreef Daniel Baum via Ql-Users  
:



Hi all,

Latest pictures.

Qbase is now rescalable. It starts at 512x256:

https://www.dropbox.com/s/exexw4s5ppexyi4/qbaseTab512x256.jpg?dl=0

and can get as big as you want:

https://www.dropbox.com/s/o9yi56lqms4ppg3/qbaseTabBig.jpg?dl=0

These pictures show the automatic proportional column width in the  
tabular
view, which has actually always worked, but was less than obvious until  
now.


Getting there...


Looking good.

I played with the current version as found in BP143 and I did get a Qlib  
error when hitting the Tabulate button.
I must admit it was a big database of over 3000 records and 6 fields, with  
one of 500 characters.

Qbase probably tried to get them all in one array for the menu items.
The big field could of course be cut to the visible column width.

"Qlib error 16, array too big" suggests there are too many elements.
A dimensions check would be nice here, so the Tab action can be aborted  
with a warning, before the program crashes.

(See sections 6.4 & 8.8 of the Qlib 3.3 manual)

Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;
___
QL-Users Mailing List

Re: [Ql-Users] QxlwinReader

[Bob Spelten via Ql-Users]

Op Wed, 21 Jun 2017 16:34:19 +0200 schreef Wolfgang Lenerz via Ql-Users  
:



Hi Bob,


This problem also exists on the HD drive of my Aurora or QXL-PC.
If I can find a working DD drive I may test this later.



Again just to be clear : yo also cannot read/write/format disks when  
they are HD (1.4 MiB) disks, when using he Aurora. Does this need a  
GOldcard or Supergoldcard (and if so, which do you use?).



Just to add some clarity I did some testing.

A) Machine 1 = QL(i6)+SGC +ED +HD drives, SMSQ/E v3.13 booting from  
ROMdisq.

Reading and writing a DD disk was OK on both ED & HD!
When I replaced the HD with a DD drive reading & writing was also OK.

B) Machine 2 = Aurora +SGC +ED drive, SMSQ/E v3.21 booting from Qubide  
disk.

Reading DD disk OK, writing hangs the system, hardware reset needed!
When I replaced the ED with a DD drive reading was OK, writing hangs.
No null length files were opened on the DD medium.
Also reading an msdos DD was OK but writing hangs again.
On this Aurora under QDOS, reading & writing a DD disk was not a problem.
Repeating this test with SMSQ/E v2.91 confirmed DD was OK there.

C) Machine 3 = msdos 7, QXL plus HD drive, with SMSQ/E v3.21.
Reading and writing a DD disk was OK!
My earlier claim that QXL also gave problems was based on older PC  
hardware which is no longer functioning and may have been a faulty disks.


All testing was done with QPAC2 Files using the Backup and View options  
and performed on the same disk.
I no longer have a GoldCard to compare with but these tests seem to  
suggest an Aurora/SMSQ conflict. Both SGC's report a v2.49 ROM.


Reading and writing ED or HD disks may give occasional problems which I  
suspect are individual disk faults and usually only report medium errors.
I have not done any formatting tests but problems on Aurora in the past  
made me adopt the practice of always doing this under QDOS, the whole box  
of 10 in one go.


I hope this helps,
Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;
___
QL-Users Mailing List

Re: [Ql-Users] QxlwinReader

[Bob Spelten via Ql-Users]

Op Wed, 21 Jun 2017 11:58:01 +0200 schreef Andrea Carpi via Ql-Users  
:



(...)
If it were possible, it would be nice that with QXL, you should not have 
a QXL.WIN for DOS device (C :, D :, E: etc.), but it would be

configurable as with QPC in any subdirectories

This can be simulated on the PC side in the AUTOEXEC.BAT with a DOS  
command like SUBST: e.g. SUBST X: D:\qxl\data
This way you can point win2 to drive 'X' and put your QXL.win inside the  
given directory and there is no need to create up to 8 partitions.

For 'X' you can use characters that do not upset anything on the PC side.


GC / SGG / Aurora The DD floppy problem. It's not
just formatting but also reading/writing. They just do not work.
Verified on both Aurora + SGC and QL + simple CG. I only have ED
drives, so I do not know if the problem exists by using other hardware
such as HD floppy drives or DD floppy drives.


This problem also exists on the HD drive of my Aurora or QXL-PC.
If I can find a working DD drive I may test this later.

Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;
___
QL-Users Mailing List

Re: [Ql-Users] SMSQ/E bugs: is a fix possible?

[Bob Spelten via Ql-Users]

Op Thu, 08 Jun 2017 00:38:56 +0200 schreef via Ql-Users  
:



Hi All (but especially Wolfgang, Tony, Marcel or anybody else involved in
SMSQ/E development and/or source maintainance),
(...)

1) SMSQ/E for Aurora does not read anymore DD floppy disks. Everything  
was working till 2.91. From the tests did on some SMSQ/E version we  
found 2.95

has the bug, 2.98 crashes, 3.03 has the bug


A quote from my email 17/03/2012
--->
This issue also was raised some years ago.
IIRC, the 2.91 source was not available to compare and check where it went  
wrong.

--->


2) SMSQ/E for QXL
in DISP_COLOUR 3:
- DISP_SIZE 512,256 - works OK
- DISP_SIZE 640,480 - works OK
- DISP_SIZE 800,600 - no error but the resolution is 640x480
- DISP_SIZE 1024,768 - no error but the resolution is 640x480

in DISP_COLOUR 0:
- DISP_SIZE 512,256 - works OK
- DISP_SIZE 640,480 - works OK
- DISP_SIZE 800,600 - no error but the screen is corrupted and unreadable
- DISP_SIZE 1024,768 - no error but the screen is corrupted and  
unreadable


So the maximum possible resolution is 640x480

Provided the SMSQE.EXE is correctly configured for the maximum size, the  
unknown factor is the hardware it's running on.

In mode 4, 1024x768 is not a problem here.
In mode 32 this results in 800x600 without screen corruption.
Both on my old hardware with 1MB graphics as on my current machine with  
2MB graphics card.
The RAM demand is quite high, even at 800x600 half my 8MB is gone after  
BOOT so it's debatable what the benefit is of m32@1024x768.



BAUD returns an error


No comment, never used the SER port from QXL.


3) SMSQ/E for Gold Card does not initialise external interface.

Up to v3.13 there was only 1 Gold/Aurora version so I have always used the  
Aurora .bin after that.
When this point came up recently I tested the current GoldCard.bin which  
did not see my ROMdisq after it was LRESPR'd from there.


I guess it does not make sense to spend effort for SMSQ/E for QXL, but  
the issues on the GC/SGC/Aurora versions I think would deserve at least

A try.
N.3 maybe is just a question of understanding whether it makes sense to  
keep all these versions and in case link again the "Initalise QL ROM"
where missing. The DD floppy bug would deserve a fix hoping all source 
codes of old versions are available as I think there are still quitesome  
users  with GC/SGC/Aurora with DD disks.


To answer Wolfgang's question: My QXL2 and Aurora systems are mainly used  
for testing and can, because of the slow speed compared to QPC2, be  
revealing in how PE menus are being build up.

As long as I can keep an ISA machine alive I will keep the QXL2 going.

Bob

--
The BSJR QL software site at: "http://members.upc.nl/b.spelten/ql/;
___
QL-Users Mailing List