Wednesday, September 10, 2003
The Next Generation: HP Ipaq H2210/H2215
Posted by Jason Dunn in "ARTICLE" @ 07:30 AM
"The well-known and much praised design of the Ipaq 3-series has had its day. The world's most successful Pocket PC family, according to Dataquest Gartner, now has a new family member - the 22xx series. HP has just launched the first model in this new product line - the Ipaq H2210/2215. The fact that the models H2210 and H2215 are basically the same product is bound to lead to some customer confusion. The H2215 is being distributed through retail channels, while the H2210 is targeted at business customers."
It's always interesting to read Pocket PC reviews by non-PDA sites, because there will almost always be subtle errors. I'm sure camera review site owners groan in the same way when I talk about cameras here. ;-) The authors of this article state that Windows Mobile 2003 has been "finally been optimized for XScale processors", which is false. Windows Mobile 2003 has been optimized for the ARM5 instruction yet, which will benefit the XScale CPU, but also the Samsung and any other ARM5 processor. It's a subtle, but important difference. If Microsoft chose to optimize for one CPU from one vendor, they'd be placing a big bet on that one chip. Optimizing for the instruction set instead of a single CPU is a smarter move.
Still, this is a good article if only for the benchmarking data - they've cooked up their own benchmarking tool, so the data is different than what most of you have seen.
It's always interesting to read Pocket PC reviews by non-PDA sites, because there will almost always be subtle errors. I'm sure camera review site owners groan in the same way when I talk about cameras here. ;-) The authors of this article state that Windows Mobile 2003 has been "finally been optimized for XScale processors", which is false. Windows Mobile 2003 has been optimized for the ARM5 instruction yet, which will benefit the XScale CPU, but also the Samsung and any other ARM5 processor. It's a subtle, but important difference. If Microsoft chose to optimize for one CPU from one vendor, they'd be placing a big bet on that one chip. Optimizing for the instruction set instead of a single CPU is a smarter move.
Still, this is a good article if only for the benchmarking data - they've cooked up their own benchmarking tool, so the data is different than what most of you have seen.