### Re: [Ql-Users] Mode 33 to 32

AGE "ram2_dmp1024x768_scr" went psychedelic! On 16/12/2017 11:59, Wolf via Ql-Users wrote: 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'

### Re: [Ql-Users] Mode 33 to 32

Aah! Perfect! Thanks Marcel, youre a star! So in fact I interpreted the input wrong. It should have been: GGGggRRR rrBBBbbW <- input and ggWBBBbb RRRrrGGG -> output Seems so obvious now ;) Per On 16/12/2017 15:30, Marcel Kilgus via Ql-Users wrote: 320 c\$ = c\$(4 to 5) & c\$(16) & c\$(11 to

### Re: [Ql-Users] Mode 33 to 32

Oops! That should be: GGGBBBbb RRRrrgg0 = mode 32 translated P 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

### Re: [Ql-Users] Mode 33 to 32

Thanks guys :) On 16/12/2017 00:30, Peter Graf via Ql-Users wrote: What do I do with 'w' in either case for best results? I would just use the RGB0 bit of mode 33 as G0 Bit of mode 32, which is what you probably do already. There is no perfect translation, since mode 33 has 64 clean grey

### Re: [Ql-Users] Mode 33 to 32

Sorry for yanking your chain again so soon but, on going the other way, ie from mode 32 to 33, what is the best value for W? g6, 0, 1..? Per On 16/12/2017 18:13, pjwitte via Ql-Users wrote: Aah! Perfect! Thanks Marcel, youre a star! So in fact I interpreted the input wrong. It should have

### Re: [Ql-Users] Mode 33 to 32

Thanks :) On 16/12/2017 19:36, Peter Graf via Ql-Users wrote: The least significant of the 6 green bits. Am 16.12.2017 um 19:12 schrieb pjwitte via Ql-Users: Sorry for yanking your chain again so soon but, on going the other way, ie from mode 32 to 33, what is the best value for W? g6, 0, 1

### [Ql-Users] Mode 33 to 32

I want to convert a mode 33 screen (Qxx) to mode 32 (QPC2) and visa versa. I got this far with 33 to 32, but Im not sure this is the best translation: rem %grbw = mode 33 rem %gggbrggg = mode 32 c\$ = BIN\$(PEEK_W(a), 16) c\$ = c\$(3 TO 5) & c\$(11 TO 15) & c\$(6 TO 10) & c\$(1

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

Splendid! It all works now. Thank you! :) Per On 11/06/2018 07:36, Wolf via Ql-Users wrote: Hi all, new version on the site, should keep bookmarks etc..., thanks, Per, for pointing that out. Wolfgang ___ QL-Users Mailing List

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

On 08/06/2018 17:16, Jan Bredenbeek via Ql-Users wrote: On 8 June 2018 at 15:52, pjwitte via Ql-Users wrote: When loading this into RESPR and then doing CALL base+4 I get an 'insufficient memory' error. But PEEK_L(base) returns 0 so the code never got to the point where it stores the result

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

On 08/06/2018 12:20, gdgqler--- via Ql-Users wrote: On 14 Feb 2018, at 13:49, pjwitte via Ql-Users wrote: |In later versions of the QDOS and SMSQ/E Reference Manual the documentation on QA.RESRI (aka bv.chrix), to test or stretch the arithmetic stack states: Vector \$11A Reserve Room

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

On 08/06/2018 14:29, Jan Bredenbeek via Ql-Users wrote: On 8 June 2018 at 13:26, pjwitte via Ql-Users wrote: It appears that, on an error, QDOS doesnt return here at all! Correct. Under SMSQ/E it may return an error (IMEM), but the error code is not always set! That implies that you could

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

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 ???

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

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

### [Ql-Users] iop.rptr

According to documentation when this call returns it should update the pointer record with, among other things, the ID of the channel the pointer finds itself in. This it does perfectly well when bit 7 of the return vector is set, ie on a "special" move. But in all other cases it will only

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

and thats not the inter-festive DT's talking!) The deeply philosophical line 5 (in the light of line 4) in the first code sample, is for anyone to ponder in the New Year - for which I wish y'all a happy one!.. Per On 30/12/2017 13:39, Marcel Kilgus via Ql-Users wrote: pjwitte via Ql-Users wrote: I

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

On 30/12/2017 16:10, Marcel Kilgus via Ql-Users wrote: pjwitte via Ql-Users wrote: Thanks, Marcel. Yes, I thought you might enjoy this little holiday from "industrial" programming ;) Oh well, I'm already swamped with non-industrial work, I have so many ideas and projects on what to

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

On 29/12/2017 08:06, Wolf via Ql-Users wrote: 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 Very nice, Wolfgang. Thank you! I have two questions (for now) which dont appear to be

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

Thanks, Wolfgang. Youre very helpful, as always  :) Yes, I meant drives, of course. 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. Per On 29/12/2017

### Re: [Ql-Users] Ql-Users Digest, Vol 167, Issue 2

Hehe! Spot on, Tobias Per On 05/01/2018 15:49, Tobias Fröschle via Ql-Users wrote: AF = Awfully faulty JM = jerkily mended JS = just stable MG = mainly good ;) (just joking) Tobias Am 05.01.2018 um 12:56 schrieb Norman Dunbar via Ql-Users : Hi Paolo, as far as I

### Re: [Ql-Users] Q68 Baud

On 20/01/2018 13:04, Derek via Ql-Users wrote: <> Not tried Atari ST QL emulator yet. The QVME graphics card used with the ST has a fast serial port. I got the best speeds with that. 230k, I believe, between my Mega ST + QVME and a PC (in the days when PCs had real serial ports). Per <>

### Re: [Ql-Users] Q68 Baud

On 21/01/2018 10:26, Fabrizio Diversi via Ql-Users wrote: Must be a pretty ancient Mac Book Pro if it still has a serial port. Mine is from 2008 and doesnt. <> the "PC" is a Mac Book pro using Win10 with Parallels...and finally QPC. <> ___ QL-Users

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

.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

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

On 14/02/2018 15:04, Marcel Kilgus via Ql-Users wrote: pjwitte via Ql-Users wrote: Error returns: IMEM out of memory [SMSQ] This is correct. If this is correct, isnt that bad news for any old toolkits that dont expect the call to return on IMEM (as per the original Technical Guide

### [Ql-Users] QA.RESRI info incorrect

|In later versions of the QDOS and SMSQ/E Reference Manual the documentation on QA.RESRI (aka bv.chrix), to test or stretch the arithmetic stack states: Vector \$11A Reserve Room on Arithmetic Stack QA.RESRI Call parameters                         Return parameters D1.L Number of bytes required

### Re: [Ql-Users] A polite request

! Per On 14/02/2018 21:24, Norman Dunbar via Ql-Users wrote: Hi Per, On 14/02/18 20:21, pjwitte via Ql-Users wrote: If Ive sinned, Norm, please forgive. Are you refering to anything I did? I ax cause I havent noticed the problem, so perhaps I missed something? Anyway, enjoy your wine, although I

### Re: [Ql-Users] A polite request

If Ive sinned, Norm, please forgive. Are you refering to anything I did? I ax cause I havent noticed the problem, so perhaps I missed something? Anyway, enjoy your wine, although I would have thought a hot toddy would bring more cheer after your wet waddle to Waitrose.. Per On 14/02/2018

### Re: [Ql-Users] QA.RESRI - QDOSMSQ eference guide

On 16/02/2018 10:27, Jan Bredenbeek via Ql-Users wrote: <> What puzzles me however is that, in case more space from the system is needed, this is done using a call to sms.achp (mt.alchp) rather than mt.albas. So the extra space seems to be allocated in the Common Heap rather than the S*BASIC

### Re: [Ql-Users] A polite request

On 15/02/2018 21:07, Norman Dunbar via Ql-Users wrote: <> There is plenty one could moan about on this list if one were thus inclined. Nuff said. Oh, I would tend to disagree there. Respectfully disagree of course. I think this is one of the better lists I enjoy reading - even when the

### Re: [Ql-Users] QA.RESRI - QDOSMSQ eference guide

I think the whole thing bears further investigation, as there appears to be doubt about other aspects too. Jan Bredenbeek, for example, suggests that: Call parameters                         Return parameters .. A1                                     A1 Preserved He was going to investigate

### Re: [Ql-Users] A polite request

On 15/02/2018 14:32, Marcos Cruz via Ql-Users wrote: En/Je/On 2018-02-14 19:40, Norman Dunbar via Ql-Users escribió / skribis / wrote : Please, please, please do not "hijack" a thread. Don't reply to a thread and change the subject to something completely unrelated. I agree. That is

### Re: [Ql-Users] QA.RESRI - QDOSMSQ eference guide

On 15/02/2018 14:46, Wolfgang Lenerz via Ql-Users wrote: <> Thanks for testing these. How big was the amount of memory requested? Big enough that a shift would occur? Yes. Further tests show that d0 sometimes returns zero (at least two different paths) but usually not, ie it returns with

### Re: [Ql-Users] QA.RESRI - QDOSMSQ eference guide

On 15/02/2018 18:42, pjwitte via Ql-Users wrote:     move.w qa.resri,d0     moveq #0,d0     jsr (a2)     tst.l d0 Err, that should be move.w qa.resri,a2, but I guess that's pretty obvious. The next bit isnt obvious, but is correct. Per ___ QL

### Re: [Ql-Users] QA.RESRI - QDOSMSQ eference guide

On 16/02/2018 12:50, pjwitte via Ql-Users wrote: On 16/02/2018 10:27, Jan Bredenbeek via Ql-Users wrote: <> SBASIC bahaves in much the same way as QLiberated programs. I guess QLib has always used the Common Heap for its names and variables, as SBASIC does now. Also a6 is fixed unde

### Re: [Ql-Users] QA.RESRI - QDOSMSQ eference guide

On 16/02/2018 22:12, pjwitte via Ql-Users wrote: <> If Ive understood correctly, SBASIC sets up each array in its own heap. This assumption was partially or wholly incorrect. Sorry. I'll shut up now. P ___ QL-Users Mailing List

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

via Ql-Users wrote: I have a commented (in German!) disassembly of V1.89, if thats of any interest. It seems quite thorough and detailed, but Ive not tried to reassemble it. Let me know where to send it if you want it. Per On 25/02/2018 15:51, Martyn Hill via Ql-Users wrote: Hi everyone! I'm

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

I have a commented (in German!) disassembly of V1.89, if thats of any interest. It seems quite thorough and detailed, but Ive not tried to reassemble it. Let me know where to send it if you want it. Per On 25/02/2018 15:51, Martyn Hill via Ql-Users wrote: Hi everyone! I'm looking to get a

### [Ql-Users] Merry Christmas with SMSQ/E

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.

### [Ql-Users] Buggy Christmas

Re: [Ql-Users] Merry Christmas with SMSQ/E Probably spotted by Dilwyn years ago, only weve forgotten.. ;) It was a bad day for me for sure, as shortly after, thinking lightning wouldnt strike twice (and thus not being in a hurry to save..), I managed to bomb out again by feeding DISA 3.05

### Re: [Ql-Users] Odd behavour of the DIR command?

On 26/07/2018 14:50, Jan Bredenbeek via Ql-Users wrote: What we really need, is a new file system! :) I like the way DOS_DRIVE/NFA_DRIVE work in QPC2/SMSQmulator. You can "root" the device DOS/NFA anywhere in the host's filing system. The result is transparent to the rest of the system. This

### Re: [Ql-Users] colour confusion

ore with them than anybody who simply duplicated the QJump style. Cheers, Marcel Am 24.08.2018 um 14:45 schrieb pjwitte via Ql-Users : There appears to be some inconsistency in the application of colour components of palettes by different software authors. Im referring in particula

### [Ql-Users] QD 2018 colours

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

### Re: [Ql-Users] colour confusion

On 25/08/2018 15:16, Bob Spelten via Ql-Users wrote: 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

### Re: [Ql-Users] QD 2018 colours

On 28/08/2018 14:45, Marcel Kilgus via Ql-Users wrote: pjwitte via Ql-Users wrote: 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! I've never used or seen this menu, but yes, it's

### Re: [Ql-Users] QD 2018 colours

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

### Re: [Ql-Users] QD 2018 colours

On 28/08/2018 21:10, pjwitte via Ql-Users wrote: Op Tue, 28 Aug 2018 15:26:22 +0200 schreef Marcel Kilgus via Ql-Users : Bob Spelten via Ql-Users wrote: <> There is one serious bug though, that I hope will one day be tackled by some brave and patient soul. Its hard to demonstrate and

### Re: [Ql-Users] QD 2018 colours

On 29/08/2018 00:53, Marcel Kilgus via Ql-Users wrote: pjwitte via Ql-Users wrote: So that wouldnt help you, Bob. In VB0.3 the behaviour changed again. Now DOing the resize button annoyingly resets the width to 80 coloumns for some reason as well as maxing the hight. It has never worked for me

### Re: [Ql-Users] QD 2018 colours

On 29/08/2018 00:48, Marcel Kilgus via Ql-Users wrote: 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

### [Ql-Users] colour confusion

There appears to be some inconsistency in the application of colour components of palettes by different software authors. Im referring in particular to the use of "middle ground". Correct me if Im wrong, but I assumed this option was reserved for use as the strip colour, ie the colour of the

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

On 24/01/2018 06:34, Wolf via Ql-Users wrote: Hi Per, Keep on dealing! :) Are you waiting for the next bug-fix? Sure :D Got anything cooking? P Wolfgang ___ QL-Users Mailing List

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

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

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

On 23/01/2018 11:33, Wolfgang Lenerz via Ql-Users wrote: Hi, Re-upped! Been watching The Wire? - The wire? I dont want to muddy the list with OT, but I think its only polite to reply: The Wire is a US TV series about the drug epidemic in Baltimore, and no doubt elsewhere in Americastan.

### Re: [Ql-Users] Sjef vd Molengraaf

Thanks Sjef, for arranging those great shows at Eindhoven! And thanks Bob, for letting us know. Per On 09/03/2018 16:35, Bob Spelten via Ql-Users wrote: 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

### Re: [Ql-Users] Graphic objects and padding

On 13/04/2018 17:46, Dilwyn Jones via Ql-Users wrote: 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,

### [Ql-Users] Graphic objects and padding

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

### Re: [Ql-Users] Graphic objects and padding

On 14/04/2018 20:01, Marcel Kilgus via Ql-Users wrote: pjwitte via Ql-Users wrote: 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. "The books" were writt

### [Ql-Users] QL wikis and information

fer free web hosting to anyone willing to run it. On Mon, Apr 16, 2018 at 9:47 AM, pjwitte via Ql-Users < ql-users@lists.q-v-d.com> wrote: At present there is http://qdosmsq.dunbar-it.co.uk/doku.php?id=qdosmsq:start, which is a technical wiki. There is also http://qlwiki

### Re: [Ql-Users] QL Video Card?

I found this little snippet in my files that I thought you might enjoy :o) Per Masterpiece by Miracle Systems The long awaited GRAPHICS CARD, now titled the "Masterpiece Enhanced Graphics Card” will soon see the light of day. The targeted selling price is £50 (may change). The small

### Re: [Ql-Users] FiFi

Very nice! Thank you, Wolfgang. I bought the first version years ago and have updated since then, but hadnt realised that we werent still on V4.30. BTW, Im not able to change the main display palette: Whatever I configure it to, it stays at no. 1 (no. 2, in FiFi parlance). Having fun ;) Per

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

Great!! I want my money back! ;) On 01/03/2018 21:14, Wolf via Ql-Users wrote: Hi, TT told me some time ago that it was alright to have Qmon downloadable. Wolfgang ___ QL-Users Mailing List ___

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

Well caught, Marcel :) Per On 27/02/2018 00:00, Marcel Kilgus via Ql-Users wrote: Martyn Hill via Ql-Users wrote: Specifically, when receiving via LBYTES (and SBYTES at the remote end), Minerva 1.97+ on its own receives perfectly, but once the NET driver is effectively replaced with TK2 (upto

On 28/06/2018 09:03, Wolfgang Lenerz via Ql-Users wrote: Hi, I made a small Sbasic testcase (SMSQE, not QDOS). I made a program with procedures all called "abcdefghijklmnopqrt"+ a 5 digit number at the end. The program starts at line 100, is increased by one and very 12th line a new 10 line

### Re: [Ql-Users] QD 2018

On 16/09/2018 00:55, Marcel Kilgus via Ql-Users wrote: 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

### Re: [Ql-Users] QD 2018

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

### [Ql-Users] Just testing

I discovered there had been some activity on the list which I havent received. The last message I received until today was dated 29.10.2018. Per ___ QL-Users Mailing List

### Re: [Ql-Users] New QPC release ?

What seems to be the problem? To me the only "problem" seems to be one or two small inconsistencies: DMEDIUM_TYPE returns -1 on DOS devices (the underlying iof.xinf call suggests: IOI_FTYP \$2C Byte Format type (1=qdos, 2=msdos etc) but -1 is arguable..) The other relates to iof.xinf

### [Ql-Users] Knoware.no

Just to let you know that Knoware is up and running again after ten years or so of being nowhere. While I hope there will be something of interest for anyone interested in the QL and derivatives in general, its main interest will be for those of us who like to write programs for it and

### Re: [Ql-Users] New QPC release ?

On 09/04/2019 12:51, François Van Emelen via Ql-Users wrote: Op 8/04/2019 om 14:58 schreef pjwitte via Ql-Users: What seems to be the problem? To me the only "problem" seems to be one or two small inconsistencies: DMEDIUM_TYPE returns -1 on DOS devices (the underlying iof.xinf cal

### Re: [Ql-Users] WM_move_mode and Easyptr menu

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

### Re: [Ql-Users] WM_move_mode and Easyptr menu

On 19/10/2019 17:00, François Van Emelen via Ql-Users wrote: Op 18/10/2019 om 11:34 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

### [Ql-Users] testing

I sent a response to something here, but it didnt arrive.. ___ QL-Users Mailing List

### Re: [Ql-Users] E-mail etiquette: New subject, new message

A lot of people simply dont know this because they never view their mails by thread. I know I didnt, until I was told off about this some years ago. (I hope Ive managed to behave since then!) On this list there also used to be a convention to top- or tail- reply (I can no longer remember which

### Re: [Ql-Users] SMSQmulator 2.29

Same here. And the version is marked 2B29 in the About. Per On 19/04/2020 13:22, Bob Spelten via Ql-Users wrote: 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

### Re: [Ql-Users] SMSQmulator 2.29

Hi Wolfgang, Gremlins have dissipated. Thank you SMSQmulator! Per 19/04/2020 15:38, Wolfgang Lenerz via Ql-Users wrote: 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

### Re: [Ql-Users] QL User grapic competition from 1985: Tree

On 16/04/2020 12:39, Michael Berger via Ql-Users wrote: I remember that. Cool :o) But I cant answer your question, sorry. Per ___ QL-Users Mailing List

### Re: [Ql-Users] SBASIC

Try EXEP 'SBASIC', or even EXEP 'SBASIC'; 'lrun"myprog_bas"'! Per On 22/03/2020 17:52, Giorgio Garabello via Ql-Users wrote: I'm trying to run the SBASIC command inside a compiled program (with Qliberator) but nothing happens . Ideas? 100 PRINT "STEP 1" 110 SBASIC 120 PRINT "STEP 2"

### Re: [Ql-Users] SBASIC

trying to do. Per On 22/03/2020 21:35, Giorgio Garabello via Ql-Users wrote: Il giorno dom 22 mar 2020 alle ore 18:22 pjwitte via Ql-Users < ql-users@lists.q-v-d.com> ha scritto: Try EXEP 'SBASIC', this work well! or even EXEP 'SBASIC'; 'lrun"myprog_bas"'! this not Giorgio P

### Re: [Ql-Users] Select on

On 19/06/2020 10:52, Giorgio Garabello via Ql-Users wrote: "SELect ON" instruction I find it has a major flaw that will not allow you to manage alphanumeric variables, I unfortunately don't know the assemly Would someone be available to create an extension similar to SELECT (e.g. SELECT \$)

### Re: [Ql-Users] Select on

On 19/06/2020 20:02, Daniel Baum via Ql-Users wrote: What about doing something like this. In languages like c# the equivalent of the "select on: command is hardly ever used and if .. else if ... else is much more common: 100 INPUT a\$ 110 IF a\$="a" THEN 115 PRINT "hello a" 120 ELSE 130

### Re: [Ql-Users] Select on

On 21/06/2020 13:38, Bob Spelten via Ql-Users wrote: 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

### Re: [Ql-Users] Select on

On 20/06/2020 17:00, Jan Bredenbeek via Ql-Users wrote: Op za 20 jun. 2020 14:01 schreef Dave Park via Ql-Users < ql-users@lists.q-v-d.com>: ooGyebd = Goodbye goodbye <> Goodbye Use a hash algorithm like CRC-16 or CRC-32? ;-) Thats probably the fastest solution so far :o) Maybe overkill

### Re: [Ql-Users] loopy bug

On 06/07/2021 14:13, Wolfgang Lenerz via Ql-Users wrote: Hi Per, an interesting pitfall, thanks for pointing that out. It does seem that Qlib sets the value of the repeat loop control variable to 0 at the start of the loop. Do you know how this fares on plain QDOS, not SMSQE? Regards

### Re: [Ql-Users] Lookup%

On 06/07/2021 16:18, desin via Ql-Users wrote: Am 06.07.21 um 15:07 schrieb Graeme Gregory via Ql-Users: On Tue, 6 Jul 2021, at 1:59 PM, desin via Ql-Users wrote: I agree with Francois, using LOOKUP% as alternative for EXISTS. I use it a lot. It returns the place in the name table which

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

On 28/06/2021 13:10, desin via Ql-Users wrote: Am 28.06.21 um 12:31 schrieb Bob Spelten via Ql-Users: "RETurn not in procedure or function" <> Bob hello found some oddities with Exists and SMSQE 10 if exists ("TK2_EXT"):print "TK2" 20 if exists ("MODE")   :print "mode " 30 : 40 print dig_it

### Re: [Ql-Users] Lookup%

On 06/07/2021 16:51, Graeme Gregory via Ql-Users wrote: On Tue, 6 Jul 2021, at 3:44 PM, pjwitte via Ql-Users wrote: <> If it were only that easy.. :o( I havent gone through all of it, but just a couple of things: MACHINE would be better for sorting out wots wot, except not all s

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

On 29/06/2021 11:44, Bob Spelten via Ql-Users wrote: 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

### [Ql-Users] loopy bug

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

### Re: [Ql-Users] QL-SD ROM

On 29/04/2021 19:45, Marcel Kilgus via Ql-Users wrote: An update on the progress of the external QL-SD variant: https://www.kilgus.net/2021/04/29/ql-sd-rom-tiny/ Cheers, Marcel Another poke at my regret at the necessity of getting rid of all my QL hardware! :o( Still, Im glad its out there. I

### Re: [Ql-Users] SMSQmulator 2.31

On 18/02/2021 08:35, Wolfgang Lenerz via Ql-Users wrote: Hi all, SMSQmulator 2.31 is out (wlenerz.com/smsqmulator). This is a pure bugfix release, to get rid of the syncscrap bug evoked here, as well as some others found notably by Fabrizio Diversi and Bob Spelten. Thank you, Wolfgang!

### Re: [Ql-Users] SMSQmulator 2.30

There appears to be a problem with the JVA_SYNCSCRAP job in Windows (10). I find it impossible to use the scrap, both internally (eg QD <-> QD) or from Windows (eg Notepad <-> QD). It always contains the same random text that never gets updated. Stopping the SYNCSCRAP job cures the problem

### Re: [Ql-Users] SMSQmulator

On 25/12/2021 14:29, Wolf via Ql-Users wrote: Hi all, SMSQmulator 2.33 is out now. Just a small bugfix release, notably for the NFA device, which is now marked as a format type 4. http://www.wlenerz.com/smsqmulator/ Season's Greetings to all! Thank you! Now for the dumb questions:

### Re: [Ql-Users] SMSQmulator

As my uninspiring maths teacher used to say, "You're right: No question is too dumb to ask. But you may be too dumb to understand the answer"! So theres that.. I dont know that any version of Java is installed in Windows by default, but anyway, mine was an "upgrade" from W10 and Java 8 was

### Re: [Ql-Users] INSTR_CASE

On 23/12/2021 22:31, desin via Ql-Users wrote: 100 OPEN #1,"con_" 110   WINDOW #1,256,256,0,0 120 CLS 130 a\$= "hello" :b\$= "Hello" 140 PRINT#1, a\$,a\$,a\$ INSTR a\$ 150 PRINT#1, a\$,b\$,a\$ INSTR b\$ 160 PRINT " case 1" 170 INSTR_CASE 1 180 PRINT#1, a\$,a\$,a\$ INSTR a\$ 190 PRINT#1, a\$,b\$,a\$ INSTR b\$ 200

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

Giorgio, Use the device name to make the distinction: If its called DOS, then its DOS, etc. Per On 26/11/2021 10:28, Giorgio Garabello via Ql-Users wrote: The old behavior was that DMEDIUM_DRIVE returned -1 when pointing to a dos disk. it was not "correct" but it allowed me to distinguish

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

My DevGet subroutine (www.Knoware.no/htm/basic.htm) demonstrates how you can always get the real device name. Per On 26/11/2021 10:59, Giorgio Garabello via Ql-Users wrote: It is not a safe method, it can be renamed from DOS_USE Giorgio Il giorno ven 26 nov 2021 alle ore 10:49 pjwitte via

### [Ql-Users] Knoware

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

### Re: [Ql-Users] Knoware

Thanks to all for positive feedback! Im glad so many of us are still active and keeping the show on the road in lots of different ways! Per On 22/11/2021 19:42, Urs Koenig (QL) via Ql-Users wrote: Per wrote: Thereve been some changes to Knoware since the last announced update. Wow, many 2021

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

Ive just "upgraded" to Windows 11, as I didnt want to get caught out again being forced into a paid upgrade - or risk being saddled with an unsupported older version of Windoze. (Oh do I hate "upgrades", when all I want is for things to get fixed, and incremental improvements that relate to

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

without extortion. I guess its going to get harder and harder to workaround the encroachment of the worst kinds of futures.. I dont see QLing on an iPhone as a viable option.. Per --- Regards, Derek On 8 November 2021 13:39:36 GMT, pjwitte via Ql-Users wrote: On 08/11/2021 14:11, Marcel

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

I'll post one on the forum Per On 08/11/2021 23:07, Marcel Kilgus via Ql-Users wrote: pjwitte via Ql-Users wrote: Thanks, Marcel. I arrived there by a different route, but no, it doesnt work for me. OK. I'll ask if there is a Windows 11 VM I can use at work to see it myself. I can't even

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

Sorted! Thanks to all who tried to help! Some details here, if youre interested: https://qlforum.co.uk/viewtopic.php?f=19=3965=44294#p44292 Per On 08/11/2021 23:53, pjwitte via Ql-Users wrote: I'll post one on the forum Per On 08/11/2021 23:07, Marcel Kilgus via Ql-Users wrote: pjwitte via