| The other screen-saver problems had to do with blink,
not "never coming back". This is a new one.
What are the MONITOR's settings? Are you using CDE?
And have you asked for the power-save settings in
the utilities? Is the monitor actually *in* it's
power-down mode, or is the screen just "blanked"?
|
| >> The other screen-saver problems had to do with blink,
>> not "never coming back". This is a new one.
I guess this sounded to me like the problem described in note 1770 of
the alphastation conference (and other notes 1770 refers to). The customer
rebooted to get the screen back.
>> What are the MONITOR's settings?
I'll try to get them and post them here
>> Are you using CDE?
Yes
>> And have you asked for the power-save settings in
>> the utilities?
I'm not sure what you are referring to here. Could you elaborate?
>> Is the monitor actually *in* it's
>> power-down mode, or is the screen just "blanked"?
Will try to verify. Since I'm not on site, do you know the best way I
can have the customer verify this?
John
[Posted by WWW Notes gateway]
|
| One of the system managers at the customer site provided this description
of what happened:
I actually was late that day, and most were back up by the time I got
here. All of our 500's were 'blanked' - the screens were dark like a
screen saver and the system would not wake up regardless of how many
buttons and or keys you pressed. You could rlogin or telnet in from
another host, however. Someone in the group logged in to each one and
rebooted them and they came up fine. However, one person left their
workstation up so I could poke around, which I did, remotely. What I
found was about 5 proccess running the dtlock and dtscreen blank type
command and they seemed to respawn no matter how fast I killed them.
They would die, but very quickly would restart. Nothing I did could
break the lock. I don't think it was the monitors, I think it was
somthing within cde and they way it clicks into powersave mode. No
problems since....
[Posted by WWW Notes gateway]
|