Let me give you an example of the frustrating testing process this issue is putting me, and no doubt other XMLTV users, through.
Yesterday the scheduled 8am Program Guide Load aborted after 10 minutes, which is the problem I am trying to solve. So I changed yet another Windows Power Option setting, then changed MC to run the Program Guide Load at 10am, which of course forced a manual Program Guide Load to run. I checked at about 4pm to see if the Program Guide Load had indeed run, and it had not. I decided to leave the schedule set for 10am, as any further change would result in another manual Program Guide Load.
This morning at 10:20am I checked if the HTPC was awake. As it wasn't, I assumed that either the Program Guide Load had run and aborted after 10 minutes, or it had completed in the usual 18 minutes and the HTPC has been put straight back to sleep. So I woke the HTPC to see what had happened. I use the EPGC logs to see what whether the Program Guide Load has run correctly, as I can't make sense of the MC logs and I don't want to touch MC before I check the Program Guide Load status.
Well, waking the HTPC kicked off the Program Guide Load, and EPGC started writing into its log as I was checking it! I forgot that sometimes after a manual Program Guide Load the following day's scheduled Program Guide Load can run up to 2 hours after the scheduled time. I have observed that previously. Usually after the first automatic Program Guide Load runs correctly, although late, the following days it runs on time. So it looked like it had taken me 26 hours to run one test, and the testing method had failed !!!
Fortunately MC still ran the Program Guide Load process automatically, and it still behaved as it had before. That is, the Program Guide Load aborted after 10 minutes and so EPGC failed to complete, so no XMLTV file was created, and the Program Guide was not updated.
If the MC Program Guide Load always ran first time, on time, as scheduled, instead of following some undefined internal rules as to when it may or may not run, then I could have completed this testing and perhaps solved the problem in a few hours. Or at least reported that there definitely is a problem with how MC runs the automatic Program Guide Load. Now I have to think if there is anything else about my HTPC setup that could be causing the automatic Program Guide Load to abort after 10 minutes, and spend another couple of days testing it, if I can think of something.
But I can tell you that it looks like MC is killing the automatic Program Guide Load process arbitrarily after 10 minutes, even though the external EPGC program has not completed. Is there some kind of time out programed in MC somewhere. Certainly I couldn't find any setting for a maximum time the Program Guide Load process is allowed to run. Having such a setting wouldn't even make sense, given that MC runs an external program to collect XMLTV data. What if I was running a series of program to gather data from multiple sources, and then running another program to combine the result? That sort of processing is likely to take more than 10 minutes.
Please make MC respect the Program Guide Load schedule, first time, every time, and on time, not delayed by some unknown variable factor. THANK YOU.
EDIT: Thanks Jim. Hopefully this can be sorted out. I appreciate your input.