Daylight Saving Time change (2007)

[timrob]

I have Win XP Pro SP2, SageTV 6.0, Java 1.4.1_07. Windows auto updates included the DST update, but the system time was still an hour behind, and Sage 2 hours behind. I synchronized the system time twice before it would take effect (third tab on the Windows clock). Sage was still an hour behind. I ran the tzupdater.jar recommended by Stevech, as I didn't want to screw with my stable system, and all is well. Thanks Stevech

I'm keeping my fingers crossed as I'm going on a trip for 5 days and a lot of season finales are showing.

[Pumpkinhead]

Originally Posted by Oats

I update java with the tzupdater and it now shows I have v1.4.2_11 but the time is still wrong Windows is correct.

I also fixed my cell time by turning it off and on. Too bad Sage/Java/Windows wasnt that easy.

I got it to work. The windows clock showed the right time but I didnt have the DST Windows update. After I installed the update it still didn't work. I tried to sync the time and it still didn't work. I had to uncheck 'Automatically adjust clock for daylight saving changes' and apply and then recheck it and apply. Now all is good.

On Windows 2003 standalone Sage 4 system, I tried the same tricks, had the Windows update in advance and tested, even tried the 3rd party windows update (said it was already updated.) But even after updating to the newest java 1.4 version (v1.4.2_12) rather than using tzupdater, rebooted, restarted sage, unchecked and rechecked daylight savings time, enabled and disabled syncing with Sage server - no joy with any of that - Sage always showing an hour off from the system clock. Finally, updated to java 1.5.0_11, and restarted Sage. All is good- times match, sync enabled, DST still checked.

[SprDtyF350]

Originally Posted by ARMYB77

Ok I fixed the problem with the one hour ahead here is what I did:

downloaded and ran: http://www.intelliadmin.com/DaylightSavingFix.exe
next opened SageTV and it was an hour behind, so I disabled Synchronize with system clock, and closed sage.
then I opened SageTV and the time was right, and then I was able to enable the Synchronize again. Everything was fixed.

Hope this helps,
Armyb77

I used this and it worked fine..

[PSUAviator]

Agreed. This one lays solely on those who code SageTV. This DST change was in the pipeline for two years. They chose to spend their time on feature creep instead of testing to ensure continuous operation for the users. Don't get me wrong...Sage is a great product, and I extol its virtues to all of my friends... but this was a pretty decent oversight.

When I left home today at 11a... Computer said correct time, SageTV was one hour behind.

When I return at 6p, computer is one hour behind, and Sage behind 2. Seriously? I have the latest version of Java, the MS patch has been installed for months. Everything is working as it should - except for Sage. (I imagine the -1 hour jump this afternoon was due to Sage changing the system clock to coincide with the EPG data)

Why can't we all just use GMT and ignore this? If the Sage folks come back and say it's something to do with the EPG data, I might buy that.

Update: Sun's tzupdater.jar file (mentioned here) seems to have fixed things for me. SageTV's clock and the EPG data have jumped forward, back in sync with the system clock.

SageTV: I, and likely other users, would like to hear some official word on how we'll be affected by the fall DST switch.

Originally Posted by stevech

Mine's fixed. Fortunately I'm a computer geek. No way non-geeks could cope.
SageTV REALLY BLEW IT. UNFORGIVABLE.

I have Sage v5 and Java 1.4 - it doesn't have the DST change.

I had long ago applied the Windows fix. But Java's run time environment (JRE) ignores Window's time zone setup.
(that's the anal Sun/Microsoft rivalry at work).

Go to sun's website. https://sdlc5e.sun.com/ECom/EComActi...6C4E8569369FDD
Register as a user - fill out personal info I don't want to provide.
download tzupdater.jar which is a 480KB zip file to extract. Perhaps that file is kicking around the download sites other than Sun's.
stop sage
cd to same dir as the tzupdater.jar file
java -jar tzupdater.jar -u

should run without error
restart sage

Irresponsible that Sage didn't announce and plan this months ago.

.

[nielm]

A new article has now appeared on Java's site since I posed above, listing slightly newer Java version numbers that are known to have the changed DST dates

1.3.1_18
1.4.2_13
5.0_u9
6

That article also contains a link to a tool to update Java's TZ info without doing a full upgrade.

Remember that you need both a fixed Java JRE, and the Windows DST fix. No changes to sage are requred (or indeed are possible).

[iammike]

This is starting to become a real pita for me. I had the DST problem this morning. The time in Sage was an hour behind my system clock and no matter what I did it wouldn't change. I read on here about tzupdate and tried it first. That didn't appear to work so I uninstalled java and installed the latest and greatest from Sun. I also went to Windows Update and loaded all the latest. The time finally sync'd with my system clock and I thought I was out of the woods. Didn't check it again until this evening, and the time is off again. The only difference now is my system clock is an hour behind too. Everytime I try to set the system clock to the correct time, Sage sets it back an hour. I know it's Sage, because I tried it without Sage running and the time didn't change. When I start Sage the time rolls back within a minute or less of start up.

What's going on? How come Sage is rolling the time backwards? One other piece of information, I disabled sync system clock with EPG update. Can anyone shed some light on this? I'm sure I'm probably doing something dumb, but I'm getting too mad at Sage for rational thought and need help.

I think I fixed the problem. I set the time an hour too further ahead than it's supposed to be and then let Sage have a couple minutes. Interestingly it didn't try to change the time again. Then I set the time back to the correct time, and so far Sage hasn't changed it. One other thing I forgot to mention initially was I'm running 6.1.3, although I doubt that matters for this problem.

[drbgt3]

Ever since the Daylight Saving Time change, my clock on the Sage TV software is an hour off. The clock on my computer is right, but the one on Sage is off. Since this has happened, all my recording are wrong, cause there not at the right times. Is there any way to fix this?

[DON3k]

And why was 1.4.2_13 not included in the latest Sage download packages, if they knew this was coming, especially in the BETA's?
.

[BobPhoenix]

Originally Posted by DON3k

And why was 1.4.2_13 not included in the latest Sage download packages, if they knew this was coming, especially in the BETA's?
.

1.4.2_13 has only been out a short while so the blame is still with Sun and not SageTV.

[DON3k]

1.4.2_13 did jack for me. I had to install the latest 1.5.0_10 to get things working. Finally Sage, or Java, or whoever has stopped "fixing" my time by changing it back an hr or two.

So, no Simpsons for me this evening..... Let's see if it botches-up and misses Family Guy, too....
.

[stevech]

Originally Posted by BobPhoenix

1.4.2_13 has only been out a short while so the blame is still with Sun and not SageTV.

Nope. Sage uses JRE. Sage has a responsibility in this regard, much as Peter Pan peanut butter had an obligation to tell folks of a flaw in their product due to a supplier.

[iammike]

Now I have another interesting issue. My clock is still showing the right time, but my guide has the wrong time for all the programs. Everything is showing as starting an hour earlier than it should. This problem is a real pain. How do I make the Sage guide show the right time?

[ToxMox]

Did anyone else's Sage go completely whacko tonight? I patched my XP box the other day and made sure I was running the latest Java. According to my log Sage made an EPG update and for one minute jumped the clock ahead one hour then jumped it back. Screwing with all my recordings for the two hour window. I won't know if they are OK until stuff is done recording tonight but it seems at the very least the timelines are all screwy.

[BobPhoenix]

Originally Posted by stevech

Nope. Sage uses JRE. Sage has a responsibility in this regard, much as Peter Pan peanut butter had an obligation to tell folks of a flaw in their product due to a supplier.

I believe that if you look at NIELM's earlier post 1.4.2_11 was reported to be DST change capable (what SageTV includes I believe) now it 1.4.2_13 that is DST compatible. I fail to see how SageTV can be responsible for that. 1.4.2_13 works on my client just fine. But I can't say on the Server because I run 1.6.

BobP.

Edit after seeing some of the latest problem I will retract my statement since this appears to be a SageTV not Java problem to me.

[mc2wheels]

Last night I installed the tzupdater for the version of java that sage ships with, and my XP pro got the tz update from microsoft through windows update. Now around 9 pm, while I was recording a show that started 8, the time jumped to 10pm.

Did you sage guys do something? I reset my system time back an hour, but this sure seems as if someone externally bumped the time. I have my machine set to sync with the sage server. It sure seems like you guys did something on your servers.

[technazz]

Mine just jumped ahead an hour at 9:10 and it basically ended my recordings at 9 to 10 and then I manually changed my clock had to cancel.delete the recording and then record again. What A pain. My clock was fine all day today..

Technazz

[clmolnar]

Originally Posted by technazz

Mine just jumped ahead an hour at 9:10 and it basically ended my recordings at 9 to 10 and then I manually changed my clock had to cancel.delete the recording and then record again. What A pain. My clock was fine all day today..

Technazz

Mine did the exact same thing. I fixed it manually, and it jumped ahead an hour again. Fixed it manually again and turned off the sync with Sage server option. So far the time hasn't jumped forward again. All of my recordings from 9-10 are messed up.

I am running JRE 1.6 and have all of the latest windows updates. It looks to me like Sage pushed out the wrong time via their sync.

[twieder]

I had the same problem -- the clock jumped from 9pm to 10pm..... somebody is having a little fun at our expense.
I jumped in via a remote desktop connection (haven't you all hacked your XP installs to allow RD in separate sessions?) and changed the time. Both shows that were supposed to record at 9 were also set to record the show following them on the same channels, so Sage just adjusted the show names and kept recording. Nice programming!

[DON3k]

Yep, I spoke too soon.

Sage jumped to 9:30 when my 8-8:30 recording finished...

Thanks Sage and Java!

Anyone want to explain what magic spell I have to follow to get my Sage to understand what's going on!?!
.

[kevpriest]

Yep, clock just jumped from 9 - 10, so instead of BSG it's recording Dresden Files right now. I changed the clock, but I don't know what's going to happen since the recording already started.