Ron Kirschner said:
I'm running vista business on HPDC5750 using old 17" CRT monitor. After
someone connects using Remote Desktop, I cannot get display back until PC
hibernates and is re-awakened. Just moved to new location and can't get
display at all, even though remote desktop connection works and device
manager shows all as OK. Have tired 2 different monitors. any idea how
to fix??
Hi Ron,
I dunno the exact answer, but ... this is likely to be a function of your
graphics card and driver, more than the monitor you are using.
After the screen has gone blank, and you then resume an interactive console
session, Windows will notify the graphics driver that it should star showng
pictures "locally", again. The driver in turn will cause the graphics card
to send a signal to the monitor over the VGA connection. The monitor
responds with a so-called EDID response, identifying the monitor to the
graphics subsystem. The graphics card passes the EDID structure to the
driver, which uses it to determine the properties of the monitor. The
graphics driver should then open a normal VGA working connection from
graphics card to monitor, and your local display resumes.
If part of this process breaks down, the screen will remain blank. After the
machine hibernetes and re-awakes, it follows a similar pattern but
(presumably) there is a slightly different path of logic, because this time,
it works. So, either:
- the driver does not signal the card;
- the card does not signal the monitor;
- the monitor does not respond with an EDID;
- the graphics card does not respond to the monitor's EDID; or
- the driver does not handle the EDID is receives from the card.
Some monitors do not provide reliable EDID info; but the more common source
of problems is in the graphics card, and graphics card driver.
I think the DC5750 has an integrated ATI graphics card? If so, there won't
be much scope for replacing it. Your best bet in that case would be to make
sure you have the latest video driver from the HP website - it looks like
they released an updated driver in November. If you don't have this latest
HP driver, that would be the first thing to try.
If you have an DVI LCD monitor handy, it would be worth testing that, at
least as a diagnostic - that will exercise the DVI code path instead of the
VGA code path in the graphics driver. Generally, DVI monitors seem to handle
EDID information more reliably than older VGA monitors.
Other folks may have extra ideas for you, I hope this helps a bit.
