On Sat, 28 Oct 2006 10:12:36 GMT, erewhon@[EMAIL PROTECTED]
(J French) wrote:
>On Fri, 27 Oct 2006 17:00:14 -0500,
>ArarghMail610NOSPAM@[EMAIL PROTECTED]
wrote:
>
>>On Fri, 27 Oct 2006 21:08:53 GMT, "Tom Lake" <tlake@[EMAIL PROTECTED]
>
>>wrote:
>>
>>>>>Look at my message of the 25th. I told you what to look for.
>>>>
>>>> Except he said that he was using run, not shell.
>>>
>>>That's irrelevant. When BASIC starts (either from a SHELL or RUN),
>>>it checks location &H50F. If that location is 2, BASIC assumes it's
>>>already being run in another copy of COMMAND.COM and refuses to
>>>run putting up the error, "Cannot execute as a Child of Basic".
>
>>You didn't say that, until now. :-)
>
>Yes, he did - on Wed 25th October
>
>I think there might be a News Group propogation problem and that both
>you and Seeker can not see his post.
--------
Where? The full 'Wed 25th October' post below only mentions SHELL,
not RUN.
<============>
> Of course, the section of the IBM manual that details the "Cannot
> execute as Chld of Basic" is very im****tant to help me locate the
> cause of the error.!
The error occurs because a process busy flag is set wrong in low
memory.
When you use SHELL, the flag is set to let BASIC know that it's
already
executing
a child process and it can only execute one of those at a time. If
you try
to execute
a SHELL from the SHELLed process, it checks the flag, sees it set and
refuses to
run, giving that error message. Of course, if some errant software
sets the
flag
without BASIC's knowledge, BASIC will assume it's a child process even
though
it's not. The trick, therefore, is to create a batch file that resets
the
flag then runs
BASIC. The magic location is &H50F. If that location has a 2 in it,
BASIC
won't run.
Tom Lake
<============>
--
ArarghMail610 at [drop the 'http://www.'
from ->] http://www.arargh.com
BCET Basic Compiler Page: http://www.arargh.com/basic/index.html
To reply by email, remove the garbage from the reply address.
|
