Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!batcomputer!rpi!pawl!shadow
From: shadow@pawl.rpi.edu (Deven T. Corzine)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Resident modules
Message-ID: <SHADOW.89Jun28193124@pawl.rpi.edu>
Date: 28 Jun 89 23:31:24 GMT
References: <0903.AA0903@recondo> <1380@rivm05.UUCP>
	<SHADOW.89Jun16180537@daniel.pawl.rpi.edu> <0935.AA0935@recondo>
	<7165@cbmvax.UUCP>
Sender: usenet@rpi.edu
Organization: Rensselaer Polytechnic Institute, Troy, NY
Lines: 32
In-reply-to: jesup@cbmvax.UUCP's message of 28 Jun 89 20:55:32 GMT

In article <7165@cbmvax.UUCP> jesup@cbmvax.UUCP (Randell Jesup) writes:
>In article <0935.AA0935@recondo> sirius@recondo.UUCP (Mike Stilson) writes:

>>My guess is that AmigaDOS is stopping WarmCapture from being run.  I
>>see several possibilitie.  One, when the resident module for DOS
>>executes, it does not return.  This seems unlikely, as it would keep
>>subsequent resident modules in the chain from initializing.
>>However, AmigaDOS harbors some serious brain-damage, so I wouldn't
>>put it past it.

[I was the actual author of the above paragraph; it had been misquoted]

>        Well, AmigaDOS does stop warmcapture from being called, by
>starting the initial CLI process, then doing a RemTask(0) from the
>DOS resident init code (running on exec's initial task).

Now, doesn't this seem a bit nasty to you?  What if, somehow, AmigaDOS
is NOT the last module initialized?  Is there any way to be sure of
this?  Hmm...

>        Don't count on this, folks: it may change in 1.4.

That's fine...  If you're going to stop WarmCapture from running
anyhow, forcing WarmCapture to point to a call to RemTask(0L) would be
a cleaner method, would it not?

Deven
--
shadow@[128.113.10.2]   <shadow@pawl.rpi.edu> Deven T. Corzine (518) 272-5847
shadow@[128.113.10.201] <shadow@acm.rpi.edu>  2346 15th St.    Pi-Rho America
deven@rpitsmts.bitnet   <userfxb6@rpitsmts>   Troy, NY 12180-2306  <<tionen>>
"Simple things should be simple and complex things should be possible." - A.K.