Re: A86:Multitasking
[Prev][Next][Index][Thread]
Re: A86:Multitasking
Actually, while we're at it, why don't we just save the entire memory of
the calculator, since you never know where those whacky programmers are
going to stash sensitive data, and store it, say, in some imaginary
memory chip hovering a couple inches above the calc? :)
I really don't think any kind of "multitasking" (quotes for obvious
reasons) on the 86 would be practical, although perhaps feasible.
Feasible as in it would function. Until you put a game on it that
doesn't realize that it is being run in a multitasking environment.
Unfortunately, I'm afraid that encompasses every game written for the
86. The shell would have to know exactly which memory areas outside of
the asm exec space each game uses, which is an arbitrary choice entirely
up to whoever programmed the game. And multitasking a utility program
would be out of the question; that sounds like an excellent way of
trashing memory.
Cassady Roop
Kirk Meyer wrote:
>
> That wouldn't work for a lot more than programs with their own interrupt
> handlers... that wouldn't work for anything that uses temporary space...
> Unless you save a copy of page 1, the text shadows, graph screen, the ENTIRE
> _asm_exec_ram (in case they use it for temporary data) and who knows what
> else for each program (probably you would need to save ~27kb for each
> program you are trying to multitask...)
>
> -----Original Message-----
> From: owner-assembly-86@lists.ticalc.org
> [mailto:owner-assembly-86@lists.ticalc.org]On Behalf Of
> rabidcow@juno.com
> Sent: Tuesday, June 20, 2000 1:41 PM
> To: assembly-86@lists.ticalc.org
> Subject: Re: A86:Multitasking
>
> you could install an im 1 or alt_int interrupt that would switch tasks,
> but you'd need a separate stack & asm_exec_ram for each program running.
> alos, that wouldn't work for programs that inatalled their own interrupt
> handlers, such as grayscale routines.
>
> -josh
References: