It's not going to happen the way you want. TMR0 even with the prescaler attached will not be able to give you 65 seconds. The same applies for TMR1 and TMR2. Futher, the obvious clock souces for the Timers are also halted during sleep.

But there's heaps of alternate solutions... here's one to get you thinking...

To achieve Low-Power consumption for the majority of the time, use NAP (example NAP 4 which is approximately 288mS), poll the keyboard to see if a button has been pressed, increment a timeout counter and go take another Nap...

TimeOut var Byte
.. ..

' Nap Entry Point
NapStart:
TimeOut=0
' Main Nap Loop
NapLoop:
NAP 4 ' Suspend reality for 288mS
If PortB.0=0 then goto KeyPressed
TimeOut=TimeOut+1
If TimeOut < 225 then Goto NapLoop
' Process 65 Second Timeout here

In this example, every approx quarter of a second, you poll the keyboard and check for key depression, and if less than 65 seconds have elapsed (0.288mS x 225 loop counts) then you simply just Nap again. This way, about 99.9% of the time you'll be asleep in low-power mode.

If polling the keyboard every 288mS is insufficient, then go to NAP 3, but you'll have to increase the loop-count for the 65 second timeout appropriately (if you do this then you'll have to make the TimeOut variable a WORD rather than a BYTE).

Melanie