The Sinclair QL Forum

Many thanks Martin for continuing to work on this problem. I am looking forward to again testing the new runtime. But I am not able to access my Q60 until the end of this month.

Cheers

Hi Martin,

Have finally been able to tryout RUNQ603 runtimes, copyback on smsqe 3.42.

The programs I have tried so far are:
QCoCo, ACP, EddIcon, Screen copy, Fontview, SQRView, Qtrans, QCP, Xchange, SpriteView

SQRview on attempt to load an image file produces the qlib FOR type error message with ...

Hi Martin I have not lost interest in trying amended versions of lib runtimes but I have been away from my Q60 for a few days, back next week.
If I remember correctly FInfo2 works OK with other program launchers with copyback. I doubt that the qtrans issue is due to Finfo2 itself.

Cheers

Martin said:
I have had another go at modifying the QLib runtimes for the Q60 problems.


Hi Martin, I have good news this time. Programs such as QCoCo, ACP, EddIcon, My screen copier, and others that do not have older runtimes incorporated seem to run correctly, smsq/e 3.42 plus copyback ...

Dilwyn wrote: would using Qlib_Patch_Obj to turn off the AUTO setting in a compiled program achieve a similar result?

Answer : no its not a solution. Compiling with AUTOF set to off or patching AUTO to off fails to alter the behaviour of QLiberated programs with copyback.

The problem with FOR ...

Hi Martin,

On my Q60 a first quick look at Q60test01 runtimes was not good. Booting into smsq/e 3.41 cache in writethrough Launchpad fell over with error 35 index out of range. Qdock however was Ok. Testing Qcoco, ACP and SQRV form Qdock resulted in all failing with error 35. Launchpad - bodged ...

Hi Martin,

I have run your variable listing program on both the compiled versions on the sceen copy program, one with a FOR loop and one with a repeat loop. An integer variable of type $00 is present in both, so probably not the cause of copyback problems.

Now since the version of the screen copy ...

Martin wrote: Do you have AUTOF turned off in QLib

Generally speaking I compile with AUTOF turned on.
Since you first mentioned AUTOF I have recompiled the screen copier(FOR loop) with AUTOF turned OFF. And the resulting screen copy is similar with lines skipped and approximately halfway through ...

RalfR: wrote Interesting that the program started at all

I have a small number of QLIberated programs that run apparently OK with copyback. The screen copier was not one of them obviously.

Hi Martin,

Although your patch program did not work, here is something that indicates that FOR loop variables are at least part of the incompatibility of QLib with copyback. I have a small program to copy the screen to a pic file. The program does not copy the screen correctly when compiled and ...