<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.5730.11" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2><FONT face="Times New Roman" size=3>>The
timezone only tells the system with what offset to show<BR>>the time when
asked for "local time".<BR><BR>>Sadly some operating systems have this
strange concept that changing a<BR>>time zone means changing the system clock
itself. This makes it a huge<BR>>change indeed.</FONT><BR></FONT></DIV>
<DIV><FONT face=Arial size=2>Agreed. The firmware I design works the same
way--everything internal is in UTC. Any application that must deal with
multiple time zones by virtue of market distribution or because it shares time
over a network, etc. should use UTC internally and only translate to local
time. Using a scheme such as *nix does of an integer rather than broken
down field makes the translation trivial. The hard part is deciding how to
determine the translation, whether to use hard coded rules, intelligent
observation or manual setup.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Wilton</FONT></DIV>
<DIV><FONT face=Arial size=2> </DIV></FONT></BODY></HTML>