Comcast Conversion Problems....

[LowEntropy]

Here's a revised set....BGd

[sub]

Can you zip and attach your .\BDA\ASTC directory? Somewhere its getting an odd tuning request, and I'm trying to work out from where exactly.

[johnsonx42]

I think LowEntropy may have modified or replaced his QAM.ini file based on advice given in posts 16 & 19.

[sub]

Yeah, I'm wondering if the qam.ini has some missing numbers or something.

[LowEntropy]

You were both absolutely correct there was a problem with the qam.ini file - once I fixed that it started to scan...that's the good news. The bad news is that once again (sigh) it came up empty. I initially used the qam.ini file produced by the qam.ini manager but then I modified it to focus specifically on frequencies that I know get significant hits with the WinTV scan. The GBPVR scan just cannot find anything.....BGD

[sub]

Do a scan, then post the config.exe.log and config.exe-native.log and I'll see if anything stands out.

[LowEntropy]

Thanks for hanging in there Sub - here are the logs from a scan I did earlier today....BGD

[sub]

I cant see any sign of errors there, but the device never manages to lock on to a signal, like its the wrong frequencies or the cable isnt connected.

[whurlston]

Scan using the full "Frequency with Center channel" setting from the QAM.ini manager.

[LowEntropy]

Whurlston - ran the center channel scan and once again turned up empty (and it crashed my machine). I'll humbly suggest that this appears to be an issue with several devices (Hauppage HVR 1600, 1800, 1950) as evidenced by this recemt (7-17-09) thread in the Hardware forum....

--------------------
steveum (Member)

I seem to be in a similar situation as this thread author. I have just added a 1800 to my system. I already have a 1600 in the system with QAM working great. WinTv 6 seems to find QAM channels on both cards. I say seem because i really get confused when using the WinTv suite manager, but when I do the scan i get two sets of QAM channels. I assume a set for each card.

I have the latest channel scan patch from the survival guide. I am running 1.3.11. I ran the bat for re-register the AX files. I have run the QAM.INI manager and tried several different variations. I have connected the COAX cable that had been connected to my 1600 directly to my 1800 with no new splitters. I am using the latest driver from the haupauge site. I was seeing the scan crash when I used the driver from 4.8a CD, but that seems to go away with the driver in hcw85bda_27176.zip.

I have attached my log files. I had just made several different scan attempts with various QAM.INI files.
--------------------------------------

I could be mistaken but it looks like there's little I can do from my end....I'll keep my fingers crossed that there's some type of resolution. BGD