Select to view content in your preferred language

Version 10.0 R4 unacceptable

3012
4
06-25-2012 06:44 PM
JohnZimmerman
Deactivated User
I am a long time ArcPad user, from back in 2003 with version 6 or thereabout.  I have used all versions of 6 and 7 and now 2 versions of 10.  It has been a great and reliable tool all along, generally always performing well. 

My current use is on an iPAQ 210 running windows mobile 6.  I just "upgraded" to the new version, R4. 

It is bad and it is unacceptable.  It is incredibly slow to the point where I am not sure it is not hung up and on simple tasks that were very quick before.  It has also been very unstable, freezing the machine at least 4 times in about 4 hours of use.  This is the first version I would have ever considered to be a problem, and it is really a problem.  Unless I hear that there is some fix, I plan to ask for a refund and return to version 7.
Tags (3)
0 Kudos
4 Replies
MarikaVertzonis
Esri Regular Contributor
You mention that you have used 2 versions of 10. Which 2 are they? - this will help pin point the true source of your problem. 10.0 R4 contains some very specific fixes that are not related to windows mobile performance, so I would expect the performance changes you are reporting are more symptomatic of ArcPad 10 rather than an individual service pack. (Lets not create misleading messages here).

If indeed your problems started with ArcPad 10 then what you describe is expected behavior with the hardware you are using. Remember that every application on a Windows Mobile device has a maximum memory allocation of 32MB. To start with, ArcPad 10 is simply bigger than previous versions (approximately 3MB bigger), so it will use more memory (leaving less for your project data, and subsequently a higher likelihood of insufficient memory to operate). There is also a sizable difference in the amount of memory used to start ArcPad between different versions of Windows Mobile. Windows Mobile 6.1 and 6.5 have demonstrated significantly more effective memory consumption compared to Windows Mobile 6. Windows Mobile 6 also demonstrated poor performance when loading multiple extensions. So it really is a must on Windows Mobile 6 to remove any unused extensions.

Basically somethings got to give. If you can not change your hardware, and you would like the current version of ArcPad, you must sacrifice either ArcPad Project elements (eg: use less data), or disable as much unused ArcPad functionality as possible (eg: turn off extensions).

If you would like more detail about the memory used to launch ArcPad, and its measured behavior on different operating systems, please contact Esri Tech Support. Remember ArcPad does come with Support - the kind of issues you are describing in this thread are probably better handled with Tech Support not on a forum.
0 Kudos
JohnZimmerman
Deactivated User
Thanks for that reply and I will look into the windows mobile issues.  I do realize it could be an issue on my side with hardware yet it is very frustrating to see performance go backwards.

I am not certain which previous version of AP 10 it was.  I downloaded and started to use it about 3 months ago.  I moved to r4 about 2 weeks ago.
0 Kudos
TomasRiesco
Deactivated User
I hear you, It is the same here.. V3 and V4 they both give the same problem. Im running ArcPad 10 on a new trimble GeoXT and I think it should not be giving these problems on a new hardware and new software.
0 Kudos
JohnZimmerman
Deactivated User
I hear you, It is the same here.. V3 and V4 they both give the same problem. Im running ArcPad 10 on a new trimble GeoXT and I think it should not be giving these problems on a new hardware and new software.


Well, I guess that backs up what I have been seeing.  I did take the advice above and turned off all extensions except those for images.  Still very very slow.  I have not run it enough since then to see if it still freezes often but I am not hopeful.
0 Kudos