Tom Corcoran
To: [EMAIL PROTECTED]
Sent: Thursday, August 07, 2003
06:03
Subject: [m_list_b] [DQSD-Users] RE:
Clock updating bug
Thanks Shawn,
>Maybe. There's really no telling. It could be
working correctly, and>the jscript parser might have incorrectly
Thanks Shawn,
>Maybe. There's really no telling. It could be
working correctly, and>the jscript parser might have incorrectly parsed
the>"clockupdate=1000;" line in your prefs file. Try deleting the line
and>retyping the characters explicitly, just to make sure they're
accurate.
Unfortun
Hey Alec,
Great eye, thank you man :-)
> From: "Alec Burgess" <[EMAIL PROTECTED]>> I've got no idea about the details of what you're trying,
but I'll bet => the ":08" means August:-)> Somewhere you've
probably got a date_time spec that says HH:MM that => should be HH:mm or
vice-versa.> Re
Hi Tom,
> Thanks for the post Shawn. I tried this and my
> system ground to a halt the cpu being totally
> tied up with the updating I guess. Which sounds
> like XP is not treating it incorrectly?
Maybe. There's really no telling. It could be working correctly, and
the jscript parser might have i
> From: "Shawn K. Hall" <[EMAIL PROTECTED]>>
> I have reported the problem with my clock not updating> > before
but have never got it resolved.> > clockupdate=1000;> >
IIRC this is due to XP treating the milliseconds (1000 = 1 second)>
incorrectly as seconds (1000 = 16 minutes, 40 seconds).
