2007-08-30, 04:43 AM
I read the above post after finding it on google. This is in reply to both Oz and taz. I tried opening the GBPVR.db3 file in notepad, don't recommend it :-). In fact, I messed it up so much that it crashed the config program after I tried to open it. So I deleted it. The only thing left to do then was enter the yahoo xml file as the target file for XMLTV under the Capture Sources tab. Config rebuilt the db3 file from scratch, so after that I just followed Oz's instructions, at least those which still applied, as most of the channel data was then gone, but no other data was lost.
Quote:"I was messing around with mine today, here's what I did.So in short, thanks to both of you, who saved me, literally, from a massive headache, and I guess to let you know that what works best is to just delete the db3 file, which is an sqlite file. After that, just update the EPG for yapi2xml, then add it as the XMLTV Capture Source, then click ok, then repeat for other tuners, I guess, and finally remove all unreferenced channels, which will add the channels from the xml file even though nothing is there initially. This worked perfectly for me. The only symptom I had had at the start to set me down this path was pressing the number on my remote for some channels, and getting no response. So if anyone else is getting this strange behavior, your remote is fine. It's the doubling of channels between the Capture Sources tab and the Channels tab. It must be some sort of sqlite corruption of the database file, but deleting that db3 file resets it without losing any other configurations. Hope it helps someone. --Bill
* open the capture source
* manually delete every single channel
* click ok
* remove all the channels from the other tuner
* click ok
* load the yapi2xml xml file for the first tuner
* load the yapi2xml xml file for the second tuner
* go to the channels tab and click remove all unreferenced channels"