problems with Dvico Fusion dual digital

[sub]

I'm now thinking you need two capture sources set up for this one device, one for the "FusionHDTV, BDA Tuner" as device #1, the other for "Bluebird, BDA Tuner" also as device #1. Though this is just there to confuse me, and I dont think its related to your specific error...read on.

After a second look, further down the logs I see what I think is the real error:

07:24:16.948 VERBOSE ConnectPins: 'MPEG2 Transport' to 'MPEG-2 Stream'
07:24:17.073 VERBOSE ConnectPins failed: hr = 80040217

It seems like something is using the device already. Are you running on Windows MCE?

[xela]

I think that both of them are the same card : the Dvico DUAL.
I'm using an older DVICO driver (3.41). I'll try to install the new driver and see what happans. thanks anyway.

[sub]

I think that both of them are the same card : the Dvico DUAL.

Yeah, I'd come to that conclusion aswell, but its strange that they've used different names for each tuner.

[xela]

yes, it is windows MCE.

[sub]

Have you stopped all the ehome services? If not, then MCE will be keep the devices in use, so GB-PVR will fail much like the error I mentioned above.

[xela]

I can see few eh proccesses running. is there a way not to start them at all ?

[sub]

You can probably go into Control Panel -> Administrative Tools -> Services, and view their properties to set them to disabled or manual startup.

[xela]

I did everything, still no luck. the thing is that it's working fine on the MediaPortal so I don't understand. I also stoped the ehome services and uninstalled the MediaPortal. still it's not working.

[sub]

Is it mediaportal thats hanging onto the device? Did you fully stop that software before using GB-PVR?

[xela]

Hi sub, thanks for your help.
After doing anything possible I replaced the dvico dual with dvico dvb-t plus card. the GBPVR again didn't detect any channels. then I replaced the dvico with Compro T300 (thanks god I have 10 different capture cards) and now everything is working. somehow I have the feeling that it has to do with the dvico driver (i tested 2 different versions, 3.41 and 3.50.2).
anyway, thanks for your quick help !