To be honest, I'm not really sure. There isnt any obvious cause in your logs.
trummel Wrote:I've seen some notes about removing some frequencies from the scan range, but I am not sure how to do that.
If it seems to consistently crash on the same frequency, you might have to try that. You'd have to find your satellite's ini file in "C:\Program Files\devnz\gbpvr\BDA\DVB-S", and change the frequencies to for it to not lock the signal. For example,
I have a 3200 and have had similar problems to yours, appart from applying the scan crash patch in the survuval guide I also had to remove a few scan frequencies as Sub says.
I also had to remove any entries in the sattelite ini file with S2 entries at end of them, this wont be a problem for you if your using Subs packaged ini files but may affect you if you have updated the file from king of sat or joshyfuns web site.
I also found that if scanning failed I had to remove the capture device from the config app and re-boot otherwise the next scan would find the same 5 channels 20 times over or similar.
I'll give all of the suggestions a go this evening and let you know how I get on. Sub, if you can give me a brief guide how to capture the stream, I am happy to do that and have an ftp server you can grab it from.
I am in the UK and trying to scan Astra 2A,2B,2D at 28.2. It scans without problem using the Technotrend software. I have to admit to very little understanding of the way dvb-s signals and channels work. I am also confused by all of the references to Diseqc and LNB's. I have a fixed dish with 4 cables. Can anyone suggest a good idiots guide?
I tried various permutations of everyones suggestions. Without any significant improvement. The latest iteration is to remove all but 3 of the frequencies from the 0282.ini file. Bizarrely, the config.exe still produced the crashed message during the first range, but the program appears to have continued to scan through the second and third ranges and found a decent batch of channels.
I've tried picking different frequencies as my 3 and the crash seems to occur whichever set I use. It also seems to happen at random times during the scan. In most crashes the scan continues after the crash for another minute or 2 before it gives up completely. If the last frequency has completed before it locks completely, then the scanned channels can be saved. Although it still locks up as I exit the scan.
I also tried it with just a single range. It still crashes some, but not every time. That leads me to think it may not be stream content that is at fault.