From: Digest To: "OS/2GenAu Digest" Date: Wed, 9 Apr 2008 00:01:06 EST-10EDT,10,1,0,7200,4,1,0,7200,3600 Subject: [os2genau_digest] No. 1638 Reply-To: X-List-Unsubscribe: www.os2site.com/list/ ************************************************** Tuesday 08 April 2008 Number 1638 ************************************************** Subjects for today 1 Re: Time settings : Mike O'Connor 2 Re: Time settings : Peter A Jenkins 3 Re: Time settings : zermatt at attglobal dot net" 4 Re: Time settings : Mike O'Connor 5 Re: Time settings : zermatt at attglobal dot net" 6 Re: Time settings : Peter Moylan 7 Re: Time settings : Peter A Jenkins 8 Re: Time settings : Peter A Jenkins 9 Re: Time settings : Ed Durrant **= Email 1 ==========================** Date: Tue, 08 Apr 2008 01:24:34 +1000 From: Mike O'Connor Subject: Re: Time settings Peter A Jenkins wrote: > Running ecs RC4 normal install, in SA daylight saving has finished > but my clock has not reset, showing 1 hour ahead, how do I reset to > normal time please ? > TIA > Peter at Port Pirie > Hi Peter, FWIW what does your config.sys have for the line "SET TZ = ...."? Regards, Mike ---------------------------------------------------------------------------------- **= Email 2 ==========================** Date: Tue, 08 Apr 2008 08:09:12 +0930 From: Peter A Jenkins Subject: Re: Time settings Mike O'Connor wrote: > FWIW what does your config.sys have for the line "SET TZ = ...."? > > Regards, > Mike > TZ=CST-9:30CDT,10,-1,0,7200,3,-1,0,7200,3600 This is the first time I have had any problem with DST in all the releases of ecs. Peter -- May your moccasins leave tracks, on many mounds of worth, and walk with chiefs of every tribe who live in peace on earth. Peter A Jenkins (AKA grandad or pj) Port Pirie South Australia PROUD USER OF A VIRUS & MALWARE FREE OPERATING SYSTEM Serenity Systems "Ecomstation" ver 2.0 RC4, the successor to IBM's os/2 ---------------------------------------------------------------------------------- **= Email 3 ==========================** Date: Mon, 7 Apr 2008 18:42:24 -0400 From: "zermatt at attglobal dot net" Subject: Re: Time settings TEST. Please ignore. Thx. Original Message: ----------------- From: Peter A Jenkins peter.a.jenkins at internode.on dot net Date: Tue, 08 Apr 2008 08:09:12 +0930 To: os2genau at os2 dot org dot au Subject: Re: Time settings Mike O'Connor wrote: > FWIW what does your config.sys have for the line "SET TZ = ...."? > > Regards, > Mike > TZ=CST-9:30CDT,10,-1,0,7200,3,-1,0,7200,3600 This is the first time I have had any problem with DST in all the releases of ecs. Peter -- May your moccasins leave tracks, on many mounds of worth, and walk with chiefs of every tribe who live in peace on earth. Peter A Jenkins (AKA grandad or pj) Port Pirie South Australia PROUD USER OF A VIRUS & MALWARE FREE OPERATING SYSTEM Serenity Systems "Ecomstation" ver 2.0 RC4, the successor to IBM's os/2 ---------------------------------------------------------------------------- ------ -------------------------------------------------------------------- myhosting dot com - Premium Microsoft® Windows® and Linux web and application hosting - http://link.myhosting dot com/myhosting ---------------------------------------------------------------------------------- **= Email 4 ==========================** Date: Tue, 08 Apr 2008 09:31:23 +1000 From: Mike O'Connor Subject: Re: Time settings Peter A Jenkins wrote: > Mike O'Connor wrote: > >> FWIW what does your config.sys have for the line "SET TZ = ...."? >> >> Regards, >> Mike > TZ=CST-9:30CDT,10,-1,0,7200,3,-1,0,7200,3600 > > This is the first time I have had any problem with DST in all the > releases of ecs. > Peter Hi Peter, According to that your clock would have ended DST a week earlier than scheduled, on the last Sunday in March at 0200 CST (0300CDT), but I believe the period was extended to the first Sunday in April , so the string should have read ..... 7200,4,1,0 ..... So you've probably over-corrected it already from when it adjusted the clock at end of March! :-) Regards, Mike ---------------------------------------------------------------------------------- **= Email 5 ==========================** Date: Mon, 7 Apr 2008 20:17:59 -0400 From: "zermatt at attglobal dot net" Subject: Re: Time settings Test,please ignore Original Message: ----------------- From: Mike O'Connor mikeoc at internode.on dot net Date: Tue, 08 Apr 2008 09:31:23 +1000 To: os2genau at os2 dot org dot au Subject: Re: Time settings Peter A Jenkins wrote: > Mike O'Connor wrote: > >> FWIW what does your config.sys have for the line "SET TZ = ...."? >> >> Regards, >> Mike > TZ=CST-9:30CDT,10,-1,0,7200,3,-1,0,7200,3600 > > This is the first time I have had any problem with DST in all the > releases of ecs. > Peter Hi Peter, According to that your clock would have ended DST a week earlier than scheduled, on the last Sunday in March at 0200 CST (0300CDT), but I believe the period was extended to the first Sunday in April , so the string should have read ..... 7200,4,1,0 ..... So you've probably over-corrected it already from when it adjusted the clock at end of March! :-) Regards, Mike ---------------------------------------------------------------------------- ------ -------------------------------------------------------------------- myhosting dot com - Premium Microsoft® Windows® and Linux web and application hosting - http://link.myhosting dot com/myhosting ---------------------------------------------------------------------------------- **= Email 6 ==========================** Date: Tue, 08 Apr 2008 11:12:26 +1000 From: Peter Moylan Subject: Re: Time settings Mike O'Connor wrote: > Peter A Jenkins wrote: >> Mike O'Connor wrote: >> >>> FWIW what does your config.sys have for the line "SET TZ = ...."? >>> >>> Regards, >>> Mike >> TZ=CST-9:30CDT,10,-1,0,7200,3,-1,0,7200,3600 >> >> This is the first time I have had any problem with DST in all the >> releases of ecs. >> Peter > Hi Peter, > > According to that your clock would have ended DST a week earlier than > scheduled, on the last Sunday in March at 0200 CST (0300CDT), but I > believe the period was extended to the first Sunday in April , so the > string should have read ..... 7200,4,1,0 ..... > So you've probably over-corrected it already from when it adjusted the > clock at end of March! :-) Hmm, my recollection is that South Australian DST *did* finish at the end of March, and that it was only Victoria and NSW that extended it into April. I could be wrong there, though. In any case, the TZ string doesn't actually do anything unless you have software that reads it. Time868 (a clock synchroniser) does read it. eCSClock doesn't read it, preferring to use its own internal file that holds a whole lot of TZ settings. (Although eCSClock does have the option of updating the TZ in CONFIG.SYS, for the benefit of any applications that use it.) The new PMMail probably uses it, although I haven't checked it. The original PMMail didn't use it, but instead had its own internal time zone software. My own freeware application TZset (on my web site, below) uses it. Some applications ported from Unix would use it, although for most applications the time zone is irrelevant. The essential point here is that the TZ environment string in CONFIG.SYS is for the benefit of applications, and is not used by the operating system at all. (Unless there's a change in the new eCS that I don't know about; but I doubt it, because the people doing the new eCS don't have access to the relevant source code.) Each application is supposed to do its own time calculations. That's a pretty stupid system - it would be more logical for a single part of the OS to maintain the local time, allowing any application to do an API call to ask for the current time - but there's a historical reason [1] why this wasn't done. The implementer of the original OS/2 "System Clock" object never got around to adding a time zone page to the clock settings, or alternatively to reading the TZ string. There's actually a time zone field in OS/2's internal record of the current time, but nothing in the operating system reads or writes that field, so it stays untouched unless someone writes a program to modify it. (That's why I wrote TZset, when I discovered that Weasel was getting a result of "time zone not set" when it tried to look it up.) [1] Actually, two historical reasons. The other reason is that Unix also does it the stupid way, where every application has to repeat a redundant calculation. The existence of a standard library function to read the TZ string and do this calculation hides this inefficiency from the applications programmer, therefore there has been no real pressure to fix this ancient design fault. What happened, I believe - although I have no real evidence for this - is that the "System Clock" object was still being worked on at the time that IBM started to drop support for OS/2, so the job was never finished. And the code was never released, so the only viable workaround was to dump the original system clock and develop a new one from scratch. The end solution was eCSClock. It was a good solution, but unfortunately the developer of eCSClock has stopped supporting it, and (as far as I know) nobody else has the source code. That's a flaw in Serenity's approach of getting work done by external people. The only good solution would be to get someone else to start the job again; but there's no guarantee that that person wouldn't also drop support a year or two down the track. Note that the option of copying eCSClock from an older version of eCS still exists. I don't know how legal that is, but I doubt that anyone is likely to check. -- Peter Moylan http://www.pmoylan dot org peter at pmoylan dot org ---------------------------------------------------------------------------------- **= Email 7 ==========================** Date: Tue, 08 Apr 2008 11:17:11 +0930 From: Peter A Jenkins Subject: Re: Time settings Mike O'Connor wrote: > Peter A Jenkins wrote: >> Mike O'Connor wrote: >> >>> FWIW what does your config.sys have for the line "SET TZ = ...."? >>> >>> Regards, >>> Mike >> TZ=CST-9:30CDT,10,-1,0,7200,3,-1,0,7200,3600 >> >> This is the first time I have had any problem with DST in all the >> releases of ecs. >> Peter > Hi Peter, > > According to that your clock would have ended DST a week earlier than > scheduled, on the last Sunday in March at 0200 CST (0300CDT), No, it did not change but I > believe the period was extended to the first Sunday in April , Yes so the > string should have read ..... 7200,4,1,0 ..... > So you've probably over-corrected it already from when it adjusted the > clock at end of March! :-) No it still reads the right time after I reset the time in the properties page of 'system clock" > > Regards, > Mike Peter at Port Pirie PS; there are moves afoot not to extend next year, will have to wait and see. -- May your moccasins leave tracks, on many mounds of worth, and walk with chiefs of every tribe who live in peace on earth. Peter A Jenkins (AKA grandad or pj) Port Pirie South Australia PROUD USER OF A VIRUS & MALWARE FREE OPERATING SYSTEM Serenity Systems "Ecomstation" ver 2.0 RC4, the successor to IBM's os/2 ---------------------------------------------------------------------------------- **= Email 8 ==========================** Date: Tue, 08 Apr 2008 11:19:16 +0930 From: Peter A Jenkins Subject: Re: Time settings Peter Moylan wrote: > > Hmm, my recollection is that South Australian DST *did* finish at the > end of March, No, same as Vic & NSW Peter at Port Pirie -- May your moccasins leave tracks, on many mounds of worth, and walk with chiefs of every tribe who live in peace on earth. Peter A Jenkins (AKA grandad or pj) Port Pirie South Australia PROUD USER OF A VIRUS & MALWARE FREE OPERATING SYSTEM Serenity Systems "Ecomstation" ver 2.0 RC4, the successor to IBM's os/2 ---------------------------------------------------------------------------------- **= Email 9 ==========================** Date: Tue, 08 Apr 2008 13:10:11 +1000 From: Ed Durrant Subject: Re: Time settings Peter Moylan wrote: > > Hmm, my recollection is that South Australian DST *did* finish at the > end of March, and that it was only Victoria and NSW that extended it > into April. I could be wrong there, though. > > No that was West Australia who changed on the "normal date" all other states and territories that change their clocks delayed a week. Cheers/2 Ed. ----------------------------------------------------------------------------------