Right now, both machines Send/Recv okay. The failure isn't
likely to happen until the next boot. So, the next time I get a
failure on either of the machine, I'll bypass the router after
I blow away OE-Not Responding and then restart OE to
see if the problem goes away.

The Linksys WRT54G has the latest firmware installed and
I don't have any problems with OE News or Firefox while
OE is in a state where a click on Send/Recv would freeze
OE. That is, Send/Recv is automatic with a start of OE and
I can tell at that point that the initial Send/Recv has failed, but
OE doesn't actually freeze until I manually click on Send/Recv
at that point.


"Bruce Hagen" wrote in message
...
What if you eliminate the router? Is the first machine still OK?

While I haven't seen AVG cause a problem like this, I switched to Avast
some time ago because I felt they were not keeping up with bugs as good as
they could. You might give it a try. Nothing to lose at this point.

Choose Custom Installation and under Resident Protection, uncheck:
Internet Mail and Outlook/Exchange.

Avast:
http://www.avast.com/eng/download-avast-home.html
--
Bruce Hagen
MS-MVP Outlook Express
Imperial Beach, CA


"Bill" wrote in message
...
OH OH!! The same thing has happened on the 2nd
computer here. They only share the router gateway
to the Internet. Other than that, they are two inde-
pendent desktop machines.

Both machines have AVG Internet Security without
the e-mail scanning plug-in installed.

The only updates taking place on these two machines
are the regular updates from MS and those from AVG.

See the rest of the thread for the actions taken on the
1st machine that experienced this problem.

Bill


"Bill" wrote in message
...
Just within the past week or so, OE freezes
following the morning's boot "if" I click on
"Send/Recv". Other functions "Newsgroups",
folder and message views function normally,
but as soon as I click on "Send/Recv" OE
"hour-glasses" and I have to cancel with the
Task Manager.

There are no error messages nor do I get the
opportunity to log the condition with MS.

The problem clears up if I re-boot the
machine.

I've been using OE for at least 10 years or
more without any difficulties. I don't see
anything in recent MS updates pertaining to
OE, so I can't tell if any recent MS updates
are to blame or not.

Any suggestions?

Thanks,
Bill