Is There a Work Around for the TIVO Seies 1 DST
Nevada Slim
reinput them. Takes about 30 minutes 4 times a year. Is there a work around for
the hard coded DST?
Thanks,
Slim
Character
There should be no such problem; there was an update that should have
been applied somewhere in 2007. As I recall, at the time you had to
call them and arrange for the update to be sent to your system.
Call customer care - they should be able to help you.
1-877-367-8486
- Character
Nevada Slim
Tried your suggestion, but the only way to get TIVO help is to subscribe to
their service.
Thanks,
Slim
Character
You're right; I assumed that you had.
You do have a one-time option - subscribe to the service, then cancel
within 30 days. That should be plenty long enough to be able to
download the updated DST module. I'm not sure whether or not they
charge you for the time you used - probably not.
Don't you have to dial up occasionally to make sure that the clock is
right?
- Character
Nevada Slim
I do, and the clock is current. Every time the DST changes all my recorder
events are off by 1 hour. Maybe subscribing for 1 month is the only answer.
Thanks again,
Slim
Doug McIntyre
>I do, and the clock is current. Every time the DST changes all my recorder
>events are off by 1 hour. Maybe subscribing for 1 month is the only answer.
The only other choice would be to hack the box, and run up the scripts
that jacked your clock around the proper amount 4 times a year.
Wes Newell
> I do, and the clock is current. Every time the DST changes all my
> recorder events are off by 1 hour. Maybe subscribing for 1 month is the
> only answer.
I'd ask them first. They may not even support software upgrades for your
unit any longer. It's also possible that you could get a new drive from
weaknees.com with the latest update. If all else fails, you would have to
hack the box with a terminal, get root access, and replace the timezone
files with the correct files. A lot of work you probably don't want to
attempt. And if you can find someone to send you the latest software
image, you could upgrade your old drive for nothing using the mfs tools.
--
Want the ultimate in free OTA SD/HDTV Recorder? http://mythtv.org
My Tivo Experience http://wesnewell.no-ip.com/tivo.htm
Tivo HD/S3 compared http://wesnewell.no-ip.com/mythtivo.htm
AMD cpu help http://wesnewell.no-ip.com/cpu.php
Questor
have to do it again when the sdt really goes into effect.
"Character" <Ch...@cters.bold.italic> wrote in message
news:qt4Gm.115869$Gs.1...@en-nntp-01.dc1.easynews.com...
Wes Newell
>> I do, and the clock is current. Every time the DST changes all my
>> recorder events are off by 1 hour. Maybe subscribing for 1 month is
>> the only answer.
>
> Actually, it isn't an answer at all.
>
> There is no 'fix'. For the S1, a small update is pushed out around the
> beginning and end of DST basically saying ok, your time is going to be
> wonky. This isn't really a software update per se, it is just a
> workaround for a TiVo WITH A SUBSCRIPTION to deal with manual recordings
> and the cosmetic issue with season passes and such. And that is all it
> is for a subbed TiVo, a cosmetic issue. What is on at 7, TiVo thinks
> will be on at 6...but that is ok because when it IS 7, TiVo will think
> it is 6 and record just fine. The problem comes when using an unsubbed
> TiVo as a VCR and just using manual recordings. In which case...yeah
> you have to do the work yourself.
Linux handles time change via timezone tables. The only reason a fix is
needed is because the US changed the switch over days a few years ago.
I'm assuming Tivo also implemented timezone since it's a part of the
standard install. When the dates were changed, newer timezone tables were
released. All one had to do was load them and there won't be another
problem unless our stupid congress changes something again. So to correct
the problem Tivo needed to send the new timezones tables anytime during a
call in. Did they? I don't know. If not, shame on them. The one time
patch was all that was needed. And it's all that's needed now. On a linux
box type man timezone.
Chris Adams
>Linux handles time change via timezone tables. The only reason a fix is
>needed is because the US changed the switch over days a few years ago.
>I'm assuming Tivo also implemented timezone since it's a part of the
>standard install.
IIRC, TiVo runs the Linux system in UTC, and then keeps time and time
zone information in the MFS database.
--
Chris Adams <cma...@hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
Gordon Burditt
>been applied somewhere in 2007. As I recall, at the time you had to
>call them and arrange for the update to be sent to your system.
As I recall, the fix sucked. I called customer service at the time
and had the fix sent. It *would* get things recorded at the right
time. It did, however, display the wrong time for things (upcoming
shows) across the time zone transition.
I'm not sure how it worked with manual time-and-channel recordings
as I didn't use these much.
My Series I is now retired and its subscription transferred.
Character
>>There should be no such problem; there was an update that should have
>>been applied somewhere in 2007. As I recall, at the time you had to
>>call them and arrange for the update to be sent to your system.
>
>
> As I recall, the fix sucked. I called customer service at the time
> and had the fix sent. It *would* get things recorded at the right
> time. It did, however, display the wrong time for things (upcoming
> shows) across the time zone transition.
>
We're in that interim period now, and my fully subscribed S1 shows the
correct time, says that programs are on at the correct time, and
records at the right time.
I disagree with Howard that the implementation involves downloading a
temporary patch every time DST changes. If that were true, there'd be
an interval with the wrong time unless every TIVO in each time zone
dialed up at exactly 2:AM on the appropriate Sundays. Never happen!
The 2007 patch changed the DST tables in the software.
- Character
Character
> Character <Ch...@cters.bold.italic> wrote in news:rSoGm.102303$ua.11163@en-
> nntp-05.dc1.easynews.com:
>
>
>>I disagree with Howard that the implementation involves downloading a
>>temporary patch every time DST changes. If that were true, there'd be
>>an interval with the wrong time unless every TIVO in each time zone
>>dialed up at exactly 2:AM on the appropriate Sundays. Never happen!
>
>
> Just going by what TiVo says.
>
> http://support.tivo.com/app/answers/detail/a_id/119/session/L3NpZC95eENQZUd
> Mag==/kw/dst/r_id/100041/sno/0
>
> Series1 TiVo DVRs
>
> (DVRs with TiVo Service Numbers containing prefixes 000, 010 or 002)
>
> On the second Saturday of March and the last Saturday of October, TiVo
> sends out an update for Series1 DVRs that corrects the internal clock. If
> your DVR is making regular connections to the TiVo service, it will receive
> the update and reboot at 2am the following day to install the update.
>
> During the 2 weeks before your DVR downloads this update, the Program Guide
> data for upcoming shows may appear to be off by one hour. Do not be
> alarmed. Season Passes, WishList recordings, individually scheduled
> recordings and TiVo Suggestions will record at the proper time regardless
> of whether the update is installed. Manual recordings will only be affected
> if the update is not installed.
>
I stand corrected. They do it with the forced Reboot at 2:AM instead
of my silly impossible suggestion of a simultaneous dial up. I just
checked the Tivo schedule on my S1 and indeed it now displays the Jay
Leno show at 10:PM until the end of October and at 11:PM thereafter.
However, as described in the text on that page, it's wrong! Daylight
savings time ends in the U.S. NOT on the sunday after the last
Saturday in October, but on the first Sunday in November. Since it
worked correctly in 2007 and 2008, I can only assume that the text is
wrong and the updates are correct.
Again, I apologize for misleading anyone. And yes, the 30-day sign-up
would only work once, and then only if you did it at the right time.
You couldn't sign up again for over a year, so that wouldn't really
help the OP.
- Character
Wes Newell
> Once upon a time, Wes Newell <w.ne...@invalid.invalid> said:
>>Linux handles time change via timezone tables. The only reason a fix is
>>needed is because the US changed the switch over days a few years ago.
>>I'm assuming Tivo also implemented timezone since it's a part of the
>>standard install.
>
> IIRC, TiVo runs the Linux system in UTC, and then keeps time and time
> zone information in the MFS database.
Afaik, all Linux systems *run* on UTC. The timezone tables are what does
the +/- to convert to local time.
Chris Adams
>On Thu, 29 Oct 2009 12:25:23 -0500, Chris Adams wrote:
>> IIRC, TiVo runs the Linux system in UTC, and then keeps time and time
>> zone information in the MFS database.
>
>Afaik, all Linux systems *run* on UTC. The timezone tables are what does
>the +/- to convert to local time.
Yes, but what I mean is the Linux system is configured as UTC (not in
local timezone). If you get a shell on a TiVo and run any command that
shows the date (e.g. "date", look at log files, etc.), you'll only see
UTC, not local time.
Doug McIntyre
>Once upon a time, Wes Newell <w.ne...@invalid.invalid> said:
>>On Thu, 29 Oct 2009 12:25:23 -0500, Chris Adams wrote:
>>> IIRC, TiVo runs the Linux system in UTC, and then keeps time and time
>>> zone information in the MFS database.
>>
>>Afaik, all Linux systems *run* on UTC. The timezone tables are what does
>>the +/- to convert to local time.
>Yes, but what I mean is the Linux system is configured as UTC (not in
>local timezone). If you get a shell on a TiVo and run any command that
>shows the date (e.g. "date", look at log files, etc.), you'll only see
>UTC, not local time.
He just doesn't get that its the TiVo software itself that is the one
doing the date arithmatic, not any of the installed linux software/libs.
Scott Lurndal
>Once upon a time, Wes Newell <w.ne...@invalid.invalid> said:
>>On Thu, 29 Oct 2009 12:25:23 -0500, Chris Adams wrote:
>>> IIRC, TiVo runs the Linux system in UTC, and then keeps time and time
>>> zone information in the MFS database.
>>
>>Afaik, all Linux systems *run* on UTC. The timezone tables are what does
>>the +/- to convert to local time.
>
>Yes, but what I mean is the Linux system is configured as UTC (not in
>local timezone). If you get a shell on a TiVo and run any command that
>shows the date (e.g. "date", look at log files, etc.), you'll only see
>UTC, not local time.
If you type "TZ=PST8PDT date" the date command will convert the UTC to
PDT/PST.
It's a function of the TZ environment variable and/or the tz config.
Dates are _always_ stored in UTC in linux (and unix). It's only at
display time that any conversions are done.
scott
Scott Lurndal
And the tivo software is using libc, and libc does the date display
(ctime, asctime, strftime, etc) based on the timezone database and
the current timezone setting (e.g. TZ environment variable).
scott
Chris Adams
Again, I know that, I've been using Unix and Linux for almost 20 years.
You should say _filesystem_ dates are stored in UTC; for example, log
entries from syslog are typically in local time. Other applications use
local or UTC on an app-by-app basis.
The point is, THAT'S NOT WHAT TiVo USES. TiVo does all of its date/time
handling internally to mfsapp. It doesn't use the C library time
functions that use TZ and/or /etc/localtime. Later TiVo software
versions get the DST rules from MFS, but the Series1 apparently had them
hard-coded.
Doug McIntyre
And what says that they have to be using the date routines that ship
in the linux libc?
Even if you hack the box, and runup tivoapp with the TZ variable set,
edit up the tzinfo files, its not going to affect anything, they wrote
their own date routines for their own code.
Just because there are date routines provided in libc, doesn't mean
that a programmer has to use them, or its applicable to the specific
services that an application wants to provide, and they want to do
things their own way.
But if you do hack the box, you can jack the time around back and
forth an hour the four times of the year that the old rules vs. the
new rules shift around. But editing the tzinfo files won't do squat
for you.
Peter H. Coffin
It does not matter, if the code doesn't ever use those things. TiVo
software doesn't use them. Just because they're *available* doesn't mean
they're *used*.
--
The consquences of any action will never be fully understood until after
it's too late to do anything about it.
-- Schwartz's Second Law