On 9/14/05, Jinx wrote: >=20 > > 0x00 crossing went undetected ) as decision or better with T0IF flag. > > > > DELAY1S > > movlw -const > > movwf TMR0 > > bcf INTCON,T0IF > > > > btfss INTCON,T0IF > > goto $-1 >=20 > That would be my preferred way too Dmitriy. I did mention to > Sean that T0IF could be polled. It has the advantage of the > rollover being recorded if the code is busy elsewhere at the > time of the rollover. In Sean's case he has such a slow Fosc, > very long TMR0 period and s/w that is doing nothing else that > there is ample time and opportunity to poll T0IF. As you say, > in this example it's simpler to load a "-ve" count-up-to-00 value > into TMR0 and then examine T0IF >=20 Wouldn't it take multiple overflows to count to a second if I switch my OSC= =20 up to 8Mhz? Wouldn't that involve me using some memory location as a place= =20 to count the number of overflows? Actually, the only reason my OSC is set s= o=20 low, is because this is the easy'est way for me to count seconds. I welcome= =20 any alternative that works at 8Mhz OSC setting with a 1x prescaler setting. Sean. -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist