Darklight said:
I am not saying it's the OS but i am sure that some one in an OS related
news group might have had this problem. And if so might be able to help.
What do you have to lose.
Ok just went on the net and found this hope this helps
http://www.overclock.net/t/1384187/gtx-660-ti-dual-monitor-how-to
This is some one who has the same problem you do
http://forums.anandtech.com/showthread.php?t=2289726
this is related to the above
http://www.pcadvisor.co.uk/how-to/pc-peripheral/3365585/how-tell-dvi-i-dvi-d-cables-apart/
The one additional symptom is though, the PC doesn't boot
with one of the connector choices. So it's worse than just
a "single nominated display" rule for BIOS usage.
I'd have said "defective card, send it back", but it
isn't normal for a display choice to cause a BIOS to
freeze up or stop the boot process. The BIOS should
load the VESA BIOS off the video card, and assume it
can run 800x600 or whatever, until the OS comes along
later and changes it.
UEFI could change that, as UEFI is more of a GUI thing.
And I don't really have much useful info on UEFI
boot differences (what matters to it). You would think
they'd still be using VESA BIOS info for that, but you
never know. Maybe a UEFI BIOS actually uses the
EDID info from the monitor ?
Even the notion, that one of the connectors on the
660 is DVI-I and the other one is DVI-D, is a
departure from the norm. I'm not aware of higher
end cards doing that. There are only a few cards,
that did strange things to their DVI connector
(there were some $30 cards, that split what would
normally be a DVI-I into a DVI-D and a VGA connector,
and were sort of sharing them - you couldn't use both
connectors at once, because they shared the same
EDID wiring). The end result, is the cheap cards
look like they're dual head, when in fact they
aren't. The card is functionally single-headed.
A 660 is well above the price range of such
stupidity.
*******
It just occurred to me, a BIOS setting of
Halt On [No Error]
might allow the BIOS to boot with the monitor
not functioning. The default is to have the BIOS
halt on certain errors, and using the [No Error]
option is the best way to get around a design defect.
I had a PC with a low-speed CPU fan, and that's how you'd
get it to boot without dropping into the BIOS. (The
BIOS thought the CPU fan was dead.)
Paul