Daylight Saving Time change (2007)

[Mike]

Originally Posted by kevpriest

I'm "saving" my daylight by sitting inside trying to figure this stupid stuff out.

I hear you load and clear! Right now my computers that have all the current Windows updates think that it is still CST. Sage now thinks that it's CDT (sync system clock is disabled). I'm going to have to be happy with that for a while I guess.

Mbrew

[clayfree]

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

OK, I applied this and it fixed everything! Funny thing, the DirecTivo is still an hour behind. The shows are the same as DirecTV but the Tivo guide is an hour behind.

[stevech]

Nice job, SageTV, of just doing the blame game on Java.

Meanwhile, the Spouses laugh at us.

I have no clue as to how to fix mine. Windows is correct. Sun's Java website is ambiguous for non-Sun-OS users.

I have Java 1.4 and dare nor update to a newer version based on memory leak issues I read about.

[Goodspike]

Originally Posted by stevech

Nice job, SageTV, of just doing the blame game on Java.

Meanwhile, the Spouses laugh at us.

I have no clue as to how to fix mine. Windows is correct. Sun's Java website is ambiguous for non-Sun-OS users.

I have Java 1.4 and dare nor update to a newer version based on memory leak issues I read about.

The Sun site does suck, but it is a Java issue. You can get version 6 here:

https://sdlc5c.sun.com/ECom/EComActi...8FFF6CE695849B

[mruseless]

Originally Posted by malore

I joined the ranks of those with the SageTV's clock being off by an hour this morning. Before DST started I saw that the scheduled recordings were off by an hour so a show that should be from 9-10 was listed as 8-9. So I was expecting trouble.

By looking at the running programs, I determined that SageTV was using windows\system32\java.exe
So, I opened a command prompt at that location and executed "java -version" and was shown 1.4.2...
I then exited SageTV and downloaded and installed the current version of Java from http://www.java.com/en/download/manual.jsp
I then checked the version of Java and this time it was 1.5.0_11-b03
I fired up SageTV and everything is back to normal.

Now hopefully the new version of Java won't mess anything up, so I don't have to dig through the debates about the best version of Java to use.

I am curious that even though this thread is sticky, I don't really see much in the way of an official response. TiVo on the other hand, sent me both an email and an onscreen message detailing what to expect.

Thanks, Malore! Updating my Java versioin to 5 worked.

[computer33]

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

Yes this helped! Thanks.

[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.

.

[Goodspike]

Originally Posted by stevech

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

.

Are you sure Sun did?

[stevech]

Originally Posted by Goodspike

Are you sure Sun did?

I'm a Sage Customer. Not Sun's customer.

[setherd]

Fwiw I had issues this AM also. I had the windows update applied but whenever I started sage up it would set my clock back an hour. I had an old java 1.4 something installed. So I downloaded 1.6, then I uninstalled the old java I had and everything is working fine now.

for those of you still having problems I would suggest using java 1.6 and then look at any other software on your system that may be causing an issue.

[stevech]

Beware Java JRE 1.6 has reported serious bugs. That's why, as I list above, I patched the older JRE 1.4 with the tzupdate.jar.

[setherd]

Originally Posted by stevech

Beware Java JRE 1.6 has reported serious bugs. That's why, as I list above, I patched the older JRE 1.4 with the tzupdate.jar.

Thanks, Good to know, I'll keep an eye out for problems and know what to look at first

[Oats]

I have this problem too, its 1:45 and sage thinks its 2:45. Hopefully it doesn't take me too long to fix now that all you guys have figured it out

However, my cell phone says its 12:46 and I it is not possible to change the time because it gets it from the cell network.

[Goodspike]

Originally Posted by stevech

Beware Java JRE 1.6 has reported serious bugs. That's why, as I list above, I patched the older JRE 1.4 with the tzupdate.jar.

I've heard nothing but positives about it on these forums, even in its prior beta version. 1.5 I'd heard a lot of bad things about.

[Goodspike]

Originally Posted by stevech

I'm a Sage Customer. Not Sun's customer.

I think you missed my point. I don't know when Sun issued a fix for this, but until they did, there wasn't a thing Sage could do about it. So blaming Sage without knowing what Sun did or didn't do is pre-judging them.

I would say though, that an email would have been nice, rather than just an announcement in these forums.

[dflachbart]

Originally Posted by stevech

Beware Java JRE 1.6 has reported serious bugs.

Where did you get this idea ?? Java 6.0 has been rock-stable for me and (as far as I know) everyone else here posting in the forums...

Dirk

[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.

[stevech]

Originally Posted by flachbar

Where did you get this idea ?? Java 6.0 has been rock-stable for me and (as far as I know) everyone else here posting in the forums...

Dirk

OK - I stand corrected - JRE 1.5 is to be avoided but 1.6 is error free. Right? The Java 6.0 jargon confuses me. JRE is all we ordinary Sage users care about.

edited to remove content repeated in all recent posts

[mike1961]

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 tried that and Sage was then off by Four hours so there was one final thing I had to do - I had to restart the computer. Then after restarting the computer I noticed the system time was advanced one hour so I set it to the correct time, then started Sage and then everything worked so I then resynced it with the file server. Ironically, I had this problem on TWO out of THREE of my workstations. So, I can't explain why it worked fine on one of my workstations. The only thing I can think of is I already had a DST patch on the third workstation and I restart that daily anyways.

Mike

[mike1961]

What happens when the real DST was supposed to start? Will we have more computer bugs again and will all the computers now set our clocks forward thinking DST starts 3 weeks from today?

Mike