On 18 Sep 2010, at 22:25, Tobias Fröschle wrote:
you seem to be taking this from HOT_REXT. Where did you get the sources for
this?
When looking into SMSQ/E sources, there is nothing comparable to what you see
there (sms.lthg is in util_thg_lthg_asm. Nothing in there touches memory on
Am 19.09.2010 11:06, schrieb gdgqler:
On 18 Sep 2010, at 22:25, Tobias Fröschle wrote:
you seem to be taking this from HOT_REXT. Where did you get the sources for
this?
When looking into SMSQ/E sources, there is nothing comparable to what you see there
(sms.lthg is in util_thg_lthg_asm.
QL Today Volume 15 Issue 1 arrived here(Germany, Eifel) yesterday.
I like it
Regards to all,
Frank-Guido Dibowski
___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
gdgqler wrote:
If you add a Thing to the list of Things by using the software
described in the manual for the Trap #1 routine sms.lthg you will
Just to be sure, none of the trap #1 thing entry routines are
supported in SMSQ/E. Just the traditional HOT_REXT way of calling
them.
find that the
On 19 Sep 2010, at 14:48, Marcel Kilgus wrote:
gdgqler wrote:
If you add a Thing to the list of Things by using the software
described in the manual for the Trap #1 routine sms.lthg you will
Just to be sure, none of the trap #1 thing entry routines are
supported in SMSQ/E. Just the
Am 19.09.2010 16:18, schrieb gdgqler:
However, I have set up two programs as executable Things with both the Thing
itself and the linkage block being inside the program. When these programs are
LRESPRd they are owned by the
Which obviously collides with the rule The thing linkage block must
On 19 Sep 2010, at 17:06, Tobias Fröschle wrote:
(but remember where the system assumes your likage block lives - directly
after a common heap header)
This may be obvious - but only after a very large amount of digging into the
software. Unless . . .
Is there somewhere in the manuals that
