Vista - WM5 and WM6 devices died after faulty sync with WMDC

Okay, I have three devices I am trying to sync with Outlook 2007 and Vista
via WMDC final release (no betas).

One of them I left off the loop because it is my main phone.

My two HTC Wizards (one is a Qtel 9100 Vodafone and the other one is a
T-Mobile with the MB WM6 "beta" version) simply won't fully sync the first
time.
I had a stuck progress bar after30% in one device and 95% in the other one.
After about two hours I decided to click on the STOP button, but, as I would
surely imagine, it was useless.
I then tried to force a stop from within Activesync on my WM device. Hard to
get to the proper screen, because WMDC seems to entirely dry the device's
juice. When I finally and patiently get there, the stop is also useless (yes,
I am very patient sometimes).
What is, then, left to do? Yup, pull the plug.

Bad news is each device no longer pass the second boot screen. I keep seeing
the Windows Mobile screen forever, unless I do a hard reset, which is painful.

Folks, am I a sole soul suffering from this blackmagic or is there someone
to commiserate and try to join forces to find a workaround?

Also, is there any logging tool that would help us with finding the culprit
for that?

I know it is hard to be an early adopter most of the time, but WMDC has been
tested over three beta versions prior to reaching the "secure" streets of
"Released to Distribution"; I fealt like it shoulde have been doing better.
Tons of problems (especially with Live OneCare) are emerging and people are
getting frustrated. We should see a quicker response and I see nothing. We
are forum users and most of us are above average users; if we are chasing our
tails, go figure what is going on with the average users...

Please someone shed a light in the tunnel!



-Feaps®

Okay, here is what I had to do in order to get it to work: I took the latest
PST file I had for Outlook 2003 before moving to Vista/Office2007. I imported
all the data to my new Outlook 2007. After that, sync worked fine.

Go figure...



-Feaps