Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uwm.edu!psuvax1!rutgers!cbmvax!andy
From: andy@cbmvax.commodore.com (Andy Finkel)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: 1.3 Shell DeadLock
Keywords: bug Workbench1.3 Shell
Message-ID: <17761@cbmvax.commodore.com>
Date: 17 Jan 91 22:50:22 GMT
References: <1991Jan17.182709.23562@odin.diku.dk>
Reply-To: andy@cbmvax.commodore.com (Andy Finkel)
Organization: Commodore, West Chester, PA
Lines: 36

In article <1991Jan17.182709.23562@odin.diku.dk> bombadil@diku.dk (Kristian Nielsen) writes:
>However, my problem is that sometimes the shell will deadlock immediately
>after typing return on a command, but before loading the command from disk.
>Sometimes the entire screen will tremble for a split second before the crash.
>The deadlock semms to have nothing to do with the command that locks up, or
>the previous one. What happens is that a command sequence like this:
>
>	GetDF1 DF0:		;scriptfile, basically diskcopy df0: rad:
>	cd ...
>	assign...
>	copy ...
>	run ...
>
>will cause the deadlock, while changing the first line to

I'm not quite sure what you mean by deadlock ... you you mean the
machine hangs and the mouse doesn't move ?  Do you mean crash, ie GURU ?
Do you mean get a software error task held ?

>
>	s:GetDF1 DF0:

My first thought is you have something else called GetDF1 somewhere.
Do a which GetDF1 and see what turns up.


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

"God was able to create the world in only seven days because there
 was no installed base to consider."

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