MacBook Pro :: Cannot Detect External Display

I have a 2011 MBP (thunderbolt) that I've had for about a year now. I use it daily at work, with an external LCD monitor connected with a mini-dvi -> DVI, no problem, except for the occasional need to restart when first connected.

However, at home I have an AOC Razor 24" monitor that until recently was connected to my home PC via HDMI, working just fine. However, my PC died and now I would very much like to be able to use this monitor at home until such a time when I get around to finding a desktop replacement. My MacBook Pro, however, has completely different ideas it seems... It completely refuses to recognise the monitor. I don't get the blue "flash" and it doesn't show up int eh display panel at all, not "sleeping" or otherwise, it simply looks as if it's not there.

Having trawled the forums, I've done the Jan/Feb firmware update, I've tried two different HDMI converters (One the Moshi from my local Apple retailer, the other a no-name brand converter, which works fine elsewhere), I've even tried a mini-dvi -> DVI -> HDMI converter (I know, I didn't expect it to work, but when you're at then end of your wits, you're at the end of your wits ). I've gone through three HDMI cables and tried an assortment of "black magic" solutions found on the net, with the adapter half-way plugged in, resetting the PROM, closing/opening the lid, running gfxCardStatus ( just in case it did something ) and checking the monitor elsewhere.

The only thing I haven't done (that I can think of) is swap the actual MBP,however, as mentioned, I use an external DVI monitor every day, so it doesn't seem likely that that's where the problem is... I'm guessing it's got to do with how the monitor handles HDMI or some such thing but I don't seem to be able to find much of a comment from anyone else on the net, so here I am... I considered sacrificing a goat at full moon, but I'm not entirely convinced that'll do much either and I upgraded to Lion as I saw a throwaway comment somewhere from someone, indicating that that might or might not have helped them with a slightly similar problem... So this problem now spans 10.6 AND 10.7... 

Info:
MacBook Pro, Mac OS X (10.7.3)