Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!psuvax1!rutgers!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.sys.amiga.programmer Subject: Re: Copper mystery Message-ID: <20197@cbmvax.commodore.com> Date: 29 Mar 91 09:16:55 GMT References: <1991Mar27.211732.2436@kth.se> Reply-To: jesup@cbmvax.commodore.com (Randell Jesup) Organization: Commodore, West Chester, PA Lines: 15 >>Question number two: >>The program exits without restoring multitasking, still multitasking starts >>again when the program ends. Why? Two things happen: if you Wait() while disabled, exec re-enables interrupts for you. Second, Disable() is remembered as part of your task. During task removal, exec re-enables interrupts, removes Forbid()s, etc (since they're stored in the task structure, this is almost automatic). -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com BIX: rjesup Thus spake the Master Ninjei: "To program a million-line operating system is easy, to change a man's temperament is more difficult." (From "The Zen of Programming") ;-)