bazyar@ernie (Jawaid Bazyar) (04/19/91)
Myself and a collaborator (DT) have been playing with some heavy-duty interrupt routines. Basically what we have is a task switcher driven by the heartbeat manager. We stick three short programs into a queue, and one runs until the next heartbeat comes, when the next one in line is executed. This part works great. Our grief comes when we try to access the CDA Control Panel. Horrible things happen (usually dumps into the monitor at the same location time after time), and the process stops running (actually, the process 'becomes' the monitor and the monitor and the other two routines are running). The strange thing is that going into the Control Panel causes no problems when only one process is set up to run. We're using the new GetInterruptState and SetInterruptState calls in MiscTools (they work marvelously, BTW, once you play a few tricks to set yourself up right). So, I'm looking for information concerning the following: stack/dp/memory usage of the control panel (how much, where, when) interrupt 'friendliness' of the control panel (is it an interrupt routine?) (the processes, BTW, are just short 5 instruction programs that cycle through numbers on the screen- they use no stack or direct page space). One of these days I'm just going to have to pay the $300 developer fee. -- Jawaid Bazyar | "Twenty seven faces- with their eyes turned to Senior/Computer Engineering | the sky. I have got a camera, and an airtight bazyar@cs.uiuc.edu | alibi.." Apple II Forever! | I need a job... Be priviliged to pay me! :-)