At 2004-05-22T231932+0000, Caleb Sawtell wrote: ^^^^^^^^^^^^^^^^^^^^^^ > Ok is it fixed now??? *sigh*
Nope. It looks like you've changed the system clock rather than fix the
problem. Instead of fixing the problem, you've made it worse.
Before, your system clock was correct, but your timezone was wrong.
Now, your system clock is wrong and your timezone are wrong.
Try following Nick's suggestions for troubleshooting the problem.
Cheers,
-mjg
--
Matthew Gregan |/
/| [EMAIL PROTECTED]
