Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!decwrl!ucbvax!POSTGRES.BERKELEY.EDU!dillon
From: dillon@POSTGRES.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga.tech
Subject: Problem trying to get RUN to work from processes w/no consoletask.
Message-ID: <8811200108.AA29768@postgres.Berkeley.EDU>
Date: 20 Nov 88 01:08:47 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 42


		NOTE NOTE:  OS1.3 C:RUN, not the 1.2 RUN

	This is the problem.  To avoid referencing "*" by Execute() itself,
I have to specify a nil: file handle for the second and third arguments of 
Execute():

	1> run <nil: >nil: program

Where "program" contains an Execute() like this:

	Execute("some-command", NilFH, NilFH);

Unfortunetly, nothing can be a 'run', like this without crashing
the machine:

	Execute("run list", NilFH, NilFH);

However, it CAN be a run if you do this:

	Execute("run <nil: >nil: list", NilFH, NilFH);

			or

	Execute("run <nil: >nil: list >ram:x", NilFH, NilFH);

	It appears that if pr_ConsoleTask is NULL, the ONLY valid way to
do a 'run' via Execute is if you use the above construction.  Attempts to
replace pr_ConsoleTask with a port and simulate a dos device to handle the
supposed reference to "*" that run makes if you do otherwise have failed...
the port is never accessed.

	Anybody who's a *real* DOS guru (i.e. C-A) no how I can do:

	Execute("run Date", NULL, NULL);

	Without crashing the machine?  Note that here I do not specify the
nil: file handles.  I have not confirmed this, but I think by NOT using
the nil: file handles the Execute() also attempts to access "*" for a 
brief period, causing the machine to become unstable.

						-Matt