Brian,
This reminds me of a problem I had with one particular box (I think the machine was a Compaq Prolinea) where the Windows 95 time display tended to run slow. As soon as some user went into the Windows time settings and brought the clock time forward, the BIOS clock and the "Windows clock" went out of synch.

The solution on that box was to reset the Windows time and then reboot the machine. The BIOS clock and the Windows clock would then remain in synch until next time someone reset the Windows clock!

It was some time ago but I seem to recall that we felt we got around the problem by replacing the rom bios battery regularly to avoid the problem of the clock slowing down!

Regards,
Helen

At 11:17 AM 06-08-01 +0800, you wrote:

>Hi,
>
>I have a very strange problem, that has appeared on only 1 of many sites.
>
>When I run this SQL:
>
>select cast ('now' as timestamp) from rdb$database;
>
>the time returned is always the current time + 30 minutes.
>
>IOW, if the time is 11:00 then the sql will return 11:30.
>
>The problem occurs whichever workstation runs the SQL statement. Even if I
>run the statement from WISQL running on the server computer I still get the
>same result.
>
>I am running NT 4 and Borland IB 6.01. None of my other sites exhibit this
>problem.
>
>The system has no daylight savings enabled.
>
>What could be causing this?
>
>TIA,
>
>Brian
>
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

All for Open and Open for All
InterBase Developer Initiative · http://www.interbase2000.org
_______________________________________________________