Is SBASIC programming on SMSQE difficult?

[NormanDunbar]

Sorry folks. The QDOS version is now 260 bytes, I forgot to initailise the exponent when the value was zero. Sorry.

The previous post has been updated with a new version of the QDOS zip file, please re-download or you'll get weird results/crashes depending on the value in D5.W.

The size is now 260 bytes for QDOS. The SMSQ version remains unchanged.

[RalfR]

As TT said in Eindhoven: A bit of a bug is a bug of a bit.

[Derek_Stewart]

I will try to update SMS2

How??? There is no update from TT for years.

The update is SMSQ/E...

[EmmBee]

When it comes to QLiberator external procedures, there's been extensive discussion about them here and how people couldn't get them to work on SMSQ/E systems up to and including v3.36 of QLiberator. Some versions of SMSQ/E even came with a patch program for QLIB_run and QLIB_ext files to help get Externals to work. I presume (I have no exerience to know) that this applies to SMS/SMS2 as well.

Versions of QLIberator AFTER v3.36 (the versions worked on by EmmBee and Per Witte and others) have had a lot of work done on them and there are references in the updated documents to changes made in more recent versions - might be worth looking through the documents with the various version to see if any changes were made relevant to your needs.

For QLiberator version 3.44, Per produced a new Qlib_run with a rather nice printout on #0,
"Q_Liberator Runtimes Release V3.42 © 1993-2021 Liberation Software".
Unfortunately, that version contained a bug that affects Qlib external procedures and functions. I did not notice this bug until sometime after the V3.44 was released. When I next used my DCOPY program, the whole QL crashed, completely freezing QPC2. This was a particularly bad crash, as any work not saved to disk is then lost. All one can do in this case is to restart the QL afresh. I had originally thought that this crash might have been down to a recent Windows update. On further investigation, I found the cause to be with Qlib_run. After noticing this, I immediately E-mailed Per Witte, and he replied that he would look into it. The eventual remedy was a brand new Qlib_run, version 3.44, and this is in the final edition so far of QLiberator V3.45.

[Derek_Stewart]

Hi,

I can not get the examples of external procedure and function detailed in the Qliberator Manual, with Qliberator v3.36, v3.44 in SMSQ/E v3.38

Using Minerva v1.98 every works as expected.

There must be something wrong with SMSQ/E, even if Qliberator v3.44 has a problem with Externals, surely v3.36 should work.

[EmmBee]

I can not get the examples of external procedure and function detailed in the Qliberator Manual, with Qliberator v3.36, v3.44 in SMSQ/E v3.38

Try this version of QLIB_run ...

QLIB_run336_mod2.zip

(8.19 KiB) Downloaded 283 times

EmmBee

[Derek_Stewart]

I can not get the examples of external procedure and function detailed in the Qliberator Manual, with Qliberator v3.36, v3.44 in SMSQ/E v3.38

Try this version of QLIB_run ...

QLIB_run336_mod2.zip

EmmBee

Hi,

Works great, all working.

Thank you for the bug fix.

[pjw]

I can not get the examples of external procedure and function detailed in the Qliberator Manual, with Qliberator v3.36, v3.44 in SMSQ/E v3.38

Try this version of QLIB_run ...

QLIB_run336_mod2.zip

The version of Qlib_run found in the latest distro, Qlib345, is supposed to
be identical to QLIB_run336_mod2, apart from the identification, which says
"Q_Liberator Runtimes Release V3.44 © 1993+ Liberation Software". (Type the
command Q_L at the console to see this, or view the binary.)

The current version of the Qlib compiler itself contains an external
procedure. That program compiled itself, and the result of that compilation
compiled the version of Qlib that you find in the User distribution of
V3.45, so I presume that externals work in V3.35! If this is what you are
using, and this doesnt work, perhaps you could explain?

I feel that the last thing we need is further confusion about which set of
files and sub-versions work and dont work. (Spare a thought for noobs and
recidivists!) As far as Im concerned, there are only two versions of Qlib:
V3.36, which was the final official release (works great on BBQLs) and
V3.45, which has new features and development potential. Apart from the
need for TK2 to run the compiler itself, and a preference for real
directories, it too should work across the board. Why not just use that?

[pjw]

I can not get the examples of external procedure and function detailed in the Qliberator Manual, with Qliberator v3.36, v3.44 in SMSQ/E v3.38

Try this version of QLIB_run ...

QLIB_run336_mod2.zip

The version of Qlib_run found in the latest distro, Qlib345, is supposed to
be identical to QLIB_run336_mod2, apart from the identification, which says
"Q_Liberator Runtimes Release V3.44 © 1993+ Liberation Software". (Type the
command Q_L at the console to see this, or view the binary.)

The current version of the Qlib compiler itself contains an external
procedure. That program compiled itself, and the result of that compilation
compiled the version of Qlib that you find in the User distribution of
V3.45, so I presume that externals work in V3.45! If this is what you are
using, and this doesnt work, perhaps you could explain?

I feel that the last thing we need is further confusion about which set of
files and sub-versions work and dont work. (Spare a thought for noobs and
recidivists!) As far as Im concerned, there are only two versions of Qlib:
V3.36, which was the final official release (works great on BBQLs) and
V3.45, which has new features and development potential. Apart from the
need for TK2 to run the compiler itself, and a preference for real
directories, it too should work across the board. Why not just use that?

[Derek_Stewart]

Hi,

Thanks for the update, but no one said anything till the fixed runtimes appeared