Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-lcc!ames!ucbcad!ucbvax!decvax!decwrl!sqm.dec.com!jmsynge From: jmsynge@sqm.dec.com (James M Synge, DTN 381-1545) Newsgroups: comp.sys.amiga Subject: Re: Message ports in 68000 Message-ID: <9663@decwrl.DEC.COM> Date: Sun, 3-May-87 17:23:20 EDT Article-I.D.: decwrl.9663 Posted: Sun May 3 17:23:20 1987 Date-Received: Sun, 3-May-87 23:35:27 EDT Sender: daemon@decwrl.DEC.COM Organization: Digital Equipment Corporation Lines: 27 COGSCI.BERKELEY.EDU!bryce writes: > ... each process has an associated pre-allocated message port that > can be had quite simply: > - > - move.l 4,a6 > - suba.l a1,a1 > - jsr _LVOFindTask(a6) > - add.l #pr_MsgPort,d0 > - > Now is this being clever, or will problems crop up later? The only caution I would add is that you must be SURE that you are being executed in an AmigaDOS PROCESS, not just a TASK. 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. James Synge USENET: {decvax, ucbvax, allegra}!decwrl!sqm.dec.com!jmsynge ARPAnet: jmsynge%sqm.DEC@decwrl.DEC.COM #include "Ken Olsen can speak for Digital, not me!"