Hello Todd,

Thanks for responding.

TA> Having said that, I don't believe in coincidences- if this McAfee
TA> snafu happened around the same time, it's extremely likely to be the
TA> culprit. However...

I have not at all ruled that out, espeically since I cannot be sure if the
McAfee SNAFU occurred before or after the Axim stopped syncing with the laptop.
All I can say is they happened about the same time.

TA> Are you sure about the timeline here- did the error start before or
TA> after the OneCare install?

Absolutely certain it was before the OneCare install. I was having the two
issues at the same time -- the lack of synchronicity between Axim and laptop,
and the antivirus software problem. Since the latter was more important than
the former, I concentrated on that until I managed to get the laptop to a
point where it is no longer vulnerable and I can concentrate on the Axim
sync problem.

Incidentally, after I uninstalled McAfee and before settling on trying OneCare,
I tried installing the trial version on Norton Antivirus 2007. What a joke.
It would not activate so I could not even get it to install properly let
alone work. I called their Tech Support and the chap I online chatted with
said essentially that I would not have this problem with the purchased version!
I asked him if he was saying that the trial version was useless then, and
he said yes! Still desperate for protection, I bought it from WalMart and
installed it -- same issue ... would not activate. So I uninstalled, ran
its cleanup tool and checked the Registry personally. That is when I decided
to look at OneCare.

TA> Others have posted that they've had to
TA> manually open the OneCare firewall to let WMDC work if OneCare was
TA> installed after WMDC.

Yeah, I read that, but doesn't apply in this case since I had the same problem
before OneCare.

TA> If you did have the troublebefore, then McAfee might not be
TA> completely uninstalled, and manually removing all McAfee references
TA> from the PC's registry might be worth a try, followed by a reboot
TA> (insert all "dangers of modifying your registry" disclaimers here.)

Did that. More than once. After each attempt.

TA> The fact that McAfee won't reinstall is a good indicator it's still
TA> messing up the works somehow.

That is my feeling .... the ghost of McAfee .... actually I think it is all
gone but before going, it screwed some setting or the other. That is what
I believe is causing this problem.

TA> Best of luck- tracking down a sync problem is a b*tch, partially
TA> because no one wants to reproduce your issue on their own PCs just
TA> in case! ;-)

I agree. Funny enough, I had it with ActiveSync, and that is why I upgraded
to Vista .... just so I had WMDC, *despite* what some people said about WMDC
at the time. I had a bear of a time getting Vista to see my Axim, and even
had the MS Research Department (like level 3 tech support) call me daily
trying this and trying that, when all I wanted was a Registry tweak that
would get the two talking. Eventually I solved it on my own, after researching
and all it took was 5 minutes. I shared this fix with him and he was grateful.
Now ask me if I remember what it was!

Anyway ... thanks for your help. I am hoping that someone else who might
have had a similar problem with this error knows what the fix is.

Regards,
Wayne Moses
Houston, Texas