Looking at the results you're getting, I'm not too surprised, Mark.
Clearly there's a difference between the results returned from our
respective machines - which means that my suggestion can't be
considered as a general approach.
To demonstrate why I suggested what I did, I've added the output from
my test machine for comparison:
This is the entire output of "pmset -g" on my laptop:
Currently in use:
womp 1
dps 1
dim 0
reduce 0
autorestart 0
spindown 10
sleep 0
acwake 0
lidwake 1
ring 0
No AC connection:
----------------
Active Profiles:
Battery Power 1*
AC Power -1
Currently in use:
acwake 0
sleep 10
autorestart 0
ring 0
halfdim 1
reduce 0
disksleep 10
displaysleep 2
lidwake 1
lessbright 1
----------------
With AC connection:
----------------
Active Profiles:
Battery Power 1
AC Power -1*
Currently in use:
womp 1
acwake 0
sleep 70
autorestart 0
ring 1
halfdim 1
reduce 0
disksleep 10
displaysleep 43
lidwake 1
----------------
And here's the output of "pmset -g cap"
Capabilities:
dim
spindown
sleep
reduce
dps
womp
ring
acwake
autorestart
lidwake
No AC connection:
----------------
Capabilities for Battery Power:
displaysleep
disksleep
sleep
reduce
ring
acwake
autorestart
lidwake
lessbright
halfdim
----------------
With AC connection:
----------------
Capabilities for AC Power:
displaysleep
disksleep
sleep
reduce
womp
ring
acwake
autorestart
lidwake
halfdim
----------------
Back to the drawing board, I guess. I wonder if the profiles, etc.
are available elsewhere on your machine...
