[dba-Tech] RunDLL32

"they've done everything they could, and have finally determined that it is
something in Windows itself" Kathryn

...bs :)

...they've left something in your registry, startup, or ini files ...no
matter what they tell you :(

...Mike suggested using msconfig from the run command and that will probably
do it ...if not, use Norton Utilities WinDoctor ...and if THAT doesn't do it
...go over to www.langa.com and search his archives on "startup" ...he's had
a number of excellent step-by-step articles and tool reviews on just this
type of problem.

William Hindman
<http://www.freestateproject.org> - Next Year In The Free State!


----- Original Message ----- 
From: "Kathryn Bassett" <kathryn at bassett.net>
To: "DBA-Tech" <dba-tech at databaseadvisors.com>
Sent: Thursday, January 01, 2004 4:17 PM
Subject: [dba-Tech] RunDLL32


> I've been having an annoying problem for a number of months. I had been
cleaning up by uninstalling programs that I don't use. One is Ofoto, which
seemingly successfully uninstalled. However, every time I boot up, I get an
error message http://www.ourmailinglist.org/ofotoscreens/theError.JPG
>
> Well, duh, of course it can't be found as I deleted the program. But why
does it RunDLL keep looking for it? I've had several phone conversations
with Maurice at Ofoto, and they've done everything they could, and have
finally determined that it is something in Windows itself, and they can't
help me further. I must say that we tried a lot of things, and I agree that
it is not them.
>
> The underlying problem seems to be getting rid of one registry entry which
refuses to go away.
>
> HKEY_CURRENT_USER
>    Software
>       Windows
>          CurrentVersion
>             Run
> OfotoNow USB Detection C:\WINNT\System32\RunDLL32.exe
C:\PROGRA~1\Ofoto\OfotoNow\OFUSBS.DLL,WatchForConnection OfotoNow
>
> I can delete that OfotoNow USB Detection entry, but it won't stay gone.
Something seems to be telling regedit to put it right back. One possiblity
that Ofoto suggested as the most likely culprit was ZoneAlarm, so that was
uninstalled and (after appropriate reboots), we tried again to delete it.
Still comes right back.
>
> I've just been putting up with getting that error message then closing it,
but it really is annoying. Any ideas?
>
> --
> Kathryn Rhinehart Bassett (Pasadena CA)
> "Genealogy is my bag" "GH is my soap"
> kathryn at bassett.net
> http://bassett.net
>
> _______________________________________________
> dba-Tech mailing list
> dba-Tech at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-tech
> Website: http://www.databaseadvisors.com