zap2it.xml file corrupt

[David]

Sub,

I have GB-PVR save the zap2it.xml file for processing by zaptools. Several times now, I've noticed that zapimport fails which I only notice when the EWA doesn't display the extended information from zaptools.

When this happens I find that the new XML data set is smaller than a previous data set, but the zap2it.xml file is not being completely re-written by GB-PVR. The new data is over writing the beginning of the existing file. The XML is then considered corrupt due to the garbage at the end of the file (left over from a previous download). zapimport appears to crash on the bad file and IE 7 is not able to parse and display it either. I thought maybe it was a fluke, but it has happened at least 3 times now.

I've updated my postEPGUpdate.bat file to delete the zap2it.xml file (after saving off a copy) when done processing.

Sorry, I have not kept a corrupt zap2it.xml file to show you.

[sub]

I am aware of a bug that can cause this, and I will try to fix it in the next release.

In my own defense, I'd only ever intended this file to be used by myself - sort of a debug file that I could open up and manually look at a few show times etc.

[David]

I am aware of a bug that can cause this, and I will try to fix it in the next release.

In my own defense, I'd only ever intended this file to be used by myself - sort of a debug file that I could open up and manually look at a few show times etc.

All your unintended features are way too good to not be used. I like not having to hit up zap2it for the same dataset twice.

I am fairly confident that I fixed the problem for myself, but figured that you would like to know my findings and fix it for everyone.

Thank You!

[gkreis]

I am fairly confident that I fixed the problem for myself, but figured that you would like to know my findings and fix it for everyone.

This has been happening to me as well, for probably 70% of the days in the last two weeks. I just started to investigate it when I came across this thread.

What was your fix specifically? When you made a copy of the file, what did you name it and how does that help?

[David]

This is only an issue if you have configured GB-PVR to save the zap2it.xml file AND you have configured zapimport to use the zap2it.xml file instead of downloading new data.

My fix was to delete the zap2it.xml file after running zapimport in my PostEPGupdate.bat file. This way GB-PVR has to create a new file instead of over writing the old one.

I simply included the following line:

del c:\zap2it.xml

[sub]

I've corrected this bug for the next release.

[gkreis]

This is only an issue if you have configured GB-PVR to save the zap2it.xml file AND you have configured zapimport to use the zap2it.xml file instead of downloading new data.

Sure enough, that is what I have done.... I hate to tax the Zap2It folks that are nice enough to offer this service free.

My fix was to delete the zap2it.xml file after running zapimport in my PostEPGupdate.bat file. This way GB-PVR has to create a new file instead of over writing the old one.

I simply included the following line:

del c:\zap2it.xml

Makes sense. I was confused when you said you copied first. That threw me for a loop.... ;-)