I recall something like this coming up on the Cygwin list some time
ago, but I forget the details. What version of cygwin1.dll are you
using, and if not the latest, have you tried the latest?
Regards,
David
On 16 Jul 02, Jaap-Henk Hoepman writes:
Ooops... sorry.... just realised the native windows version ran on another
laptop, so it could well be a bios problem. disregard what i wrote.
Jaap-Henk
On 16 Jul 2002 07:12:37 +0200 Jaap-Henk Hoepman <hoepman(a)cs.utwente.nl> writes:
> Dear Stephen,
>
> You're correct in assuming that (current-time-string) gives the correct result
> always. However, i've never seen this behaviour with the native windows port of
> XEmacs, only with the cygwin version.... so why does only the windows version
> do-the-right-thing?
>
> Jaap-Henk
>
> On Fri, 5 Jul 2002 05:01:36 +0200 "Stephen J. Turnbull"
<stephen(a)xemacs.org> writes:
> > >>>>> "Jaap-Henk" == Jaap-Henk Hoepman
<hoepman(a)cs.utwente.nl> writes:
> >
> > Jaap-Henk> After a suspend and the next resume, the value of
> > Jaap-Henk> (decode-time (current-time)) has increased by more than
> > Jaap-Henk> a day (see eg header of this mail; that's how i
> > Jaap-Henk> discovered this in the first place)! This happens
> > Jaap-Henk> independent of the length of the suspended state,
> > Jaap-Henk> although it seems that the longer the system is
> > Jaap-Henk> suspended, the larger the time increase
> > Jaap-Henk> becomes. Needless to say both windows and cygwin report
> > Jaap-Henk> the correct time.