TiVo Community Forum banner

6.3e changed my Service Number prefix

2971 Views 15 Replies 8 Participants Last post by  wscannell
When I was on 6.2 my prefix for my Hughes dvr40 was 151, matching the suffix on my software version. After 6.3e my prefix changed to 351. Has anyone else seen this? :confused:
1 - 16 of 16 Posts
151 is the HDRV2. I do not know why your machine had the wrong number.

Series 1 units
001 - DSR6000, DSR6000r, DSR600r01
011 - SAT T-60
031 - GXCEBOT, GXCEBOTD

Series 2 units
101 - DSR7000, DSR7000R
121 - DVR39
151 - HDVR2

Series 2 units with RID
301 - DSR704, DSR708
321 - DVR40, DVR80
351 - SD-DVR40, SD-DVR120
357 - HR10-250
381 - SIR-S4040R, SIR-S4120R
3F1 - ?

Series 2.5 units
521 - R10
See less See more
snickerrrrs said:
When I was on 6.2 my prefix for my Hughes dvr40 was 151, matching the suffix on my software version. After 6.3e my prefix changed to 351. Has anyone else seen this? :confused:
That is very odd. As previously mentioned, 351 is the correct prefix for the Hughes SD-DVR40. Are you sure you are remembering that correctly? OR, did you upgrade your unit with an image you might have gotten from somewhere else?
This appears to be normal this time around. There's been discussion on the "other forum" about it. Here's a snippet from a DSR704. These slices arrived almost 2 weeks ago.
Code:
BaSh2.02 /$ mfs_ls /SwSystem
dir: fsid=3969 count=4
      fsid   type     name
      -----------------------------------
     15608   tyDb     6.2a-01-2-301
    194693   tyDb     6.3e-01-2-101
    194698   tyDb     6.3e-01-2-121
     15608   tyDb     ACTIVE
This seems to be happening alot lately. There are 8 (iirc) different service codes for Series2 DTivos, 9 if you count the R10. There seems to only be about 4 or so different 6.3e slices. It's been suggested that they're "consolidating code", so all that remains to be seen is which old service codes match to which new software slices. If people whose units have updated automatically would care to report, we can map service numbers to software slices to determine the slices to use for manual updates.

The 6.3e slices that I have seen reports of are 101,121,151,381, and 521. I think it's safe to say the R10 is probably the only one which must have the exact, correct, matching-numbers slice.

I've put together a table based on posts I've read here and somewhere else. Where it has been confirmed that a model self-upgraded to a non-matching slice, I've cited a reference. Until I see otherwise, I've assumed that models for which matching slices have been seen will upgrade to the matching slice, and I have listed them as such.

DirecTV Tivo Model --> Tivo Service Number --> 6.3e software slice.

Phillips DSR7000------------------> 101 --> 101, assumed
RCA DVR39-----------------------> 121 --> 121, assumed
Hughes HDVR2--------------------> 151 --> 151, assumed
Phillips DSR(704,708)--------------> 301 --> 101, confirmed, ddb @ showthread.php?t=54367&page=3
RCA DVR(40,80,120)--------------> 321 --> 121, confirmed, ddb @ showthread.php?t=56718
Hughes SD-DVR(40,80,120)--------> 351 -->151, unconfirmed
HR10-250-------------------------> 357 --> 357, unconfirmed
Samsung SIR-Sxxxx---------------->381--> 381, assumed
????????????---------------------->3F1--> ???
DirecTV R10----------------------->521-->521, assumed
????????????---------------------->5F1--> ???

The pattern I see emerging here is that the RID units and the non-RID units have had their code converged. Notice that (throwing the R10 out of consideration...call it the red-headed-stepchild) the RID units all have TSN prefixes starting with "3", and the non-RID units have TSN prefixes beginning with "1". Essentially, if the first digit of your TSN is a "3", change it to a "1" to get the correct software version, with the exception of the Samsung, which was not available in a non-RID "flavor. Perhaps a better way to explain it is to say that only the second two digits need to match (with exception for the red-headed-stepchild again).

I also noticed the second digit of the TSN prefix seems to correspond to the manufacturer, where 0=Phillips, 2=RCA, 5=Hughes, and 8=Samsung.
See less See more
Yeah, but what the OP described was sort of the opposite of what you are suggesting (not that what you are suggesting isn't happening more generally, though).

He claimed that he had an SD-DVR40 with a 3-digit prefix of 151 and that it BECAME 351; not the other way around.

So that means one of several things:

1) a typo - he has an HDVR2, not and SDDVR40
2) a misread - it was 351 all along
3) he manually installed the 351 version of 6.2 last time around (all the slices came down on all the units, but if auto-installed, the correct slices should have installed
4) he had the wrong version of the software on the unit, to begin with (not sure that it would have upgraded in the way described if he had
5) ?
I doubt his Tivo Service Number prefix changed. In the past, if you were running the correct software for the unit, the 3 digit suffix of the software version number matched the 3 digit prefix of the Tivo Service number. While the OP did say "prefix", I think he meant the version suffix, but I stand prepared to be corrected.
CrashHD said:
While the OP did say "prefix", I think he meant the version suffix, but I stand prepared to be corrected.
I interpreted it that way, too.
tivoupgrade said:
4) he had the wrong version of the software on the unit, to begin with (not sure that it would have upgraded in the way described if he had
Regarding that, I think even units with mismatched 6.2x software are upgrading, see ddb @ showthread.php?t=56718 where a 321- unit loaded with -301 software self-upgraded to -121 software.
There are some images floating around out there with missing "ModelInformation" object in MFS.

Maybe upgrade software gets confused if it's missing that object.

RID models should have that object.

If you have RID model (RCA DVR40, 80,120, Hughes SD-DVR40,80,120, Philips DSR704,708) but Tivo reports DSR7000 under system information, you are in this category.
It could be software consolidation. When they released 7.x for the standalones, they made the 140 and 240 DVRs get one version.
I think the units with the missing model information are the ones from the 6.2 minimal image. Even if you manually installed the correct slice with that image, the model information came back missing. I had units installed from that image that upgraded to the correct slice back with the 6.2a upgrade thought, so I don't think that threw it off. There's also the fact that I've only seen reported sightings of 4 different slices for 6.3e. I think it's a code consolidation thing.
CrashHD said:
I think the units with the missing model information are the ones from the 6.2 minimal image. Even if you manually installed the correct slice with that image, the model information came back missing. I had units installed from that image that upgraded to the correct slice back with the 6.2a upgrade thought, so I don't think that threw it off. There's also the fact that I've only seen reported sightings of 4 different slices for 6.3e. I think it's a code consolidation thing.
Actually, its more than that. My original thoughts were along the lines of that particular image that is floating around, as well.

But that is unlikely to be the case here - spike's post reminded me of the fact that back when I forced the install of 6.2a on each of my DirecTiVo SD units (I have one of EVERYTHING) I saw the same thing on several different units. I don't have the list any more, but several of the units displayed incorrect IRD information and it sounds consistent with that observation (it also led me to document the three digit prefix/suffix rule to verify that you have the right version of the software, even if the IRD info is listed incorrectly).

In any case, I am working on a customer unit right now -- a SDDVR120 (351) that has 6.3e with a 151 in it; so there does appear to be some consolidation or at least change, in how things are being handled...
RCA DVR39-----------------------> 121 --> 121, assumed
The DVR39 has been a 101 since 6.2a. It even shows the name as a DSR-7000.
That would be a DVR39 with the incorrect software slice set active (nothing wrong with that, it will function as normal that way). There is a 6.2a swsystem slice that matches the DVR39's -121.
Actually, it was a DVR39 with DVR39 software on it before it upgraded via the satellite feed to 6.2a. After the upgrade, it because a DSR7000 with -101. The unit has not been reloaded with a different image.
1 - 16 of 16 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top