Re: [Ql-Users] A feature or a bug?

Hi, I often use something like this for ftest 100 DEFine FuNction ftest2(file$) 110 LOCal dad$,ded$,prd$,a 120 dad$=DATAD$ 130 ded$=DESTD$ 140 prd$=PROGD$ 150 DATA_USE "" 160 DEST_USE "" 170 PROG_USE "" 180 a=FTEST(file$) 190 DATA_USE dad$ 200 DEST_USE ded$ 210 PROG_USE prd$

Re: [Ql-Users] A feature or a bug?

Yes. Cheers, Norm. On 14 June 2016 20:53:15 BST, "Ralf Reköndt" wrote: >Does this ommit TK2? > >- Original Message - >From: "George Gwilt" > >> Using Turbo Toolkit’s DEVICE_STATUS might be safer. >> >> George >

Re: [Ql-Users] A feature or a bug?

You could use max_devs and dev_name from the truly wonderful DJTOOLKIT too, if you were inclined! I'm surprised that DJ didn't mention it! ;) Cheers, Norm. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ QL-Users Mailing

Re: [Ql-Users] Feature or bug?

I'm not 100% certain, but possibly f$ is suffering from being prefixed by datad$ which obviously exists hence the line 30 execution. I'm not near my QPC at the moment so I can't confirm. What do you get if you set dadtad $ to something like empty or even, something that doesn't exist?

Re: [Ql-Users] A feature or a bug?

Does this ommit TK2? - Original Message - From: "George Gwilt" Using Turbo Toolkit’s DEVICE_STATUS might be safer. George ___ QL-Users Mailing List

Re: [Ql-Users] A feature or a bug?

Well, in the first place, I always thought, that FTEST makes an direct check on the file or device, omitting every TK2 occurence. Unfortunately, I was wrong. - Original Message - From: "Dilwyn Jones" To: Sent: Tuesday, June 14, 2016

Re: [Ql-Users] Q_Liberator externals

BTW: Does anybody know, why TT has omitted the message " Extensions missing" in his own written QLOAD, if used extensions were not loaded? That was very helpful. - Original Message - From: "Marcel Kilgus" To: Sent: Tuesday, June 14,

Re: [Ql-Users] Q_Liberator externals

Michael Bulford wrote: > One of the features I like about Q_Liberator is that resident > procedures and functions can be written in Basic, and compiled into > machine code, to be lrespr-ed in a boot file. These functions can > even have parameters. This works well with Q-emuLator. With QPC2 >

[Ql-Users] Q_Liberator externals

Hi everyone, One of the features I like about Q_Liberator is that resident procedures and functions can be written in Basic, and compiled into machine code, to be lrespr-ed in a boot file. These functions can even have parameters. This works well with Q-emuLator. With QPC2 there seems to

Re: [Ql-Users] A feature or a bug?

- Original Message - From: "Marcel Kilgus" Ralf Reköndt wrote: It's really that awful, as OPEN tries the device you told it, then, if no success, uses DATAD$ or somewhat others, DEV or such. DATAD$, PROGD$ or DESTD$ is prepended to the filename, depending on the call. DEV is just

Re: [Ql-Users] A feature or a bug?

Dilwyn Jones wrote: > There are device open functions out there in other toolkits which do the > same job without checking the TK2 defaults system. This is an important point. This is not an OS feature, i.e. the raw TRAPs do not behave this way, it's strictly a feature of the BASIC commands. That

Re: [Ql-Users] A feature or a bug?

There are device open functions out there in other toolkits which do the same job without checking the TK2 defaults system. Also, it's easy enough to do an error-trapped open_in on most systems, whether you use WHEN ERRor (JS or later ROM), Q_ERR_ON (Qliberator compiler), WHEN_ERROR and

Re: [Ql-Users] A feature or a bug?

It's really that awful, as OPEN tries the device you told it, then, if no success, uses DATAD$ or somewhat others, DEV or such. To be really successfull, you should set the SV_DATAD to "", keep the value then try to open the device. This is the only way to see, if *that* device is not

Re: [Ql-Users] A feature or a bug?

François Van Emelen wrote: > So, this seems to be a feature... a very dangerous one : replacing DIR > f$ in line 30 with DELETE f$ would wipe all directories and files on > that device. That would actually be a somewhat cool feature, but DELETE is not as cool, so nothing will happen. Try it :)

Re: [Ql-Users] A feature or a bug?

I think it's just that Marcel normally just uses DATA_USE dev1_ on his system. Dilwyn -Original Message- From: Derek Stewart Sent: Tuesday, June 14, 2016 6:27 PM To: ql-us...@q-v-d.com Subject: Re: [Ql-Users] A feature or a bug? On 14/06/16 14:43, Marcel Kilgus wrote: Marcel Kilgus

Re: [Ql-Users] A feature or a bug?

Derek Stewart wrote: > I am a little confused, where does DEV1_ default to DATAD$ Never. I said DATAD$ is DEV1_ on my machine. Marcel ___ QL-Users Mailing List

Re: [Ql-Users] A feature or a bug?

On 14/06/16 14:43, Marcel Kilgus wrote: Marcel Kilgus wrote: François Van Emelen wrote: 10 f$="":REMark empty string 20 if FTEST(f$)=0 30 DIR f$ 40 ELSE 50 PRINT f$," can't be a file name" 60 ENDIF Why is line 30 executed (displaying the directory of datad$) instead of line 50? Because

Re: [Ql-Users] Help Please

Hi Dilwyn, Thank you very much. It was my problem. I was working on qxl_win but windows was working with QXL.Win and having got that far, it was very easy. Thank you again, Best Wishes, Peter On 14.06.2016 16:09, Dilwyn Jones wrote: Don't do DIR WIN_DRIVE$(3) - that won't work. If DIR

Re: [Ql-Users] A feature or a bug?

> On 14 Jun 2016, at 16:45, François Van Emelen > wrote: > > Op 14/06/2016 om 16:18 schreef George Gwilt: >>> On 14 Jun 2016, at 14:56, Bob Spelten wrote: >>> >>> Op Tue, 14 Jun 2016 15:43:00 +0200 schreef Marcel Kilgus >>>

Re: [Ql-Users] A feature or a bug?

Can someone explain this? 10 f$="":REMark empty string 20 if FTEST(f$)=0 30 DIR f$ 40 ELSE 50 PRINT f$," can't be a file name" 60 ENDIF Why is line 30 executed (displaying the directory of datad$) instead of line 50? IF line 30 is replace with VIEW f$ then the content of win (in my case Win2_)

Re: [Ql-Users] A feature or a bug?

Op 14/06/2016 om 16:18 schreef George Gwilt: On 14 Jun 2016, at 14:56, Bob Spelten wrote: Op Tue, 14 Jun 2016 15:43:00 +0200 schreef Marcel Kilgus : Marcel Kilgus wrote: François Van Emelen wrote: 10 f$="":REMark empty string 20 if FTEST(f$)=0 30

Re: [Ql-Users] Help Please

Don't do DIR WIN_DRIVE$(3) - that won't work. If DIR WIN3_ doesn't work, three possibilities: 1. Name of the qxl.win isn't correct (e.g. period or underscore, see below, or QXL3_WIN is in a sub-diretory or different Windows drive) 2. system doesn't support WIN_DRIVE command (though I would

Re: [Ql-Users] Help Please

Hi Dilwyn, Firstly thank you. I have used win_drive to define win_drive$(3) as being c:\QXL3_WIN. However if I do a dir win3_ or dir win_drive$(3) all I get is win1 QDOS directory. What, please have I done wrong? Looking forward to hearing from you, TIA & Best Wishes, Peter On

[Ql-Users] A special request: recreate an MD though an MDV image on a real QL

Hi to all there ;) I'm sending this e-mail now at the English QL ML and I would like to know If someone can collaborate with our Preservation program. In particular we need a person that can write an utility that can take our MDV images (for QL Emulator, MDV format and extensione) and

Re: [Ql-Users] A feature or a bug?

> On 14 Jun 2016, at 14:56, Bob Spelten wrote: > > Op Tue, 14 Jun 2016 15:43:00 +0200 schreef Marcel Kilgus > : > >> Marcel Kilgus wrote: >>> François Van Emelen wrote: 10 f$="":REMark empty string 20 if FTEST(f$)=0 30 DIR f$ 40

Re: [Ql-Users] A feature or a bug?

Bob Spelten wrote: > I understand the datad$ but the problem is why FTEST returns a zero? I don't understand, why shouldn't it? > FTEST should return a -7, so DIR is should not be done. Clearly the directory pointed to by DATAD$ exists, so why whould it return -7? Marcel

Re: [Ql-Users] A feature or a bug?

Op Tue, 14 Jun 2016 15:43:00 +0200 schreef Marcel Kilgus : Marcel Kilgus wrote: François Van Emelen wrote: 10 f$="":REMark empty string 20 if FTEST(f$)=0 30 DIR f$ 40 ELSE 50 PRINT f$," can't be a file name" 60 ENDIF Why is line 30 executed (displaying the

Re: [Ql-Users] A feature or a bug?

I tried this and it worked as reported. I then did this: data_use "" then I ran it again, and got the error message. This confirms that datad$ is being picked up and used in the FTEST. Tim ___ QL-Users Mailing List

Re: [Ql-Users] A feature or a bug?

Marcel Kilgus wrote: > François Van Emelen wrote: >> 10 f$="":REMark empty string >> 20 if FTEST(f$)=0 >> 30 DIR f$ >> 40 ELSE >> 50 PRINT f$," can't be a file name" >> 60 ENDIF >> >> Why is line 30 executed (displaying the directory of datad$) instead of >> line 50? > Because SMSQ/E defaults to

Re: [Ql-Users] A feature or a bug?

François Van Emelen wrote: > 10 f$="":REMark empty string > 20 if FTEST(f$)=0 > 30 DIR f$ > 40 ELSE > 50 PRINT f$," can't be a file name" > 60 ENDIF > > Why is line 30 executed (displaying the directory of datad$) instead of > line 50? Because SMSQ/E defaults to dev1_ if you don't give a

[Ql-Users] Feature or bug?

Hi, Can someone explain this? 10 f$="":REMark empty string 20 if FTEST(f$)=0 30 DIR f$ 40 ELSE 50 PRINT f$," can't be a file name" 60 ENDIF Why is line 30 executed (displaying the directory of datad$) instead of line 50? IF line 30 is replace with VIEW f$ then the content of win (in my

[Ql-Users] A feature or a bug?

Hi, Can someone explain this? 10 f$="":REMark empty string 20 if FTEST(f$)=0 30 DIR f$ 40 ELSE 50 PRINT f$," can't be a file name" 60 ENDIF Why is line 30 executed (displaying the directory of datad$) instead of line 50? IF line 30 is replace with VIEW f$ then the content of win (in my

Re: [Ql-Users] Help Please

Hi Peter, If your version of SMSQ/E has the WIN_DRIVE command, you can use this command from SBASIC: WIN_DRIVE drive_number,qxl_win_name where drive_number would be a drive from 1 to 8 inclusive - sounds like you need drive 3 and qxl_win_name would be the DOS filename including drive and

Re: [Ql-Users] Help Please

Hi Peter, Sounds like this is a pseudo hard drive file for QXL, QPC etc. You don't open it as such, you connect it to QPC, for example, as a hard drive on the startup screen. HTH Cheers, Norm. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

[Ql-Users] Help Please

Hi there, I have a QXL3_win and need to open it. Not having the manuals anymore, what is the syntax to open QXL3_Win file, please? TIA & Regards, Peter Fox --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus