Page 30 of 30

Re: Q_Liberator malaise

Posted: Thu Jul 17, 2025 11:13 am
by Martin_Head
Try this.
qtrans2DB4.zip
(56.19 KiB) Downloaded 4 times
This is the original 'bodged' version of QTrans2. In which I have patched all the Q_ERR... keyword definitions to Q_XXX..

This is to 'disable' the built in Q_ERR keywords. Before EXECing the program, LRESPR the QERR601B_bin file to add the replacement Q_ERR keywords.

Re: Q_Liberator malaise

Posted: Thu Jul 17, 2025 11:42 am
by RalfR
Is it now clear that the cache problems are caused by Q_ERR_xx?

Re: Q_Liberator malaise

Posted: Thu Jul 17, 2025 2:28 pm
by NormanDunbar
Dilwyn" wrote:CHECK looks for the FI2_CALL keyword (returns 1 if it exists and 0 if it doesn't - it's a function in DJToolkit).
I can thoroughly recommend DJToolkit. I've been using it since the 1990s, almost every time I used my QL.

:D :D :D :D :D

Cheers,
Norm.

Re: Q_Liberator malaise

Posted: Thu Jul 17, 2025 4:15 pm
by Artificer
Hi Martin,
Thanks for your work and the rapid turnaround of a new software test.
Unfortunately I am again away from home and the Q60 and so I won't be able to test and report back until a week on Monday.

Cheers

Re: Q_Liberator malaise

Posted: Thu Jul 17, 2025 5:02 pm
by Martin_Head
Artificer wrote: Thu Jul 17, 2025 4:15 pm Hi Martin,
Thanks for your work and the rapid turnaround of a new software test.
Unfortunately I am again away from home and the Q60 and so I won't be able to test and report back until a week on Monday.

Cheers
I have done the same patch for SQRview. It's just a shot in the dark to see if it fixes the problems with SQRview

Same as before LRESPR QERR601B_bin first

Re: Q_Liberator malaise

Posted: Fri Jul 18, 2025 11:07 am
by BSJR
Martin_Head wrote: Thu Jul 17, 2025 5:02 pm I have done the same patch for SQRview. It's just a shot in the dark to see if it fixes the problems with SQRview

Same as before LRESPR QERR601B_bin first
I don't know what you did to SQRview but I wonder if this will work.
Versions 1.01 & 1.02 have the old ('94) QLib_ext built in, so any recently loaded version should be ignored by SQRview's own Q_ERR version.

On my QPC2, with a recent QLib_run (02.06.25), this SQRview102D4B stops with an "invalid name" on Q_ERR_ON when loading a picture.

BSJR

Re: Q_Liberator malaise

Posted: Fri Jul 18, 2025 2:13 pm
by bixio60
RalfR wrote: Thu Jul 17, 2025 11:42 am Is it now clear that the cache problems are caused by Q_ERR_xx?
Hi,
I'm a little embarrassed to arrive when most of the work has been done, but due to health reasons, I've been away.

Using the Q60 without Copyback enabled is a major limitation.

So, here's my test environment:
- SMSQE 3.42 (Q60 with copyback always enabled)
- Normal boot that loads the many drivers I normally use.
- In my boot, I replaced the qlib_sys driver with the new Q604F runtime and Lrespr QERR601B_bin.

In this test environment:
- ACP (original version) started working again.
- Qtrans2DB4 works normally.
- Qcoco works.
- SQRview102DB4 works.

Almost all the apps I regularly use that didn't include the Qlib runtime work again. Launchpad only works when launched with the QEX command.

This is a positive news, after my initial tests, waiting for much more competent people like Artificer to finish their tests.

Re: Q_Liberator malaise

Posted: Fri Jul 18, 2025 2:51 pm
by Martin_Head
BSJR wrote: Fri Jul 18, 2025 11:07 am
Martin_Head wrote: Thu Jul 17, 2025 5:02 pm I have done the same patch for SQRview. It's just a shot in the dark to see if it fixes the problems with SQRview

Same as before LRESPR QERR601B_bin first
I don't know what you did to SQRview but I wonder if this will work.
Versions 1.01 & 1.02 have the old ('94) QLib_ext built in, so any recently loaded version should be ignored by SQRview's own Q_ERR version.

On my QPC2, with a recent QLib_run (02.06.25), this SQRview102D4B stops with an "invalid name" on Q_ERR_ON when loading a picture.

BSJR
What I did, was that I patched the SQRview object files definitions of the Q_ERR_ commands to Q_XXX_. But not the references in the compiled SuperBASIC.

So the compiled program will still look for Q_ERR_ON, but not find it in the compiled program, so will look outside for it. So you need to LRESPR the QERR601B_bin file first. To add the new Q_ERR_ commands to the job 0 SuperBASIC.

The invalid name looks like you did not install the new Q_ERR_ commands first.

Here's some screen shots with different runtimes
Image4.png
Image5.png
Image7.png

Re: Q_Liberator malaise

Posted: Fri Jul 18, 2025 2:53 pm
by Martin_Head
And here's with normal runtimes
Image9.png
Image10.png
Image11.png