The Evaluation Edition software enables you to build Windows XP Embedded with Service Pack 2-based operating systems for 120 days from the day of installation.
Windows XP Embedded with Service Pack 2 Evaluation Edition
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Isn’t ‘XP Embedded’ something of a misnomer? I mean, how big is the kernel alone? ;-P
@xVariable: if a big kernel isn’t suitable for embedding, then is the monolitic Linux kernel suitable?
good gawd look at those system requirements. How can anyone believe XP embedded is the answer for embedded systems when the system requirements for developing are so gargantuous. Remember when W95 shipped on 2gb or SMALLER harddrive computers? look at how bloated this thing has become since then.
let me know if i’m wrong because i’d love to be I really would about this but I’m going to guess the reason for the bloat is:
1) IE
2) WMedia Player
basically stuff that’s not operating system related.
thanks,
Rob
bu you can modularize and not compile in support for things you don’t need, andmake the kernel very small. In fact, after a lot of tweaking, I got my own kernel bzImage down to ~2 Mb with almost 6 MB worth of modules (ALSA, nVidia drivers, USB stuff, etc.)
Well I remember working in a school back in the late 90’s on machines running Win95 on 600mb HDs. It hasn’t enough. lol
In someways the kernel bloat has been overcame by the availability of some dirt cheap flash storage. The same is true with totally bloated applications and cheap hard drives. What was once critical mass is now “oh well”.
Yep…They are gargantuous…The finished product only includes what components you put in it…And get this, you can put the drive in a different pc and it’ll boot into the xp desktop. This is the service pack one version though.
I once only had a 170 MB drive, which i used under Windows 95. If i used Double Space (or how it was called), I could also install Starcraft *g*
Of course you need a fast machine for developing an image. And that’s because it’s possible to include IE or WMP in your WinXP Embedded builds. Of course you don’t have to. Peter already gave the 2MB figure, which is just about as small as you can make it. You can also include everything and build a totally over-full WinXP I guess (I haven’t tried). But: All this needs a modern system to be arranged and compiled, that’s just self-explanatory, isn’t it?
Win CE has a smaller footprint than XP embedded. However, most apps that work with XP will work with XP embedded as the binaries are the same. Embedded tutorial can be found here http://www.acrosser.com/winEOS/winembedded.htm
Er, Peter’s figure was for Linux.
This reminds me of the post about contiki on osnews.
http://www.sics.se/~adam/contiki/
now THAT’s a small footprint!
You want to talk about bloat? I upgraded to Gnome 2.8 yesterday and it and needed to recompile 3 browsers and 3 media players.
The benefits of having one standard browser and media player in an OS are becoming obvious.
Oops, you’re right… heh. Anyway, similiar results are possible with WinXP Embedded. I remember talking to someone who built an image with at most 5 MB or something; of course it didn’t include the GUI.