Path: utzoo!censor!geac!torsqnt!hybrid!scifi!bywater!uunet!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.sys.amiga.programmer Subject: Re: How do we change the scheduler? Message-ID: <17593@cbmvax.commodore.com> Date: 15 Jan 91 08:02:19 GMT References: <1991Jan10.130741.11570@ux1.cso.uiuc.edu> <1991Jan12.175908.6479@Latour.Sandelman.OCUnix.On.Ca> Reply-To: jesup@cbmvax.commodore.com (Randell Jesup) Organization: Commodore, West Chester, PA Lines: 33 In article dillon@overload.Berkeley.CA.US (Matthew Dillon) writes: >In article <1991Jan12.175908.6479@Latour.Sandelman.OCUnix.On.Ca> mcr@Latour.Sandelman.OCUnix.On.Ca (Michael Richardson) writes: >> >> Does 2.0 make sending DOS packets, and doing asynch dos I/O any >>easier? Can one abort a DOS request? Thought not... > > I do not think it made it, though it is simple to do. The basic > problem is that the multi-packets-pending problem was never fixed. > DOS still expects the packet is sends synchronously to be the FIRST > one returned to the message port. Thus, you cannot have multiple > packets pending because only one of them will be 'first' replying > back. You ought to read the autodocs/notes more closely, Matt. ;-) There are calls in 2.0 Dos for sending packets asynchronously, with a user-specified replyport. You must service the replyport yourself, and if it's your process message port, you must not do any synchronous I/O until you WaitPkt(). There's an entry for AbortPkt, but we couldn't figure out any good method to do it in the timeframe available (it'll require rewrites of most of the handlers, some may be major). 2.0 also has synchronous packet calls (DoPkt), and calls for allocating and inititalizing packets (AllocDosObject). As I said, it's in there... :-) -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com BIX: rjesup The compiler runs Like a swift-flowing river I wait in silence. (From "The Zen of Programming") ;-)