🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.sys.amiga.tech
1 messages
1 total messages Started by Kristian Nielsen Thu, 17 Jan 1991 18:06
1.3 Shell lockup
#8037
Author: Kristian Nielsen
Date: Thu, 17 Jan 1991 18:06
59 lines
3278 bytes
Using the Workbench1.3 (Commodore) shell, I have experienced a dreadfull
deadlock problem. It is extremely difficult to provoke (took me ages to find
a sequence of actions that would cause it), though it can be easily
reproduced. So, before spending still more time, I thought I would try to
get a response from people having the same problems.

The problem seems to be with the automatic execution of script files with
the s bit (typically in the S: directory, like SPat and DPat). To use this
facility to its full, you add a 'path s:' to your startup-sequence, and all
is fine - you can do 'spat type #?' and the like.

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

	s:GetDF1 DF0:
	^
	Note: Absolute path

makes the problem disappear (imagine finding a bug like that....)
The bug persisted even after disabling most of my startup-sequence, which
seems to rule out that third-party programs caused this. My system is an
A2000 with GVP3001 '30/'882/4Mb/80Mb HD (1 Mb chipmem). I have never had
this problem before installing the 68030, but then I didn't use scriptfiles
much before getting a harddisk.

So, if anyone has any comment to this, especially if this bug is allready
known to Commodore, I should very much like to hear it before trying to
reproduce the bug on a standard WorkBench disk and reporting it through the
proper channels. Also, while I could probably get rid of this problem by
changing to 2.0 (and I think I will, soon), I am getting rather curious as
to what's causing this. So in short, any comments will be welcomed.

	Looking forward to hear from you

	Kristian

==========================================================================
Kristian Nielsen                          |      ///   Only the AMIGA
Student at DIKU, University of Copenhagen |     ///
(Department of Computer Science)          | \\\///     makes it possible!
Denmark                                   |  \XX/
==========================================================================
-- 
==========================================================================
Kristian Nielsen                          |      ///   Only the AMIGA
Student at DIKU, University of Copenhagen |     ///
(Department of Computer Science)          | \\\///     makes it possible!
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads