195.62 Driver + FW900 CRT = "3D Ready display not found" Vista 64
1 / 2
Hi, I've been looking through the forums and seeing a bunch of threads about issues with CRTs.
I just used Driversweeper in safe mode to clean the system, then installed the latest 195.62 GPU driver and then the 195.62 3D vision driver.
Vista 64 detects the CRT properly as Sony GDM-FW900. I have set the FW900 as primary monitor and set it to a conservative resolution of 1280x800 @120Hz in Nvidia Control Panel.
When I run the 3D vision setup it changes modes and jumps the FW900 to its max resolution: 2304x1440 @80Hz.
It asks to plug in the IR transmitter and detects it fine when plugged in. But on the next screen selecting any of the 3 Gaming Environments brings up "3D Ready display not found".
I'm not seeing the "StereoCPLAPI returned invalid refresh rate" like people have reported, but the install is stuck here and will not go forward.
Is there a way to force the installer to run with a different mode? Instead of 2304x1440 @80Hz that it defaults to on this CRT?
Any ideas or successful workarounds would be very appreciated.
Hi, I've been looking through the forums and seeing a bunch of threads about issues with CRTs.
I just used Driversweeper in safe mode to clean the system, then installed the latest 195.62 GPU driver and then the 195.62 3D vision driver.
Vista 64 detects the CRT properly as Sony GDM-FW900. I have set the FW900 as primary monitor and set it to a conservative resolution of 1280x800 @120Hz in Nvidia Control Panel.
When I run the 3D vision setup it changes modes and jumps the FW900 to its max resolution: 2304x1440 @80Hz.
It asks to plug in the IR transmitter and detects it fine when plugged in. But on the next screen selecting any of the 3 Gaming Environments brings up "3D Ready display not found".
I'm not seeing the "StereoCPLAPI returned invalid refresh rate" like people have reported, but the install is stuck here and will not go forward.
Is there a way to force the installer to run with a different mode? Instead of 2304x1440 @80Hz that it defaults to on this CRT?
Any ideas or successful workarounds would be very appreciated.
Report your issue/s to driver assurance and customer care [url="http://www.nvidia.com/object/driverqualityassurance.html"]http://www.nvidia.com/object/driverqualityassurance.html[/url] CC is right the driver is an insult, similar to the reply I receved from customer 'lack of' care, but they need to be TOLD!
Report your issue/s to driver assurance and customer care http://www.nvidia.com/object/driverqualityassurance.html CC is right the driver is an insult, similar to the reply I receved from customer 'lack of' care, but they need to be TOLD!
EVGA X58 760 Classified (VREG,NB/SB WB Koolance seperate loop), i7 980X@4.4+GHz 33x134 1.3625V Thermaltake Venoumous S with CoolerMaster push-pull fans, 12GB OCZ 8-8-8-24@16000 1.65V, ATI 5970 WB Koolance on seperate loop @1.16V 850-1200 or Nvidia 295, Xonar HDAV 1.3 Deluxe into Yamaha RX-V3800, 4x300GB Velociraptors Raid 0 on Adaptec 4505 RAID, 4x60GB OCZ Vertex SSD RAID 0 LSI 9750, 1TB WD SATA3, 128GB Falcon SSD, Thermaltake 1200W, Thermaltake TX Mozart, Logitech diNovo Bluetooth Keyboard + MX1000 Mouse, Logitech Sphere MP webcam, Logitech cordless Rumblepad2, 50" Samsung 3D PS50B450 plasma, Samsung SSG1000 3D glasses, Nvidia 3D Vision, Windows 7 Ultimate x64 RTM
Yea, it seems this 195.62 driver does something different in its setup to check if a display is 3D Ready.
I just ran Driversweeper in safe mode again and installed the old 190.62 GPU Driver, then the 190.62 3D vision driver using Launch.exe(same method used to install the 195.62)
190.62(CD v1.11) detects the FW900 CRT as 3D Ready just fine. 3D vision completes setup and works in games.
I made no change to the system other than the driver. 190.62's setup detects the display properly, 195.62's setup does not.
The problem I see with the older 190.62 drivers is the convergence hotkeys have no effect in Resident Evil 5(convergence hotkeys work in COD4, etc)
I was hoping to install these newest drivers with latest fixes and updated profiles, but its not letting me complete setup with this "3D Ready display not found" error.
Does anyone know how to trick the setup into going forward? Its clear the display is 3D Ready.
Yea, it seems this 195.62 driver does something different in its setup to check if a display is 3D Ready.
I just ran Driversweeper in safe mode again and installed the old 190.62 GPU Driver, then the 190.62 3D vision driver using Launch.exe(same method used to install the 195.62)
190.62(CD v1.11) detects the FW900 CRT as 3D Ready just fine. 3D vision completes setup and works in games.
I made no change to the system other than the driver. 190.62's setup detects the display properly, 195.62's setup does not.
The problem I see with the older 190.62 drivers is the convergence hotkeys have no effect in Resident Evil 5(convergence hotkeys work in COD4, etc)
I was hoping to install these newest drivers with latest fixes and updated profiles, but its not letting me complete setup with this "3D Ready display not found" error.
Does anyone know how to trick the setup into going forward? Its clear the display is 3D Ready.
I cant even get the setup to run without an error , I even formatted my system yesterday to see if that was the problem. NOPE
Every time I run the setup wizard I get a error of 1920x2160 (weird numbers) but if I hook any other monitor the setup will run but no 3D display is found.
I also run setup then disconnect and reconnect the right monitor then it crashes with the same error.
It does some type of check that is prevent a real 3D DLP form even using the setup wizard, it wont even make it to the first screen once the DLP is connected.
Do not buy these glasses until Nvidia fixes the major issues!
I cant even get the setup to run without an error , I even formatted my system yesterday to see if that was the problem. NOPE
Every time I run the setup wizard I get a error of 1920x2160 (weird numbers) but if I hook any other monitor the setup will run but no 3D display is found.
I also run setup then disconnect and reconnect the right monitor then it crashes with the same error.
It does some type of check that is prevent a real 3D DLP form even using the setup wizard, it wont even make it to the first screen once the DLP is connected.
Do not buy these glasses until Nvidia fixes the major issues!
Well I went back and started trying the BETA drivers to see when the problem began.
195.62 WHQL (CD v1.17) 2009.11.26 = 3D Ready display not found.
195.55 BETA (CD v1.16) 2009.11.18 = 3D Ready display not found.
195.39 BETA (CD v1.15) 2009.10.30 = Setup completes, working.
190.62 WHQL (CD v1.11) 2009.07.29 = Setup completes, working.
This lines up with what many others have experienced. CD v1.17 and CD v1.16 do not detect displays properly. CD v1.15 and below seem to detect displays properly.
If Nvidia would revert whatever change in display detection routine was added between release 195.39 and 195.55, many people here would appreciate it.
New game profiles and fixes in the newer driver releases are unavailable to many because setup will not complete without detecting the display as 3D Ready.
A workaround to force setup forward for known 3D Ready displays would be useful until a new BETA driver is released.
Driver install method used was:
Device Manager(devmgmt.msc) > expand Display Adapters > right click on Display Adapter > Uninstall.
Control Panel > Programs and Settings(appwiz.cpl) > Uninstall Nvidia PhysX, Uninstall Nvidia Stereoscopic 3D Driver.
Unplug IR transmitter from USB cable.
Run [url="http://www.guru3d.com/category/driversweeper/"]Driversweeper[/url] > tick Nvidia Display, Nvidia PhysX > Analyze and Clean. Reboot.
F8 boot into Safe Mode, run Driversweeper again as before to delete locked/in-use files. Reboot.
Install new Driver set from CD directory using Launch.exe: first GPU driver is installed, reboots, then 3D Vision driver is installed, plug in IR transmitter when prompted by setup.
This lines up with what many others have experienced. CD v1.17 and CD v1.16 do not detect displays properly. CD v1.15 and below seem to detect displays properly.
If Nvidia would revert whatever change in display detection routine was added between release 195.39 and 195.55, many people here would appreciate it.
New game profiles and fixes in the newer driver releases are unavailable to many because setup will not complete without detecting the display as 3D Ready.
A workaround to force setup forward for known 3D Ready displays would be useful until a new BETA driver is released.
Driver install method used was:
Device Manager(devmgmt.msc) > expand Display Adapters > right click on Display Adapter > Uninstall.
Control Panel > Programs and Settings(appwiz.cpl) > Uninstall Nvidia PhysX, Uninstall Nvidia Stereoscopic 3D Driver.
Unplug IR transmitter from USB cable.
Run Driversweeper > tick Nvidia Display, Nvidia PhysX > Analyze and Clean. Reboot.
F8 boot into Safe Mode, run Driversweeper again as before to delete locked/in-use files. Reboot.
Install new Driver set from CD directory using Launch.exe: first GPU driver is installed, reboots, then 3D Vision driver is installed, plug in IR transmitter when prompted by setup.
muu5, I registered to this forum just to say Thank You! I have a Samsung HL67A750 and I bought the 3-D vision yesterday and was about to give up and return it when I found your instructions, they worked pretty much perfectly (Things got a bit strange while uninstalling, but I just plowed through) Thanks again!
muu5, I registered to this forum just to say Thank You! I have a Samsung HL67A750 and I bought the 3-D vision yesterday and was about to give up and return it when I found your instructions, they worked pretty much perfectly (Things got a bit strange while uninstalling, but I just plowed through) Thanks again!
[quote name='vhold' post='956961' date='Nov 28 2009, 09:30 PM']muu5, I registered to this forum just to say Thank You! I have a Samsung HL67A750 and I bought the 3-D vision yesterday and was about to give up and return it when I found your instructions, they worked pretty much perfectly (Things got a bit strange while uninstalling, but I just plowed through) Thanks again![/quote]
This procedure working for device with Vesa plug like Samsung plasma PS50B450(1) ? Somebody checked it out?
[quote name='vhold' post='956961' date='Nov 28 2009, 09:30 PM']muu5, I registered to this forum just to say Thank You! I have a Samsung HL67A750 and I bought the 3-D vision yesterday and was about to give up and return it when I found your instructions, they worked pretty much perfectly (Things got a bit strange while uninstalling, but I just plowed through) Thanks again!
This procedure working for device with Vesa plug like Samsung plasma PS50B450(1) ? Somebody checked it out?
[quote name='Hadron' post='957203' date='Nov 29 2009, 03:26 PM']This procedure working for device with Vesa plug like Samsung plasma PS50B450(1) ? Somebody checked it out?[/quote]
[quote name='Hadron' post='957203' date='Nov 29 2009, 03:26 PM']This procedure working for device with Vesa plug like Samsung plasma PS50B450(1) ? Somebody checked it out?
According to Andrew the 195.62 works fine with CRT displays, but you need to have the display driver installed - the inf file with what resolution/refresh the monitor supports.
According to Andrew the 195.62 works fine with CRT displays, but you need to have the display driver installed - the inf file with what resolution/refresh the monitor supports.
[quote name='Bloody' post='957264' date='Nov 29 2009, 05:39 PM']According to Andrew the 195.62 works fine with CRT displays, but you need to have the display driver installed - the inf file with what resolution/refresh the monitor supports.[/quote]
[quote name='Bloody' post='957264' date='Nov 29 2009, 05:39 PM']According to Andrew the 195.62 works fine with CRT displays, but you need to have the display driver installed - the inf file with what resolution/refresh the monitor supports.
[quote name='Bloody' post='957264' date='Nov 29 2009, 06:39 PM']According to Andrew the 195.62 works fine with CRT displays, but you need to have the display driver installed - the inf file with what resolution/refresh the monitor supports.[/quote]
Hmm, can you link to this post? What I was looking for was a workaround, a way to force detection in setup, since this CRT is known to be 3D Ready and working with older drivers.
I have the display driver for the CRT installed, Nvidia control panel sees it properly as a Sony GDM-FW900, all its modes are listed properly and are available to select.
Yet the 3D vision setup on both CD v1.17 and CD v1.16 run into a dead-end with "3D Ready display not found" during display detection. CD v1.15 detects the CRT fine without making any other changes.
What I posted earlier about Driversweeper was just the method for cleanly uninstalling old drivers, sometimes components from old drivers are left behind and can cause problems.
[quote name='Bloody' post='957264' date='Nov 29 2009, 06:39 PM']According to Andrew the 195.62 works fine with CRT displays, but you need to have the display driver installed - the inf file with what resolution/refresh the monitor supports.
Hmm, can you link to this post? What I was looking for was a workaround, a way to force detection in setup, since this CRT is known to be 3D Ready and working with older drivers.
I have the display driver for the CRT installed, Nvidia control panel sees it properly as a Sony GDM-FW900, all its modes are listed properly and are available to select.
Yet the 3D vision setup on both CD v1.17 and CD v1.16 run into a dead-end with "3D Ready display not found" during display detection. CD v1.15 detects the CRT fine without making any other changes.
What I posted earlier about Driversweeper was just the method for cleanly uninstalling old drivers, sometimes components from old drivers are left behind and can cause problems.
Well I've tried now the "old" 190.62 drivers, and the 3D Vision wizard sets the resolution directly to 2304x1440. Can I change that? Because of that setting the wizard says "3D Ready display not found".
I also used Driversweeper to delete all other/old driver information on my computer.
I also own a Sony GDM-FW900 (or SGI GDM-FW9011.. same model), but the 2304x1440 is selected as the native resolution so I think thats the reason why the wizard picks it to test the 3D functionality...
Well I've tried now the "old" 190.62 drivers, and the 3D Vision wizard sets the resolution directly to 2304x1440. Can I change that? Because of that setting the wizard says "3D Ready display not found".
I also used Driversweeper to delete all other/old driver information on my computer.
I also own a Sony GDM-FW900 (or SGI GDM-FW9011.. same model), but the 2304x1440 is selected as the native resolution so I think thats the reason why the wizard picks it to test the 3D functionality...
[quote name='muu5' post='957359' date='Nov 30 2009, 01:10 AM']I have the display driver for the CRT installed, Nvidia control panel sees it properly as a Sony GDM-FW900, all its modes are listed properly and are available to select.[/quote]
I have CRT and the same problem with 195.62, while previous version of driver worked. There should be the manual way to set CRT in registry, maybe after new drivers can be used with shutter glasses.
Previous driver did not work with CRT without undocumented manual editing of registry, and the support did no help with it. The current driver's release do not work with such editing already. I think nvidia try by this way to disable using of CRTs with its shutter glasses, in order to increase sales of monitors/tvs/projectors of its business partners.
[quote name='muu5' post='957359' date='Nov 30 2009, 01:10 AM']I have the display driver for the CRT installed, Nvidia control panel sees it properly as a Sony GDM-FW900, all its modes are listed properly and are available to select.
I have CRT and the same problem with 195.62, while previous version of driver worked. There should be the manual way to set CRT in registry, maybe after new drivers can be used with shutter glasses.
Previous driver did not work with CRT without undocumented manual editing of registry, and the support did no help with it. The current driver's release do not work with such editing already. I think nvidia try by this way to disable using of CRTs with its shutter glasses, in order to increase sales of monitors/tvs/projectors of its business partners.
I just used Driversweeper in safe mode to clean the system, then installed the latest 195.62 GPU driver and then the 195.62 3D vision driver.
Vista 64 detects the CRT properly as Sony GDM-FW900. I have set the FW900 as primary monitor and set it to a conservative resolution of 1280x800 @120Hz in Nvidia Control Panel.
When I run the 3D vision setup it changes modes and jumps the FW900 to its max resolution: 2304x1440 @80Hz.
It asks to plug in the IR transmitter and detects it fine when plugged in. But on the next screen selecting any of the 3 Gaming Environments brings up "3D Ready display not found".
I'm not seeing the "StereoCPLAPI returned invalid refresh rate" like people have reported, but the install is stuck here and will not go forward.
Is there a way to force the installer to run with a different mode? Instead of 2304x1440 @80Hz that it defaults to on this CRT?
Any ideas or successful workarounds would be very appreciated.
I just used Driversweeper in safe mode to clean the system, then installed the latest 195.62 GPU driver and then the 195.62 3D vision driver.
Vista 64 detects the CRT properly as Sony GDM-FW900. I have set the FW900 as primary monitor and set it to a conservative resolution of 1280x800 @120Hz in Nvidia Control Panel.
When I run the 3D vision setup it changes modes and jumps the FW900 to its max resolution: 2304x1440 @80Hz.
It asks to plug in the IR transmitter and detects it fine when plugged in. But on the next screen selecting any of the 3 Gaming Environments brings up "3D Ready display not found".
I'm not seeing the "StereoCPLAPI returned invalid refresh rate" like people have reported, but the install is stuck here and will not go forward.
Is there a way to force the installer to run with a different mode? Instead of 2304x1440 @80Hz that it defaults to on this CRT?
Any ideas or successful workarounds would be very appreciated.
EVGA X58 760 Classified (VREG,NB/SB WB Koolance seperate loop), i7 980X@4.4+GHz 33x134 1.3625V Thermaltake Venoumous S with CoolerMaster push-pull fans, 12GB OCZ 8-8-8-24@16000 1.65V, ATI 5970 WB Koolance on seperate loop @1.16V 850-1200 or Nvidia 295, Xonar HDAV 1.3 Deluxe into Yamaha RX-V3800, 4x300GB Velociraptors Raid 0 on Adaptec 4505 RAID, 4x60GB OCZ Vertex SSD RAID 0 LSI 9750, 1TB WD SATA3, 128GB Falcon SSD, Thermaltake 1200W, Thermaltake TX Mozart, Logitech diNovo Bluetooth Keyboard + MX1000 Mouse, Logitech Sphere MP webcam, Logitech cordless Rumblepad2, 50" Samsung 3D PS50B450 plasma, Samsung SSG1000 3D glasses, Nvidia 3D Vision, Windows 7 Ultimate x64 RTM
I just ran Driversweeper in safe mode again and installed the old 190.62 GPU Driver, then the 190.62 3D vision driver using Launch.exe(same method used to install the 195.62)
190.62(CD v1.11) detects the FW900 CRT as 3D Ready just fine. 3D vision completes setup and works in games.
I made no change to the system other than the driver. 190.62's setup detects the display properly, 195.62's setup does not.
The problem I see with the older 190.62 drivers is the convergence hotkeys have no effect in Resident Evil 5(convergence hotkeys work in COD4, etc)
I was hoping to install these newest drivers with latest fixes and updated profiles, but its not letting me complete setup with this "3D Ready display not found" error.
Does anyone know how to trick the setup into going forward? Its clear the display is 3D Ready.
I just ran Driversweeper in safe mode again and installed the old 190.62 GPU Driver, then the 190.62 3D vision driver using Launch.exe(same method used to install the 195.62)
190.62(CD v1.11) detects the FW900 CRT as 3D Ready just fine. 3D vision completes setup and works in games.
I made no change to the system other than the driver. 190.62's setup detects the display properly, 195.62's setup does not.
The problem I see with the older 190.62 drivers is the convergence hotkeys have no effect in Resident Evil 5(convergence hotkeys work in COD4, etc)
I was hoping to install these newest drivers with latest fixes and updated profiles, but its not letting me complete setup with this "3D Ready display not found" error.
Does anyone know how to trick the setup into going forward? Its clear the display is 3D Ready.
Every time I run the setup wizard I get a error of 1920x2160 (weird numbers) but if I hook any other monitor the setup will run but no 3D display is found.
I also run setup then disconnect and reconnect the right monitor then it crashes with the same error.
It does some type of check that is prevent a real 3D DLP form even using the setup wizard, it wont even make it to the first screen once the DLP is connected.
Do not buy these glasses until Nvidia fixes the major issues!
Andrew where are you and why is this happening?
Every time I run the setup wizard I get a error of 1920x2160 (weird numbers) but if I hook any other monitor the setup will run but no 3D display is found.
I also run setup then disconnect and reconnect the right monitor then it crashes with the same error.
It does some type of check that is prevent a real 3D DLP form even using the setup wizard, it wont even make it to the first screen once the DLP is connected.
Do not buy these glasses until Nvidia fixes the major issues!
Andrew where are you and why is this happening?
Look at Iz3d ! They PWN in that regard !
No doubt many customers have chosen to go that route for their customer service ALONE.
Look at Iz3d ! They PWN in that regard !
No doubt many customers have chosen to go that route for their customer service ALONE.
195.62 WHQL (CD v1.17) 2009.11.26 = 3D Ready display not found.
195.55 BETA (CD v1.16) 2009.11.18 = 3D Ready display not found.
195.39 BETA (CD v1.15) 2009.10.30 = Setup completes, working.
190.62 WHQL (CD v1.11) 2009.07.29 = Setup completes, working.
This lines up with what many others have experienced. CD v1.17 and CD v1.16 do not detect displays properly. CD v1.15 and below seem to detect displays properly.
If Nvidia would revert whatever change in display detection routine was added between release 195.39 and 195.55, many people here would appreciate it.
New game profiles and fixes in the newer driver releases are unavailable to many because setup will not complete without detecting the display as 3D Ready.
A workaround to force setup forward for known 3D Ready displays would be useful until a new BETA driver is released.
Driver install method used was:
Device Manager(devmgmt.msc) > expand Display Adapters > right click on Display Adapter > Uninstall.
Control Panel > Programs and Settings(appwiz.cpl) > Uninstall Nvidia PhysX, Uninstall Nvidia Stereoscopic 3D Driver.
Unplug IR transmitter from USB cable.
Run [url="http://www.guru3d.com/category/driversweeper/"]Driversweeper[/url] > tick Nvidia Display, Nvidia PhysX > Analyze and Clean. Reboot.
F8 boot into Safe Mode, run Driversweeper again as before to delete locked/in-use files. Reboot.
Install new Driver set from CD directory using Launch.exe: first GPU driver is installed, reboots, then 3D Vision driver is installed, plug in IR transmitter when prompted by setup.
195.62 WHQL (CD v1.17) 2009.11.26 = 3D Ready display not found.
195.55 BETA (CD v1.16) 2009.11.18 = 3D Ready display not found.
195.39 BETA (CD v1.15) 2009.10.30 = Setup completes, working.
190.62 WHQL (CD v1.11) 2009.07.29 = Setup completes, working.
This lines up with what many others have experienced. CD v1.17 and CD v1.16 do not detect displays properly. CD v1.15 and below seem to detect displays properly.
If Nvidia would revert whatever change in display detection routine was added between release 195.39 and 195.55, many people here would appreciate it.
New game profiles and fixes in the newer driver releases are unavailable to many because setup will not complete without detecting the display as 3D Ready.
A workaround to force setup forward for known 3D Ready displays would be useful until a new BETA driver is released.
Driver install method used was:
Device Manager(devmgmt.msc) > expand Display Adapters > right click on Display Adapter > Uninstall.
Control Panel > Programs and Settings(appwiz.cpl) > Uninstall Nvidia PhysX, Uninstall Nvidia Stereoscopic 3D Driver.
Unplug IR transmitter from USB cable.
Run Driversweeper > tick Nvidia Display, Nvidia PhysX > Analyze and Clean. Reboot.
F8 boot into Safe Mode, run Driversweeper again as before to delete locked/in-use files. Reboot.
Install new Driver set from CD directory using Launch.exe: first GPU driver is installed, reboots, then 3D Vision driver is installed, plug in IR transmitter when prompted by setup.
This procedure working for device with Vesa plug like Samsung plasma PS50B450(1) ? Somebody checked it out?
This procedure working for device with Vesa plug like Samsung plasma PS50B450(1) ? Somebody checked it out?
Samsung 3D-Ready PLASMA PS50B450
ill check on my 61 samsung now
UPDATE
Doesent work , didnt think it would either
driver issue
ill check on my 61 samsung now
UPDATE
Doesent work , didnt think it would either
driver issue
intel i5 2500k @ 4.6 30C Stable
EVGA gtx 470 SLI
windows vista 64 bit
8 gig Corsair Vengeance RAM
My 3D Vision Blog - 3dvision-blog.com
has he mentioned the dlps?
has he mentioned the dlps?
intel i5 2500k @ 4.6 30C Stable
EVGA gtx 470 SLI
windows vista 64 bit
8 gig Corsair Vengeance RAM
Hmm, can you link to this post? What I was looking for was a workaround, a way to force detection in setup, since this CRT is known to be 3D Ready and working with older drivers.
I have the display driver for the CRT installed, Nvidia control panel sees it properly as a Sony GDM-FW900, all its modes are listed properly and are available to select.
Yet the 3D vision setup on both CD v1.17 and CD v1.16 run into a dead-end with "3D Ready display not found" during display detection. CD v1.15 detects the CRT fine without making any other changes.
What I posted earlier about Driversweeper was just the method for cleanly uninstalling old drivers, sometimes components from old drivers are left behind and can cause problems.
Hmm, can you link to this post? What I was looking for was a workaround, a way to force detection in setup, since this CRT is known to be 3D Ready and working with older drivers.
I have the display driver for the CRT installed, Nvidia control panel sees it properly as a Sony GDM-FW900, all its modes are listed properly and are available to select.
Yet the 3D vision setup on both CD v1.17 and CD v1.16 run into a dead-end with "3D Ready display not found" during display detection. CD v1.15 detects the CRT fine without making any other changes.
What I posted earlier about Driversweeper was just the method for cleanly uninstalling old drivers, sometimes components from old drivers are left behind and can cause problems.
I also used Driversweeper to delete all other/old driver information on my computer.
I also own a Sony GDM-FW900 (or SGI GDM-FW9011.. same model), but the 2304x1440 is selected as the native resolution so I think thats the reason why the wizard picks it to test the 3D functionality...
thanks
MCX
I also used Driversweeper to delete all other/old driver information on my computer.
I also own a Sony GDM-FW900 (or SGI GDM-FW9011.. same model), but the 2304x1440 is selected as the native resolution so I think thats the reason why the wizard picks it to test the 3D functionality...
thanks
MCX
I have CRT and the same problem with 195.62, while previous version of driver worked. There should be the manual way to set CRT in registry, maybe after new drivers can be used with shutter glasses.
Previous driver did not work with CRT without undocumented manual editing of registry, and the support did no help with it. The current driver's release do not work with such editing already. I think nvidia try by this way to disable using of CRTs with its shutter glasses, in order to increase sales of monitors/tvs/projectors of its business partners.
I have CRT and the same problem with 195.62, while previous version of driver worked. There should be the manual way to set CRT in registry, maybe after new drivers can be used with shutter glasses.
Previous driver did not work with CRT without undocumented manual editing of registry, and the support did no help with it. The current driver's release do not work with such editing already. I think nvidia try by this way to disable using of CRTs with its shutter glasses, in order to increase sales of monitors/tvs/projectors of its business partners.