We are having the same problem with one of our servers. According to
Allaire, it is a problem with the Visual C++ that was used to create Cold
Fusion. It doesn't recognize April 1st as the first day of Daylight
Savings. It recognizes April 8th. This means that it should correct itself
on Sunday. The other fix is to upgrade to 4.5.1 because the problem has
been fixed since that version.
http://forums.allaire.com/DevConf/Thread.cfm?&&Message_ID=691270&_#Message69
1270
http://forums.allaire.com/DevConf/Thread.cfm?&&Message_ID=690790&_#Message69
0790
-----Original Message-----
From: Scott Becker [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 06, 2001 7:08 AM
To: CF-Talk
Subject: CF Time off by an hour?
Our Windows NT 4 Server, running Cold Fusion 4.01 switched over with
daylight savings time,
yet Cold Fusion seems to still be an hour off.. The system time itself is
correct, but running
a script which outputs #now()# reports an hour behind. Has anybody else
encountered this
problem and have a fix for it? We've rebooted the machine, as well as
stopped and started the
Cold Fusion services, but it doesn't seem to have any effect...
Thanks,
Scott Becker
Web Developer : ConnectWise, Inc.
www.ConnectWise.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
