|
well, alot of the question you asked me were answered in my first post.
But, from what MSCONFIG showed me, i only had one instance of rundll32 running and i stopped it, and regardless, like i said, the drivers are of the newer brand that should not be affected by this issue anyway (beyond 41.09) wich i DID upgrade to by uninstalling the previous drivers first (i dont always do that though). But yes, i can access my cards controll panel anyway and all the files listed are up to date
Also, i beleive i TRIED to use detonator destroyer, but i dont think it was released for win2k yet. If it was, then i may have used it.
Spyware? I have ad-aware 6, but i havent done a full scan for a while (although i did a "quick scan" a couple weeks ago and dumped some stuff from that) so i could try that, but do you really think spyware is causing rundll32 to run after i start windows up? I dunno.
To address one last thing you mentioned, am i SURE rundll32 didnt reactivate on startup? No, i'm not, how would i check that (as i dont see it in the taskmanager, and i've NEVER seen nview running regardless). Hell, i dont even know if the Msconfig program is doing it's job, wich is where i unchecked rundll32 to stop on startup. (wich i downloaded btw, i AM running win2k, wich doesnt normally have msconfig....wich for a while pissed me off because i couldnt do that common solution).
i'll let that sink in for ya (since the error is obviously still here, it's possible that rundll32 didnt go away like it should but i dont know how to check that) and in the meantime will try and find time to do a full spyware scan.
|
14-09-2003, 23:58
Hybrid Mode
