All my boxes have the correct name in the system info screen but on the now playing list they all say DVR. Does it just take time for the names to show up? The boxes have been named on TiVo.com for a long time.

Click to expand...

I am also annoyed with the same issue. My one S3 unit remains to be called 'DVR', as well and I also changed the name of one of my S2 units today, however it refuses to update the unit for some reason...

Yeah in fact I used the exact same URL as I did with my other Series3 that works, except I changed the last octet of the IP of course. I guess I'll force another call and another reboot even though it says a,a,a.

All my boxes have the correct name in the system info screen but on the now playing list they all say DVR. Does it just take time for the names to show up? The boxes have been named on TiVo.com for a long time.

Click to expand...

Both of my boxes (S3 and THD) had the name in the Info screen about 2:00 today. My THD finally recognized the correct name for the S3 about 5:00. The S3 still shows the default name (DVR) for the THD. Also, the S3 also shows a duplicate list for the THD called "_Tivo-videos DVR". I have transferred from the default DVR list and from the _Tivo-videos DVR list and they both work. Strange.

Both of my boxes (S3 and THD) had the name in the Info screen about 2:00 today. My THD finally recognized the correct name for the S3 about 5:00. The S3 still shows the default name (DVR) for the THD. Also, the S3 also shows a duplicate list for the THD called "_Tivo-videos DVR". I have transferred from the default DVR list and from the _Tivo-videos DVR list and they both work. Strange.

Click to expand...

I have that _Tivo-videos in 3 of my boxes. In those boxes I have 4 DVRs listed plus the _Tivo-videos, so I don't know what it is from. I should only have 4 boxes showing up. I guess it will sort itself out overnight.

I have that _Tivo-videos in 3 of my boxes. In those boxes I have 4 DVRs listed plus the _Tivo-videos, so I don't know what it is from. I should only have 4 boxes showing up. I guess it will sort itself out overnight.

Click to expand...

You can compare the NPL of the weird box to your other boxes to determine which one is duplicated. FWIW.

I got 1 S3 and 1 THD. I can see both units on each unit however if I transfer it fails...

Just rebooted both...about to tryin again.

Click to expand...

Have you TiVo's connect to the servers again. Sometimes even though you have a,a,a something isn't setup correctly and you will get the unrecognized format error. I had the same problem, connected a few hours later, and everything was fixed.

I got 1 S3 and 1 THD. I can see both units on each unit however if I transfer it fails...

Just rebooted both...about to tryin again.

Click to expand...

Same here. Trying to pull a show from my S3 to my THD. Haven't tried the opposite yet.
It's really frustrating to not see it working after all this waiting. Perhaps we should start a separate thread to track this error?

"There was a problem transferring the requested program to this DVR. To view which programs won't be transferred and why, go to TiVo Central and select "Find Programs" > "To Do List" > "View Recording History".

When I do that, I see:

<Program>: <Episode> from Series 3 (transfer attempted on 10/23/07 at 8:55pm)
This program was not transferred onto this DVR because the program was recorded in an unknown format.

nope thats not it, got plenty of stuff in my tivo video folder. also tivo to go seems to work fine, i can connect to my tivo with no problem, maybe i just need to wait and hopefully it will pop up?

Click to expand...

Maybe - I did notice on mine all kinds of things that seemed "broken" at first, and they all worked themselves out over time. Such as -
My Bedroom TiVo could see my LivingRoom TiVo, but not the other way around.
My PC showed up on one, but not the other at first.
TiVo Desktop transferred from my Bedroom, but listed LivingRoom as unsupported.
Both TiVo's (S3's) listed the other as simply "DVR".

All of those little issues and more simply ironed themselves out as the thing eventually got fully up to operational status.

Hopefully the same will happen to the rest of the users here with similar issues.