Re: Randomize working - Activesync 4.2 Beta & Windows Mobile 2005

Hi again Paul :

Very important ! I have detected the possible cause of but syncs.
As you know I only can sync once every 20 tries, more or less... looking
with Ethereal I've detected everytime I have a bad sync (at start, during the
sync, at the end of the sync...), I can see some SRVLOC protocol paquets
going from computer (169.254.2.2) to strange addresses (not the PDA address).
So VERY PROBABLY this paquets make some king of bug during sync (yes...
activesync or PDA is unestable and can not continue working OK after this
paquets).

When a correct sync is done the PDA will continue working OK until I take
it out from the USB dockstation (for example eight hours later). And If I
take a look at ethereal I will see there aren't SRVLOC paquets NEVER...

Just... if I see SRVLOC paquets during the start of the sync, it will SURE
not work.

Tha'ts the cause... now let's work for the solution... how can I stop SRVLOC
paquets from computer ? Why sync is unestable in front of this kind of
paquets ?

Best regards,

Paco Plus

"Paul G. Tobey [eMVP]" wrote:

I've been out of town, but I don't have any information on a schedule for
final release or a list of resolved problems. I'm sure that they do need
more people, but, even if they added 100 tomorrow, that wouldn't give some
sort of sudden leap forward in stability. That's just the nature of
engineering; it takes time to start being productive.

In the grand scheme of software development, it's pretty unusual to get a
released version within a month of a beta that fixes every known problem.
If there is a third-party component that will actually fix the problem that
you know you have, I don't see any reason not to use it. Results are what
matter. The fact is, though, that the communication stuff is likely to be
the same in AS and their software, at least for the same connection types.
You'd better be sure that they aren't running on top of ActiveSync before
assuming that adding in some more software is going to fix anything.

Paul T.


"Paco Plus" <PacoPlus@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6A4162C7-B91B-4B9B-86B6-D6D05C30055D@xxxxxxxxxxxxxxxx
Hi again Paul !

Is there any progress in Activesync 4.2 beta ?

I'm still having the same inestabibilities I had the first day, one month
ago.

Any solution from Microsoft ? Do they need some more resources,
programmers
? Inestabilities and bugs resolved ?

Ok... let's start thinking about buying Intellisync...

Yes... they have probably less programmers than Microsoft but I think
their
software is stable and works better than Activesync (as I see in some
forums).

Possibly they take seriously about their product.

Best regards,

Paco Plus




"Paul G. Tobey [eMVP]" wrote:

- Why Activesync 3.X was more estable than 4.X ?

3.8 was the eighth generation of the same basic software, so it had been
tested, retested, modified to fix problems, eight times. 4.0 had been
tested once, by MS using the set of test machines that MS had, etc. I
don't
think that there was even a beta of the 4.0 that was publicly available
(since you had to have a WM5 device to use it, there wasn't a large group
of
field people, even MVPs, that had a device to test with), so it's testing
cross-section was very small. There may have been a beta of 4.1, but,
again, the number of people who could actually test this was pretty
small.
There is presently a beta of 4.2 in progress and, since the number of
people
with WM5 devices is much larger now than six months ago, this has the
potential to actually get valuable input from the field. Use it! Report
problems to astell <at> microsoft.com. Don't expect them to be fixed
instantly, but carefully detail what versions of things you are using,
what
hardware you are using it on, and what the results are. If MS doesn't
happen to have the same laptop as you, they'd need to be able to, at
least
potentially, buy one, so don't expect overnight changes.

- Why did AS team decided to take out TCP/IP sync (wireless or cabled),
and
at the same timek decided to implement a TCP/IP sync over USB ? ¿?¿?

Security. This has been beat to death on the newsgroup. They targeted
business/enterprise users with WM5, an area not particularly hot on WM
devices previously. My guess is (and this is a *guess*, but I hope a
good
one), that enterprise network administrators told MS that they would not
allow these devices/ActiveSync on their systems because there were too
many
security holes. MS addressed this by blocking the biggest/hardest-to-fix
one, which was network sync to a desktop PC.

The implementation of TCP/IP as the carrier for all sync traffic allows
MS
to add new features that should work in both desktop and Exchange sync
more
easily because the sync engine on the device end is the same for both
cases.
Long-term, it will result in a more-stable and more-functional product,
which is good for everyone. Short-term, it resulted in a less-stable,
less-functional, although only for a small subset of the total customer
base, product. Those who knew about wireless sync in 3.8 and cared
missed
it, but this is a small fraction of total customers.

- Why did AS team decided to switch off interesting options like
'Schedule'
button ?

Since my last device before the WM5 devices that I've used recently was
very
old, I don't know what this was, so I can't speak to it. If you can be
more
specific, I might be able to get an answer... At a guess, because it
takes
resources to maintain any option that's in the software and their
research
told them that very few people were using it and they didn't, therefore,
want to spend their limited resources to support it.

Paul T.


"Paco Plus" <PacoPlus@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6AFE7958-0BA8-4A30-BE6A-D79C9DDA2DB6@xxxxxxxxxxxxxxxx
Hi Paul :

Sorry about my last e-mail.

I'm sure Microsoft ActiveSync team is doing something... but possibly
not
enough.

I've tried E_V_E_R_Y suggested possibility, reading a lot of forums,
Microsoft ActivesSync 4.X help, bypassing Firewall, bypassing
antivirus,
sniffing IP information with Ethereal to try to undersand what's
happening,
reading log files created by activesync (not too much helpfull,
really),
looking to system messages saved in Administrator tools, changed to
every
USB
port in computer, reseting ActiveSync in PC, reseting full PC, reseting
full
PDA, juts TCP/IP service in Windows Mobile-based device (switch off
file
and
printer sharing, microsoft client, ...), praying (oh, my God, oh my
God),
dancing to the Devil, ...

I'm Telecomunications engineering, it doesn't mean I know everything
about
technological possible problems, but just that I know something more
than
'Press start down-left in Windows to see the menu'.

I'm happy to see a lot of answers from Microsoft Activesync team in
this
forum, it means you worry about our problems.

As you said (i don't remember where) the problem probably is in the
Networking part, not in the USB. I see, when I loose syncronization (or
simply don't get connected) I can still PING my PDA and obtain ping
answer...

I just ask myself :

- Why Activesync 3.X was more estable than 4.X ?
- Why did AS team decided to take out TCP/IP sync (wireless or cabled),
and
at the same timek decided to implement a TCP/IP sync over USB ? ¿?¿?
- Why did AS team decided to switch off interesting options like
'Schedule'
button ?

Best regards,

Paco Plus

"Paul G. Tobey [eMVP]" wrote:

Nothing, huh? And you're sure about that why? Do you know *anything*
about
it? Or are you concluding that, because you aren't willing to
actually
try
anything suggested here to fix your problem, Microsoft isn't working
to
improve ActiveSync?

Paul T.

"Paco Plus" <PacoPlus@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CD790266-ED3D-4DB3-B715-4A4EFA66823B@xxxxxxxxxxxxxxxx
Hi Fernando:

As I see, thousands of 'happy' users with Windows Mobile 2003 &
ActiveSync
3.8 are having serious problems with Windows Mobile 2005 &
ActiveSync
4.1
(4.0, 4.2, ...).

Microsoft is doing nothing about that... that's all.

Best regards,

Francesc Mas


"Fernando Rodrigues" wrote:

I Used a XDA II mini with Mobile Windows 2003 64mg ROM and he/she
didn't
have these problems.

Now I decided to change for a Torq P120 with Mobile Windows 2005
with
128
mb
ROM and it is a hell to synchronize.

I have + - 1000 contacts and he don't get to synchronize nor 600

He/she locks periodically

What do make??? Do I go back to the old?? The microsoft doesn't
talk
anything about this, million in investment and thousands of
programmers
and
nothing works well!!!

Fernando

--------


Eu Usava um XDA II mini com Windows Mobile 2003 64mg ROM e não
tinha
estes
problemas.

Agora resolvi trocar por um Torq P120 com Windows Mobile 2005 com
128
mb
ROM
e está um inferno sincronizar.

Tenho +- 1000 contatos e ele não consegue sincronizar nem 600

Trava periodicamente

O que faço ??? Volto para o antigo ?? A microsoft não fala nada
sobre
isto,
milhões em investimento e milhares de programadores e nada funciona
bem!!!

"Paco Plus" <PacoPlus@xxxxxxxxxxxxxxxxxxxxxxxxx> escreveu na
mensagem
news:AFBE3861-73B7-46FD-9F73-BFD45C40278E@xxxxxxxxxxxxxxxx
Hi :

I recently bought a new Dell Axim X51V PDA. I was a 'more or
less'
happy
user of Dell Axim X5, windows mobile 2002 & activesync 3.8, which
few
times
had some USB problems to synch, but normally worked OK.

Now, with the new PDA, I feel like a Beta tester, using a 'beta'
version
of
Windows Mobile 2005 with a beta Activesync 4.1 (or 4.2). I see
miles
of
mails
in different world forums, too many people asking why are so many
problems
to
sync through USB, and why Microsoft decided to forget about synch
through
Wireless wifi, a very fast and confortable method used for so
many
users.
Why
Microsoft deleted the Schedule button just for Windows Mobile
2005
(it
was
very useful with Windows Mobile 2002).

My panorama :

Two PC's (home and work) equipped with Windows XP, SP2 and the
last
updates,
Activesync 4.1 or 4.2 Beta, correct setup for firewall and
antivirus,
ethernet services like share deleted.
.