Crash2009 wrote:Sancho, lets try this again and document everything, maybe we can come up with the steps required. PM me when you get close to installing the locked up card in your spare WMC. That one will have to be totally de-configured from being a network client to your main WMC. You likely want to do an image, in case you want to go back.
I appreciate the offer. This PC is being used temporarily to try and fix this card. That's what I did on another PC with the card I got off eBay. Of course, that PC never had anything to do with Ceton, but I'm thinking I can rid this client PC of all references to its past Ceton life. I'm not going to reimage, as I can't afford to do more to it than I already am. If it works, great, but if not, I'm OK with that.
To that end, I've been messing about with it tonight. Without going into the gory details, here's what I found:
Trying to set the Ceton network device to 10.0.0.2 caused an IP address conflict error. That was actually a very good thing, as that was the IP I used for this messed up card in its original, host, PC. It got me thinking why Windows would think it was conflicting. The Ethernet NIC on this test PC was set to use 10.0.0.5 for Network Tuners.
I assigned 10.0.0.1 / 255.0.0.0 manually and BINGO! the Diag Tool finally saw the card. Of course, when I go into the web page to reset the network, it fails to do so. It's stuck on 10.0.0.2; can't assign a different static IP, can't reset to DHCP server. I tried combos of that with and without using the Diag Tool, but no dice. I did not install Network Tuners for these tests, so of course the WMC tool is not present.
Then I started poking around the registry looking for instances of 10.0.0.2. There were plenty of them, all related to WMC from what I could tell. So I decided to uninstall the Ceton software, since I know how to set the adapter to be able to access it. After uninstalling, I searched the registry again for 10.0.0.2. Most were deleted, but these remained:
..\Media Center\Service\ehPrivJob\AllowedTestUPnPTunerDevices\Ceton InfiniTV PCIe (ID) Tuner 1 ... Tuner 2, etc. Four entries
So I exported the registry, then just that subset, then nuked those four keys, rebooted and reinstalled the Ceton software. All of the above still applies. I can access the InfiniTV if I set the network device to any IP in the 10.0.0.0 network. The netmasks don't even need to match. The card is stuck on 10.0.0.2 / 255.255.255.0, while the network device is using 10.0.0.1 / 255.0.0.0. I also used 10.0.0.66 / 255.255.255.0. I still get the web page, and the Network Settings still won't change.
I also tried a Repair using the software installer. Nada. It only had the effect of adding InfiniTVWizard.exe, which was not available before Repairing.
I was wrong about the Hardware Version. The defective card is 6212, not 6912. The one from eBay is in fact 6829. Assuming Ceton revision numbers follow a sane person's logic, the defective one is older. The card in my main HTPC is 6210, but it works fine, took the latest pre-Beta firmware on the first try, and even ran Network Tuners a year or so ago. Make of that what you will.
As a side note, I tried the steps outlined here:
http://www.avsforum.com/forum/26-home-t ... lient.html
(for running InfiniTVWizard.exe)
While I was able to get the listing, I was unable to clear it. I tried again after nuking the reg keys and reinstalling, but the result was the same. Since that command interfaces directly with the card, it says to me that the flashable part of the card is all jacked up.
So, I think I'm done, unless someone comes back with something I haven't tried that involves only dealing with the Ceton. I can't muck about with Windows anymore than I have. At least WMC has been cleaned up a bit for when I take my next shot at Network Tuners via the 5G network.
I'll leave this test PC in its current state (Ceton installed, side panel off, etc.) until sometime tomorrow. I'll need to reassemble it by Sunday afternoon at the latest.
