Turbo Fix v3d (as amended by D.Santachiara April 2003)

Fixed bug which cleared byte at $28000
Removed SET_PRIORITY TYPE_IN COMMAND_LINE for Turbo compatibility



           Turbo Fix v3 (as amended by D.Santachiara March 2003)

Updated SMSQ/E Minerva recognition routine



           Turbo Fix v2 (as amended by Rich Mellor 29th June 1992)


SET_PRIORITY
This originally allowed you to only set priorities in the range 0...127.
This has been amended for Minerva (and any other ROM which allows the
range 0...255), and now accepts the range -128...127, thus allowing
users to access Minerva's background Jobs. LIST_TASKS had always
displayed negative Job priorities in any event.

This now also reports 'Bad Parameter' if you try to set the priority of
SuperBasic to Zero, thus preventing you from locking SuperBasic out
altogether (it originally tried to do this but failed miserably!).


TYPE_IN
A little amendment to the code for this command, meant that on Minerva
ROMs (and most probably other Sinclair ROMs), the text which it was
actually trying to type into the current keyboard queue could be lost.
This has now been fixed.


COMMAND_LINE
To take account of Minerva's new facilities, this now sets the current
keyboard queue to the command line for either SuperBasic or a MultiBasic.
This works by looking up the task table until it finds a Basic
interpreter.

Due to the way in which this works, this command will work fine when
entered within a MultiBasic or SuperBasic program (or used as a direct
command). However, if used from within a task to access SuperBasic (or
MultiBasic), it will only find the Basic Interpreter which owns the
current Task.

Unfortunately, Toolkit II's EX and EXEC commands always link a new Task
with Job 0, meaning that this command will miss a MultiBasic. To
overcome this, you will need to use Turbo Toolkit's EXECUTE commands. In
any event, the search will only work on Minerva v1.80 (or later) - any
other ROM and these type of commands only allow you to access SuperBasic
(Job 0) as in earlier versions of the Turbo Toolkit.

This also now actually works correctly, as it did on pre v3.22 versions
of the Toolkit !!

The command also no longer assumes that SuperBasic's #0 would have a
channel ID of 00000000 - this is not necessarily so, especially on
Minerva and the THOR XVI where #0 can be safely re-opened.


BASIC_NAME$, BASIC_INDEX%, BASIC_TYPE%, BASIC_F, BASIC_L, BASIC_W% and
BASIC_B%

All of these will now either access SuperBasic's variables or those of a
MultiBasic (see above).