Guest apprentice idiot Posted July 15, 2007 Posted July 15, 2007 Having just installed an LG L226WA monitor, the startup button on my xpc SD37P2 has been rendered quasi-inoperative. Whether on reboot from hibernate or cold fire-up, it takes up to one half-hour to cajole and trick my system into getting underway. Anyone know how to fix this?
Guest Tony Sperling Posted July 15, 2007 Posted July 15, 2007 Re: Shuttle startup button quasi-useless with new monitor Are you running a multi-display setup, or did you exchange the old one? Since multiple displays are supported on most hardware today - did you completely un-install the old monitor? If you are having both connected, some trickery may be required to get it working. Many Graphics Cards supporting multiple outputs are only having digital output for the second display, if I'm not mistaken??? Tony. . . "apprentice idiot" <apprenticeidiot@discussions.microsoft.com> wrote in message news:9512E6CE-ABFF-4199-976A-D8E7F08F44DB@microsoft.com... > Having just installed an LG L226WA monitor, the startup button on my xpc > SD37P2 has been rendered quasi-inoperative. Whether on reboot from hibernate > or cold fire-up, it takes up to one half-hour to cajole and trick my system > into getting underway. > > Anyone know how to fix this?
Guest apprentice idiot Posted July 15, 2007 Posted July 15, 2007 Re: Shuttle startup button quasi-useless with new monitor No, I simply went flatscreen. My NVIDIA card would have handled both types of display. But as I'm using single, this is not the case. Any other suggestions? "Tony Sperling" wrote: > Are you running a multi-display setup, or did you exchange the old one? > Since multiple displays are supported on most hardware today - did you > completely un-install the old monitor? If you are having both connected, > some trickery may be required to get it working. Many Graphics Cards > supporting multiple outputs are only having digital output for the second > display, if I'm not mistaken??? > > > Tony. . . > > > "apprentice idiot" <apprenticeidiot@discussions.microsoft.com> wrote in > message news:9512E6CE-ABFF-4199-976A-D8E7F08F44DB@microsoft.com... > > Having just installed an LG L226WA monitor, the startup button on my xpc > > SD37P2 has been rendered quasi-inoperative. Whether on reboot from > hibernate > > or cold fire-up, it takes up to one half-hour to cajole and trick my > system > > into getting underway. > > > > Anyone know how to fix this? > > >
Guest Tony Sperling Posted July 15, 2007 Posted July 15, 2007 Re: Shuttle startup button quasi-useless with new monitor I'm about to go down and order a 30" myself, so have no real experience yet - first, I would try and uninstall the graphics card via Device Manager and the display driver too (Software Removal), then do a reboot (coldboot) into VGA and have Windows find the thing and set it up again. Please let us hear of any 'funny stuff' you experience, I'd like to be prepared when I go dip my toes. Tony. . . (Fail to prepare, and you'll prepare to fail!) ******************************** "apprentice idiot" <apprenticeidiot@discussions.microsoft.com> wrote in message news:A06EB160-02E6-4D83-B6E4-434884C49B4B@microsoft.com... > No, I simply went flatscreen. My NVIDIA card would have handled both types of > display. But as I'm using single, this is not the case. > Any other suggestions? > > "Tony Sperling" wrote: > > > Are you running a multi-display setup, or did you exchange the old one? > > Since multiple displays are supported on most hardware today - did you > > completely un-install the old monitor? If you are having both connected, > > some trickery may be required to get it working. Many Graphics Cards > > supporting multiple outputs are only having digital output for the second > > display, if I'm not mistaken??? > > > > > > Tony. . . > > > > > > "apprentice idiot" <apprenticeidiot@discussions.microsoft.com> wrote in > > message news:9512E6CE-ABFF-4199-976A-D8E7F08F44DB@microsoft.com... > > > Having just installed an LG L226WA monitor, the startup button on my xpc > > > SD37P2 has been rendered quasi-inoperative. Whether on reboot from > > hibernate > > > or cold fire-up, it takes up to one half-hour to cajole and trick my > > system > > > into getting underway. > > > > > > Anyone know how to fix this? > > > > > >
Recommended Posts