I only worked with Windows 95 and later. If you mean Windows 3.x then you might be right. Now that I think about it, since Windows 3.x starts from DOS it must use local time like DOS.
I think the reason for the popup was due to the problem with DOS programs using local time, by which I mean programs run from the DOS box within Windows. The problem still exists in the latest versions of Windows, but they assume that you won't be using DOS for critical functions. -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Rob van der Heij Sent: Friday, April 28, 2006 3:40 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Problem with RMFPMS and the recent time change On 4/28/06, Fargusson.Alan <[EMAIL PROTECTED]> wrote: > This isn't quite right. Windows does use GMT (it might be UTC, but I think > it is GMT). The confusion comes from two things: Some Windows users don't > set the timezone right, and this makes the hardware clock wrong. Some RTCs > are broken, especially old 386 based systems. The trick of getting the local > time from the RTC is to work around broken RTCs. So that's more recent windows then? I am pretty sure Windows would set the RTC to local time, even DST. This was the reason for the pop-up window after the time change because in dual-boot you never knew whether another OS already had changed the RTC to DST. -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
