dziegler@watdcsu.UUCP (Rudolf Shmitt) (11/27/85)
In order to allow people who do not know assembly to write interrupt code for a data aquisition system I am trying to set up a system whereby ( actual (slow) hadrware ) interrupts can be written in applesoft . It is important that this code use the same variables as the main program ( so don't suggest using the two address spaces of the IIe/c ) . I've tried a simulated CTRL-C with an onerr in the main program , but was foiled by the microsoft HAPPY-CODE ( not to mention needing a ramcard which is undesirable ) . My current version maintains a second zero page for the interrupt ( except for pointers to variable space ) , and the interrupt applesoft sits elsewhere in memory . I am having weird but persistent problems with this scheme and am looking for suggestions as to what they might be , or viable alternate methods .
dziegler@watdcsu.UUCP (Rudolf Shmitt) (11/27/85)
error : I forgot to mention that I do in fact also swap the stack and the processor registers ( stack pointer included ) . One weird bug is that if the interrupt prints a string out n characters long while the main program is waiting for input , then applesoft reads the current line as n characters long . Does anyone know of the existance of a second input /output pointer ,( perhaps in dos ) that might cause this .