Active power profile at Welcome Screen

This is a query left over from XP days; it was never properly answered
(could recite design intentions) properly or at all. I'm hoping
knowledge in Win 7 community exceeds that in XP.

Consider a set of scenarios where 0, 1, 2 or more users are logged on to
a Win 7 machine. Each user has a separate (and different power profile
selected, i.e., no two users' profiles agree on all of type of sleep
(suspend or hibernate), time to dim monitor, time to initiate sleep, and
whether a password is necessary to resume from the welcome screen when
the suspend is broken. The machine is currently at the welcome screen.

Which user's power profile controls behavior?

Don't suggest testing as that assumes that one could control sporadic
process activities, schedules, etc. Little bits of execution can reset
many of the suspend-related timers and a controlled experiment would
need to track or control them well enough to answer the question WITHOUT
disturbing the environment enough to effect the answers. This would
probably require recompiling the OS with hooks. So my question concerns
the DESIGN INTENT.

Any help appreciated.
--
Jeff Barnett

On 11/2/2014 3:55 PM, Jeff Barnett wrote:
This is a query left over from XP days; it was never properly answered
(could recite design intentions) properly or at all. I'm hoping
knowledge in Win 7 community exceeds that in XP.

Consider a set of scenarios where 0, 1, 2 or more users are logged on to
a Win 7 machine. Each user has a separate (and different power profile
selected, i.e., no two users' profiles agree on all of type of sleep
(suspend or hibernate), time to dim monitor, time to initiate sleep, and
whether a password is necessary to resume from the welcome screen when
the suspend is broken. The machine is currently at the welcome screen.

Which user's power profile controls behavior?

Don't suggest testing as that assumes that one could control sporadic
process activities, schedules, etc. Little bits of execution can reset
many of the suspend-related timers and a controlled experiment would
need to track or control them well enough to answer the question WITHOUT
disturbing the environment enough to effect the answers. This would
probably require recompiling the OS with hooks. So my question concerns
the DESIGN INTENT.

Any help appreciated.

My experience has been that the last logged on user's power profile is
what is active at the log-on screen. YMMV

Bob I wrote, On 11/2/2014 8:22 PM:


On 11/2/2014 3:55 PM, Jeff Barnett wrote:
This is a query left over from XP days; it was never properly answered
(could recite design intentions) properly or at all. I'm hoping
knowledge in Win 7 community exceeds that in XP.

Consider a set of scenarios where 0, 1, 2 or more users are logged on to
a Win 7 machine. Each user has a separate (and different power profile
selected, i.e., no two users' profiles agree on all of type of sleep
(suspend or hibernate), time to dim monitor, time to initiate sleep, and
whether a password is necessary to resume from the welcome screen when
the suspend is broken. The machine is currently at the welcome screen.

Which user's power profile controls behavior?

Don't suggest testing as that assumes that one could control sporadic
process activities, schedules, etc. Little bits of execution can reset
many of the suspend-related timers and a controlled experiment would
need to track or control them well enough to answer the question WITHOUT
disturbing the environment enough to effect the answers. This would
probably require recompiling the OS with hooks. So my question concerns
the DESIGN INTENT.

Any help appreciated.

My experience has been that the last logged on user's power profile is
what is active at the log-on screen. YMMV

Well do you mean the last user to LOG IN or the last user to RETURN to
the welcome screen? And what about after you boot up, nobody logs on,
and the machine sits there?

Has anyone seen a principals of operation document on this? You would
think this would be a well-covered design area since most of ACPI and
plug-and-play spec is about energy states and management. I haven't read
enough of the UEFI spec to say, but I imagine that too is big on energy
management.

Does anyone know how similar issues are addressed by the UNIX family OS?
--
Jeff Barnett

On 11/4/2014 12:47 AM, Jeff Barnett wrote:
Bob I wrote, On 11/2/2014 8:22 PM:


On 11/2/2014 3:55 PM, Jeff Barnett wrote:
This is a query left over from XP days; it was never properly answered
(could recite design intentions) properly or at all. I'm hoping
knowledge in Win 7 community exceeds that in XP.

Consider a set of scenarios where 0, 1, 2 or more users are logged on to
a Win 7 machine. Each user has a separate (and different power profile
selected, i.e., no two users' profiles agree on all of type of sleep
(suspend or hibernate), time to dim monitor, time to initiate sleep, and
whether a password is necessary to resume from the welcome screen when
the suspend is broken. The machine is currently at the welcome screen.

Which user's power profile controls behavior?

Don't suggest testing as that assumes that one could control sporadic
process activities, schedules, etc. Little bits of execution can reset
many of the suspend-related timers and a controlled experiment would
need to track or control them well enough to answer the question WITHOUT
disturbing the environment enough to effect the answers. This would
probably require recompiling the OS with hooks. So my question concerns
the DESIGN INTENT.

Any help appreciated.

My experience has been that the last logged on user's power profile is
what is active at the log-on screen. YMMV

Well do you mean the last user to LOG IN or the last user to RETURN to
the welcome screen? And what about after you boot up, nobody logs on,
and the machine sits there?

Has anyone seen a principals of operation document on this? You would
think this would be a well-covered design area since most of ACPI and
plug-and-play spec is about energy states and management. I haven't read
enough of the UEFI spec to say, but I imagine that too is big on energy
management.

Does anyone know how similar issues are addressed by the UNIX family OS?

I've had the multiuser argument with the linux gurus.
My take is that win7 is a SINGLE user operating system.
Yes, you can "switch user" to a second single user leaving some processes
running attached to the first user. But the first user can't really do
anything except wait.
It would be dangerous to let the "switched-to"
user change the power profile...or anything that could affect processes
initiated by the initial/first user to "logon".
That leads to the problem that your system may behave differently if
you switch-to rather than logon.

I'd also like to learn what actually happens.

On 11/4/2014 2:47 AM, Jeff Barnett wrote:
Bob I wrote, On 11/2/2014 8:22 PM:


On 11/2/2014 3:55 PM, Jeff Barnett wrote:
This is a query left over from XP days; it was never properly answered
(could recite design intentions) properly or at all. I'm hoping
knowledge in Win 7 community exceeds that in XP.

Consider a set of scenarios where 0, 1, 2 or more users are logged on to
a Win 7 machine. Each user has a separate (and different power profile
selected, i.e., no two users' profiles agree on all of type of sleep
(suspend or hibernate), time to dim monitor, time to initiate sleep, and
whether a password is necessary to resume from the welcome screen when
the suspend is broken. The machine is currently at the welcome screen.

Which user's power profile controls behavior?

Don't suggest testing as that assumes that one could control sporadic
process activities, schedules, etc. Little bits of execution can reset
many of the suspend-related timers and a controlled experiment would
need to track or control them well enough to answer the question WITHOUT
disturbing the environment enough to effect the answers. This would
probably require recompiling the OS with hooks. So my question concerns
the DESIGN INTENT.

Any help appreciated.

My experience has been that the last logged on user's power profile is
what is active at the log-on screen. YMMV

Well do you mean the last user to LOG IN or the last user to RETURN to
the welcome screen? And what about after you boot up, nobody logs on,
and the machine sits there?


The LAST one to LOG-ON, re-boot still has the last one that logged on.

Bob I wrote, On 11/4/2014 5:08 PM:


On 11/4/2014 2:47 AM, Jeff Barnett wrote:
Bob I wrote, On 11/2/2014 8:22 PM:


On 11/2/2014 3:55 PM, Jeff Barnett wrote:
This is a query left over from XP days; it was never properly answered
(could recite design intentions) properly or at all. I'm hoping
knowledge in Win 7 community exceeds that in XP.

Consider a set of scenarios where 0, 1, 2 or more users are logged
on to
a Win 7 machine. Each user has a separate (and different power profile
selected, i.e., no two users' profiles agree on all of type of sleep
(suspend or hibernate), time to dim monitor, time to initiate sleep,
and
whether a password is necessary to resume from the welcome screen when
the suspend is broken. The machine is currently at the welcome screen.

Which user's power profile controls behavior?

Don't suggest testing as that assumes that one could control sporadic
process activities, schedules, etc. Little bits of execution can reset
many of the suspend-related timers and a controlled experiment would
need to track or control them well enough to answer the question
WITHOUT
disturbing the environment enough to effect the answers. This would
probably require recompiling the OS with hooks. So my question concerns
the DESIGN INTENT.

Any help appreciated.

My experience has been that the last logged on user's power profile is
what is active at the log-on screen. YMMV

Well do you mean the last user to LOG IN or the last user to RETURN to
the welcome screen? And what about after you boot up, nobody logs on,
and the machine sits there?


The LAST one to LOG-ON, re-boot still has the last one that logged on.

If I understand this sentence, it's wrong. The last one to log on is not
necessarily the last one to return to the welcome screen. Think of two
or more users who have logged on and use the computer randomly for five
minutes at a time and return to the welcome screen after that period.
The order of log ons has no necessary relationship to the order of use.
--
Jeff Barnett