Mike, I'm not sure that is still the way it works.
Windows systems may still keep time in localtime, but they have mechanisms to compute UTC or any other localtime from that via the registry. TZEDIT.exe is your friend. Cheers, Ken -----Original Message----- From: On Behalf Of HENDERSON MIKE, MR "Why do people [with NT systems] change the system time to deal with daylight savings changes?" Because that's the way MS-DOS did it. On Unix systems, the hardware clock runs in UTC, and the TZ variable is used to determine the difference between UTC and local time (including allowing for daylight Saving if appropriate), and local time is output by the various utilities. On MS-DOS systems, and their 'Windows' heirs and successors, the hardware clock is the direct source of system time, so it runs local time. The new-fangled (Windows95?) automatic time zone management simply writes a new value into the hardware clock on the motherboard on 'flip-over' from summer to winter time. As I understand it, even Vista and Windows Server 2008 still work that way. Horrible. [Digression: I wonder how a VM-ed Windows environment copes with that? Can you have different VMs in different Time Zones on the same real host? Can you use VMs to 'time travel', by setting the date/time on one VM to a completely different value to another and/or to the real time on the host?] ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
