I fixed the three items mentioned by someone in that thread. Seems to
have done the trick. That particular file didn't come up.

Thanks for the response.


Tom R. wrote:

> I'm no expert so maybe someone else has the answer but
> I read your log and I would question this:
>
> O2 - BHO: (no name) - {0D49D952-6AD8-4B76-BF04-BAFEF961E9BD} -
> C:\WINNT\system32\tvrlykjg.dll
>
> Good Luck,
> Tom
>
>

--
J. S. Greenfield

I represent nobody but myself. The opinions expressed --
especially any particularly stupid ones -- are mine, and
mine, alone.