Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ll-xn!mit-eddie!bu-cs!halleys!ulowell!miner
From: miner@ulowell.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Making a Task a Process (was: Message ports in 68000)
Message-ID: <1253@ulowell.cs.ulowell.edu>
Date: Tue, 5-May-87 09:57:11 EDT
Article-I.D.: ulowell.1253
Posted: Tue May  5 09:57:11 1987
Date-Received: Wed, 6-May-87 06:45:00 EDT
References: <9663@decwrl.DEC.COM> <1251@ulowell.cs.ulowell.edu>
Reply-To: miner@ulowell.cs.ulowell.edu (Rich A Miner (.ram))
Organization: University of Lowell
Lines: 14

In article <1251@ulowell> page@ulowell.cs.ulowell.edu (Bob Page) writes:
>jmsynge@sqm.dec.com (James M Synge) wrote in article <9663@decwrl.DEC.COM>:
>>What I want (and am slowly working on) is a library of routines which a TASK
>>can call which enable it to do all disk related activity just like a PROCESS.
>
>...either Flip or AndyF posted to allow a TASK to become a PROCESS,

Even if this exists, I do not think it is what James is looking for.  A
process would use AmigaDOS, James wants to have DOS-like functionality 
from the well behaved world of an EXEC task.  

So long AmigaDOS, hello EXEC-DOS (written in C), I can dream also!

-- 
Rich Miner  ULowell-Cntr for Productivity  !ulowell!miner  617-452-5000x2693