Detonator 52.16's and DualView

I installed these and found that my dualview would no longer activate. The screens would turn black as if they were changing settings, but the computer would seem to lock up.

This topic was started by ,


data/avatar/default/avatar02.webp

8 Posts
Location -
Joined 2002-03-21
I installed these and found that my dualview would no longer activate. The screens would turn black as if they were changing settings, but the computer would seem to lock up. I reverted to older drivers and it still would not work... I have tried removing all traces of the drivers from the files and registry and still no luck... I have also tried several driver versions, including the ones that were built-in with Windows. I am pulling my hair out trying to get it working again. I know it worked before the 52.16s because I use it often. Any advice? I'm trying to aviod a full system reinstall, it takes me almost 2 days to get fully reconfigured....

Thanks in advance,
Kevin

Windows XP Pro SP1
GeForce2 MX based ASUS V7100 Deluxe
Detonator 45.33

Participate on our website and join the conversation

You have already an account on our website? Use the link below to login.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This topic is archived. New comments cannot be posted and votes cannot be cast.

Responses to this topic


data/avatar/default/avatar02.webp

139 Posts
Location -
Joined 2003-01-19
Try system restore

And if you want advice:
Dont' use beta drivers! They're beta for a reason.

data/avatar/default/avatar02.webp

8 Posts
Location -
Joined 2002-03-21
OP
turns out I had system restore disabled, besides, whenever I've tried in the past to use it, it never seems to work, and sometimes makes things worse. What I don't understand is how after completely obliterating all traces of the drivers, it doesn't work with the old ones?

data/avatar/default/avatar02.webp

139 Posts
Location -
Joined 2003-01-19
You disabled system restore? gah...well that's a shame then. It's gotten me out of many a bind (well, back when I did stupid things like install beta stuff...I learned my lesson though from all the eventual reinstalls of windows)

Anyway, I don't know what else you can try.

data/avatar/default/avatar03.webp

10 Posts
Location -
Joined 2003-04-23
Have you tried using the roll back feature for the driver to roll back to the old ones?

data/avatar/default/avatar02.webp

8 Posts
Location -
Joined 2002-03-21
OP
yes, same results, that's what prompted me to remove any and every trace of the drivers from the system, then install them fresh, which still causes the same thing, I'm probably just gonna reinstall my system, no more beta drivers for me!

data/avatar/default/avatar02.webp

8 Posts
Location -
Joined 2002-03-21
OP
Well, I fixed it. I had started to reinstall windows, when I got the idea of letting it boot with only the tv out cable attatched. Worked like a charm. After a few test boots and playing with changing the primary display and resolutions. Now I wonder if the 52.16s would have worked if I tried this... I'm not gonna risk it though, I'll wait until an official release comes.

data/avatar/default/avatar02.webp

139 Posts
Location -
Joined 2003-01-19
yes, same results, that's what prompted me to remove any and every trace of the drivers from the system, then install them fresh, which still causes the same thing, I'm probably just gonna reinstall my system, no more beta drivers for me!


The lesson is only learned the hard way :

data/avatar/default/avatar04.webp

18 Posts
Location -
Joined 2003-01-27
52.16 drivers aren't beta...last I checked, WHQL means certified.

data/avatar/default/avatar02.webp

139 Posts
Location -
Joined 2003-01-19
So, doesn't mean they're of the same quality as an official release, how do you know they're not missing files/mismatched versions, etc. What's the point of using leaked drivers anyway? You think you're getting a magical performance increase?