must exit gbpvr to reflect timezone change!

[sub]

The same thing is happening here. I'm running Windows 2000 and using Zap2it for epg. Zap2it schedules are correct on their site, but GBPVR times are 1 hour off despite having run TZEdit. I've restarted the GBPVR service and reimported the epg, but still no joy .

GB-PVR hasnt had a bug or change in this area for over two years now, and previous daylight savings changes have been fine, so I'm pretty confident there is no GB-PVR bug. During EPG importation GB-PVR just asks Windows to convert the zap2it supplied UTC date/time into a local time, which are saved in the database. GB-PVR itself doesnt care when daylight savings starts and begins, and doesnt even know (or need to).

It'll be either the windows patch isnt applied correctly, or your PC timezone isnt set correctly, or zap2it is supplying the incorrect times.

Remember to do an 'Empty EPG' first when testing any changes, or you'll continue to see listings with the original times.

[cmgeek2]

Remember also that the conversion to local time is done at the time the listings are imported. So if you're changing any settings to try and fix your problem, you'll need to do an 'empty epg' to get rid of existing show listings with the incorrect times.

If you just applied the MS patch before posting, then this was probably your problem. You should of applied it at least a week or so ago (assuming you have about a weeks worth of listings), then it all would have rolled by smoothly.

Thanks Sub, that worked perfectly. :o I can't believe I forgot to update this machine

[markw]

Remember to do an 'Empty EPG' first when testing any changes, or you'll continue to see listings with the original times.

That was it! I don't recall having to do that for the other time changes since I've been using GBPVR, but maybe I didn't record anything until the new data was used. I assume unless the EPG is emptied it only appends new data, and if I had looked at the most recently imported data later in the week it would have reflected the correct times even though today's data didn't? If that's so, I will have to flush the EPG at every time change?

Thanks for the quick reply. You're as responsive as your software .

[sub]

Remember to do an 'Empty EPG' first when testing any changes, or you'll continue to see listings with the original times.

That was it! I don't recall having to do that for the other time changes since I've been using GBPVR, but maybe I didn't record anything until the new data was used. I assume unless the EPG is emptied it only appends new data, and if I had looked at the most recently imported data later in the week it would have reflected the correct times even though today's data didn't? If that's so, I will have to flush the EPG at every time change?

You wouldnt normally have to empty the EPG, and wouldnt expect anyone to have do this now (unless they've only just applied the Microsoft timezone fix, or havnt applied it yet). ie, you'd only have to do that if sometime in the last few days Windows wasnt able to correctly convert a UTC

When GB-PVR is importing the zap2it listings it ask Windows to convert each of the UTC date/times into a local time, then saves it in the database. For example, a few days ago GB-PVR might have asked Windows to convert "UTC 2007-3-12 14:30" into a local date, and Windows is supposed have been able to do that by correctly taking into account whatever timezone and daylight savings rules would apply at "UTC 2007-3-12 14:30".

[LaserBait]

Remember Win 2000 users: TZedit (http://support.microsoft.com/gp/dst_hu2?systemlist=w32) is your friend, you'll need it! I was beating my head against the wall until I updated with it.