Review: Mullenger's Windows CE 4.2 ROM upgrade for the SIMpad

Juergen,

You've got to take that in the context of me talking about Windows CE 4 devices (4.0, 4.1, 4.2), not Windows CE devices as a whole.

Don't think of WM2003 devices as CE4.2, as bad things will happen if you blur that line.

C:Amie,

to be honest, for one, maybe two moments I was thinking of you blurring that line . A lot of developers and software houses formerly well known for their magnificent hpc software now aim on WM2003 - but whom do I tell, probably you know much better than I do .
I don't really _know_ any developers (well, maybe two or three...), so I don't see what happens in the background. What I see is only the result of their efforts, software offered for download/ purchase. I see a lot of 3.0 software releases offered for hpc and pocketpc, but 4.0, 5.0, 6.0 releases only available for pocketpc. I see (as a pocketpc user, too) the number of WM2003 applications jumping up. But I haven't seen yet that many CE.NET 4.2 applications. Not a quarter as many to speak of 'lion share'.
From my point of view you're absolutely right in theory - a standardised SDK is a strong argument why developers should aim on CE.NET 4.2. But do they really do? I don't know. I have to take your word for that and happily await plenty of brand-new programs for my Netbook Pro .

well that's my opinion too. there's not much programs available specifically written for ce.net 4.2
but if it's true... i want them!

Windows CE is empirically something of a user trap.
Effectively you have to try and visualise, and maintain that idea of Windows CE not really being what you're using on most devices.

It is the subject of a lot of confusion for users, the fact that they have a Windows CE device, but it doesn't by nature of the trademark run Windows CE Software.

I often use the Linux analogy to try and clear it up.
If you go and download Mandrake (or whatever it is called these days), Suse, Red Hat/Fedora etc. You are downloading a Linux based OS (don't think of the OS as the GUI level, think of it as the hard core programming beneath it that you never see). With that comes the user level, the GUI (gnome/kde), the x server, the driver support, server programs, network tools, games, multimedia apps, office apps and so on.

Windows CE 4.x is the base OS. It is designed to be taken by developers and built upon to produce custom solutions. It intrinsically was not designed to be dropped onto commercial devices as is. Microsoft wanted OEM's to take the bSquare approach and build CE 4 user level up from the ground , of course no one did that.
Developers don't target CE4 because it is a limited margin area, where devices are not encouraged to be prevalent in the general user population, but more orientated towards the specialist market, where as part of a solution the device would serve as the corner piece of a custom built application bundle (data warehousing, hospital aids, kiosks, petrol pumps and so on).

The problem with developing for the 2.12, 3.0, 4.0 and 4.1 release was that if you were an independent developer you are reliant on the OEM for a specially constructed Dev kit. Which are generally acknowledged as being a nightmare to get hold of, and not all OEM's released them anyway. This makes writing apps for the devices difficult. In 4.2 and 5.0, in addition to the OEM tailored SDK option, there is also the Standard Dev Kit release, which gives the developer access to the entire API, BUT requires that they tailor apps to the device on their own.
There for making it easier for Developers to actually muddle through the process without buying Visual Studio 2003.

The Platform Releases - H/PC Pro, HPC2000, Pocket PC 2000, 2002, Windows Mobile 2003, 2003SE, 5.0 make up the basket where Microsoft want to see the consumer. A standardised, tightly controlled OS and Shell subset through which the developer, consumer and OEM all knew exactly what they are getting.

A footnote here is that CE1 and 2.0 don't count in the distinction, as there was only one path at that time - the platform release.

When you say you see a lot of Windows CE 3.0 releases, what in most cases you are seeing is a cumulative bundling together of a binary that will run on HPC2000, PPC2000 and PPC2002.

i've tried to complete the form but it always gives me an error
anyone successful with it??

i've known that for a long time now. no news to me.
however it still doesn't change the sad fact we (Juergen and I) were talking about

Thought of that when re-reading my post... It was obviously misleading the way I've said that. I didn't mean 'Windows CE 3.0' releases but any elder, e.g. 3.0, release of any software where the hpc thread of developement was stopped and all more actual releases are solely available for pocketpc. In fact I had especially Iliumsoft's ListPro in mind as an example for a really tragic loss. When Iliumsoft launched ListPro 4.0 they thereby abandoned hpc, but you still could order the 3.0 hpc release. A few days ago a friend of mine told me Iliumsoft now even doesn't offer ListPro 3.0 any longer. Bad luck...

One question:

Does CE4.2 support WPA-PSK when using the Siemens i-GATE card? I recently switched my WLAN from WEP to WPA-PSK and now my Simpad is pretty offline. Therefore my hope is that I could get WPA-PSK support through the ROM upgrade. Is this the case?

Marcus

hm yeah ce.net 4.2 is able to support that, dunno about the simpad version. oh and your igate card must be able to support it as well.

Simon,

TY for joining the thread.
I hope you can find a distribution method that doesn't require me to send you my Simpad.
I realize the implications of offering an unencrypted or unkeyed image image being offered over the internet. The last thing I want is for you to stop refinement of your product because of piracy.

But, please consider the following points.

1. You may be denying yourself a large number of sales because people like myself can't / won't take the risk of sending my SL4 to Europe and back. There's the risk of loss or damage and the serious inconvenience of being without the unit for a substantial time.

2. Updates. You are constantly refining the image I imagine. I'd hate to think after I took the risks and paid a substantial sum for the update a major or even minor update would become available. At a minimum I'd face shipping costs a second time.

3. Fair use. After paying the update fee I feel I should maintain the freedom to flash my SL4 with any other OS of my choice and back to your image without any additional fees. This was the spirit in which Seimens released their various ROM images into the community.

4. Crashes. No product is bug free and if I ever needed a reflash because your image failed or otherwise became faulty I'd be very upset.

5. Imminent piracy. As I write this someone has probably pulled your image from an updated SL4 and will distribute it through the warez channels if your current distribution method doesn't change

Asking users to send their units once is one thing. Asking users to send their units a second or third time will create a lot of ill-will.

Please find a distribution method that doesn't require my unit to be shipped.

Thank you

Maybe the Activation thingie was not such a bad idea afterall!

Simon, if there is any method you can use to verify the legitimacy of the image to my machine I'll buy into it. No activation method can be as frustrating as needing to ship my unit around the planet.

Can the image somehow be tied to an internal serial # of the SL4? At least the image would suit only one machine and could travel with that machine during its life. Of course someone will hack this eventually but as I mentioned someone probably already has pulled your updated image off a SL4 and has it sitting like a trophy on a hard disk. One thing for sure, I *wouldn't* trust an image from an unknown source no matter how badly I wanted it. But others won't see it the same way.

Simon, if nothing else perhaps you could partner with an American/Canadian firm so users in my continent aren't shipping overseas? That still doesn't address all the issues I raised but for some people it may be enough to sway them to purchase.

Edited by wallythacker 2005-09-06 8:10 AM

oh yes you just need a good dumprom tool for that and that's it. it's far from impossible. still, i haven't heard of any warez 4.2 image for the simpad yet.

You have to be braindead to even think about using warez for an OS.

Something like the Simpad rom is too critical to chance. I read it's not too hard to brick an SL4 based on improper bootloader and whatnot. Then there's the issue of ongoing support.

If Simon continues making a profit he has a reason to continue. If not, well....

i never meant to do warez of it. sorry if you misunderstood just mentioned it doesn't look too difficult to copy the rom, but somehow it must be, as i never heard of any 4.2 images on P2P or anywhere