SUBSIM Radio Room Forums - View Single Post

Arclight · 05-08-09, 04:25 AM

Don't mind questions at all, I like speculating.

Card is 8800GTS 512 (G92 core, like the 9 series). Once the problem occured it didn't matter what I installed, but it initially happened while running 182.06 32-bit drivers. Board has Intel P35 chipset.

I think the mix of CRT and LCD monitors might have something to do with it, though I think the lack of support for older CRTs lies at the core; more people are using LCD nowadays so that's where they focused their efforts. For some reason Win7 thinks the CRT can't do more than 60hz unless it's running 1024x768, while XP recognized the screen being capable of 1280x960 @70hz.

2 things to mention: I had Rivatuner set up to force 70hz at 1280x960 at all times, which didn't seem to be working. The problem occured as I was trying to set up a custom res in Nvidia control panel (1280x960 70hz). Clicked the icon for the CRT, set up the res, tested, failed. Tried again, test, succes. But the res got assigned to the LCD instead of the CRT. Deleted it, selected CRT again, set it up, clicked test and went black. Just seems to be some conflict between Win7 and CRTs or Win7 and Nvidia control panel.

Now that I think about it, had an issue with my new install too: couldn't select 75hz for the LCD in Nvidia panel, but could through Win7s own method (display properties>advanced). Definitely something wrong there.

Just before everything went black, my CRT indicated it switched to a 35hz mode. It's almost like the hertzes (?) got "split" between the 2 screens; instead of 1 running at 70 and the other at 75, both got 35 which obviously doesn't work. As if the 2 screens got handled as 1? Sounds really weird, but it's the best sense I can make of it.

The LAN problem was because I have 2 NICs: 1 onboard (realtek) and 1 add-in card (antique 3com leftover) to connect to a switch and other PCs on a network. For some reason windows decided to ignore the onboard and opted to use the add-in card for internet. Probably could have straightend it out, but because the monitors where freaking out I choose to reïnstall. Why the problem occured in the first place is beyond me.

Oh, and that Corsair 650Watt has Seasonic components. Good choice IMHO.

05-08-09, 04:25 AM	#21
Arclight Navy Seal Join Date: Jun 2008 Location: Land of windmills, tulips, wooden shoes and cheese. Lots of cheese. Posts: 8,467 Downloads: 53 Uploads: 10	Don't mind questions at all, I like speculating. Card is 8800GTS 512 (G92 core, like the 9 series). Once the problem occured it didn't matter what I installed, but it initially happened while running 182.06 32-bit drivers. Board has Intel P35 chipset. I think the mix of CRT and LCD monitors might have something to do with it, though I think the lack of support for older CRTs lies at the core; more people are using LCD nowadays so that's where they focused their efforts. For some reason Win7 thinks the CRT can't do more than 60hz unless it's running 1024x768, while XP recognized the screen being capable of 1280x960 @70hz. 2 things to mention: I had Rivatuner set up to force 70hz at 1280x960 at all times, which didn't seem to be working. The problem occured as I was trying to set up a custom res in Nvidia control panel (1280x960 70hz). Clicked the icon for the CRT, set up the res, tested, failed. Tried again, test, succes. But the res got assigned to the LCD instead of the CRT. Deleted it, selected CRT again, set it up, clicked test and went black. Just seems to be some conflict between Win7 and CRTs or Win7 and Nvidia control panel. Now that I think about it, had an issue with my new install too: couldn't select 75hz for the LCD in Nvidia panel, but could through Win7s own method (display properties>advanced). Definitely something wrong there. Just before everything went black, my CRT indicated it switched to a 35hz mode. It's almost like the hertzes (?) got "split" between the 2 screens; instead of 1 running at 70 and the other at 75, both got 35 which obviously doesn't work. As if the 2 screens got handled as 1? Sounds really weird, but it's the best sense I can make of it. The LAN problem was because I have 2 NICs: 1 onboard (realtek) and 1 add-in card (antique 3com leftover) to connect to a switch and other PCs on a network. For some reason windows decided to ignore the onboard and opted to use the add-in card for internet. Probably could have straightend it out, but because the monitors where freaking out I choose to reïnstall. Why the problem occured in the first place is beyond me. Oh, and that Corsair 650Watt has Seasonic components. Good choice IMHO. __________________ Contritium praecedit superbia.