Driverheaven - Driver Cleaner 2.0

s}{aggy · Sep 11, 2003, 10:24 AM

PROBLEM !!!!!!!!!!!!!!!!

ran driver cleaner to uninstall my omega drivers...ran DC then uninstalled drivers from add/remove.

now computer doesnt even see my nvidia card?????

reinstalled card.....different drivers...add hardware..

still dont see cardf???

help !!!

**Spike** · Sep 11, 2003, 01:30 PM

What you mean you run Driver Cleaner 1st and than add/remove through the control panel?

animal001 · Sep 16, 2003, 12:51 PM

Hi. Im having the same problem. I used the cleaner before I uninstalled
the video card drivers. Now I dont even see it in the Device Manager.
I can't select it in the Device manager so I can install new drivers. I have
tried installing several different Detonator drivers to no avail. I am hoping
that with a new installation of my operating system, that all will be restored.
I can understand the purpose of this tool is to COMPLETELY wipe out any trace of the drivers, and
it does a good job at it. But you must understand that a lot of people will simply ignore the README
file that you supplied like I did. I know I should have read it, and I blame myself for not doing so,
but not everyone has the option of reinstalling their operating system. It is a very tedious
task and wastes a lot of time. I suggest you add some sort of dialog box or some big capitalized
letters to your program that warns the user of the risks involved instead of having to resort
to a text file that most users wont even look at. Thanks for your time.

**Spike** · Sep 16, 2003, 01:52 PM

animal i am sorry that it did go wrong by you, but i find it cool that you admitted that you didn't read the readme. I will add something that when you start the program a messagebox will popup with something like:

Make sure to follow the steps in the readme or you can run into problems.

~~HawK~~ · Sep 16, 2003, 01:56 PM

Have you tryed to search for new HardWare ? in device manager right click on your Comp. name (top) choose scan for Hardware changes

tcmjr · Sep 21, 2003, 11:14 AM

Lol , I really wonder sometimes.
Why ppl dont read the readme....
Maybe we should name them notreadme and ppl will read.

Btw , I dont think that dev's should worry too much about newbie user , maybe the only way they learn is learning the hard way.
All information is supplied with the tool , and nonetheless this tool is not supposed to be used by newbie (standard user) as they should not be playing around with changing driver and stuff.
Learn the hard way like we all did in the old time , no newbie friendly interface and instruction.
Just my Humble opinion.

**Spike** · Sep 21, 2003, 12:09 PM

Now i have a new way for the next version. I added a message at the program start that will state that you need to follow the detailed instructions in the readme or the can have problems. This popup can be turned off also, but it gives the new users and indication that they need to follow the steps. I hope people will than follow it so that noby experience any problems anymore

BountyHunter · Sep 26, 2003, 08:14 PM

Spike, first off...I think you are doing a great job with your DC utility. You're bloody awesome!
Secondly, I have a suggestion for your next version of DC...would you be able to add such a functionality where DC can clean out the monitor information that gets plugged into the registry every time one installs a new video driver?
I'll use RefreshForce as an example of what I mean...as you can see, I have redundant monitor information in the registry somewhere. I'm the kind of person who wants everything to be neat and tidy, and this really pisses me off about Windows XP.

Thank you for your time and consideration regarding this matter.

**Spike** · Sep 27, 2003, 02:39 AM

Yep i am allready working on a tool for that, but until now it only works in 98/me. In xp and 2000 the os locks that part of the registry. First i need to write something that hacks it to a state that i can delete it and than set it back, but until now nothing has worked.

BountyHunter · Sep 27, 2003, 10:22 AM

Quote:

Originally posted by Spike
Yep i am allready working on a tool for that, but until now it only works in 98/me. In xp and 2000 the os locks that part of the registry. First i need to write something that hacks it to a state that i can delete it and than set it back, but until now nothing has worked.

Thank you for your reply.
Wish you the best of luck with that.

vietz · Sep 28, 2003, 11:07 AM

for cab cleaner should i clean just driver cab?

ihave windows xp sp1

**Spike** · Sep 28, 2003, 12:28 PM

viets you should select driver.cab and after that sp1.cab

dzjepp · Oct 19, 2003, 10:50 PM

Hey Spike,

Do you know how to efficiently downgrade/uninstall VIA drivers from the system? I've noticed that you mentioned that the VIA Uninstall functionality is still a little rough in Driver Cleaner and in the new 2.0 it has been taken away.

Right now I have 4in1 4.49p but I would like to go back to 4in1 4.47 because I suspect it is causing a problem on my PC and this way I would like to troubleshoot it. Can I simply install 4.47 on top of 4.49p, I would like to do it the best possible way.

And thanks for providing this awesome tool for the community - and GL with all the future development of DC and other tools.

Karmacop · Oct 21, 2003, 02:04 AM

Ok, this is a long story but I was hoping someone may be able to help.

Sometimes I would get an error like this when running opengl programs

Microsoft Visual C++ Runtime Library
Runtime Error!

Program: C:\QUAKE2\Q2E.EXE

abnormal program termination

Just as an example. This happens with quake 3 etc (not sure about d3d games), and now iut happens everytime, I can't even play.
Anyway, I've got the latest video drivers, reinstalled windows, upgraded my bios etc but I kept getting this error.

Then I found out about driver cleaner. I followed the instructions and I no longer got the error. But, I was getting 10fps in games. Then I rebooted my machine and I got the speed back, but again I'm getting this error.

Any ideas? I find it strange that driver cleaner can fix it (sort of) and a reboot can revert it back to normal.

Thanks. Great program by the way.

**MIG-31** · Oct 21, 2003, 02:53 AM

try this.

uninstall drivers.

reboot into safe mode

use driver cleaner then reboot

re-install dx9.0b reboot

re-install chipset drivers reboot

re-install vga drivers reboot.

just to say also many new comers to driver cleaner has had problems by using driver cleaner without removing drivers first.and fail to read the read me included.

give that a try it might help.

Karmacop · Oct 21, 2003, 06:31 AM

I just tried that and I get the same original error

**Spike** · Oct 21, 2003, 06:50 AM

dzjepp just run the installer of via and select uninstall. Than install the older version after that.

Phillychuck · Oct 24, 2003, 05:33 PM

So whats the fix if you didn't read the readme? I don't usually read them.

I like the concept of your program, but I feel that if you know the outcome results in a broken OS for not following proceedure your making a big mistake. Most people can't read, I've experienced it as a Sysop of a BBS for years and as a MMORG player. You can say something 20 times to 50 people and only 10% at best will read it...

I'll probably reinstall XP since I've been fooling with stuff for an hour already...

I guess a little info on which driver I goofed on would help:

Was tring to clean Nvidia for the new Forceware drivers, now no matter what version I try to install it won't take (no error), and a manual install of the driver says the device is a Code 19. Something about corrupted system file or registry.

-Chuck

**Spike** · Oct 25, 2003, 03:21 AM

Chuck, i made a small adjustment in the new version, for people that don't read readme's. you get now a popup telling that you should follow it or you can run into problems. Also in the new version is a new special nvidia cleaning file for people that had problems before or am not sure.

The problem you have is for every person different. Some have it and a lot not, i tried it a lot of times to see if i can get into that problem, but no effect. By me it works perfect. So i hope with that new cleaning file that the problem will be solved.

But what you can do is run the xp cd and select repair.