Help with Q Liberator

[gregtaylor]

Have found the boot program calls at the end boot_use which incorrectly was set to flp1_ not win1_. Have corrected that but still errors loading liberate. The last line of boot_use is Q_L. No sure what that does.

[gregtaylor]

Have tried that on the command line and also by changing win1_boot_use to qlib_use win1_,win1_ as there is no directory used.

[gregtaylor]

Have tried that on the command line and also by changing win1_boot_use to qlib_use win1_,win1_ as there is no directory used.

[dilwyn]

Have found the boot program calls at the end boot_use which incorrectly was set to flp1_ not win1_. Have corrected that but still errors loading liberate. The last line of boot_use is Q_L. No sure what that does.

A largely undocumented command (in QLIB_run), Q_L enforces the definitions where necessary. Seems to work fine without it.

Can you compile just by using the command LIBERATE to bring up the "front end" window of the compiler, and compiling from there? You would need to create the work file (filename ending in _wrk) first if you don't have the QSAVE commands on your system. LIBERATE 'filename' (i.e. the version without the comma at the end) would generate the work file.

Steps:
1. ensure the compiler extensions have been LRESPRed (since you can get pass 1 working that seems to be in order), and that an appropriate QLIB_USE command is in force.
2. save the basic program somewhere convenient, e.g. SAVE ram1_test_bas
3. create the work file with the command LIBERATE ram1_test_bas which should create a file called ram1_test_bas_wrk (not sure if v3.36 would create ram1_test_wrk or ram1_test_bas_wrk like v3.46)
4. if LIBERATE "ram1_test_bas_wrk", doesn't compile, try just the command LIBERATE to bring up the front end screen and fill in the boxes (this is version 3.46 on my system, not too different to the v3.36 you said you had apart from slight differences in handling the filename extensions, which you'll soon notice, on some versions it finds the extensions automatically, others you have to type them in).

QLib front end

qlib.jpg (15.82 KiB) Viewed 218 times

The options across the top are the same ones as used in the 10-digit string as last parameter of QLIB_USE (see section 14 of manual).

If still not working, maybe you should try it on another system to see if there are any differences in how it runs on QL2K comparaed to other systems. Although I have QL2K x64 installed, it doesn't seem to run on Windoze 11, it gets as far as the 10 second "Postcardware" countdown then just vanishes. Haven't yet tried the compatibility or administrator modes.

On QPC2 at least, my copy of QLib seems to work fine with the above steps, both with the LIBERATE commands and from the front end, although it's a different version number to yours.

[Derek_Stewart]

Hi,

I have download QL2K and copied QLIB 2.46 to an MDV image, load the MDV image to MDV1 and started up QL2K

I use a smaller boot programme, that only loads the bare minimum: ENV_BIN, QLIB_RUN, QLIB_BIN, QLIB_EXT and set QLIB_USE "mdv1_qlib_","mdv1_qlib_"

Once the basics are understood, the other extension like Overlay file can be used, See the user manual for more information.

Qliberator v2.46 need the environmental variable extension - ENV_BIN

See screen shot of loading the Qliberator front end with the LIBERATE command:

have saved the Qliberator v2.46 files to a MDV image if this helps

I have compressed the MDV file due to rubbish Forum setup not allowing MDV files. Just uncompress with any unzip programme and insert into the QL2K MDV directory.


**** I uploaded the wrong zipped up MDV image, this is the correct one

QLIB.MDV.zip

(57.22 KiB) Downloaded 3 times

[gregtaylor]

Have tried qlib_use win1_,win1_ (no directory) but no joy. Have also tries a JS ROM and also tied the same thing in QPC2 with no joy. Will have another go today.

[Derek_Stewart]

Hi,

I run QL2K on a Linux system under WINE, which makes things a little slower, bu the MDV image can be read and runs the Qliberator compiler.

Code: Select all

LRESPR "mdv1_ENV_BIN"
LRESPR "mdv1_QLIB_RUN"
LRESPR "mdv1_QLIB_BIN"
LRESPR "mdv1_QLIB_EXT"
QLIB_USE "mdv1_qlib_","mdv1_qlib_"

this should get Qliberator running from MDV1_

Can you post your boot file, maybe we can help.

[gregtaylor]

Here we go:

100 td1$='win1_'
110 REMark Q_Liberator Boot 3.36
120 REMark Copyright 1991 Liberation Software
130 :
140 PRINT #0,"Q_Liberator Loading ..."
150 :
160 REMark ** Load Qlib system **
170 REMark Contains all of the files
180 REMark Qlib_bin,Qlib_run,Qlib_ext,Qlib_ovl
190 REMark Produced using RPM, control file for
195 td$='win1_'
200 REMark RPM is QLIB_rpm
210 :
220 a=RESPR(16008)
230 LBYTES td$&'Qlib_sys',a : CALL a
240 :
250 GO TO 500
260 :
270 REMark +++++++ Files can also be loaded individually ++++++++++++++
280 :
290 REMark ** Load Phase 1 of compiler **
300 REMark contains LIBERATE QX QW QX_JOB0
310 REMark GLOBAL DEF_INTEGER EXT_PROC EXT_FN
320 REMark QLIB_USE
330 :
340 a=RESPR(2910)
350 LBYTES td$&'Qlib_bin',a : CALL a
360 :
370 REMark ** Load runtime system **
380 a=RESPR(10552)
390 LBYTES td$&'Qlib_run',a : CALL a
400 :
410 REMark ** Load OVERLAY and UNLOAD **
420 a=RESPR(1006)
430 LBYTES td$&'Qlib_ovl',a : CALL a
440 :
450 REMark ** Load SuperBASIC extensions **
460 REMark QERR QJ etc
470 a=RESPR(1472)
480 LBYTES td$&'Qlib_ext',a : CALL a
490 :
500 REMark If ROM version AH or JM we must merge
510 REMark BOOT_USE to set QLIB_USE defaults.
520 REMark With JS and later ROMS we can include
530 REMark a QLIB_USE call in the same program.
540 :
550 LRUN td$&'boot_use'


boot_use:

1000 REMark SET DEFAULTS FOR Q_Liberator
1010 REMark Compiler load device, Help file device
1020 QLIB_USE win1_,win1_
1030 Q_L

Greg

[Andrew]

Here we go:
......
Greg

You are not loading Env_bin
See Derek's example above.

[RalfR]

You are not loading Env_bin

Not needed in v3.36.