The Sinclair QL Forum

Hello Martin & everyone else that has taken an interest in sorting QLiberator for the Qx0 systems.
Now that I am back from my travels I have had time to test the latest modified version of Qtrans and SQRview plus the patched eQLib error trapping routines.

The qtrans_obj_bodgedDB4 executable now ...

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 found time to test qtrans2DB3A and qtrans2DB3B on my Q60.
The DB3A version when using the internal viewer stops at line 18232 with the program hanging as before. No channel open to the chosen file.

TheDB3B version steps through all the debugs steps and displays the chosen file. The file can ...

pjw wrote:
Q_ERR_xxx figures largely in the Qlib compiler itself..

True, and QLib unmodified does not run on the Q60 with copyback enabled, at the moment it needs Wolfgang Lenerz's patch programs.

Cheers

I have tweaked and compiled the snippet of code Dilwyn Jones supplied. The image shows the code and the outcome indicating that the program
hangs after Q_ERR_ON was set and when error trapping OPEN_IN.

I don't know if you want to try to write a test program to try to replicate the problem on the Q60.

I will modify one of my existing programs to use QLib error trapping and see what happens.
Might take me a few days as I am unfamiliar with the QLib error trapping system.

Cheers

I have attached the screen shot for QTrans debug2. As you can see the last report before it hangs is at line 18232.
The jobs menu shows that the channel to be opened at line 18240 has not been opened.
Could the Q_ERR_ ON keyword cause the qtrans to hang. If so it may explain why Q604F runtimes work ...

The code in the procedures called in line 18340 Top_Of_File : Scroll_Bar might also be useful to look at.

Is QEXEC Wolfgang's 'turn off the cache' program?

Yes it is Wolfgang's solution that on the fly allows copyback incompatible programs to run in writethrough.
It looks like the problem might be between lines,
18232 and 18362.

Cheers

BSJR wrote:
Another test object could be SuQcess, where DBAS can not be ignored.

Thanks for reminding me about SuQcess, all 3 versions of this that I have work perfectly with copyback on indicating that the DBAS file is not an issue with
SRQview. SuQcess is a lovely program with it's GD2 window ...