|
Hi Diane,
Sorry it took me so long to get back to you but I got involved in working on the Accu-Basic compiler for V2 and suddenly it's getting dark... The ISR message contains 2 pieces of information, the interrupt vector number and the memory address at which the processor was interrupted. In this case ISR19 is for an I/O trap which means that the I/O trap was enabled on the processor and then it tried to do some I/O, usually a write to the LCD. The address C000:6075 may or may not have meaning depending on what happened and is relevant only to a particular firmware release. In this case all I can tell is that the processor was executing something on the expansion ROM. How did this happen? Good question. I sometimes see this when I'm developing and it usually means that my program has modified some memory that causes the I/O trap flag to be set and then I get this on the next LCD update. In this case it's usually very reproducable and I can track it down and fix it. What happened in your case is probably a random event (I like to blame the cosmic rays) unless you see it or other ISRs a few more times. For ISRs, I always recommend that you record the message, the serial number, the firmware release, and what the unit was doing when it happened. If one machine gets multiple ISRs, it has a problem and the details can help Ian fix it. If you get similar ISRs on multiple machines, it could be a firmware bug and the details can help me to fix it. The only real danger with ISRs is if they happen when the memory card is being updated since this can corrupt the memory card -- you'll know when you cycle the power. I hope this helps. Guy Ian Piper wrote: Diane: I don't know. I will have to forward this to Guy Lancaster. Ian |