Acer H5360 - not longer detected?
It's really really strange. I have two displays connected to my GTX-260, the Samsung Rz2233 and the Acer H5360 (Samsung via DVI and the Acer via DVI-HDMI). I used to switch to the Acer when playing games which was no problem until today. I installed the newly released Full driver CD started my PC and now only the Samsung is detected as compatible.

When I click the option "Setup multiple displays" (Nvidia Control panel) I not longer have the choice between the Sammy and the Acer. There is only the Sammy displayed. Even the detection routine doesn't detect the Acer.

It gets even stranger. While the boot-routine is running the Acer is detected and displays the whole boot-routine including the Windows 7 symbol. At the point when you have to log in all of a sudden the Acer doesn't display anything anymore and the Sammy is now the active display. The boot routine has been this way from day one but the difference is I can't switch back to the Acer now. At the time you have to log in it seems detection for the Acer is gone although the Acer displayed the boot routine just seconds before.

Anyone any idea or maybe facing the same problems?
It's really really strange. I have two displays connected to my GTX-260, the Samsung Rz2233 and the Acer H5360 (Samsung via DVI and the Acer via DVI-HDMI). I used to switch to the Acer when playing games which was no problem until today. I installed the newly released Full driver CD started my PC and now only the Samsung is detected as compatible.



When I click the option "Setup multiple displays" (Nvidia Control panel) I not longer have the choice between the Sammy and the Acer. There is only the Sammy displayed. Even the detection routine doesn't detect the Acer.



It gets even stranger. While the boot-routine is running the Acer is detected and displays the whole boot-routine including the Windows 7 symbol. At the point when you have to log in all of a sudden the Acer doesn't display anything anymore and the Sammy is now the active display. The boot routine has been this way from day one but the difference is I can't switch back to the Acer now. At the time you have to log in it seems detection for the Acer is gone although the Acer displayed the boot routine just seconds before.



Anyone any idea or maybe facing the same problems?

#1
Posted 03/17/2010 08:53 PM   
Ok, I guess the problem could be fixed if I switch back to one of the old drivers (my AcerH5360 worked just fine with one of the recent drivers). It should be possible to keep the new 3D vision driver while switching the Geforce driver back to an old one.

Before I do this I would like to know if there is anyone here who has installed the newly released full driver CD and still has no problems with his Acer H5360 (I use Windows 7 64-Bit).
Ok, I guess the problem could be fixed if I switch back to one of the old drivers (my AcerH5360 worked just fine with one of the recent drivers). It should be possible to keep the new 3D vision driver while switching the Geforce driver back to an old one.



Before I do this I would like to know if there is anyone here who has installed the newly released full driver CD and still has no problems with his Acer H5360 (I use Windows 7 64-Bit).

#2
Posted 03/18/2010 09:35 AM   
Hi,

I have Acer H5360 and today I also upgraded my drivers to CD v1.23 with no problems on windows 7 (64 bit).

Did you do a clean install? I mean removed the old drivers before installing a new one? Did you use driver sweeper to remove remains of the old driver?

Try connecting just the acer projector as display device and see if it works.

I hope this might be of some help.

best of luck.
Hi,



I have Acer H5360 and today I also upgraded my drivers to CD v1.23 with no problems on windows 7 (64 bit).



Did you do a clean install? I mean removed the old drivers before installing a new one? Did you use driver sweeper to remove remains of the old driver?



Try connecting just the acer projector as display device and see if it works.



I hope this might be of some help.



best of luck.

#3
Posted 03/18/2010 10:01 AM   
I removed the old driver before installing the new one. But I didn't run driver sweeper. Maybe that could fix my problem. We'll see.......
I removed the old driver before installing the new one. But I didn't run driver sweeper. Maybe that could fix my problem. We'll see.......

#4
Posted 03/18/2010 10:54 AM   
[quote name='lohan' post='1021869' date='Mar 18 2010, 06:54 AM']I removed the old driver before installing the new one. But I didn't run driver sweeper. Maybe that could fix my problem. We'll see.......[/quote]


Well just try it. Sometime strange things can happen because of old drivers.

While uninstalling Nvidia drivers it asks to reboot the machine. At that point during startup boot in safe mode by holding the F8 key. Then run drive sweeper in safe mode. After everything is cleaned up, install the new drivers.

May be it will solve your problem. BUt did you try with just the projector connected?
[quote name='lohan' post='1021869' date='Mar 18 2010, 06:54 AM']I removed the old driver before installing the new one. But I didn't run driver sweeper. Maybe that could fix my problem. We'll see.......





Well just try it. Sometime strange things can happen because of old drivers.



While uninstalling Nvidia drivers it asks to reboot the machine. At that point during startup boot in safe mode by holding the F8 key. Then run drive sweeper in safe mode. After everything is cleaned up, install the new drivers.



May be it will solve your problem. BUt did you try with just the projector connected?

#5
Posted 03/18/2010 06:50 PM   
The PJ is permanently connected to my GTX260. But I enable it only when I want to play on the big screen.

Before I try this driver sweeper routine I just wanted to test one other option. And now it gets even stranger than it is already (if that's possible). I just switched the GTX ports for the Samsung and the Acer. Normally the Samsung is connected with Port 1 while the Acer is connected with Port 2. I just switched both so the Acer is in Port 1 and the Sammy in Port 2. Now........right the Acer is working just fine while the Samsung is no longer detected.

If I wouldn't know better I would say Port 2 is somehow malfunctioning but remember when the Acer was connected with Port 2 the Acer displayed the whole OS boot up sequence to the point where you have to log into Windows...........
The PJ is permanently connected to my GTX260. But I enable it only when I want to play on the big screen.



Before I try this driver sweeper routine I just wanted to test one other option. And now it gets even stranger than it is already (if that's possible). I just switched the GTX ports for the Samsung and the Acer. Normally the Samsung is connected with Port 1 while the Acer is connected with Port 2. I just switched both so the Acer is in Port 1 and the Sammy in Port 2. Now........right the Acer is working just fine while the Samsung is no longer detected.



If I wouldn't know better I would say Port 2 is somehow malfunctioning but remember when the Acer was connected with Port 2 the Acer displayed the whole OS boot up sequence to the point where you have to log into Windows...........

#6
Posted 03/18/2010 07:12 PM   
Hail to imarun.....just did the driver sweeper routine and now everything works just as fine as it used to. Both displays are detected again and I can switch between the two displays like crazy :-)

THANKS ALOT MAN!
Hail to imarun.....just did the driver sweeper routine and now everything works just as fine as it used to. Both displays are detected again and I can switch between the two displays like crazy :-)



THANKS ALOT MAN!

#7
Posted 03/18/2010 10:31 PM   
New driver installed last night.
Strange thing happened and I could run 3D without flickering for the first time but I got permant warning message in RED saying I m doing 3D in incorect mode or something like that.
When I fixed this message issue flickering come back again. I am thinking I somehow managed doing 3D at 100hz or 110hz on the PJ with this new driver.
New driver installed last night.

Strange thing happened and I could run 3D without flickering for the first time but I got permant warning message in RED saying I m doing 3D in incorect mode or something like that.

When I fixed this message issue flickering come back again. I am thinking I somehow managed doing 3D at 100hz or 110hz on the PJ with this new driver.

#8
Posted 03/18/2010 10:34 PM   
Scroll To Top