Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!samsung!zaphod.mps.ohio-state.edu!function.mps.ohio-state.edu!vidynath From: vidynath@function.mps.ohio-state.edu (Vidhyanath K. Rao) Newsgroups: comp.sys.amiga.programmer Subject: Re: How do we change the scheduler? (Was Re: Multitasking at home...) Message-ID: <1991Jan22.205630.834@zaphod.mps.ohio-state.edu> Date: 22 Jan 91 20:56:30 GMT References: <1991Jan10.130741.11570@ux1.cso.uiuc.edu>> <1991Jan17.204425.8037@ncsuvx.ncsu.edu> Sender: news@zaphod.mps.ohio-state.edu Organization: Me? Organized? Lines: 20 Nntp-Posting-Host: function.mps.ohio-state.edu In article <1991Jan17.204425.8037@ncsuvx.ncsu.edu> kdarling@hobbes.ncsu.edu (Kevin Darling) writes: [deleted material on how to age tasks] >The only difficulty is that the task structure size seems to be hardcoded, >so adding a variable might be tough...or does Exec copy the task structure >elsewhere on AddTask? kevin The taks structure size is hardcoded because of the way the AmigaDOS process structure is defined. Otherwise, I don't think that the task structure size is fixed for eternity. Task structure [upto v1.3 at least] has a "free" variable: There is something called UserData. If you just want to experiment, you can make it point at an extension area. But if you want to do this for every one, you will need to make sure that no one else uses it. -- Vidhyanth Rao It is the man, not the method, that solves function.mps.ohio-state.edu the problem. - Henri Poincare (614)-366-9341 [as paraphrased by E. T. Bell]