To view parent comment, click here.
To read all comments associated with this story, please click here.
Re: "The bug is actually in Palms software on WM5."
Please clarify what software you believe is not Microsoft's running in Windows Mobile 5.0 that is causing the issues mentioned (ie: memory hog, inability to close applications, poor screen resolution).
Re: "The 700w is also grossly underpowered and as such has TONS of problems. Even browsing on the 700w is DOGGEDLY slow (but this is not true on any other WM5 device)."
This is not a hardware issue but instead is an OS memory allocation and resource issue directly associated in the way Microsoft designed Windows Mobile 5.0. If you take a look at the Treo 650 you'll notice that even though the device has less memory the OS (Garnet) handles multitasking better and the use of memory is more logical. Reports flying around the net is that the Treo 700P is similar to the 650 with the way memory is allocated. Which means with the increased memory added in the 700 series there should be more memory accessible to the user than those using the 700W. Unless of course Microsoft produces a free update to resolve the glitches.
Edited 2006-03-30 15:14
Actually, there was no memory increase from the 650 to the 700w.
It is running on the same exact hardware.
Of course WM5 is heavier than Palm (as it should be, it's a much more capable OS, though it should be lighter than it is, but that is beside the point).
No other WM5 device has these problems that are on the 700w. There is also a LOT of Palm software on the 700w. Microsoft only made the OS (same OS that runs on any other WM5 device, which all work perfectly fine).
This has nothing to do with how WM handles memory.







Member since:
2005-07-06
The bug is actually in Palms software on WM5.
If you'll notice, no other WM5 product has this issue.
The 700w is also grossly underpowered and as such has TONS of problems. Even browsing on the 700w is DOGGEDLY slow (but this is not true on any other WM5 device).