Op Thu, 19 Nov 2009 00:09:40 +0100 schreef John Gilpin
<[email protected]>:
I think that my BOOT sequence would look something like this:-
"BOOT" - Choose the Operating System required and load same. (QDOS OR
SMSQ) [if QDOS is selected then do nothing since QDOS is the native OS
whereas if SMSQ is selected, LRESPR SMSQ_GOLD) - LRUN BOOT2
"BOOT2" - check whether the required toolkits and extensions are loaded
(LRESPRd) and if not, load (LRESPR) them generally in line with the
sequence advised by Dilwyn (FROM Job0!!). LRUN "BOOT3"
"BOOT3" - Check and adjust time and date if required. LRUN "BOOT4"
Seems like a good idea.
My BOOT (0) also writes some parameters to a file that tells it; what
machine it's running on, the mouse- and OpSys type and if ProWesS needs to
be loaded. The next BOOT's can read this file and act automatically.
Queries:- on my QLs (Aurora, SGC, QuBide, etc.) TK2 is loaded
automatically at power-on (AUTOTK2F1 command), the file "BOOT" is
located, LOADed and runs automatically. Are the "EXTRAS" within TK2
LRESPRd in the same manner as if TK2 were LRESPRd from either the
command line or from within a boot program?
GC, SGC and Trump cards have TK2 in ROM so only needs to be initialised by
TK2_EXT (or AUTOTK2F1 on the SGC), SMSQ/E has it in the code and doesn't
even need initialising. You never need to load TK2 separately on these
platforms.
When a SB program is EXECd (from SMSQ) I have noticed that it
too becomes resident in the same way as an LRUN SB program. Does this
mean that the EXECd program also becomes Job0?
No, it becomes a new job, the same way as when you issue the SBASIC
command and LRUN the SB program there.
A good way to test programs. Any LRESPRs done by this program will be
local to that job and EXTRAS from there will only show these local
keywords. If it crashes it's most likely just that job.
Can anyone see why this sequence of programs {which I am
confident will run on both QDOS and SMSQ on the Auroras} should not run
exactly the same under QPC2 on my Vista PCs? (which is the original
point I raised with my existing programs).
In contrast to George G., my BOOT's are the same for all my platforms. You
may need to add some machine testing lines though, to know which tools to
LRESPR or not. There were some examples of this in QL Today v7i2&3.
Finally, I am surprised that no one has yet written a RELIABLE version
of "EXTRAS" as a stand alone tool to enable the name list to be
investigated - or perhaps they have? If it was called "EXTRAS" would it
overwrite the TK2 "EXTRAS"?
Yes it would, so it's not clever to give it the same name.
There is a database of keywords "Keywords_v21_dbs" out there (The QLT Docs
CD, Dilwyns site?) to check for conflicting keyword names.
EXTRAS is part of TK2, Minerva and SMSQ/E but I assume they all act the
same.
Bob
--
The BSJR QL software site at: http://members.chello.nl/b.spelten/ql/
_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
