[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Recommendations on a clock for an enhanced //e
- Subject: Re: Recommendations on a clock for an enhanced //e
- From: mkelsey@eecs.wsu.edu (Michael Kelsey - Systems Staff)
- Date: 1998/03/06
- Newsgroups: comp.sys.apple2
- Organization: Washington State University
- References: <6dlo8o$pm3$1@leopard.it.wsu.edu> <6dmq3b$mt0@catapult.gatech.edu>
In article <6dmq3b$mt0@catapult.gatech.edu>,
gt5460c@acmez.gatech.edu (Martin Tuck) writes:
> mkelsey@spam.eecs.wsu.edu wrote:
>: It looks like my ThunderClock Plus has lost the ability to store time.
>: I had held onto it knowing that interrupts could be programmed and hoped
>: at one point to begin tweaking with a multitasking kernel, but now all
>: that fun has ended (sigh)
>
> Hey, now that sounds like a neat idea. I have a question though.
> Do you really need to store the time to implement your interrupt queued
> multasking kernel? Wouldn't it just matter that when the thing had power
> it could keep track of elapsing time (even if the time/date stored was
> wrong)?
>
> -Martin Tuck
Martin,
I just wanted it for the selectable interrupt rate. I believe the
ThunderClock Plus had three interrupt rates, 60, 200, 1000, or something
like that. At that rate I could ensure every task received an equal time-
slice. Awhile back somebody wrote a "type-ahead" buffer for ProDOS using
the interrupt features of a mouse card. The Apple II Mouse card is only
selectable at 60Hz, I believe.
--
-/\/\ichael-
[-][-]-[-][-]-[-][-]-[-][-]-[-][-]-[-][-][-][-]-[-][-]--[-][-][-][-]
[] Michael Kelsey : mkelsey@eecs.wsu.edu : kelsey@mail.wsu.edu []
[] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . []
[] Washington State University []
[] Network Systems Asst., Staff Comp. Systems Tech, Staff []
[] Extended University Services, School of Electrical Engi- []
[] neering & Computer Science, []
[-][-]-[-][-]-[-][-]-[-][-]-[-][-]-[-][-][-][-]-[-][-]--[-][-][-][-]