Asus PHC3-100 ATSC/QAM tuner

[Hobbes]

When I changed the filter_tuner line as requested a message box with the text below appears when I try to do a scan.

Code:

GB-PVR was unable to start the BDA device you have configured.
Check the device is configured properly, and not already in use

Even though the message box appears, it still does the scan. I just move the box out of the way to see the scan progress. I tried this with the same 5 choices using QAM.ini manager but still did not receive any QAM channels.

Hobbes

[whurlston]

That error usually occurs when another application has control of the device. Mak sure that TotalMedia is not running. I believe they have a tray app that may need to be closed as well.

[Hobbes]

I had shutdown the tray icon for TotalMedia before trying the scans but just to be sure I uninstalled TotalMedia and got the same message box about not being able to start the BDA device. It is not looking good for QAM channels using GBPVR with this tuner card.

Hobbes

[whurlston]

Yeah, I'm not sure what else you can try, sorry.

[Hobbes]

Whurlston,

Thanks for your help.

Hobbes

[whurlston]

One last thing you can try:

Edit your config.xml file to read:

Code:

<BDAUseGenericNPForATSC>true</BDAUseGenericNPForATSC>

If that setting doesn't exist, you can add it.

Then set the bda.ini entry back to the QAM/ATSC tuner entry.

[Hobbes]

I changed the filter_tuner line in bda.ini and also added the new line to config.xml. When I tried to perform a scan I got both the message box about not being able to start the bda device and also a .NET Framework unhandled exception. I included a pic of the framework exception and the text from the details.

Just to be sure that the new line in config.xml caused the exception I changed it to 'false' and it did not generate the error but of course it did not lock onto any QAM channels as before.

Hobbes

[sub]

I changed the filter_tuner line in bda.ini and also added the new line to config.xml. When I tried to perform a scan I got both the message box about not being able to start the bda device and also a .NET Framework unhandled exception. I included a pic of the framework exception and the text from the details.

Just to be sure that the new line in config.xml caused the exception I changed it to 'false' and it did not generate the error but of course it did not lock onto any QAM channels as before.

Hobbes

Can you reproduce this error, and post the config.exe.log?

[Hobbes]

Config.exe.log is attached.

Hobbes

[sub]

Can you also post the config.exe-native.log?