Re: HELLO MICROSOFT
- From: "Cliff Milliken" <cliffm@xxxxxxxxx>
- Date: Mon, 9 Apr 2007 12:31:06 -0400
Well, well!
Problem is finally fixed.
Axim x50v with WM 5.0.
- Do a full backup to the storage card.
- Do a hard reset.
- Do a full restore.
- Sit back and enjoy a beverage of your choice.
This fixed the synchronization problems with calendar and contacts,
(0x8007000e error) and the IE problems (could not connect using wireless,
but I could ping the web).
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT
com> wrote in message news:u30XaGhdHHA.3956@xxxxxxxxxxxxxxxxxxxxxxx
Yep, that should do the same thing as the memory applet.
The MS DST update is not an application, but a set of registry changes.
There is no executable code involved with it at all.
It is impossible to completely remove ActiveSync from the PDA. It's part
of the OS. You can, with various hacks, prevent it from running when you
connect to the PC, I guess, but it seems like the utility of the PDA would
be compromised if no syncing were supported, wouldn't it?
Paul T.
"Cliff Milliken" <cliffm@xxxxxxxxx> wrote in message
news:u7hlXEadHHA.2268@xxxxxxxxxxxxxxxxxxxxxxx
Paul,
Thanks for the description of the memory management in the PDA. That
helps.
I regularly use the Switcher Bar application to kill unwanted processes.
I believe that is the same as using the Memory control panel.
There are 2 applications installed on the Dell x50v PDA: Dell GPS and
Microsoft DST Update. Both are valid WM 5.0 applications (although I
must doubt that the MS DST Update is a proper application for any version
of the PDA OS!).
These assumptions lead me to this question. How do I completely remove
ActiveSync from the PDA?
--
Cliff Milliken
Systems Vision Consulting
(513) 383-7689
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam
DOT com> wrote in message news:%23vctssUdHHA.1216@xxxxxxxxxxxxxxxxxxxxxxx
Yes, for quite a while, in fact. There's not going to be any action on
*another thread* because you posted this message. You can try bumping
your thread by posting another message to it in hopes of drawing
attention to that fact that it's unresolved, but it's too much to ask
someone to go hunting through the recent threads looking for the one
you're talking about.
There is memory protection, at least for some of the address space, in
WM5. There are 32 process slots, none of which can access the other
slots' memory. There is, however, a large size shared memory area
which, if you have a bad application or driver, could certainly stomp on
something. Since ActiveSync generally doesn't just crash, it's something
about what you are doing specifically. Note also that upgrading to
AS4.5 on the PC *DOES NOT MODIFY THE VERSION OF ACTIVESYNC ON THE
DEVICE*.
If your crash is occurring on the device, you might go into the Memory
Control Panel applet on the device and stop any programs that you are
not using (the X on applications in Windows Mobile does *not* close the
applications; it just hides them, so you may have a large number of
applications running without knowing it). If you've tried to soft reset
the device (which is more-or-less like a Ctrl+Alt+Del warm reboot of a
PC), and AS fails when you try it immediately after that, I'd uninstall
any programs that you've installed on the device which might not be WM5
compatible. It's possible that some program might install a DLL in the
Windows folder on the device which is 'wrong' for the rest of the
operating system, including ActiveSync. At some point, a hard reset of
the device may be necessary and a careful, one application at a time,
reinstall of potential problem apps.
Paul T.
"Cliff Milliken" <cliffm@xxxxxxxxx> wrote in message
news:uZaDQFNdHHA.596@xxxxxxxxxxxxxxxxxxxxxxx
Paul,
Have you been reading the posts in this newsgroup? I think it should
be clear that there is a problem with SOMETHING, but I know not what.
There have been a number of changes needed to implement DST. This is
just 1 small piece of the puzzle, and it appears to have broken a LARGE
number of PDAs sync application.
I have posted the details in another thread! This is just a post
indicating my frustration with ActiveSync 4.5 breaking my sync with
Exchange, and the TOTAL lack of response of MS to the problem.
You responded to "Ilene" in another thread. I mentioned to her that my
sync went away after following MS's DST instructions for a PDA. I
think she mentioned the DST issue because we exchanged posts about that
subject. The MS instructions included an upgrade to AS 4.5. No way an
upgrade should break anything, but I can not find anyway to reverse the
process. It obviously broke the process.
FYI, I have been using/training/consulting MS products for the better
part of 2 decades. This is the first time I have been at a total loss
locating information about how to fix a problem. I exhausted Google
and my MCT forums. That implies a) no one has the problem, or b) I am
the only one on the planet that has the problem. The large number of
problems on this forum implies that neither "a" or "b" is true, and
that no one has a fix. Those that continue to work might never have
applied the DST fix, or as you suggested to Ilene, might not have
upgraded to AS 4.5.
Oh well!
I must assume that at some point in time, MS will release an "upgrade"
to AS that might work. It might only work on WM 6.0, at which time I
might as well throw my Axim 50v in the trash. BTW, the error in my
other post refers to code 0x8007000E, which implies lack of memory. I
expect that error is due to a memory overrun in the AS program, but
I've no clue how to solve that problem. My guess is that there is no
memory protection available in the WM operating system and it simply
trashed the OS, but I can't find any documentation about that either.
If you can refer me to some information that will help me be a bit more
proactive, that would be helpful.
--
Cliff Milliken
Systems Vision Consulting
(513) 383-7689
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam
DOT com> wrote in message news:ucbHCd8bHHA.1216@xxxxxxxxxxxxxxxxxxxxxxx
I think that it should be clear that you're going to have to give more
information than "severely broken" to get something fixed. You haven't
told us 1) what device you're using and what version of Windows Mobile
it's running, 2) what version of ActiveSync you're running, or 3) what
the problem is. Many (I don't know what percentage, but "many"), are
running AS 4.x with the DST fixes applied to the PC and to the device
and not having issues...
Paul T.
"Cliff Milliken" <cliffm@xxxxxxxxx> wrote in message
news:eI2eSToaHHA.2436@xxxxxxxxxxxxxxxxxxxxxxx
Is anyone listening?
The ActiveSync software is severely broken after applying DST
changes!
Yoo Hoo - Please help!
--
Cliff Milliken
Systems Vision Consulting
(513) 383-7689
.
- Follow-Ups:
- Re: HELLO MICROSOFT
- From: Paul G. Tobey [eMVP]
- Re: HELLO MICROSOFT
- References:
- Re: HELLO MICROSOFT
- From: Cliff Milliken
- Re: HELLO MICROSOFT
- From: Paul G. Tobey [eMVP]
- Re: HELLO MICROSOFT
- From: Cliff Milliken
- Re: HELLO MICROSOFT
- From: Paul G. Tobey [eMVP]
- Re: HELLO MICROSOFT
- Prev by Date: Re: Many Problems With Vista Sync Center
- Next by Date: Re: HELLO MICROSOFT
- Previous by thread: Re: HELLO MICROSOFT
- Next by thread: Re: HELLO MICROSOFT
- Index(es):
Relevant Pages
|
