|
spiff72
|
 |
« on: August 14, 2008, 07:57:12 PM » |
|
All signs point to NO! There have been numerous reports of these DVRs being able to download the necessary guide data via a digital TV broadcast.
Check out the other topics in this "DTV Transition" section of the forum.
|
|
|
|
|
Logged
|
|
|
|
E55 KEV
Newbie
Posts: 7
|
|
« Reply #1 on: May 02, 2009, 09:25:40 AM » |
|
Looks like these thread can be removed.  |
|
|
|
|
Logged
|
|
|
|
CH MN
Newbie
Posts: 5
|
|
« Reply #2 on: June 30, 2009, 10:22:25 PM » |
|
It looks like they are still working even after June 12. Even if not, if you have had one since 2005 like I have and divide the cost by the hours used, it was not really all that expensive after all. Compared to TIVO or other DVR, which continue to cost you no matter how long you own it, these were a real bargain.
I have not had to lift mine since I installed it so I forgot what it weighs... would it make a good door stop?
|
|
|
|
|
Logged
|
|
|
|
|
mabuttra
|
|
« Reply #3 on: August 30, 2009, 07:05:28 AM » |
|
I posted this on AVS, so thought I would post it here as well. This topic seemed to be the appropriate place. TVGOS base version 08.01.42 test. For anyone who is interested, I have just recovered from a complete reset in a digital environment with the 1.2.13 firmware. You can follow the results here. My goal is to put to rest the claims that the 08.01.42 TVGOS base software does not work in a digital environment. It works if macrovision/rovi is providing complete TVGOS data (which we already know is not the case in some parts of the country). Mark |
|
|
|
|
Logged
|
|
|
|
|
HoustonPerson
|
|
« Reply #4 on: December 29, 2009, 12:51:22 PM » |
|
I posted this on AVS, so thought I would post it here as well. This topic seemed to be the appropriate place. TVGOS base version 08.01.42 test. For anyone who is interested, I have just recovered from a complete reset in a digital environment with the 1.2.13 firmware. You can follow the results here. My goal is to put to rest the claims that the 08.01.42 TVGOS base software does not work in a digital environment. It works if macrovision/rovi is providing complete TVGOS data (which we already know is not the case in some parts of the country). Mark Mark, Do you think your proceedure above would also work with firmware .05 as well in Houston with OTA digital source? Also on a similiar note; should VBI Test = Pass on .05 .13 and .21 for OTA digital only? If VBI Test = Fail on the .21 firmware with OTA digital source; is that an indication of a reason why Houston will not build a grid? |
|
|
|
|
Logged
|
|
|
|
|
mabuttra
|
|
« Reply #5 on: December 29, 2009, 02:40:12 PM » |
|
Mark, Do you think your proceedure above would also work with firmware .05 as well in Houston with OTA digital source?
Also on a similiar note; should VBI Test = Pass on .05 .13 and .21 for OTA digital only? If VBI Test = Fail on the .21 firmware with OTA digital source; is that an indication of a reason why Houston will not build a grid?
I don't have .05, so I don't know, but I would guess that it should work the same as .13. The .21 firmware does not pass the G* Test on a digital channel. I think Sony "fixed" this in .21 because there is no such thing as VBI in a digital signal, so the VBI test fails. The ATSC slicer screen is where you can tell if digital data is coming in. The G* Test has always only indicated the presence of data, but made no distinction as to whether the data was good or not. Mark |
|
|
|
|
Logged
|
|
|
|
|
HoustonPerson
|
|
« Reply #6 on: December 29, 2009, 03:08:56 PM » |
|
Mark, Do you think your proceedure above would also work with firmware .05 as well in Houston with OTA digital source?
Also on a similiar note; should VBI Test = Pass on .05 .13 and .21 for OTA digital only? If VBI Test = Fail on the .21 firmware with OTA digital source; is that an indication of a reason why Houston will not build a grid?
I don't have .05, so I don't know, but I would guess that it should work the same as .13. The .21 firmware does not pass the G* Test on a digital channel. I think Sony "fixed" this in .21 because there is no such thing as VBI in a digital signal, so the VBI test fails. The ATSC slicer screen is where you can tell if digital data is coming in. The G* Test has always only indicated the presence of data, but made no distinction as to whether the data was good or not. Mark Ok, thanks; that confirms that VBI Test Fails with OTA digital only is A-Ok. Sometimes I think I am losing my mind. I noticed in your pictures that when HostSUFlags got to 0xff8, the VBI State was 0x07. My SonyBox still only gets to 0x05……….somehow I feel those two issues are related, but I do not know how? Just wish I knew of a way to get Rovi to fix the problem, but that I suppose is not going to happen. |
|
|
|
|
Logged
|
|
|
|
|
HoustonPerson
|
|
« Reply #7 on: December 29, 2009, 07:58:37 PM » |
|
Mark, Do you think your proceedure above would also work with firmware .05 as well in Houston with OTA digital source?
Also on a similiar note; should VBI Test = Pass on .05 .13 and .21 for OTA digital only? If VBI Test = Fail on the .21 firmware with OTA digital source; is that an indication of a reason why Houston will not build a grid?
I don't have .05, so I don't know, but I would guess that it should work the same as .13. The .21 firmware does not pass the G* Test on a digital channel. I think Sony "fixed" this in .21 because there is no such thing as VBI in a digital signal, so the VBI test fails. The ATSC slicer screen is where you can tell if digital data is coming in. The G* Test has always only indicated the presence of data, but made no distinction as to whether the data was good or not. Mark Ok, thanks; that confirms that VBI Test Fails with OTA digital only is A-Ok. Sometimes I think I am losing my mind. I noticed in your pictures that when HostSUFlags got to 0xff8, the VBI State was 0x07. My SonyBox still only gets to 0x05……….somehow I feel those two issues are related, but I do not know how? Just wish I knew of a way to get Rovi to fix the problem, but that I suppose is not going to happen. Second group of questions: Mark on page one (Step 1) of your procedure with the .13 firmware you have two pictures of the “Reset Info” before and after the first G Test you ran. Each of those shows “1” reset. Then as the Steps continue you went on to G Test 2 and 3 to make the box complete the set up process. After the next two patches were downloaded and after the third G Test, was the “reset count” on 3? Or 4? Thank You |
|
|
|
|
Logged
|
|
|
|
|
mabuttra
|
|
« Reply #8 on: December 31, 2009, 07:31:06 AM » |
|
Second group of questions:
Mark on page one (Step 1) of your procedure with the .13 firmware you have two pictures of the “Reset Info” before and after the first G Test you ran. Each of those shows “1” reset.
Then as the Steps continue you went on to G Test 2 and 3 to make the box complete the set up process. After the next two patches were downloaded and after the third G Test, was the “reset count” on 3? Or 4?
Thank You
I don't know, I only used that picture to show that the PowerOn field was N/A before the G* Test, and was set to the current time and date after the G* Test. After the second patch loads, if you look at the Reset Info-Error Tracker screen, the top two numbers in the left column should be 0x102. Each one of those is a reset that the patch does after it gets installed. Mark |
|
|
|
|
Logged
|
|
|
|
|
HoustonPerson
|
|
« Reply #9 on: December 31, 2009, 09:42:43 AM » |
|
Second group of questions:
Mark on page one (Step 1) of your procedure with the .13 firmware you have two pictures of the “Reset Info” before and after the first G Test you ran. Each of those shows “1” reset.
Then as the Steps continue you went on to G Test 2 and 3 to make the box complete the set up process. After the next two patches were downloaded and after the third G Test, was the “reset count” on 3? Or 4?
Thank You
I don't know, I only used that picture to show that the PowerOn field was N/A before the G* Test, and was set to the current time and date after the G* Test. After the second patch loads, if you look at the Reset Info-Error Tracker screen, the top two numbers in the left column should be 0x102. Each one of those is a reset that the patch does after it gets installed. Mark I am actually doing the exact same procedure here; but with the .05 not .13. So far I have been able to get clock and ads in less than 12 hours; but of course waiting for a Grid – very unlikely for Houston? After you got a grid how long did you stay with the .13? I assumed you went back to the .21 update or is it still running .13 original? Thanks |
|
|
|
|
Logged
|
|
|
|
|
mabuttra
|
|
« Reply #10 on: December 31, 2009, 05:59:42 PM » |
|
I am actually doing the exact same procedure here; but with the .05 not .13. So far I have been able to get clock and ads in less than 12 hours; but of course waiting for a Grid – very unlikely for Houston?
After you got a grid how long did you stay with the .13? I assumed you went back to the .21 update or is it still running .13 original?
Thanks
I kept the .13 firmware for about 3 days after I got the grid, then I switched back to the .21 firmware. I don't intend to ever go back to .13. Mark |
|
|
|
|
Logged
|
|
|
|
|
