themisfit610
Golden Member
Hey all,
So I just got a new workstation at work - it's a Q6600 from Dell with an x38 chipset - pretty solid overall. It runs XP Pro, 4 GB of RAM (3 recognized) and a 9600gt
Anyway, my job is to encode video. Here's the problem:
I queue up a lot of stuff to run overnight. This system ideally would run 24/7, as the other encoder boxes do. However, when I walk away at night - the group policy of our domain mandates that the screensaver comes on after 10 minutes, and the account locks 10 minutes after that.
When the PC is locked, all encoding jobs stop.
You tell me.
I've verified this by starting an encode, locking the workstation manually, and coming back 10 minutes later with no frames encoded.
This doesn't make sense! Locking a workstation should not slow down active processes.
The process priorities of my encode(s) (usually run two in parallel to max out the quad) are always set to "below normal" which should be more than enough to grab all idle processor time. Heck - when I'm using the system, the CPU is always pegged at 100%.
I've disabled any and all power management - and just to be clear - the system is NOT going into sleep, standby, or hibernate.
Infuriating! Ideas?
~Misfit
So I just got a new workstation at work - it's a Q6600 from Dell with an x38 chipset - pretty solid overall. It runs XP Pro, 4 GB of RAM (3 recognized) and a 9600gt
Anyway, my job is to encode video. Here's the problem:
I queue up a lot of stuff to run overnight. This system ideally would run 24/7, as the other encoder boxes do. However, when I walk away at night - the group policy of our domain mandates that the screensaver comes on after 10 minutes, and the account locks 10 minutes after that.
When the PC is locked, all encoding jobs stop.
You tell me.
I've verified this by starting an encode, locking the workstation manually, and coming back 10 minutes later with no frames encoded.
This doesn't make sense! Locking a workstation should not slow down active processes.
The process priorities of my encode(s) (usually run two in parallel to max out the quad) are always set to "below normal" which should be more than enough to grab all idle processor time. Heck - when I'm using the system, the CPU is always pegged at 100%.
I've disabled any and all power management - and just to be clear - the system is NOT going into sleep, standby, or hibernate.
Infuriating! Ideas?
~Misfit
