I'm having the same problem with an Aver M780. It scans a little while for Digital QAM channels and then crashes on 88. I tried your patched Config.exe, but that crashes as well. Sub, are you still looking into this issue? Let me know if I can help with any information. I've added my logs from serveral attempts with your patched Config.exe.
No, I wasnt. I pretty much work on a reminder system. If no asks me about a bug they've reported in the past, you can be pretty sure I'm not looking at it.
Does it find any channels before it gets to this crash on 88?
You'd need to set you logging to flush to disk, and be 'debug' level for any useful log info. Your logs are currently empty, I think because of the flushing setting.
Maybe try creating a c:\temp directory, and adding a HKEY_LOCAL_MACHINE\Software\Devnz\LogPsiProcessing=2 (DWORD) registry setting, then do a scan, then zip and attach the c:\temp\psi.log file, then remove the registry setting. I'll take a look at this log.
Unfortunately there is no useful clues in there. Make sure you remove that registry settings, or it'll cause future performance problems.
Maybe try editing your .\bda\atsc\qam.ini, and set the '87=88,0,0' line to '87=8,0,0' forcing it to not scan 88, then see if the scan proceeds any further.
Sub, my QAM.ini uses frequencies. See attached. I tried what you suggested after using the QAM.ini Manager.exe to create a default with Channel numbers QAM.ini file. I then made the edits so that is looked like '88=8,0,0' instead of '88=88,0,0' - it still crashes on 88=8,0,0.
Just curious, does it write a list of channels that it found before it crashes? (over in the channel list). Or does it crash as soon as it gets a signal?
[SIZE="1"] Server= Asus M3A78-EM, 4 gigs ram, AMD A64 5200+, Windows 7 home premium 32, 1 HVR-1800, 1 PCH A-100, Test Rig, Biostar 880g+, AMD X2 260, 4 gb ram, Windows, 7 Home Premium 32, 1 DCR-2650 cablecard tuner [/SIZE]
[SIZE="1"][/SIZE]