DVI output shows blank screen (GEForce MX)

[boozle]

I have a fairly old PC (see spec below) and recently upgraded to a lovely 22" LG flatron monitor.

I have only ever used the VGA output on my GeForce MX 440 AGP8x 128mb and plugged in using DVI for the first time. Unfortunately I get a blank screen.

- I have installed the LG drivers, and windows does recognize the monitor and its default settings.

- The monitor displays a dark screen at all times (before and during windows boot), if I unplug one cable it says 'check cable' so I know it receiving some sort of signal

- The monitor works using VGA output no problem

- I have updated the graphics card driver to the latest possible. However, the PC BIOS is dated 2003 (I am reluctant ot flash it or the graphics card BIOS since I have no other issues)

Before I take the plunge into flashing my video BIOS, does anyone have any other suggestions? Is there some really obvious piece of kit I have to install? Or setting I have to change?

In regard to BIOS, should I flash the MB BIOS or the Graphics card BIOS? or both? Which one first?

Many thanks,

B

SPEC

MB: MSI k7n2 Delta-L

CPU: AMD Athlon XP 2600

OS: Windows XP sp2

GC: GeForce MX 440 AGP8x 128mb

 

[Toxcity]

Wait, stop... flashing bios's is not gunna help anything.

Have you enabled a second monitor in the NVIDIA drivers? if not try that.

NO FLASHING!

 

[boozle]

I have definately got 2nd monitor activated, as both monitors are recognised, and i can switch between the two and even spread the desktop over both if I wanted... but as soon as I attempt to switch to the DVI output, the screen just appears black.

Any other suggestions?!

 

[nrage]

I have definately got 2nd monitor activated, as both monitors are recognised, and i can switch between the two and even spread the desktop over both if I wanted... but as soon as I attempt to switch to the DVI output, the screen just appears black.

Any other suggestions?!

Dodgy DVI cable? Got another one to try it with?

 

[boozle]

I have tried another cable, that's definately not the issue..