Your "Display Adapter" aka video card can do all that. But what are capabilities of your "Monitor" driver. All I know is Generic PnP Monitor aka monitor.sys is very suck at these kinds of things. Which driver are you using for you Monitor ? If you are using Monitor.sys, can you try see if you can use the Monitor.sys from Vista somehow.
Since there is no special device-driver for my monitor it just uses the generic Monitor.sys per PnP. As for capabilities; check the list in the first post. It lists all resolutions with all refresh rates the screen can normally do under a Win OS. (In fact it can do even more. The highest possible resolution for instance is actually 2048x1536@75Hz. And all resolutions lower than 2048x1536 can in actuality do at least 85Hz.) It may be worth a try. But somehow i dont think it would help, (call it a hunch), because the internals of these ultra-generic system files rarely change and if they do they arent being stripped down to a bare minimum of functions. Just think; except for 640x480 all 60Hz resolutions are gone without a trace, which means that for instance all LCD screens that dont support any other refresh rate wouldnt even work under 7 at all then. Nah, that wouldnt make sense. God knows they do a lot of stupid things at microsoft but something like that would be a tad too heavy even for these guys. Besides, other people dont seem to have this problem so apparently it is something that only occurs under certain circumstances. Otherwise the internet would be full of complaints by now... Actually i have thrown out these crappy LCDs because these things just arent my idea of a decent display device. I wont go into details now because its irrelevant to the topic, (and they are widely known anyway), so lets just say i prefer a HighEnd CAD CRT over ANY LCD for many reasons, not the least of which being that i like to be able to use all sorts of resolutions at all sorts of refreshrates without loosing valuable picture quality due to interpolation and similar mumbo-jumbo. Fact is an LCD has precisely one native resolution. On a CRT every resolution is 'native'. Not to be rude or ungrateful, (i appreciate all tips), but if i wanted to do that i probably would have just done it and not tried to find the cause of it in any forums. But im definitely not going to make what...like 50+ custom profiles only because my shiny new 'nextgen' OS is too stupid to do what its predecessors all could without problems; namely setting up my screen according to its capabilities...
What about that app for Registry differences from the other thread, why couldn't you make a few custom resolutions using the manual NVIDIA method. Then use that app to see what changes NVIDIA is making. (make couple different resolutions so can get many of the syntax's) Then we might be able to look at how the custom settings are being pushed and if it looks straightforward enough, then maybe we start think on how to write loop that will create registry settings.
Yeah, we could try that when i reinstalled 7. (For now im back to Vista...the 7 partition is already formatted again because i needed it for temporary workspace yesterday.)
I just reinstalled 7 and did some more checking... What i do know: It has definitely something to do with the nvidia driver, because with my ATI onboard solution all the refresh rates are there. Where exactly the problem lies is not entirely clear, however, since the same driver makes no problems at all in Vista (and 7 uses it 1:1) i tend to believe that 7 does 'something' to prevent the driver from making these modes available. What i dont know is what to do about this. I must have checked half the registry for entries that might be responsible and found nothing. (Probably all well obscured in some letters&numbers key.) I also tried to make custom profiles to find out how the control panel would store them in the registry. Unfortunately that was quite a shot in the foot too, because after making a profile for a certain resolution (like 1600x1200@60Hz) i was no longer able to use that resolution at any other refresh rate in 32bit TrueColor mode. It would only allow for 16bit HighColor then, except for the 60Hz profile. So i had to delete the profile to be able to use 32bit again. Everything i try seems to be leading right into a dead end. And since i can hardly use an onboard graphic solution for gaming, what am i supposed to do now? Wait for SP5? Or for Windows14? I really dont know what to do anymore...and quite frankly this is really starting to tick me off...
I figured you liked alice. Most the young bucks around here were filling green diapers last time alice had an album. Private joke - so don't flame
I would post this issue on an official nvidia forum or contact their tech support or go someplace where they deal with video drivers a lot like Guru3d or LaptopVideo2go.
Yeah .. I was just about to suggest LaptopVideo2go! They have all sorts of custom driver packages to try out .. worth a try anyway!
Well, i found a fix. Its certainly not the most elegant of solutions since it involved deliberate damaging of equipment, but i guess thats just the price you have to pay these days if you want to use a decent screen on a fairly new nvidia card with the latest microsoft operating system... The Story: After doing some more testing it became quite obvious that either Windows or the nv driver (or both of them in combination) are badly misinterpreting the monitors EDID data. Hence i pulled Pin12 from a spare VGA cable to disable EDID altogether, so that Windows and driver are no longer able to see the monitors capabilities at all. This finally did the trick; now i have all the resolutions my monitor can do, (up to 2048x1536), plus all the refresh rates (up to 170Hz) which are specified via the min/max H/V frequencies as per the values given in the monitor inf file. Like i said, not exactly elegant, but at least it works. I only wonder why such a stupid stunt is necessary in the 1st place...i mean if that is supposed to be the much-advertised 'backward compatibility', how many other things have to be brute-disabled in such a manner to make something work...?
That has more to do with the Nvidia driver then anything. I have a GTS 250 and i can add custom settings if i wanted to - gives me the option to.
Maybe Microsoft expected a monitor that old to have frayed cables and programmed the driver to anticipate that.