🚀 go-pugleaf

In article <8811200108.AA29768@postgres.Berkeley.EDU> dillon@POSTGRES.BERKELEY.EDU (Matt Dillon) writes:
>	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.

I know the problems you are having and plan to fix them up for 1.4.
It's the use of the * as stderr that's biting us here,  I suspect.

However, the specific example

Execute(run date",0L,0L); works fine on my 1.3 machine.

(even if I run the program containing the Execute() statement)

ie 

run testprog

Possibly you are hitting a 16 bit/ 32bit defined constant problem ?
(or your compiler is opening * for you in some other manner)

The problem with the way the consoletask works with now is
understood.  Now all I have to figure out is a way to fix it properly.
If it weren't for DeviceProc() I'd be home free :-)

-- 
andy finkel		{uunet|rutgers|amiga}!cbmvax!andy
Commodore-Amiga, Inc.

"Possibly this is a new usage of the word 'compatible' with which
 I was previously unfamiliar"

Any expressed opinions are mine; but feel free to share.
I disclaim all responsibilities, all shapes, all sizes, all colors.