This is a bug in TV Pack. The guide will become corrupt, and scheduled recordings stop taking place. Until a patch is released by MSFT, your only option is to completely go through TV setup again. Even then, there's no guarantee that the guide won't become corrupt again.
aaronp:.... I think S3 standby in Vista is still quite buggy and unreliable. I've had problems on 2 different computers with 3 different video cards. Aaron
I have to disagree. As long as you have reasonably new hardware and BIOS (bug-free ACPI support), and the latest of any manufacturers' drivers, S3 sleep works very reliably, with no need for any standby tool. I accept that some manuafcturers' drivers are worse than others - for example when I had a Hauppauge tuner card it would rarely sleep on idle (and they acknowledged the bug), but with BlackGold everything works superbly. Sleep wake sleep wake, wake to record, sleep after record, away mode when recording, then sleep after that, correct sleep on idle, etc.
I would however say that when I tried TV Pack it did screw that reliability completely. At least in my experience.
The problem with Media Center is that everybody's experience is so different. That's not a bug, but a bit of a general Windows architectural flaw in my opinion. Maybe too much is delegated down to drivers.
JB
aaronp:Control Panel - Administrative Tools - Event ViewerLook at the System and Media Center logs for that time span, maybe there are some clues. I think S3 standby in Vista is still quite buggy and unreliable. I've had problems on 2 different computers with 3 different video cards.
In my experience with the TV Pack guide corruption bug, there would be no evidence in Event Viewer of missed recordings. The recordings would show up in my scheduled recordings list for that day, and when the time would come for the PC to wake and record, nothing happened. No errors, no warnings, no crash files generated, no Media Center log entries created noting missed recordings or scheduling conflicts -- it'd just miss the recording.
And I agree with the previous commenter. With fairly new hardware, S3 in Vista is very reliable. The only problems I've had involved the PC randomly waking at unwanted times when I played around with installing WebGuide.
Well I guess that qualifies as fairly new hardware.
For what it's worth, my setup (full-time HTPC) is an Asus M2A-VM Mobo, AMD Sempron, and integrated ATI X1250 graphics. I switched to the Asus about a year ago that from a 3 year old Gigabyte Mobo, because I did have S3 sleep problems with that, and was as frustrated as you are now! Also, AMD and ATI are one and the same, and the Asus was an AMD accredited/approved socket AM2 Mobo, so I was fairly sure it would all work together, and it does.
I've got all the latest drivers, but it's worth saying that with standard 'Windows update' audio driver sometimes I'd have problems with either no-sound or distorted sound after wake-up, but with the latest RealTek driver from their website there are no such problems. With very early Catalyst drivers there were also problems with the screen not coming on after wake, but they've all been long-since fixed by ATI.
I guess if there are 'bugs' in the Vista S3 sleep process, then it's in the way it allows drivers to 'break the rules', or at least not do things Microsoft were expecting them to do - otherwise I can't see how everybody's experience is so different.
I wish there was single point of reference for 'Green-Button-User accredited' hardware and drivers, where everyone can rely on it working in the real World, and not just on the manufacturer's say-so.