2008-11-30, 06:46 PM
Recently, I switched from Yapi2xml to Schedules Direct. In doing so, I nuked the db3 file and reinstalled the tuners from scratch.
When I was using Yapi2xml, it had the habit of getting stuck, and therefore preventing hibernation, completely separate from the VMR9 FSE problem. This is how I've come to notice Yapi2xml popping up in the process manager.
Something is still invoking Yapi2xml as a scheduled task, run under "system". What is causing this, and how can it be rooted out?
When I was using Yapi2xml, it had the habit of getting stuck, and therefore preventing hibernation, completely separate from the VMR9 FSE problem. This is how I've come to notice Yapi2xml popping up in the process manager.
Something is still invoking Yapi2xml as a scheduled task, run under "system". What is causing this, and how can it be rooted out?
