Q_Liberator malaise

[dilwyn]

I don't use FileInfo2, but I don't see the connection to Qtrans, it dos not seem to ask for it.

I am not sure but if you start a program via Qtrans, it should use FI2.

If it detects the presence of one of the FileInfo keywords, it can try to launch files using fileinfo2. Not near a computer to check atm, I *think* it uses something like IF CHECK('FI2_CALL') THEN....

CHECK is a keyword from DJtoolkit which tests for presence of a given extension name.

[Martin_Head]

Artificer said Qtrans hung with FileInfo2, So I don't know if the hang is due to QTrans, or FileInfo on the Q60. I don't know if FileInfo has been tested on the Q60 with the caches on.

Just had a quick look at the FileInfo2 download. It looks like is uses some Qlib files and it states that it can have problems with QTrans

- QTrans (buggy under SMSQ/E v3+ and uses deprecated FileInfo PROC/FN).

[RalfR]

Just had a quick look at the FileInfo2 download. It looks like is uses some Qlib files and it states that it can have problems with QTrans

FI2 itself is an MC Extensions. The Config program is QLiberated. So if FI2 itself makes problems on the Qx0, the MC extensions is perhaps the reason.

[Artificer]

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

[dilwyn]

Before you criticise Qtrans too much in relation to FileInfo2 (and I detest the statement that it's "buggy" - I wrote it, I use it constantly with SMSQ/E and FileInfo2 without a single problem), here is the code used. It really is all that's used. It's in a procedure.

IF CHECK('FI2_FCALL') THEN
fer=FI2_FCALL(filename$)
ELSE
REM no fileinfo 2 v3.5
fer=FEXF(filename$)
END IF

That's easy enough to test as a BASIC program, then compile it for test on a Q60 by anyone who has one.

[RalfR]

fer=FEXF(filename$)

I can't find FEXF in WL's Reference guide

[tofro]

fer=FEXF(filename$)

I can't find FEXF in WL's Reference guide

One F too much - It's FEX, likely. Likely caused because FEX once was EXF (and still has that alias). I understand the confusion...

[dilwyn]

fer=FEXF(filename$)

I can't find FEXF in WL's Reference guide

Depends which version of FilInfo2 you're using - Older versions have FEXF , more recent versions have FI2_CALL

Because of the different keywords in different versions I had to do the check on which keyword existed, in order to use the recommended keyword for the version concerned. Documentation for v3.50 states: "The FEX procedure (and FEXF function) is the exact equivalent of FI2_CALL... FEX and FEX_W are kept for upward compatibility with older FileInfo things only; these procedures should not be used any more in modern programs as their name clashes with SMSQ/E v3+ built in procs. By default FI2 v3.50+ is configured so to skip the initialisation of the FEX and FEX_W procs... and of the FEXF and FEXF_W functions"

FileInfo2 keywords

[RalfR]

Ah...

[BSJR]

fer=FEXF(filename$)

I can't find FEXF in WL's Reference guide

One F too much - It's FEX, likely.

FEW, FEX are SMSQ/E v3+ keywords and there are also FEXP (Lightning math) & FEXP$ (TK2,Minerva).
FEX, FEX$, FEX_W; FEXF, FEXF_W are (old) FI2 keywords, and now replaced by FI2_CALL to avoid conflicts with SMSQ/E .https://www.wlenerz.com/smsqe/addkeys.html#FFF
The old keywords are switched off by default in FI2 but if a program expects the old ones they can be switched on again.

One of these programs is DiskMate5. To use that I edited all FEX names in both DM5 and FI2 to FFX and made them active in FI2, next to the FI2_CALL function for those that expect it.

BSJR