Re: [Ql-Users] SMSQmulator 2.28

2020-02-29 Thread Wolf via Ql-Users

Hi,

The scanner emulates a keyboard?

Does it input anything other than normal keystrokes (i.e. no shift, 
ctrl, alt, no home/end etc, cursor keys etc?)


Wolfgang

Le 29/02/2020 à 11:41, Kjartan Geble Olsen via Ql-Users a écrit :

Would it be possible to speed up the keyboard handling?
It fails to correctly read a barcode scanner.
Random characters lost on each scan.

Kjartan

On Fri, 07 Feb 2020 11:34:02 +0100, Wolfgang Lenerz via Ql-Users 
 wrote:



Hi all,

SMSQmulator 2.28 is out now.

(www.wlenerz.com/smsqmulator)

Have fun!

Wolfgang

NB Sorry if this gets double-posted, I haven't had a return yet...
___
QL-Users Mailing List




___
QL-Users Mailing List

Re: [Ql-Users] QL-VGA

2020-01-17 Thread Wolf via Ql-Users

Hi,

I'd like that too, since I'm on no social media nor the forum.

Wolfgang



I like to see at least major posts here on the QL-Users mailing list.

QL forever!

Cheers,
Urs


___
QL-Users Mailing List


Re: [Ql-Users] Assembly language eComic, issue 7, out now!

2019-09-30 Thread Wolf via Ql-Users

Hi Norman,

as always an enjoyable read.


Wolfgang
Nb Why e"Comic"?
___
QL-Users Mailing List


Re: [Ql-Users] PWfile and SMSQmulator

2018-12-06 Thread Wolf via Ql-Users

Hi,

ah ok, thanks.

Wolfgang


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.



___
QL-Users Mailing List


Re: [Ql-Users] PWfile and SMSQmulator

2018-12-06 Thread 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)?


Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] PWfile and SMSQmulator

2018-12-06 Thread Wolf via Ql-Users

Hi,



But then my next question is : why is 'nfa' OK  and  'dos' is not OK?




Because SMSQmulator does not have a DOS device, unless you explicitly 
set the NFA device's usage name to "DOS", either using the "nfa_use" 
command, or through the "Config" menu.


Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] PWfile and SMSQmulator

2018-12-06 Thread Wolf via Ql-Users

Hi,

Yes, their website states:
"
ProWesS is now available for free using the GPL, you can download it 
(distribution, documentations, examples, source) "


Wolfgang


an someone confirm that all PROGS' Prowess stuff is now open source and

can/may be copied and distributed freely?

If so, I could send those programs to Dilwyn.

François Van Emelen



___
QL-Users Mailing List

___
QL-Users Mailing List

Re: [Ql-Users] PWfile and SMSQmulator

2018-12-04 Thread Wolf via Ql-Users

Hi,

as far as I know, all PROGS' Prowess stuff is now open source, perhaps 
you could send the programs to Dilwyn for inclusion on his site...


Regards

Wolfgang


on 04/12/2018 10:35, François Van Emelen via Ql-Users wrote:

Op 4/12/2018 om 7:25 schreef Wolfgang Lenerz via Ql-Users:

Hi,

where can you get this program?

Wolfgang


Hi All,

Has someone been able to use PWfile (file manager ProWesS/ProForma) 
with a 'NFA'-device with SMSQmulator ?


François Van Emelen




___
QL-Users Mailing List

___
QL-Users Mailing List


Hi Wolfgang,

PWfile is part of the programs I bought from PROGS such as PWfile, 
PWsearch,PWlist... all running with ProweSS/ProForma.




___
QL-Users Mailing List

___
QL-Users Mailing List

[Ql-Users] QD 2018

2018-09-21 Thread Wolf via Ql-Users

Hi,

I'll check this when the chaos from moving houses abates.

Wolfgang

On 21/09/2018 00:27, pjwitte via Ql-Users wrote:

On 20/09/2018 23:57, desin via Ql-Users wrote:



Anyone else have these symptoms?

Per


System QPC 4.05 SMSQE.3.33

from FiFi to QD B 05  (B 04 is ok)

QD hangs then QPC freezes

i bet Sysmon would be yodeling


greetings from Switzerland

    Markus

Strange. Ive been using QD B05 heavily these past few days, including 
with FiFi. No problem until I needed to test something on SMSQmulator.. 
And, yes; there was pronounced yodeling


P


___
QL-Users Mailing List

___
QL-Users Mailing List

Re: [Ql-Users] QL-SD order page

2018-09-02 Thread Wolf via Ql-Users

Hi,

So Marcel has become a hardware manufacturer...



And yes, also thanks to Wolfgang for writing the first driver! Without
it I would probably not have done what I did.



Whilst I may have had the original idea and written the original driver 
(adapted from the Q68 SDHC driver), the driver as it stands now is 
practically entirely Marcel's work, so all the kudos goes to him!


Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] FiFi 5.01

2018-09-01 Thread Wolf via Ql-Users

Hi all,

Due to some linking problems, the non-english versions of FIFI 5.01 
didn't work - I've re-upped the correct version now.


Thanks to Giorgio for spotting that.

Wolfgang
(scraping the egg off his face)
___
QL-Users Mailing List


[Ql-Users] FiFi 5.01

2018-08-31 Thread Wolf via Ql-Users

Hi all,

FiFi 5.01 is out. It contains various bug fixes including an Lrespr bug 
(thanks to Marcel for pointing this out) and there is now an italian 
version (thanks to Giorgio Garabello for translations).


www.wlenerz.com/qlstuff

Have fun!

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] QL Pawn

2018-08-11 Thread Wolf via Ql-Users

Hi Dilwyn,

a big thanks to you and Rich for making this available.

Wolfgang

On 10/08/2018 11:18, Dilwyn Jones via Ql-Users wrote:
Thanks to the former Magnetic Scrolls team; QL Pawn has now been added 
to the Sinclair QL Homepage - 
http://www.dilwyn.me.uk/games/adventures/index.html as freeware.


Rich Mellor has sent me both a floppy disk image version, and a zip file 
containing the three MDV images and a short instruction file telling you 
which microdrive image goes in which slot and when to change to the 
third cartridge image.


Description of The Pawn available on the QL Wiki at 
https://qlwiki.qlforum.co.uk/doku.php?id=qlwiki:ql_pawn[]=pawn


Dilwyn
___
QL-Users Mailing List



___
QL-Users Mailing List


Re: [Ql-Users] return values QPC2 <>SMSQMULATOR

2018-08-05 Thread Wolf via Ql-Users

Hi,
does your comment mean the question is solved?

Wolfgang

On 05/08/2018 10:31, François Van Emelen via Ql-Users wrote:


Thank you for your explanation.

Have a fine day,

François Van Emelen



___
QL-Users Mailing List

___
QL-Users Mailing List

Re: [Ql-Users] return values QPC2 <>SMSQMULATOR

2018-08-04 Thread Wolf via Ql-Users

Hi,

I didn't get the original question, for a few days I seem to have had 
some email trouble...


Wolfgang

On 04/08/2018 18:01, Norman Dunbar via Ql-Users wrote:

On 03/08/18 12:01, François Van Emelen via Ql-Users wrote:

Hi all,
(if there is still someone listening, of course.)


I'm listening, but unfortunately, I don't know the answer. Sorry. :(


Cheers,
Norm.


___
QL-Users Mailing List

[Ql-Users] Qptr manual 6.04

2018-07-22 Thread Wolf via Ql-Users

Hi all,

I updated the QPTR manual to version 6.04, some additional corrections 
and information are now included.


wlenerz.com/qlstuff

Have fun!


Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] Q68 & QD

2018-06-30 Thread Wolf via Ql-Users

Hi,

this has been solved and fixed.

The fixed binary version (only) is included in the binaries zip file 
which I re-upped to the smsqe site.


Thanks to Bob for finding this and testing!

Have fun.

Wolfgang

On 23/06/2018 14:07, Bob Spelten via Ql-Users wrote:

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


___
QL-Users Mailing List


Re: [Ql-Users] Q68 & QD

2018-06-23 Thread Wolf via Ql-Users

Hi,

 I'll check this next week.

Wolfgang






Le 23/06/2018 18:55, Derek via Ql-Users a écrit :

Hi Bob,
I tried QD B.01 on a Q68 SMSQ/E 3.33, in 1024x768 (DISP_MODE 7) with the QD 
margin set to120 characters.
Typing past 120 characters makes the Q68 freeze.
I also tried in DISP_MODE 4 - 1024x768 4 colours. Much faster, but same 
problems.
I will try all screen resolutions and report back.
RegardsDerek
 Original message From: Bob Spelten via Ql-Users  
Date: 23/06/2018  13:07  (GMT+00:00) To: ql-users  Cc: Bob Spelten 
 Subject: [Ql-Users] Q68 & QD
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


___
QL-Users Mailing List

Re: [Ql-Users] Qdos/Sms reference manual

2018-06-10 Thread Wolf via Ql-Users

Hi all,

new version on the site, should keep bookmarks etc..., thanks, Per, for 
pointing that out.


Wolfgang
___
QL-Users Mailing List


[Ql-Users] Qdos/Sms reference manual

2018-06-10 Thread Wolf via Ql-Users

Hi all,

the updated Qdos/Sms reference manual (v. 4.4) is now on my site.

Have fun!

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] QA.RESRI info incorrect

2018-06-10 Thread Wolf via Ql-Users



Hi Per,

yes I misquoted myself.

On SMSQ/E it is not necessary for A1 to contain the ARI stack pointer 
before calling this vector.


Regards

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] QA.RESRI info incorrect

2018-06-08 Thread Wolf via Ql-Users

Hi,

I'll amend the documentation. I will also mention that this vector, 
under SMSQ/E, simply does nothing when called from a compiled program. I 
already added a note that under SMSQ/E it is not necessary to save the 
stack pointer in BV_RIP(A6) before calling this vector.


There are also other additions/corrections to the documentaton.

I'll release the new doc either today or tomorrow.

Wolfgang




On 08/06/2018 19:29, pjwitte via Ql-Users wrote:
Having gone through it all again, Ive come to the conclusion that the 
bugs are in the documentation! This is what it should look like:

||Vector $11A Reserve Room on Arithmetic Stack QA.RESRI
Call parameters Return parameters
D1.L Number of bytes required  D1 ???
D2 D2.L ???
D3 D3.L ???
A0 A0 Preserved
A1 A1 ???
A2 A2 Preserved
A3 A3 Preserved
Error returns: none
In other words, in the case of insufficient memory this routine returns 
to a higher level; it never comes back here. There is no need, in fact 
it is a mistake, to test d0 on return from this routine.

If anyone knows otherwise then please let ut know!

Per
___
QL-Users Mailing List



___
QL-Users Mailing List

[Ql-Users] BouQLder Qlash source code

2018-05-26 Thread Wolf via Ql-Users

Hi all,

the source code for BouQLder Qlash is now available from my site.

Have fun!

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] Front Page

2018-05-25 Thread Wolf via Ql-Users

Hi Dilwyn,

Thanks for that, and for your untiring efforts to make your website so 
comprehensive and up-to-date!


Regards

Wolfgang

On 21/05/2018 19:50, Dilwyn Jones via Ql-Users wrote:
I'm pleased to announce that Peter Chambers of GAP Software has given 
permission for the Front Page range of QL desktop publishing programs to 
be made available as freeware.


So I have made available copies of Front Page, Front Page Extra and 
Front Page Extra 2 programs.


Front Page was the first version and can run on unexpanded systems.
Front Page Extra was an enhanced version.
Front Page Extra 2 added even more facilities such as higher resolution 
fonts.


I've included manuals for FP Extra and FP Extra 2 as scanned Word and 
PDF files. Unfortunately, I don't have a copy of the manual for the 
original version, so if anyone has a copy which could be scanned and 
made available, please get in touch.


Download the Front Page programs from the Graphics page on my website at 
http://www.dilwyn.me.uk/graphics/index.html


Dilwyn

___
QL-Users Mailing List



___
QL-Users Mailing List


Re: [Ql-Users] How do you find the Driver Definition Block (DDB) base-address from SBASIC for the NET device

2018-05-19 Thread Wolf via Ql-Users

Hi,


Glad I could help, I'll be interested to see how it goes!

Have fun.

Wolfgang

On 19/05/2018 16:31, Martyn Hill via Ql-Users wrote:

Great observation, Wolfgang!

So, that adjustment to a3 comes out to $1E (30) bytes /*later */in the 
DDB - so rather, once the ndt_ctab offset of $50 is added, we need to 
look at $6E through $8E for the timing constant table.


I now see:

$6E:    134
$70:  13570
$72: 19
$74:    328
$76:   2034
...

This looks more promising! Now I need to check against the expected values.

The calculations carried out in nd/initv take three words for each 
constant stored by the macros in qxl.asm (time,offset,scale), which for 
the first 5 values (assuming a 20MHz clock) are:


nqx_wgap:    200,28,28 =   141
nqx_bace:    2,28,28  = 14185
nqx_csct:    30,28,28 = 20
nqx_esct:    485,28,28    =   345
nqx_wsct:    3000,28,28   =  2141
...

Aha! We have accounted for the 5% difference between nominal QNET 
timings and what was measured down the wire from my QXL!


The actual clock-rate is empirically measured somewhere else in the 
initialisation code and stored in d1 ready for nd/initv to use, rather 
than a fixed 20Mhz scale-factor which is how the original scaling factor 
assumed in qxl.asm. Would seem that the measured clock-rate was slightly 
lower than it really is.


I'll go ahead and switch-out the stored values in the DDB constants 
table with the 5% higher figures and re-test.


I love a good detective-story!

Stand-by!
M.
On 19/05/2018 13:48, Wolf via Ql-Users wrote:

Hi,

This is what you can find in the NET driver i/o code:

nd_io
    pea ndd_test(a3)    push pseudo return address

    lea ndd.leni(a3),a3 normal linkage ***

    move.w  io.serio,a2 and do serial IO
    jmp (a2)

As  you can see, A3 is adjusted there, perhaps you sould look at the 
DDB with the same offset.


HTH

Wolfgang


On 19/05/2018 13:15, Martyn Hill via Ql-Users wrote:

Thanks Wolfgang (and Jan via the Forum)

Having now found what looks like the DDB - taking in to account the 
-$18 offset from the entry in the CDB - the resultant list of words 
at offset ndt_ctab ($50) looks suspicious, thus:


50:       0
52:     124
54:  -18236
56:       0
58:      36
5A:       1
...
6A:   20085
6C:       0
6E:     134

The '20085' at offset $6A in particular looks more like an RTS 
instruction than the timing constant for 'receive bit timeout'.


Anyway, I'll keep digging. Thanks!

Martyn.

On 19/05/2018 09:41, Wolf via Ql-Users wrote:

Hi,

The best way would be to get the channel definition block (CDB) for 
a channel to the device. I don't know offhand of a Basic keyword 
that will do it for you, Toolkit III used to have such a function, I 
don't know whether that still available, though.


If you have that, then the pointer to the driver definition block 
(DDB) lies at offset chn_drvr (=4) in the CDB - you can just PEEK_L 
that. Be careful, however, the pointer there normally points to 
offset iod_iolk (=$18) within the DDB, so all other offsets should 
be reduced by that same amount.


HTH

Wolfgang

On 18/05/2018 22:01, Martyn Hill via Ql-Users wrote:

Hi everyone

In the spirit of double-posting between here and the QL Forum :-) I 
thought I'd ask my question here, too...


I'm continuing to explore the QL network across a range of 
platforms - now with my refurbished QXL2 card (thanks, Derek!)


The bit-timings on the QXL under SMSQ/E v3.33 (and also on v2.76) 
prove to be slightly-out from the nominal 11.2us, resulting in 
failed/unreliable comms with both my Iss7 QL and my prototype QNET 
to USB adapter (still a work in progress.)


Given that the timings-constants for the NET device are exposed 
under SMSQ/E and stored ready for adjustment in the DDB of the NET 
device, I'm trying to find the base address of the DDB from SBasic.


Any help appreciated!

The original post appears here, with pictures :-)

 https://qlforum.co.uk/viewtopic.php?f=3=2462

Regards,
Martyn.

___
QL-Users Mailing List

___
QL-Users Mailing List



___
QL-Users Mailing List



___
QL-Users Mailing List

Re: [Ql-Users] How do you find the Driver Definition Block (DDB) base-address from SBASIC for the NET device

2018-05-19 Thread Wolf via Ql-Users

Hi,

This is what you can find in the NET driver i/o code:

nd_io
pea ndd_test(a3)push pseudo return address

lea ndd.leni(a3),a3 normal linkage  ***

move.w  io.serio,a2 and do serial IO
jmp (a2)

As  you can see, A3 is adjusted there, perhaps you sould look at the DDB 
with the same offset.


HTH

Wolfgang


On 19/05/2018 13:15, Martyn Hill via Ql-Users wrote:

Thanks Wolfgang (and Jan via the Forum)

Having now found what looks like the DDB - taking in to account the -$18 
offset from the entry in the CDB - the resultant list of words at offset 
ndt_ctab ($50) looks suspicious, thus:


50:       0
52:     124
54:  -18236
56:       0
58:      36
5A:       1
...
6A:   20085
6C:       0
6E:     134

The '20085' at offset $6A in particular looks more like an RTS 
instruction than the timing constant for 'receive bit timeout'.


Anyway, I'll keep digging. Thanks!

Martyn.

On 19/05/2018 09:41, Wolf via Ql-Users wrote:

Hi,

The best way would be to get the channel definition block (CDB) for a 
channel to the device. I don't know offhand of a Basic keyword that 
will do it for you, Toolkit III used to have such a function, I don't 
know whether that still available, though.


If you have that, then the pointer to the driver definition block 
(DDB) lies at offset chn_drvr (=4) in the CDB - you can just PEEK_L 
that. Be careful, however, the pointer there normally points to offset 
iod_iolk (=$18) within the DDB, so all other offsets should be reduced 
by that same amount.


HTH

Wolfgang

On 18/05/2018 22:01, Martyn Hill via Ql-Users wrote:

Hi everyone

In the spirit of double-posting between here and the QL Forum :-) I 
thought I'd ask my question here, too...


I'm continuing to explore the QL network across a range of platforms 
- now with my refurbished QXL2 card (thanks, Derek!)


The bit-timings on the QXL under SMSQ/E v3.33 (and also on v2.76) 
prove to be slightly-out from the nominal 11.2us, resulting in 
failed/unreliable comms with both my Iss7 QL and my prototype QNET to 
USB adapter (still a work in progress.)


Given that the timings-constants for the NET device are exposed under 
SMSQ/E and stored ready for adjustment in the DDB of the NET device, 
I'm trying to find the base address of the DDB from SBasic.


Any help appreciated!

The original post appears here, with pictures :-)

 https://qlforum.co.uk/viewtopic.php?f=3=2462

Regards,
Martyn.

___
QL-Users Mailing List

___
QL-Users Mailing List



___
QL-Users Mailing List

[Ql-Users] SMSQE 3.33

2018-05-19 Thread Wolf via Ql-Users

Hi,

I've also re-uploaded the source code.

Have fun!

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] How do you find the Driver Definition Block (DDB) base-address from SBASIC for the NET device

2018-05-19 Thread Wolf via Ql-Users

Hi,

The best way would be to get the channel definition block (CDB) for a 
channel to the device. I don't know offhand of a Basic keyword that will 
do it for you, Toolkit III used to have such a function, I don't know 
whether that still available, though.


If you have that, then the pointer to the driver definition block (DDB) 
lies at offset chn_drvr (=4) in the CDB - you can just PEEK_L that. Be 
careful, however, the pointer there normally points to offset iod_iolk 
(=$18) within the DDB, so all other offsets should be reduced by that 
same amount.


HTH

Wolfgang

On 18/05/2018 22:01, Martyn Hill via Ql-Users wrote:

Hi everyone

In the spirit of double-posting between here and the QL Forum :-) I 
thought I'd ask my question here, too...


I'm continuing to explore the QL network across a range of platforms - 
now with my refurbished QXL2 card (thanks, Derek!)


The bit-timings on the QXL under SMSQ/E v3.33 (and also on v2.76) prove 
to be slightly-out from the nominal 11.2us, resulting in 
failed/unreliable comms with both my Iss7 QL and my prototype QNET to 
USB adapter (still a work in progress.)


Given that the timings-constants for the NET device are exposed under 
SMSQ/E and stored ready for adjustment in the DDB of the NET device, I'm 
trying to find the base address of the DDB from SBasic.


Any help appreciated!

The original post appears here, with pictures :-)

     https://qlforum.co.uk/viewtopic.php?f=3=2462

Regards,
Martyn.

___
QL-Users Mailing List

___
QL-Users Mailing List

Re: [Ql-Users] SMSQ/E 3.33

2018-05-16 Thread Wolf via Ql-Users

Hi,

thanks Thierry and Marcel for pointig this out.

Re-uploaded with thr missing chunk inserted.


Wolfgang

On 17/05/2018 01:25, simon629--- via Ql-Users wrote:

I have tested on QDT and Dilwyn Jones LaunchPad it seems to be Good for me and 
it so Urs QLE please Give  Mr  MK Time to Fix this  Please Do not Keep on 
asking Him he works very Hard doing Lots for Us OK Good night


Sent from Yahoo Mail for iPhone


On Wednesday, May 16, 2018, 19:43, Marcel Kilgus via Ql-Users 
 wrote:

Thierry Godefroy via Ql-Users wrote:

I am faced with a problem in v3.33: the "WMAN system colours" config block
is gone (!) and as a result, most of PE programs (especially old ones) are
affected and only display in the ugly (and CRT screen killing) white
background/green borders/black text default.


Oh, somebody actually uses the config block, interesting ;-) Even
though I have written it I have never used it myself, I just set the
colours during boot.


Is that a bug, or (I barely even dare making such a silly supposition)
something that was done on purpose ?


Not silly, I have removed it for QDOS WMAN to get the size of the
binary down again, but it's supposed to be included in SMSQ/E. Looks
like it somehow got lost between me and Wolfgang. Wolfgang, please
check that the second input line in smsq_smsq_wman_link reads

input dev8_ee_wman_config_rel

Cheers, Marcel

___
QL-Users Mailing List



___
QL-Users Mailing List


___
QL-Users Mailing List

[Ql-Users] SMSQ/E 3.33

2018-05-11 Thread 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.



Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] BouQLder Qlash

2018-05-06 Thread Wolf via Ql-Users

HI,

> Giorgio Garabello via Ql-Users wrote:

There's a little error on the web page
the following link is wrong


OK, thanks, I corrected that.

> Francois Lanciault via Ql-Users wrote

14 pixel less and it would run on the Aurora...


Argh, typo, it's 512 * 384

I didn't mention the Aurora as I can't test it on there. If it does run 
correctly (and sufficiently fast), drop me a line, I'll add a mention to 
it on the website.


> Peter Graf via Ql-Users wrote:
> Awesome!!! Looks like the first QL arcade game of this century!
Let's hope it won't be the last!

Wolfgang
___
QL-Users Mailing List


[Ql-Users] BouQLder Qlash

2018-05-06 Thread Wolf via Ql-Users

Hi all,

thereTs a new game on my site called BouQLder Qlash.
It's an an arcade game inspired by an old 8 bit game called Boulderdash.
I programmed it initially to showase some of the capabilities of the Q68.

It's now extenedd to run also on Q60, QPC and SMSQmulator.

The game needs SMSQ/E and a screen of at least 526 x 384 pixels in 8 bit 
colours. It comes as either a ready-made qxl.win type file or a normal 
zip file. In both cases, run the supplied boot file from job 0. A 
manual called help_txt is included.


i'll release the source code later.

www.wlenerz.com/qlstuff


Have fun.

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] Q40 and Q60 video controller for flatscreen monitors

2018-05-01 Thread Wolf via Ql-Users

Hi all,


> I have developed an alternative video controller for Q40 and Q60:


I've been testing this for a few months now. At last I can use the Q60 
with a more modern flatscreen with VGA and 1024*768 resolution.


The image is correctly displayed, but the bottom third of the monitor 
remains black (since the Q60 y resolution is 512 pixels, not 768).


Kudos to Peter for making this work.

Wolfgang


On 01/05/2018 11:34, Peter Graf via Ql-Users wrote:

Hello,

I have developed an alternative video controller for Q40 and Q60:

http://qlforum.co.uk/viewtopic.php?f=2=2434

All the best
Peter
___
QL-Users Mailing List



___
QL-Users Mailing List


Re: [Ql-Users] Probleme mit smsq_q40_boot_make_bas

2018-04-30 Thread Wolf via Ql-Users

Dqrnit, I fell into the same trap.

Sorry!

Wolfgang

On 30/04/2018 17:31, Wolf via Ql-Users wrote:

Hallo peter,



1. smsq_q40_boot_make_bas führt menuconfig nicht sichtbar aus, ziemlich
verwirrend, da man nicht weiss ob und woher er die Konfiguration dann 
nimmt.




ja genauso wie in ..._doc oder ..._txt beschrieben und erklärt, aus 
Deinen vorherigen Configs (menuconfig_inf).



2. Zeile 760 gibt ein "not found", weil komischerweise ofile$ seinen
Wert verloren hat.


Was? Ich habe es hier mehrmals extra ausgeführt, werde es überprüen!



Könnte man gzip, menu_rext und menuconfig nicht in das WIN File legen?


Muss mal sehen, die haben ja eigenlich nichts mit SMSQE zu tun, nicht 
mal in so einem entfernten Sinn wie QL-SD und TK2.


LG

Wolfgang
___
QL-Users Mailing List

___
QL-Users Mailing List

Re: [Ql-Users] SMSQ/E 3.33

2018-04-30 Thread Wolf via Ql-Users

Hi Giorgio,

From the sources

; Network I/O function-vector initialisation  V0.1   2018  Marcel Kilgus
;
; This is used to split the physical I/O routines, which need to be in ROM
; (because that has different timing from RAM), from the eneric 
driver/server

; code, which is too big to fit into the new TK2 ROM.


Wolfgang

On 30/04/2018 08:08, Giorgio Garabello via Ql-Users wrote:

Good work! Thanks so much.
I'm very curious, what are the improvements to the network?

Giorgio

Il dom 29 apr 2018, 11:41 Wolf via Ql-Users <ql-users@lists.q-v-d.com> ha
scritto:


Hi all,

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

What's new in this version :

Final bugfix for LRESPR in procedures (means everybody should upgrade)
Better QL networking.
Gold card is configured not to use ABC keyboard.
Improvements in standard QL EE.
Q68 & SMSQmulator better  handling.

The sources for the stand-alone TK II are included in the SMSQ/E sources.
Moreover, whilst they aren't really part of SMSQE, the new QL-SD drivers
are built on the basis of the SMSQ/E "dv3" driver acihtecture, so their
sources are also included in the SMSQ/E sources (remember, the compiled
drivers are at wlenerz.com/qlsd).

If you have a Qx0 machine and access to an EPROM burner, this may be of
interest to you : The Qx0 may now have a compressed SMSQ/E so newer
versions thereof fit in the standard EPROMs. There is a certain process
involved in making these EPROMs - but it is clealy described in the
"smsq_q40_boot_doc" or "smsq_q40_boot_txt" files in the SMSQ/E sources.

Finally, Q68 has better handling of some slower SDHC cards. Also, and
that is an officially unofficial and undocumented feature, the Q68 may
also be able to read most older SD (not SDHC) cards. However, make sure
that this actually works with your cards before using them in earnest.
Offficially, the Q68 still only supports SDHC cards.

Have fun!
___
QL-Users Mailing List


___
QL-Users Mailing List



___
QL-Users Mailing List


Re: [Ql-Users] Probleme mit smsq_q40_boot_make_bas

2018-04-30 Thread Wolf via Ql-Users

Hallo peter,



1. smsq_q40_boot_make_bas führt menuconfig nicht sichtbar aus, ziemlich
verwirrend, da man nicht weiss ob und woher er die Konfiguration dann nimmt.



ja genauso wie in ..._doc oder ..._txt beschrieben und erklärt, aus 
Deinen vorherigen Configs (menuconfig_inf).



2. Zeile 760 gibt ein "not found", weil komischerweise ofile$ seinen
Wert verloren hat.


Was? Ich habe es hier mehrmals extra ausgeführt, werde es überprüen!



Könnte man gzip, menu_rext und menuconfig nicht in das WIN File legen?


Muss mal sehen, die haben ja eigenlich nichts mit SMSQE zu tun, nicht 
mal in so einem entfernten Sinn wie QL-SD und TK2.


LG

Wolfgang
___
QL-Users Mailing List

[Ql-Users] SMSQmulator 2.26

2018-04-29 Thread Wolf via Ql-Users

Hi all,

a new SMSQ/E version often entails a new SMSQmulator version.

This is no exception, some bugfixes make it advisable to upgrade.

www.wlenerz.com/SMSQmulator

Have fun!

Wolfgang
___
QL-Users Mailing List


[Ql-Users] SMSQ/E 3.33

2018-04-29 Thread Wolf via Ql-Users

Hi all,

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

What's new in this version :

Final bugfix for LRESPR in procedures (means everybody should upgrade)
Better QL networking.
Gold card is configured not to use ABC keyboard.
Improvements in standard QL EE.
Q68 & SMSQmulator better  handling.

The sources for the stand-alone TK II are included in the SMSQ/E sources.
Moreover, whilst they aren't really part of SMSQE, the new QL-SD drivers 
are built on the basis of the SMSQ/E "dv3" driver acihtecture, so their 
sources are also included in the SMSQ/E sources (remember, the compiled 
drivers are at wlenerz.com/qlsd).


If you have a Qx0 machine and access to an EPROM burner, this may be of 
interest to you : The Qx0 may now have a compressed SMSQ/E so newer 
versions thereof fit in the standard EPROMs. There is a certain process 
involved in making these EPROMs - but it is clealy described in the 
"smsq_q40_boot_doc" or "smsq_q40_boot_txt" files in the SMSQ/E sources.


Finally, Q68 has better handling of some slower SDHC cards. Also, and 
that is an officially unofficial and undocumented feature, the Q68 may 
also be able to read most older SD (not SDHC) cards. However, make sure 
that this actually works with your cards before using them in earnest. 
Offficially, the Q68 still only supports SDHC cards.


Have fun!
___
QL-Users Mailing List


[Ql-Users] QL-SD

2018-04-27 Thread Wolf via Ql-Users

Hi all,

I added a new driver to the QL-SD driver package. This one also allows 
you to read Qubide formatted container files on the SD Crd, to allow 
easy transfer to the qxl.win format.


wlenerz.com/QLSD

Have fun.

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] FiFi

2018-03-31 Thread Wolf via Ql-Users

I'm not sure I understand the question?

FiFI is at version 5.00 now.

Wolfgang



On 31/03/2018 08:35, simon629--- via Ql-Users wrote:

Will  you ever Updated Again  to 4.32
  


 On Friday, 30 March 2018, 13:18, François Van Emelen via Ql-Users 
<ql-users@lists.q-v-d.com> wrote:
  


  Op 30/03/2018 om 6:48 schreef Wolf via Ql-Users:

Hi all,

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

www.wlenerz.com/qlstuff

Have fun!

Wolfgang
___
QL-Users Mailing List



Hi Wolfgang,

Thank you. I suppose it is the same version as the one I bought many
year ago from Jochen Merz.

François Van Emelen



___
QL-Users Mailing List


___

QL-Users Mailing List


___
QL-Users Mailing List

[Ql-Users] SMSQE additional files

2018-03-31 Thread Wolf via Ql-Users

Hi all,

Following Dilwyn's suggestion, I've uploaded some additional files for 
SMSQE into the additional info and data section of the SMSQE site.


Have fun.

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] FiFi

2018-03-30 Thread Wolf via Ql-Users

Hi,

Can I bundle it with my WiFi card 


Sure

and call it WiFiFi? ;)

Only if the answer is "just because :-)

BTW

Giorgio Garabello pointed out to me that I had switched off the 
integrated help system in the version that was on my site. This has been 
crrected and the new version is already on the site (no version number 
change).



Wolfgang


Dave

On Fri, Mar 30, 2018 at 9:30 AM, Derek via Ql-Users <
ql-users@lists.q-v-d.com> wrote:


Hi,
I supplied FiFi as part of a licenced software package on the Q60.
Very nice software.
RegardsDerek
 Original message From: Marcel Kilgus via Ql-Users <
ql-users@lists.q-v-d.com> Date: 30/03/2018  13:37  (GMT+00:00) To:
ql-us...@q-v-d.com Cc: Marcel Kilgus  Subject:
Re: [Ql-Users] FiFi

Am 30.03.2018 um 14:18 schrieb François Van Emelen via Ql-Users <

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

Thank you. I suppose it is the same version as the one I bought many

year ago from Jochen Merz.

Actually I know one user who has bugged Wolfgang so much that he did a few
updates recently ;) No, it's not me!

Fifi is such an essential tool for me, I've used it at least a million
times to search through the vast sources that are SMSQ/E.

Thanks! Marcel
___
QL-Users Mailing List
___
QL-Users Mailing List






___
QL-Users Mailing List

Re: [Ql-Users] FiFi

2018-03-30 Thread Wolf via Ql-Users

Hi François,

no, there were some changes.

Wolfgang

On 30/03/2018 14:18, François Van Emelen via Ql-Users wrote:

Op 30/03/2018 om 6:48 schreef Wolf via Ql-Users:

Hi all,

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


www.wlenerz.com/qlstuff

Have fun!

Wolfgang
___
QL-Users Mailing List



Hi Wolfgang,

Thank you. I suppose it is the same version as the one I bought many 
year ago from Jochen Merz.


François Van Emelen



___
QL-Users Mailing List

___
QL-Users Mailing List

[Ql-Users] FiFi

2018-03-29 Thread Wolf via Ql-Users

Hi all,

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

www.wlenerz.com/qlstuff

Have fun!

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] R: Source code availability for Minerva v1.92 or v1.89?

2018-03-01 Thread Wolf via Ql-Users

Hi,

TT told me some time ago that it was alright to have Qmon downloadable.

Wolfgang
___
QL-Users Mailing List


[Ql-Users] QA.RESRI - QDOSMSQ eference guide

2018-02-14 Thread Wolf via Ql-Users

Hi,

thanks, Per, for pointing out the inconsistencies in the entry 
conditions in vector QA.RESRI.


I'll make a note in the next version of the "QDOS SMS Reference guide" 
(ex Technical Manual and ex QDOS SMS reference manual) that on SMSQ/E it 
is not necessary to save the stack pointer in BV_RIP(A6) before calling 
this vector. However, I'm going to leave the general requirement in, 
since I don't know how this is handled in QDOS (AH, JM, JS etc), or in 
Minerva.



Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] Wined

2018-02-09 Thread Wolf via Ql-Users


Hi,

in theory yes, depending on what the damage is.
It requires you to know exactly what you are doing. If the filesystem is 
destroyed or damaged, even wined probably can't help. If any information 
is missing, it can't recreate it.


HTH

Wolfgang




On 09/02/2018 18:39, Giorgio Garabello via Ql-Users wrote:

Excuse me, my english is bad. If I install WINED on an emulator, can I use
it to repair damaged files in a .win file?



Il 09 feb 2018 18:21, "Wolf via Ql-Users" <ql-users@lists.q-v-d.com> ha
scritto:


Hi,


I'm not sure I understand what you mean.

Wined can edit standard hard disks sector by sector.

HTH

Wolfgang



On 09/02/2018 09:28, Giorgio Garabello via Ql-Users wrote:


I did not know this program ... it's very interesting!
Is it able to read the .win files as well?

Giorgio

<https://www.avast.com/sig-email?utm_medium=email_source
=link_campaign=sig-email_content=webmail>
Mail
priva di virus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email_source
=link_campaign=sig-email_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2018-02-09 8:01 GMT+01:00 Wolf via Ql-Users <ql-users@lists.q-v-d.com>:

Hi all,


I have uploaded WINED, a formely commercial win,flp and file editor as
freeware.

You can get if grom the usaul address (www.wlenerz.com/qlstuff).

Have fun.

Wolfgang
___
QL-Users Mailing List

___

QL-Users Mailing List


___

QL-Users Mailing List


___
QL-Users Mailing List



___
QL-Users Mailing List


Re: [Ql-Users] Wined

2018-02-09 Thread Wolf via Ql-Users

Hi,


I'm not sure I understand what you mean.

Wined can edit standard hard disks sector by sector.

HTH

Wolfgang



On 09/02/2018 09:28, Giorgio Garabello via Ql-Users wrote:

I did not know this program ... it's very interesting!
Is it able to read the .win files as well?

Giorgio

<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
Mail
priva di virus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2018-02-09 8:01 GMT+01:00 Wolf via Ql-Users <ql-users@lists.q-v-d.com>:


Hi all,

I have uploaded WINED, a formely commercial win,flp and file editor as
freeware.

You can get if grom the usaul address (www.wlenerz.com/qlstuff).

Have fun.

Wolfgang
___
QL-Users Mailing List


___
QL-Users Mailing List



___
QL-Users Mailing List


[Ql-Users] Wined

2018-02-08 Thread Wolf via Ql-Users

Hi all,

I have uploaded WINED, a formely commercial win,flp and file editor as 
freeware.


You can get if grom the usaul address (www.wlenerz.com/qlstuff).

Have fun.

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] Assembly Language ePeriodical Issue 4 - Available Now!

2018-02-06 Thread Wolf via Ql-Users

Hi Norman,

nice, thanks.

Wolfgang

On 06/02/2018 19:31, Norman Dunbar via Ql-Users wrote:
It seems that I managed to upload a PDF file with lots of spelling 
errors and a couple of bugs in the listings. Sigh! I've taken the 
liberty of fixing the copyright date as well - thanks Dave.  ;)


I have uploaded a fixed PDF, so the same URL as before applies: 
http://qdosmsq.dunbar-it.co.uk/downloads/AssemblyLanguage/Issue_004/Assembly_Language_004.pdf 



I have also uploaded the source code for the ASMReformat utility - which 
might save you a lot of typing. You can get that at: 
http://qdosmsq.dunbar-it.co.uk/downloads/AssemblyLanguage/Issue_004/ASMReformat.asm 



Or on github, if you prefer: https://github.com/NormanDunbar/ASMReformat.

If you downloaded that code yesterday, there are two bugs in it that I 
only noticed yesterday - they don't seem to affect the working of the 
code, funnily enough, but I'm almost certain that George would have 
spotted them and give me, rightfully, a hard time!  ;)



Have fun.

Cheers,
Norm.



___
QL-Users Mailing List

[Ql-Users] QL-SD driver

2018-01-29 Thread Wolf via Ql-Users

Hi all,

The new driver for this has been updated, to remove the rename bug found 
by Martyn Hill and to make use of more than one card.


The syntax of the card_init and win_drive commands has changed, to take 
into account the fat that more than one card slot might be available.


www.wlenerz.com/qlsd

Have fun

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] New WIN/SDC driver: RENAME curiosity...

2018-01-28 Thread Wolf via Ql-Users

sorry, this was meant for Martyn

On 29/01/2018 07:25, Wolf via Ql-Users wrote:


Hi Martyn,

thanks for pointing this out, I'll have a look.

I presume that the difference between "targetPth$" and "targetPath$" 
below is just a typo here.


Wolfgang


On 28/01/2018 18:20, Martyn Hill via Ql-Users wrote:

Hi everyone

Thanks to Wolfgang for his work on porting the WIN driver to QDOS and 
merging with the SDC driver.


As a result, I am now able to mount a number of .WIN container files 
as WIN1_, WIN2_ etc and in the process, ease the transfer of files 
from QPC to my QL(s).


Loving it!

One curiosity that I have spotted which worked as expected with the 
original QubIDE/SDC driver but now throws an error under WIN/SDC is 
use of RENAME. I've also posted this to the QL Forum, but as I 
understand WL tends to hang-out here more than there, I'm posting to 
this list as well:


I'm running Minerva v1.98 on this QL, with the WIN/SDC driver burnt in 
to the usual 16k ROM slot at 0c000.
Using my home-brew file-transfer app, I moved a file over to the QL, 
as I do all the time from QPC. The app captures the file-fragments via 
the SERial port in to a temporary file and, once the transfer is 
complete, renames the tmp file to its final resting place on the SD 
Card, with a given name.
The following worked fine under QubIDE/SDC, but errors-out with the 
WIN/SDC driver (all else being equal):


   RENAME tmpFile$ TO targetPth$ & fileName$

The variables in question in this case were:

   tmpFile$ = 'sdc1_tmp_1801281611'
   targetPath$ & fileName$ = 'sdc1_RMS_RMS_v4t4k_exe'

The first 'RMS_' in the target file-path is a hard directory on SDC1_.
A WIN_USE 'sdc' appears in my Boot file, prior to running this app.
The error reported under WIN/SDC is 'bad name' and appears the same 
whether using RENAME from the command line with explicit names in 
place of the variables and even trying WREN in place of RENAME.
I can COPY the tmp file to its new name without problem (i.e. 
replacing RENAME with COPY and keeping the rest as-is.) I can then 
delete the original file manually as well.
When using WREN, the expected 'Do you want to copy xxx to yyy' prompt 
appears and the error appears only after accepting with 'Y'.


Any thoughts?
___
QL-Users Mailing List

___
QL-Users Mailing List

___
QL-Users Mailing List

Re: [Ql-Users] New WIN/SDC driver: RENAME curiosity...

2018-01-28 Thread Wolf via Ql-Users


Hi Martyn,

thanks for pointing this out, I'll have a look.

I presume that the difference between "targetPth$" and "targetPath$" 
below is just a typo here.


Wolfgang


On 28/01/2018 18:20, Martyn Hill via Ql-Users wrote:

Hi everyone

Thanks to Wolfgang for his work on porting the WIN driver to QDOS and 
merging with the SDC driver.


As a result, I am now able to mount a number of .WIN container files as 
WIN1_, WIN2_ etc and in the process, ease the transfer of files from QPC 
to my QL(s).


Loving it!

One curiosity that I have spotted which worked as expected with the 
original QubIDE/SDC driver but now throws an error under WIN/SDC is use 
of RENAME. I've also posted this to the QL Forum, but as I understand WL 
tends to hang-out here more than there, I'm posting to this list as well:


I'm running Minerva v1.98 on this QL, with the WIN/SDC driver burnt in 
to the usual 16k ROM slot at 0c000.
Using my home-brew file-transfer app, I moved a file over to the QL, as 
I do all the time from QPC. The app captures the file-fragments via the 
SERial port in to a temporary file and, once the transfer is complete, 
renames the tmp file to its final resting place on the SD Card, with a 
given name.
The following worked fine under QubIDE/SDC, but errors-out with the 
WIN/SDC driver (all else being equal):


   RENAME tmpFile$ TO targetPth$ & fileName$

The variables in question in this case were:

   tmpFile$ = 'sdc1_tmp_1801281611'
   targetPath$ & fileName$ = 'sdc1_RMS_RMS_v4t4k_exe'

The first 'RMS_' in the target file-path is a hard directory on SDC1_.
A WIN_USE 'sdc' appears in my Boot file, prior to running this app.
The error reported under WIN/SDC is 'bad name' and appears the same 
whether using RENAME from the command line with explicit names in place 
of the variables and even trying WREN in place of RENAME.
I can COPY the tmp file to its new name without problem (i.e. replacing 
RENAME with COPY and keeping the rest as-is.) I can then delete the 
original file manually as well.
When using WREN, the expected 'Do you want to copy xxx to yyy' prompt 
appears and the error appears only after accepting with 'Y'.


Any thoughts?
___
QL-Users Mailing List

___
QL-Users Mailing List

Re: [Ql-Users] Re-upping QL-SD new driver [OT]

2018-01-24 Thread Wolf via Ql-Users

Hi,


Got anything cooking?


I've got my fingers in many pies that are a-cooking, but mostly for 
in-house consumption.


Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] Re-upping QL-SD new driver [OT]

2018-01-23 Thread Wolf via Ql-Users

Hi Per,


Keep on dealing! :)



Are you waiting for the next bug-fix?

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] QL-SD new driver

2018-01-22 Thread Wolf via Ql-Users

Hi Per,

done, re-upped with the keys.

BTW, I forgot to add that the driver is for v. 0.82 of the interface. If 
you have v. 0.75, please holler!!


Wolfgang

On 22/01/2018 17:08, pjwitte via Ql-Users wrote:

On 22/01/2018 10:41, Wolfgang Lenerz via Ql-Users wrote:

Nice one, Wolfgang :)

The sources state: include 'DEV1_q68_qlsd_keys', but I cant find the 
file anywhere..


Per

Hi all,

I've released a new driver for QL-SD that uses standard qxl.win drives
instead of Qubide ones.

It's for Minerva only, though.

You can download it from www.wlenerz.com/QLSD

Have fun.

Wolfgang
___
QL-Users Mailing List





___
QL-Users Mailing List



___
QL-Users Mailing List


Re: [Ql-Users] QL-SD new driver

2018-01-22 Thread Wolf via Ql-Users

Hi,


Does this new driver support QL-SD with two SD cards?


No, not as it is now. I was under the impression that a QL-SD with two 
SD cards practically doesn't exist.

If necessary, I could extend the driver to take care of that.

Wolfgang




On Mon, Jan 22, 2018 at 8:37 AM, Alain HAOUI via Ql-Users <
ql-users@lists.q-v-d.com> wrote:


Hi all,
Actually I am on the way to achieve a new browser (only browser now) for
all ql platforms and emulators which can deal with qubide or qlwa/qwa
multipartitioned devices or disk raw images, data cdrom or iso 9660 cd
images and qxl.win containers in any device or image.
It needs tk2, PE and should work on any ql platform with ~300kb of free
ram, under qdos or smsq.
For physical cdrom needs qubata driver or TG atapi/cdrom things.
Will be available within a few days.
Regards
Alain Haoui
Envoyé de mon téléphone

De : Graeme Gregory via Ql-Users
Envoyé le :lundi 22 janvier 2018 14:41
À : ql-users@lists.q-v-d.com
Cc : Graeme Gregory
Objet :Re: [Ql-Users] QL-SD new driver



On Mon, 22 Jan 2018, at 9:41 AM, Wolfgang Lenerz via Ql-Users wrote:

Hi all,

I've released a new driver for QL-SD that uses standard qxl.win drives
instead of Qubide ones.

It's for Minerva only, though.

You can download it from www.wlenerz.com/QLSD


And the next trick make qubide do the same :-D

Graeme
___
QL-Users Mailing List

___
QL-Users Mailing List






___
QL-Users Mailing List

Re: [Ql-Users] Char_Select problem

2018-01-22 Thread Wolf via Ql-Users

Hi,

yes, same here (in QL Mode 4 colours).

Wolfgang

On 22/01/2018 14:20, Giorgio Garabello via Ql-Users wrote:

Hi all, I found an error in the char_select menu of the extension 8.04 menu
The INK color of the character table remains black regardless of the
palette used.
Can you check if it happens to you too?

Giorgio


Mail
priva di virus. www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
___
QL-Users Mailing List



___
QL-Users Mailing List


Re: [Ql-Users] New document on DV3 drivers

2017-12-29 Thread Wolf via Ql-Users

Hi Per,

Some programs, such as Qpac2 Files and Qmenu's DIR_ and FILE_SELECT$ 
seem to assume a maximum of 8 DDDs so, presumably, devices beyond that 
would not be accessable via these programs.




Sure, the number of devices displayed is applicton specific. Marcel's 
latest version of the menu extensions dir_select (not file_select) 
allows for up to 10 devices, Qpac2 only 8, as you noted.


Of course, in all you can also manually enter the device to display.

Regards

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] New document on DV3 drivers

2017-12-29 Thread Wolf via Ql-Users

Hi Per,


1) Is there is a limit to the number of directory device drivers that 
can be loaded at once (I believe there is/was and the number was 8?)


No, there is no limit that I'm aware of. I'm pretty sure I already had 
more than 8 different devices loaded at some time. (you can test this 
with the sub device, jut use Wined or some such to change the device 
name every time and load it 10 times)




2) Is there is a limit of 16 devices (ie driver + device number 1..8) 
that can be in use at the same time?


It is true that only 16 drives (not devices) can be accessed at once.
This limit is set in the system variables :

sys_fsdd equ$0100   16*long pointers to Filing System Drive
Definitions
sys_fsdt equ$0140   Filing System drive Definition table Top
sys.nfsd equ$10 max Number of Filing System Drive definitions
sys_fsch equ$0140   longlinked list of Filing System CHannel
blocks

Back in the day, I seem to recall 
that once one had accessed one's allotted 16 devices, no further devices 
could be opened. (One had to do a DEL_DEFB to proceed.) 


Yes, except that it's drives, not devices.
So if you have files open on flp1 ... flp8 and win1 ...win8 - that's it.

Recently I 
discovered that if a device is no longer in use, its slot will be 
re-used, but I havent seen this documented anywhere. Do you have 
information on any of this?


Not without checking in the source code, but I'm pretty sure that this 
is the correct scheme.


HTH

Wolfgang
___
QL-Users Mailing List


[Ql-Users] New document on DV3 drivers

2017-12-28 Thread Wolf via Ql-Users

Hi all,

I've added a small technical explanation of DV3 drivers for SMSQE to the 
additional info and data section on the SMSQE site.


Have fun

Wolfgang
___
QL-Users Mailing List


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

2017-12-28 Thread Wolf via Ql-Users

Hi,

yes, that part of SMSQ/e probably hasn't been touched for ages.

Wolfgang


On 28/12/2017 13:44, Bob Spelten via Ql-Users wrote:
Op Thu, 28 Dec 2017 07:43:13 +0100 schreef Wolf via Ql-Users 
<ql-users@lists.q-v-d.com>:



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


___
QL-Users Mailing List


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

2017-12-28 Thread Wolf via Ql-Users

Yup,
hence my original message...

Wolfgang

On 28/12/2017 13:16, Jan Bredenbeek via Ql-Users wrote:

On 28 December 2017 at 13:10, Wolf via Ql-Users <ql-users@lists.q-v-d.com>
wrote:


Hi,

ok,  ok, but I didn't even use the word "odd"!



:)

In any case, if you jump to an odd location (whether strange or not even)
on a QL you will usually be in big trouble...

Jan.


___
QL-Users Mailing List


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

2017-12-28 Thread Wolf via Ql-Users

Hi,

ok,  ok, but I didn't even use the word "odd"!

Wolfgang

On 28/12/2017 13:03, Jan Bredenbeek via Ql-Users wrote:

On 28 December 2017 at 12:59, Wolf via Ql-Users <ql-users@lists.q-v-d.com>
wrote:



Hi,

To my mind, a "jump to a strange address" is not an address error which
would give rise to that exception.



He he that's a language thing :). 'Odd' in English can mean 'strange' but
also 'not even'. What I meant was the latter of the two so it really should
have been an address error...

Jan.


___
QL-Users Mailing List


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

2017-12-28 Thread Wolf via Ql-Users


Hi,

To my mind, a "jump to a strange address" is not an address error which 
would give rise to that exception.


Wolfgang

On 28/12/2017 12:32, Jan Bredenbeek via Ql-Users wrote:

On 28 December 2017 at 07:43, Wolf via Ql-Users <ql-users@lists.q-v-d.com>
wrote:


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.

On the Q68 it also freezes, but other jobs keep running (probably with

corrupted OS).
It looks like the processor in the Q68 behaves somewhat differently, as I'm
unable to get an address error exception even when jumping to an odd
address...

Jan.
___
QL-Users Mailing List



___
QL-Users Mailing List


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

2017-12-27 Thread 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.


Wolfgang


On 26/12/2017 18:31, pjwitte via Ql-Users wrote:
If you want a really miserable Christmas, you could try the following - 
without saving your work first:


1 x% = 32000
2 y% = x%
3 z% = 1600
4 t  = x% * y% * z%: REMark Kabm!!!
5 PRINT "-- Im dead!"

The above crashes SMSQ/E 3.32 on QPC2 and SMSQmulator! Even the 
four-finger reset wont work. The following is, as youd expect, fine:


1 x% = 32000
2 y% = x%
3 z% = 1600
4 t  = x% * y%
5 t  = t * z%
6 PRINT "Yippi! - Im still alive!"

Per
___
QL-Users Mailing List

___
QL-Users Mailing List

Re: [Ql-Users] Mode 33 to 32

2017-12-16 Thread Wolf via Ql-Users

Hi Per,

The PC switches the bytes around.

So
gggb rgg0
actually means
rgg0 gggb


In other words, you're switching the third highest byte for green on or off.
If you sure that's what you want, then that's fine.

Wolfgang




On 16/12/2017 11:43, pjwitte via Ql-Users wrote:
I havent tested your suggestion yet, Wolfgang, but what I found so far 
was that gggbrgg0 appears (to my eye) to look cleaner than 
gggbrggW. Is that so wrong? ;)


BTW, when converting the translation to assembler, I found the following 
representation helpful:


GGGggRRR rrBBBbbW = mode 33
gggBBBbb RRRrrGGG = mode 32
gggBBBbb RRRrrGGW = mode 32 translated

Per
On 16/12/2017 10:55, Wolf via Ql-Users wrote:

No, not the same as %gggbrggW, as suggested in the original post.

Wolfgang

On 16/12/2017 10:18, Peter Graf via Ql-Users wrote:

Wolfgang Lenerz via Ql-Users wrote:

I'd do it this way

%ggWbrggg


Which is the same :)




___
QL-Users Mailing List



___
QL-Users Mailing List


.



___
QL-Users Mailing List



___
QL-Users Mailing List


Re: [Ql-Users] Mode 33 to 32

2017-12-16 Thread Wolf via Ql-Users

No, not the same as %gggbrggW, as suggested in the original post.

Wolfgang

On 16/12/2017 10:18, Peter Graf via Ql-Users wrote:

Wolfgang Lenerz via Ql-Users wrote:

I'd do it this way

%ggWbrggg


Which is the same :)




___
QL-Users Mailing List



___
QL-Users Mailing List


[Ql-Users] SMSQE 3.32

2017-12-10 Thread Wolf via Ql-Users

Hi all,

SMSQE 3.32 is out now.

Below is a swmall account of what has changed.

 - Bugfixes:
There are various bugfixes for network drive names resolution.
QPC & SMSQmulator use the correct SQRT replacement routines.
QPC better handling of removable drives.

Additional features:

- Filesystem for FAT16 disks of up to 256 MiB (currently only ysed in Q68).

- Filesystem for QUBide drives.

- Q40/Q60:
It is now possible to use IDE hard disks formatted with FAT32 and contining
QXL.WIN "drives" (see explanation in the extras_new directory).
The purpose of this is to allow easier data exchange between the Qx0 and 
the rest of the QL world : Adapters exist which will plug into the Q40 
IDE connector and can read SDHC memory cards. If you format such a card 
on FAT32, you can exchange QXL.WIN drives easily! You can, of course, 
also use a FAT32 formmated hard disk with QXL.WIN files on it0

DISP_MODE command for Qx0 introduced.
Please note that this version cannot be burned into an EPROM.

- Q68
Q68 version of SMSQE introduced.

Find it at

http://www.wlenerz.com/smsqe/


Have fun.

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] QMenu 8.04

2017-12-10 Thread Wolf via Ql-Users

Hi Marcel,

thanks a lot for fixing these bugs!

Xolfgang

On 09/12/2017 23:34, Marcel Kilgus via Ql-Users wrote:

I have just released QMenu 8.04 with these changes:

; 8.04  Fixed QDOS compatibility broken in 8.03
;   FSEL Allow up to 8 devices
;   DSEL Now really allow up to 10 devices (buggy since 7.55)
;   FSEL/DSEL Ensure device selection keystroke is unique
;   LIST Fixed crash on editing of strings that are too big
;   LIST Redraw selection keystroke after string edit operation

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

I was able to check the QDOS compatibility using my spanking new
Tetroid Gold Card Clone :-)

Marcel

___
QL-Users Mailing List



___
QL-Users Mailing List


Re: [Ql-Users] New QLE

2017-11-18 Thread Wolf via Ql-Users

Hi,

you could use my backyp prog (wlenerz.com/qlstuff) which can copy only 
newer versions of files.


What system are you using?

Wolfgang

On 18/11/2017 12:17, simon629--- via Ql-Users wrote:

Just Copy the New Stuff from the New QLE  to The To The Old Version of QLE what 
I have Got bar mine is got some paid Software on it  Like FiF 4.31 QD2003 the 
The Full Version of QSpead and QTYP and  Q-Route and some paid Games So I want 
to Copy all the Updates  from the New one to Mine OK Thanks simon629 Simon 
Foster
  


 On Saturday, 18 November 2017, 11:03, Wolf via Ql-Users 
<ql-users@lists.q-v-d.com> wrote:
  


  Hi,
Copy from where to where?
Wolfgang

On 18/11/2017 11:34, simon629--- via Ql-Users wrote:

Hi can anyone help me what I need to copy over to update Mine QLE/QDT OK Thanks 
simon629 Simon Foster
___
QL-Users Mailing List



___
QL-Users Mailing List



___

QL-Users Mailing List


___
QL-Users Mailing List

Re: [Ql-Users] New QLE

2017-11-18 Thread Wolf via Ql-Users

Hi,
Copy from where to where?
Wolfgang

On 18/11/2017 11:34, simon629--- via Ql-Users wrote:

Hi can anyone help me what I need to copy over to update Mine QLE/QDT OK Thanks 
simon629 Simon Foster
___
QL-Users Mailing List



___
QL-Users Mailing List


Re: [Ql-Users] Q40 display mode

2017-11-11 Thread Wolf via Ql-Users

Hi,

The information on page 47 seems to be correct, at least for modes 
0,8,16,32,33. I can't check the others (does aurora lcd mode even exist 
other than in theory?).



I find the disp_type function to be quite confusing, as it mixes the 
information on colour depth with information on what kind of display (or 
even machine) is used : Mode 0,1 and 2 below basically show the same 
colour depth and a program is probably more interested in that and not 
so much in the hardware used to generate it.


This is probably due to the way SMSQE has grown and thus the need to 
keep backward compatibility.


Most programs probably only need to know the colour depth and the screen 
size.


It would thus probably be better to split disp_type up between a 
function that would return the colour depth and a function telling you 
what kind of display, hardware-wise is used.


Wolfgang

On 11/11/2017 17:58, Giorgio Garabello via Ql-Users wrote:

 From SMSQE Manual...

Page 47

DISP_TYPE
The DISP_TYPE function is used to find the type of display. For standard QL
style displays in MODE 4 (any resolution) DISP_TYPE returns 0. The value
returned on other display systems may vary according to the hardware and
colour depth. In general, on SMSQ/E versions supporting higher colour
modes, and on Atari emulator cards, the following values may be returned.
0 – QL style display (MODE 4)
1 - Extended mode 4 emulator (standard and extended display sizes) on Atari.
2 - QVME mode 4 emulator on Atari.
3 - Aurora LCD
4 - Monochrome display on Atari.
5 - Aurora QL mode
8 – QL MODE 8 display
16 – 8-bit (256 colour) mode
32 – 16-bit colour mode on QPC, QXL and SMSQmulator
*33 – 16-bit colour mode on Q40 and Q60*
64 – 24-bit colour mode (no hardware supports this at the time of writing)


Page 95

DISP_TYPE
The DISP_TYPE function is used to find the type of display. For the Q40,
there are two values that may be returned.
0 Original ST QL emulator (this value is returned on QL based hardware).
*1 16 bit colour mode.*

Which of the two is the right one?
___
QL-Users Mailing List


___
QL-Users Mailing List

Re: [Ql-Users] Dock

2017-11-10 Thread Wolf via Ql-Users


Hi all,

first of all thanks for the kind words some of you have found for me!

Concerning dock, this is supposed to be a program run in the background.

Start with EX, not LRUN


Have fun,

Wolfgang
___
QL-Users Mailing List


[Ql-Users] SMSQmulator 2.25

2017-11-05 Thread Wolf via Ql-Users

Hi all,

I just released SMSQmulator 2.25

Have fun.

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] Possible bug in the (experimental) QubIDE feature of QXLWinReader

2017-10-30 Thread Wolf via Ql-Users

Hi,

the new version of QxlwinReader is on my website.

Thanks Martyn for testing that the fix seems to work.

Have fun!

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] Possible bug in the (experimental) QubIDE feature of QXLWinReader

2017-10-29 Thread Wolf via Ql-Users

Hi,

thanks for pointing this out.

I'm a little short on time right now, but will check this as soon as 
possible.


Under which file system does this error arise, QLWA ou Qubide?

Regards

Wolfgang


On 29/10/2017 22:12, Martyn Hill via Ql-Users wrote:

Hi list and especially Wolfgang

Not sure the best way to report the issue, but as per my recent thread 
on the Forum (http://qlforum.co.uk/viewtopic.php?f=3=2146), I seem to 
have uncovered an odd behaviour when copying directory structures from 
WIN to a QL.BDI image file on SDC.


I know this feature is still experimental, but I already use it quite a 
lot - especially after corrupting my SD-Card sufficiently that it 
wouldn't get recognised on the QL, but QXLWinReader was able to read all 
the files and directories (somehow!), allowing me to recreate the QL.BDI 
image file and restore all the contents. At the moment, this valuable 
little program is my preferred way to transfer large amounts of data 
between QPC and my QL.


In short, whilst the directory structures are all copied across with 
their files (and further sub-directories), it would appear that the 
file-header copy inside each sub-directory file itself is not copied 
across intact. The effect of this is that, whilst a DIR listing shows 
the ' ->' against such sub-directories indicating that it is recognised 
as a directory-file, when you use FTYP to query the sub-dir path, it 
returns '0' as for a normal file.


I've tested this - as documented on the Forum - and think I've ruled out 
anything else (like the typical user-error that plagues most of my QL 
work!)


Would love to see this investigated and possibly addressed!

Regards,
Martyn.
___
QL-Users Mailing List



___
QL-Users Mailing List


Re: [Ql-Users] Possible bug in smsqmulator.

2017-10-11 Thread Wolf via Ql-Users

Hi,

thanks for your warning but no bug. The comment mentions what the SMSQ/E 
format routine gets, not the java side.


Cheers

Wolfgang

On 11/10/2017 23:24, Norman Dunbar via Ql-Users wrote:

Evening All,

I was nosing around in the latest source for Smsqmulator and I might have found 
a bug in the floppy driver code. Mind you, it's Java, so all bets are off!

In formatDrive() it has a comment that d0 is the format type, 0=sd, 1=dd, 2=hd 
or 3=ed etc. However the code looks to be getting the format type from register 
d2 and not d0. As in:

Int type = (this.cpu.data_regs[2]&0x)-1;

I might be wrong of course, it does happen, but it looks odd given the comments.


Cheers,
Norm.


___
QL-Users Mailing List


Re: [Ql-Users] Stupid AND

2017-09-21 Thread Wolf via Ql-Users

Hi,



FALSE AND ERROR is FALSE ? That cannot be !


I disagree.

FALSE AND ... whatever  is FALSE since whatever is never evaluated.


FALSE AND ERROR has to be ERROR !!!


Definitely not.




The first condition (a<>0) is NOT met and so, in any other programming
language I use, the second condition isn't even tested, as the result
will be "false" anyway because of this.


So you will ever get big BIG ERRORs...



I'm not sure I understand. The above example makes sure that the error 
doesn't even happen which is the whole reason to write it like that.



SBASIC is better ;-))


In this instance, not to my mind. :-(

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] TURBO and testing it exists

2017-08-19 Thread Wolf via Ql-Users

Hi,

If I understand the circumstances correctly, I would handle the chicken 
and egg problem differently.


The circumstances are that you're trying to develop a BOOT program, 
which loads a certain set of extensions. You want to avoid loading the 
extensions again if the BOOT program is run again in the same session. I 
stress that this is a BOOT program, i.e. at some time it is really the 
first program to be started.


I would then definitely use a small toolkit (several have been proposed 
here) which checks for the presence of specific keywords.


To get around the chicken and egg problem of finding out whether this 
toolkit is loaded, I'd do the following:


Check what version of machine/OS you're using, this enables you to get 
at the system variables, the address of which you put into a variable 
called sysvar_address. Then use this function:


def proc load_checking_toolkit (sysvars_address)
local a,is_loaded
  is_loaded=peek_l (sysvars_address + 372)
  if not is_loaded
 a=respr(xxx)
 lbytes ,a
 call a
 poke_l sysvars_address + 372,1
  endif
end def load_checking_toolkit


If you run this when the machine is just started up, the address at 
sysvars + 372 will be 0. This is true for SMSQE, QDOS ans Minerva.


Under SMSQE, this one of the rare unused addresses in the system 
variables, so if you poke 1 into there you know that your boot program 
has already run once.


Under QDOS/Minerva, this may eventually be filled up as and when 
channels are opened - but then you also know that you already ran the 
BOOt program.


HTH

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] Copying large files

2017-08-18 Thread Wolf via Ql-Users


Hi,

Theoretically, a cluster could contain 65536 sectors. So the qxl.win 
file could be 65536 x 65536 x 512 bytes big.


Realistically,  I wouldn't go over 2 GiB.



HTH

Wolfgang


NB there is another 65536 limit in the filesystem, that of the number of
clusters a qxl.win drive may have



so, the maximun size of a win file is?

Giorgio
___
QL-Users Mailing List



___
QL-Users Mailing List


[Ql-Users] Copying large files

2017-08-18 Thread Wolf via Ql-Users

Hi all,

as promised, I had a look at the problem of copying large files onto a 
QXL.WIN drive.


The answer is simple : if you try to write anything larger than 32 MiB, 
you'll get an end of file error. This is because, for slave blocks, 
sector numbers are  stored are in a word.


Thus, in  dev8_dv3_dv3_albf_asm you can read this:


dv3_albf
cmp.l   d3c_feof(a0),d4  ; end of file?
blt.s   dv3_lcbf ; ... no, locate

move.l  d3c_fsect(a0),d5
move.l  ddf_smask(a4),d3 ; byte within sector
and.w   d4,d3
bne.s   dlb_loc1 ; not the start of a new sector

addq.w  #1,d5; next sector***!
bcc.s   dab_do   ; ... current version can only
cope
 ; with sector number up to
65535
move.l  d4,d5; start of file?
beq.s   dab_do

moveq   #0,d5
subq.w  #1,d5; highest sector number
moveq   #err.eof,d0
rts



So, if a sector number of a file would be higher than 65536, the error 
is triggered. As each sector is 512 =Bytes long, after 65536 * 512 = 
32Mib, it's the end.


To get around this, you would have to rewrite, at least, the parts of 
the filesystem handling the slave blocks.


HTH

Wolfgang

NB there is another 65536 limit in the filesystem, that of the number of 
clusters a qxl.win drive may have

___
QL-Users Mailing List


Re: [Ql-Users] MAW in Easyptr4 - help

2017-08-18 Thread Wolf via Ql-Users

Hi,

This isn't fixable - by design.

Don't forget that a window may have several appsub windows, which may 
have the same selection keys for their elements (e.g. a filemanager that 
would have two file windows). How would you distinguish between them? 
So, appsub windows get the keystroke ony if the pointer is over them.


Makes sense to me.

HTH

Wolfgang



On 17/08/2017 20:36, Giorgio Garabello via Ql-Users wrote:

Hi everyone, I have a doubt about the EASYPTR4 Application windows
I put an array in an Application Window Menu, then I defined that the first
letters of each element are underlined and usable as shortkey.
Shortcuts can only be used if the pointer is located above the application
windows.
   If the pointer is somewhere else, these short keys can not be used. Is it
a feature or a bug?
In either case, how can I do this to use these shortkeys regardless of the
position of the pointer?

thanks in advance

Giorgio
___
QL-Users Mailing List



___
QL-Users Mailing List


Re: [Ql-Users] PCB Design v7.52

2017-07-22 Thread Wolf via Ql-Users

Hi Michael,


There is the -Q1 option in unzip to reverse the "_" <-> "."
Eg. EX unzip,#1; "-Q1 dos7_PCBDesign752.zip -d ram6_"
and they all come out with dots in them !



Great, thanks for pointing that out.



I have run the code and this does work well using QPC2, in extended screen size.



Ok, I'll have to recheck, then


WOlfgang
___
QL-Users Mailing List


Re: [Ql-Users] PCB Design v7.52

2017-07-22 Thread Wolf via Ql-Users

Hi,

Thanks for that.

In the boot all file separators are "." (eg. "tk.bin"), but when 
dezipped, the file separators are "_" as they should be, so the boot 
can't find them.


This also doesn"t seem to wrok with an extended screen under SMSQ/E?

Wolfgang



On 21/07/2017 14:31, Dilwyn Jones via Ql-Users wrote:

Lear PCB Design 7.52

Malcolm Lear has made available an updated v7.52 of his PCB Design 
program. Download from http://www.dilwyn.me.uk/graphics/index.html


Malcolm says there are many improvements and refinements, so here's an 
extract from the REVISIONS.TXT file in the program listing major changes 
in recent versions:



7.49 08-04-17 Text element was being routed though the fingerpad 
detection filter in all export modes resulting in some missing text. 
This is now fixed.


7.50 Multipage loading screen suffered lost of first character in file 
names, this is now fixed. This issue only likely showed on low 
resolution platforms such as the QL.

Function to report project file revision after loading implemented.
Nasty assembler bug that performed a word write to odd boundary when 
requesting predefined components now fixed. This problem was overlooked 
for some time due to the authors 68020 based development system.

Pad based bombsight marker is deprecated and now track based.
Automatic bombsight conversion on load has been implemented.
Flood fill clearance saved in project file (information block).
Default new label positioning, layer and orientation now based on 
properties of existing labels.

Text size on predefined fiducial corrected.
Edit mode changed from bit tests and sets to absolute values in 
assembler code thus eliminating ambiguous values.


7.51 More assembler tidying up and minimizing.

7.52 All labels, not just the first 5 can now be switched on or 2Kb of 
unused dataspace (dot matrix label buffer) removed.


Dilwyn.
___
QL-Users Mailing List



___
QL-Users Mailing List


[Ql-Users] DM5 upsetting Dates in QPC2

2017-06-29 Thread Wolf via Ql-Users

Hi,


There seems to be 2 differences between PAUSE and WAIT.

PAUSE  needs channel #0, WAIT doesn't.


True


PAUSE can be interrupted with a keypress, WAIT can't.


True


Wait comes from the outptr toolkit (on my QLStuff webpage, pointer 
tools). It just suspends the calling job for x ticks : WAIT x


You can replace it with Pause - or even a simple delay loop if you want 
to run it without windows pen (in the case of Pause).


FYI, on my machine runing SMSQmulator, the timings of the p procedure 
would look as follows:


100 DEFine PROCedure p
110 ERT HOT_KEY('g',CHR$(27))
120 EX RAM1_Dm5_Obj
130 REMark WAIT 20- not used !
140 HOT_DO('g')
150 WAIT 1
160 HOT_DO('g')
170 WAIT 1
180 HOT_DO('g')
190 ERT HOT_REMV('g')
200 END DEFine p


Have fun!

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] DM5 upsetting Dates in QPC2

2017-06-29 Thread Wolf via Ql-Users

Sorry, yes it is.

On 29/06/2017 12:04, Derek Stewart via Ql-Users wrote:

On 28/06/17 10:12, Wolf via Ql-Users wrote:

Hi Derek,

100 DEFine PROCedure p
110 ERT HOT_KEY('g',CHR$(27))
120 EX RAM1_Dm5_Obj
130 WAIT 20
140 HOT_DO('g')
150 WAIT 20
160 HOT_DO('g')
170 WAIT 20
180 HOT_DO('g')
190 ERT HOT_REMV('g')
200 END DEFine p

Adjust the key, timings and drive to suit your system.
At least you won't have to type in the date anymore.

Have fun

Wolfgang
___
QL-Users Mailing List


Hi Wolfgang,

I do not have the keyword WAIT in my SMSQ/E v3.31, is that like PAUSE ???


___
QL-Users Mailing List


[Ql-Users] SMSQDOS Reference Guide

2017-06-28 Thread Wolf via Ql-Users

Hi all,

Version 4.3 of the SMSQDOS Reference Guide is out, a few typo 
corrections & additons.


www.wlenerz.com/QLStuff/

Have fun.

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] DM5 upsetting Dates in QPC2

2017-06-28 Thread Wolf via Ql-Users

Hi Derek,

100 DEFine PROCedure p
110 ERT HOT_KEY('g',CHR$(27))
120 EX RAM1_Dm5_Obj
130 WAIT 20
140 HOT_DO('g')
150 WAIT 20
160 HOT_DO('g')
170 WAIT 20
180 HOT_DO('g')
190 ERT HOT_REMV('g')
200 END DEFine p

Adjust the key, timings and drive to suit your system.
At least you won't have to type in the date anymore.

Have fun

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] QxlwinReader

2017-06-23 Thread Wolf via Ql-Users

Hi Andrea and Bob,

thanks for your input!

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] R: R: QxlwinReader

2017-06-18 Thread Wolf via Ql-Users

Hallo Peter,

Ich hoffe Dir geht es gut, und Deinem Freund, besser.

Anbei eine neue Version von SMSQ/E (QL_RAM.BIN), und eine neue Version 
von Minerva mit eingebautem "WIN" Treiber (QL_ROM.BIN - für Dich auch 
mit integriertem Qmon).


In beiden gibt es einen neuen Treiber, der "QUB" heisst. Dieser liest 
und schreibt Imagedateien im Qubide-format, d.h die QL_BDI.BIN-Dateien.


Einschränkungen :
- Der Treiber in beiden Versionen liest und schreibt nur die erste 
Partition - wenn Du eine Beispiels-QL_BDI.BIN-Datei mit mehreren 
Partitionen hast, könnte ich das, wahrscheinlich auch ohne grösseren 
Umfang, darauf ausweiten.


- Der Treiber kann nur mit solchen Dateien umgehen die nicht mit 
Zylindern, Spuren und Köpfen erstellt wurde. Auch hier wäre eine solche 
Datei willkommen, obwohl das vielleicht mehr Arbeit erfordern würde.


- In der Minerva-version gibt es (genau wie für den "Win"-treiber) keine 
qub_ oder win_ Basicbefehle (die werden in SMSQE über "Things" 
eingebunden). D.h. es ist nicht möglich einmal schnell die Imagedatei zu 
wechseln, so wie mit WIN_DRIVE unter SMSQE. Man kann die 
QL_ROM.BIN-datei aber konfigurieren und 8 Namen für die Imagedateien 
einsetzen (genau wie bei dem "WIN"-treiber). Als Default sind QL_BDI.BIN 
für QUB1_ gesetzt, und QL_BDI2.BIN bis QL_BDI8.BIN für die QUB2_ bis QUB8_.


- In der SMSQ/E-version funktionieren QUB_USE, QUB_DRIVE und QUB_DRIVE$ 
wie ihre WIN-pendants.


Ich habe die SMSQ/E-version hier ausprobiert, sie funktioniert gut. Ich 
muss aber hinzufügen, dass ich nur eine einzige Qubide-imagedatei habe...


Minerva habe ich nur ganz kurz getestet. Die Treiber werden bei QDOS 
Classic nicht funktionieren.


Mit diesem Treiber könntest Du aber Dein FPGA umbauen, da ich ihn dann 
leicht anpassen könnte. Ich schicke Dir dann evt. einfach meinen Q68 
damit Du ihn umprogrammierst, wenn Dir das recht ist.



Schönen Sonntag noch.

Wolfgang



___
QL-Users Mailing List

[Ql-Users] QxlwinReader

2017-06-18 Thread Wolf via Ql-Users

Hi Davide,

Just to try and clear up some things about QxlwinReader.

This program reads Qubide image files. These are copies of a whole 
qubide disk, copied to a simple file. I should indeed have mentioned in 
my reply to you that the "dd" program I referred to is a utility that 
comes as standard with Linux and allows you to copy all or part of the 
content of some device to a simple file on another device. As others 
have mentioned, something similar also seems to exist for windows, 
though I have never tried that.


QxlwinReader cannot, and will never be able to, read a disk directly. To 
do that, I would either have to be able to access a real disk for a raw 
read/write which, unless I'm mistaken, java doesn't allow me to do (at 
least not in an OS independent way), or write a filesystem driver: one 
for Linux, and another for Windows, probably yet another for Mac etc - 
you can see why this isn't feasible.


Moreover, please note that QxlwinReader can only handle "LBA" type image 
files, i.e. ones where files are written consecutively to the disk (FAT 
allowing), without taking into account that they should be split up 
between tracks, cylinders and heads. If I had an example of a Qubide 
disk image file actually making use of tracks, cylinders and heads I 
**might** be able to figure this out, too. I believe that Alain Haoui 
has written a driver for these types of disks.


Moreover, for the time being, QxlwinReader only handles the first 
partition of a Qubide disk image file. There is no reason why it 
shouldn't be able to handle the other partitions, too - except that, 
there again, I don't have an example of an image file with several 
partitions, and so would be unable to test this. Knowing myself, letting 
out untested software would not be doing you a favour...



HTH

Wolfgang


On 17/06/2017 20:17, via Ql-Users wrote:

Of course I misunderstood and I thought Wolfgang was referring to a floppy
disk transfer. Can you please provide the link for the download of this "DD"
utility?

Thanks

Davide

-Messaggio originale-
Da: Ql-Users [mailto:ql-users-boun...@lists.q-v-d.com] Per conto di Peter
Graf via Ql-Users
Inviato: sabato 17 giugno 2017 20:01
A: ql-us...@q-v-d.com
Oggetto: Re: [Ql-Users] R: R: QxlwinReader

Davide wrote:


Having had to transfer a full QL system based on SGC/Qubide to .win
with 150 Mb, using DD would have been quite a nightmare.


Why should dd be a nightmare? Are you aware that dd means a utility program,
not floppies?


[...]



I understand the effort to write such sw might not be negligible, but
a utility which could manage to read native Qubide hard disks on a PC
and transfer files to a .win file (and maybe vicecersa) I think would
be very useful.


If you have a PC with IDE port anyway, then where is the problem to use dd
to get the image?

Peter

___
QL-Users Mailing List

___
QL-Users Mailing List



___
QL-Users Mailing List


Re: [Ql-Users] R: QxlwinReader

2017-06-15 Thread Wolf via Ql-Users

Hi Davide,

I'm not sure I understand what you want. You want to be able to read a 
physical Qubide formatted disk, not just an image file?


Perhaps the best way would be to copy (via "dd") the disk to an image 
file and work off that.


Regards

Wolfgang


On 11/06/2017 10:16, via Ql-Users wrote:

Hi Wolfgang,

Very nice, that was indeed one of my "most wanted" utilities. I am almost
over recovering the content of a hard disk from a Sinclair QL-Qubide system
to a WIN file via QXL. This took quite some due to the file numbers and
sizes with the bottleneck of the network speed which in any case proved to
be extremely reliable. Of course it is not so easy these days to find a QXL
and even more a host PC with ISA bus. The only other alternatives without a
QXL would have been floppy disks or sernet which however looks not as easy
as the network port to be configured also on the hw side (cables, wiring
etc).

Having a utility which could read/write WIN files and read (which for me
would be more then sufficient) Qubide formatted hard drives on a standard PC
would be really great.

Regards

Davide


-Messaggio originale-
Da: Ql-Users [mailto:ql-users-boun...@lists.q-v-d.com] Per conto di Wolf via
Ql-Users
Inviato: sabato 10 giugno 2017 19:56
A: ql-us...@q-v-d.com
Oggetto: [Ql-Users] QxlwinReader

Hi all,

I've released QxlwinReader, a small java program that allows you to
read/write qxl.win type container files directly.

There is also experimental support for Qubide formatted ("BDI") container
files.

www.wlenerz.com/QLstuff.

Have fun!

Wolfgang
___
QL-Users Mailing List

___
QL-Users Mailing List



___
QL-Users Mailing List


[Ql-Users] QxlwinReader

2017-06-15 Thread Wolf via Ql-Users

Hi all,


A new version of QxlwinReader is available on my site, better handling 
of Qubide image files.


Have fun

Wolfgang
___
QL-Users Mailing List


Re: [Ql-Users] SMSQ/E old versions

2017-06-15 Thread Wolf via Ql-Users

Hi all,

thanks to Giorgio Garabello, you can also find SMSQE v. 3.29 and 3.30 on 
my website.


Have fun.

Wolfgang
___
QL-Users Mailing List


[Ql-Users] SMSQ/E old versions

2017-06-11 Thread Wolf via Ql-Users

Hi,

No files were attached (I think the list takes them out) , could you 
send them to me directly?


Regards

Wolfgang

On 11/06/2017 16:12, Giorgio Garabello via Ql-Users wrote:

..and 3.29

2017-06-11 16:10 GMT+02:00 Giorgio Garabello <g.garabe...@gmail.com>:


3.01, 3.02, 3.03, 3.10, 3.29 and 3.30  are M.I.A.
Here 3.29 and 3.30 so you can add them.

If someone has the others M.I.A. versions, please add them!

Regard, Giorgio

2017-06-11 16:06 GMT+02:00 Giorgio Garabello <g.garabe...@gmail.com>:



3.01, 3.02, 3.03, 3.10, 3.29 and 3.30  are M.I.A.
Here 3.29 and 3.30 so you can add them.

If someone has the other M.I.A. versions, please add them!

Regard, Giorgio


2017-06-11 15:06 GMT+02:00 Wolf via Ql-Users <ql-users@lists.q-v-d.com>:


Hi,



Wolfgang, do you still have the .WIN files for the different version
that you hosted?



I don't have all but most. What I have can now be found on the website.

www.wlenerz.com/smsqe.

Go to the bottom of that page and click the "goto old versions" link.

Have fun.

Wolfgang


___
QL-Users Mailing List







___
QL-Users Mailing List



___
QL-Users Mailing List


[Ql-Users] SMSQ/E old versions

2017-06-11 Thread Wolf via Ql-Users

Hi,



Wolfgang, do you still have the .WIN files for the different version
that you hosted?


I don't have all but most. What I have can now be found on the website.

www.wlenerz.com/smsqe.

Go to the bottom of that page and click the "goto old versions" link.

Have fun.

Wolfgang


___
QL-Users Mailing List


[Ql-Users] QxlwinReader

2017-06-10 Thread Wolf via Ql-Users

Hi all,

I've released QxlwinReader, a small java program that allows you to 
read/write qxl.win type container files directly.


There is also experimental support for Qubide formatted ("BDI") 
container files.


www.wlenerz.com/QLstuff.

Have fun!

Wolfgang
___
QL-Users Mailing List


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

2017-06-07 Thread Wolf via Ql-Users

Hi,

just a few thoughts.


I will try to recup the main ones and I would appreciate if anybody could
help fixing them or at least providing ideas on how other QL users could
help.



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


The version of SMSQE I got was 2.99.
If the bug pre-existed, as it seems to be the case, then I can't find 
out what, if anything, has changed since.
The chances of me finding out what causes the bug are then next to 
inexistent.




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

BAUD returns an error


On what versions?
Here, some work was done on the QXL PC side by Bruno Coativy in 2006, an 
avid QXL user at that time. I'm pretty sure that he would have noticed 
the screen problems. I think I also tested the QXL version (but I'm not 
entirely sure anymore) and I would have noticed the screen problems. The 
QXL version needs at least a 386.



IIRC, bugs 1 & 2  were brought up by Andrea Carpi.
I already had a look at the code for both bugs but couldn't find out why 
this is happening.


I would like to know whether there is anybody out there, apart from 
Andrea, who is still using a QXL. If so, do they have the same problem?




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



I don't recollect this having been brought to my attention before. I'll 
correct it in the next version of SMSQE.




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.


Both deserve a try, and both have already got a try from me, 
unfortunately without success.




Any feedback and contributions to the above findings would be welcome.


Agreed, especially about the "contributions" part...


Wolfgang
___
QL-Users Mailing List