[wer]

It looks like Tivo Desktop 2.5 is partially broken when the computer has multiple network adapters.

If you have multiple network adapters in your computer (which you do if you have firewire ports or VMware installed) you have to make a choice in Tivo Server Properties to pick which adapter or NIC you want the Tivo software to bind to.

This worked fine in 2.4a and previous versions, but in 2.5 the choice becomes non-persistent. If you change the selected adapter away from the one the Tivo Desktop Installer program selected, your choice may be lost on your next reboot, forcing you to reconfigure this option every time you restart your computer.

This may have something to do with the HKLM\Software\Tivo\Desktop\Beacon\SelectedAdapter registry key getting erased when TivoBeacon.exe starts up.

I've reported this to Tivo, but they say the engineering team is currently "backlogged" as one of them is out.

In the meantime I wil downgrade to 2.4a to avoid this, although I lose the nifty Itunes integration.

 

[irandsert]

I've reported this to Tivo, but they say the engineering team is currently "backlogged" as one of them is out.

Now that is funny. I wish I could take a day off the week of a major project/go-live/release.

 

[wer]

Must be a long vacation... Haven't heard anything back yet.

 

[mercurial]

Bumpity bump...

I just setup a new PC that I happen to have VMware on and also happens to have two NICs... I'm hitting this issue with Ver 2.5.275381... I guess I'll just get used to manually fixing it everytime I reboot...

 

[mercurial]

Great... Unbelievable. You can't just email or fill out a form for a support case like this, you have to call... WTF!? It's called technology. Some of us have access to PCs all day but don't have the time to sit on the phone and talk to some guy who's probably going to ask us to do stupid things like "uninstall and reinstall the software" or "reboot the computer and the TiVo(s)"....

I wonder how hard it would be to steal that key from the registry and then just have a batch file that waits 5 minutes after roboot and does a command line regedit to replace it? Can you start/stop the TiVo server from the command line too? Hmmmm.....

 

[kswartz]

I've been trying to do just what mercurial suggested. In my case, the adapter selected is persistent across a reboot, but not when the machine wakes up from being in suspend mode.

I tried writing a short batch file that checked the SelectedAdapter registry value (noted above), and if it wasn't set to the value corresponding to the right network card, it killed all TivoServer processes (and stopped the TivoBeacon service), edited the registry, and restarted the service and other processes, using the same command lines as shown in the registry.

Unfortunately, whenever I do this, the server comes up still showing the old (and incorrect) adapter. I'm guessing it's caching this somewhere in memory, and not forcibly rereading the registry to get the new value. I haven't figured out if there's some other registry setting that tells the server to check again. (I haven't been at it long enough to determine if the server is just SHOWING the old adapter but using the new one -- but I'm skeptical of that.)

Anybody else have any luck coming up with a workaround for this (short from downgrading)?

Thanks,
Keith