Technisat Air2PC detected as Network Adapter (1 Viewer)

[Deusxmachina]

TV-Server Version:
MediaPortal Version:
MediaPortal Skin:
Windows Version: MCE XP32
CPU Type: e6300
HDD:
Memory:
Motherboard: Abit IP35-e
Motherboard Chipset: Intel
Motherboard Bios:
Video Card: His 2400pro
Video Card Driver:
Sound Card:
Sound Card AC3:
Sound Card Driver:
1. TV Card: Technisat Air2PC
1. TV Card Type: ATSC
1. TV Card Driver:
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec:
MPEG2 Audio Codec:
Satelite/CableTV Provider:
HTPC Case:
Cooling:
Power Supply:
Remote:
TV:
TV - HTPC Connection:

I had this card in my gigabyte S3. It was listed under Sound and Video in Device Manager, got auto-detected by MP (as a Technisat Sky), GBPVR, and Beyond TV, and for the most part worked fine. I put it in an Abit IP35-e, and it shows up under Network Adapters. It does not get detected by any TV software, and after manually adding it there is still no picture because the TV software says it can't detect a capture card.

If I disable and uninstall the onboard LAN, the LAN still works if the TV card is installed. I don't know if this has anything to do with the IP35's using the PCI bus for the LAN or not. Comodo firewall sees the onboard LAN and the TV card as ethernet devices and shows them each as having a different ip address.

If I can get the card listed under Sound/Video instead of Network Adapters, it'd probably work fine. It might not be detected by TV software because maybe it's already in use by the LAN. But as I said, disconnected and turning off the onboard LAN, it still works as a LAN device. This is more of a card/OS question than an MP question, but hopefully someone has ran into the problem before.

 

[Das Hammer]

Even if the proper drivers are used (did you download the BDA drivers???) it shows up as a Technisat SkyStar2 satellite card. At least this is what happened to me on the TVServer.

 

[mbb]

the B2C2 family cards (Skystar, Cablestar, Air2Pc) need technisat software setup4PC at least installed to be detected by MP.

 

[Deusxmachina]

On my other computer that the card worked on, I had run the Technisat viewing software and I think setup4pc with it. I never got the tv to actually work with that software, but Beyond TV, GVPVR, and MP all detected the card. Beyond TV then auto-detected the channels, but that was the only one of the three with an EPG. MP worked after changing the Skystar entry to ATSC and then it could channel scan.

I did have the BDA drivers on the current computer. I now ran the Technisat viewer software and setup4pc, and it found some channels. (I hadn't run it since I thought it was only the viewer program which never worked on the other computer.) It then gives a WinLirc failed to initialize error when bringing up the viewer, and so the TV doesn't work. I never got that error on my other computer, I just simply couldn't get a picture for whatever reason.

Media Portal now does detect the card in setup as a Skystar 2 DVB-S, and it autoscanned and found some (ATSC) channels. Going to MyTV, it first gave I think a "can't connect to mpg2 pin" error. I then changed the two Technisat entires in the .xml card file to ATSC like I did before, and now it gives a "failed to start. can't connect to ac3 pin" error.

So it looks like things are now on the right track, and I have to mess around with graphedit to get the pins right. I hope that's all there is. Pretty frustrating to have the card mostly auto-work in one computer but now barely get detected in a different computer. It's still odd that GBPVR and Beyond TV won't detect it at all and say there's no tuner present. At least now there's some hope.

I asked a Network Administrator about the card basically acting as an ethernet device, (the firewall shows the card having a separate ip address), and so far all he said is, "That's really weird."

 

[Paranoid Delusion]

I asked a Network Administrator about the card basically acting as an ethernet device, (the firewall shows the card having a separate ip address), and so far all he said is, "That's really weird."

You have 2 conflicting drivers, try doing TV card install in safe mode, without lan support enabled, or see if there is a updated BIOS\drivers for your motherboard.

Hmmm see there are no driver updates for this card since March 2006, also found this card has problems working with Nvidia based chipset motherboards, but that should not affect you as yours is intel.



Regards

 

[Deusxmachina]

So far, on the Abit forums someone said, "I don't see it as an IP35-E problem, it doesn't decide what the card is. I see it as an OS problem. I haven't heard of this problem before, but I'd be searching over at the Microsoft XP knowledge base."

Of course, Microsoft knowledge base doesn't have a whole lot of info about TV tuner cards being installed as network adapters.

I found a post on AVSforum about someone installing this card on windows 2000 and it being installed as a network adapter. Maybe that's normal for it. It did originally install on my other computer under Network Adapter (with a yellow exclamation point), but then the newest BDA driver got rid of the yellow exclamation point and installed the card under Sound/Video.

After seeing if I can get it to "find AC3 pin", I'll try reinstalling the card in safe mode. Yesterday with a fresh XP install I had to make sure I installed the onboard LAN driver first, otherwise installing the card first the computer would use that as the LAN network adapter and then I couldn't get the onboard LAN to install at all. I could install the driver, but the onboard LAN wouldn't show up in Device Manager.

I originally thought it was a driver conflict too, so it's also odd that now with server4pc installed the card does scan for channels in the Technistat viewer and in Media Portal.

 

[Paranoid Delusion]

so it's also odd that now with server4pc installed

No wonder it's showing up as a network adapter, that's the way the software\driver has been written, so it needs all these components for MP to recognise it.

it looks like they have not followed BDA guidelines for this driver, ie it will not work without assistance from it own software being installed as well.

Glad too hear it now being able to scan.

 

[Deusxmachina]

Yep, looks like it's written to go under Network Adapters due to having some kind of internal broadband link or something. I read a post on the DVBViewer forum from someone who installed everything but then uninstalled various things to get it to work. I think he got it to list under Sound, Video by doing that, but not fully sure yet, still PM'ing with him.

Somehow I got it to list under Sound, Video on my other computer, and it worked great. I had installed DVBViewer and the other things and then uninstalled various parts before trying Media Portal. Maybe that's the key. I think the magic formula is there, I just need to figure out what it is.

If a local store had any TV cards on sale today, I don't think I'd be bothering with this anymore, though.

Disabling LAN and going in safemode and all that didn't work, by the way. Same old thing, the computer uses the card as a LAN adapter. Was hoping it would have installed it to Sound, Video, but nope.

 

[Paranoid Delusion]

Made by "Broadband Technologies Inc" so it thinks its networking

sorry could not resist the pun, but again as far as customer service goes, severe lack of updates for this card is unforgivable.