Slashdot Mirror
Windows XP Embedded
Embedded Geek writes: "Embedded Systems Programming has a piece
about Microsoft organizing its employees to advocate their embedded products in online newsgroups (part of "a new culture at Microsoft" making "an effort to shed the company's reputation as an incommunicative giant.") This is coordinated with Microsoft's launch of Windows XP Embedded at their Embedded Developers' Conference (the countdown clock on their homepage says Wednesday but the launch party is Thursday)." News.com notes that this will be used in slot machines and ATMs. Insert obligatory free-money joke.
In a S/390?
This space left intentionally blank.
Where smallness, understandability, low power consumption, and bullet-proof reliability are the key factors. I don't know who would put XP in a critical device. I don't know who would put Linux in one either, for that sake. "Embedded" in the Microsoft sense must mean "PDAs and museum kiosks" and such, and not the traditional embedded market.
that already is running lots of ATM's out there. Do you ever see a BSOD on a cashpoint - I haven't?
Given the increase in complexity and code size its going to be interesting to see how it goes into devices.
Wow. It turns out you only need 512 MB RAM, 1 gig of storage and a 900MHz CPU on your embedded device to run this.
Wait a minute...
Knunov
Why do users with IDs under 100,000 or over 700,000 usually have the most worthwhile comments?
Embedded means small and fast, both of which cannot be done with Windows CE,Embedded NT, Embedded XP.
This is why 60% of all embedded systems are DOS and then Linux (The linux side is growing fast.... and I mean really fast) and then specalized.
If Microsoft can demonstrate a single floppy version of XP that needs only 4 meg of ram or less to run and leave room for my app then I'll take them serious.
Until then Microsoft products are not looked at as a serious alternative or solution, they are too expensive to impliment in the hardware requirements.
Do not look at laser with remaining good eye.
That perception, Microsoft says, is precisely why everyone on the development team of its Talisker embedded operating system now logs hours every week, chatting about the OS in news groups, checking out "bug reports" on a dedicated Web site and meeting with users face-to-face at "plugfests," where they discuss Talisker programming experiences.
Congrats to Microsoft for inventing web based bug tracking. Truly this is a great day for software.
Toronto-area transit rider? Rate your ride.
While I was at MSFT over the summer, a friend at work asked me why Open Source projects had such a community around them no matter how small they were while it seemed harder for MSFT products to build a community around them (as opposed to users which they had plenty of). He mistakenly assumed that the availability of source code was what built the community which from my minor participation in a number of Open Source projects was incorrect.
The main reason users tend to form a community around Open Source projects is that there is direct communication between the users of the product and the developers of the product without the layer of bullshit introduced by marketing and management. If I post to the dbXML, Scoop or JDEE mailing list, I know I'll get at least one response from an actual developer of the product who will make a solid attempt to solve my problem as opposed to paying umpteen dollars to be put on hold by some pimply faced teenager who probably couldn't code his way out of a paper bag.
While at MSFT I planned to evangelize such a user-centric view of interaction but never got around to doing it on as large a scale as I liked. I did however try my best to make sure that as many questions to the newsgroup of our product were answered by someone at MSFT, if not me then someone whom I felt could answer the question. It looks that finally some like minded people are springing up in other parts of MSFT.
It's just that we don't identify ourselves by our names. Most of us have always been like me: when we comment, we acknowledge our association with MS, but we don't give out any identifying information. I pass on the commentary that I pick up here to my product group. Frankly, I think that the Pocket PC is stronger for it.
There are two classes of reasons that we don't use our real names. First, we as individuals don't want to get spammed any more than we already do. Individuals from MS have been targeted and stalked in the past; none of us wants to be the victim of some kook. Second, the company has a right to manage its own messages. Sometimes, obviously, that's a bad thing; our quiet lets the company get away with lying. Usually, though, there are a number of of people who have the right to know before the public does. (Our partners, for instance, may need to adjust their strategies in response to changes that we make along the way in our own. There's nothing so humiliating as not knowing some key point about a change, and having some reporter tell you that he just read all about it in a newsgroup.) We need to protect that orderly flow of information.
Now I know this probably won't happen..but the mention of ATM got my attention.
Wouldn't the use of and embeded version of XP, which will be used for authentication and disbursement of monies, be an incentive for MS to get people and banks to use it's Passport service for authentication/verification etc?
Think about it. They want to get spending data etc, so this would be the perfect opportunity. Now I'm not bashing MS for making an embeded version of XP.
We all know CE wasn't the best...but still are making money out of it and they can most likely capitalize on XP's new features.
Personally I'd stick w/ whatever was already out there for the banking systems...I trust them more than I do MS.
No, man, working for Microsoft ROCKS! I LOVE this company! I LOVE THIS COMPANY! Who told you to sit down?! Did I mention how awesome Microsoft embedded systems are? They ROCK!
It Is the Nature of Information to Transgress Artificial Boundaries
Comment removed based on user account deletion
The embedded devices market is not all about small and fast. And even where the issue is small and fast, the XP kernel may well prove to have more to offer than many UNIX designs.
There is a wide range of embedded devices, from washing machines to cars, to industrial process machinery. Until recently only a small fraction of those systems had anything as sophisticated as an operating system.
If on the other hand you want to build a next generation audio system you are likely to find that you need an O/S, you need some sort of file system to store your MP3s, you have an ethernet and possibly a WiFi interface to support, you may even support PCMCIA or compactflash. XP has major advantages in that space since you are guaranteed to have a driver available.
The bloatware charge is and always has been bogus. People don't seem to understand that the value of a 3 year old PC is $150 and so there is no particular reason why Microsoft should limit a $100/$200 O/S so that it can run under the constraints of that machine. 512Mb SIMMs are on sale these days for the price of 16Mb SIMMs a couple of years back, nobody actually makes 20Gb 3.5" disks any more, they are too small to bother with.
RAM and disk space are not constrained resources on the PC, so don't expect companies in that space to constrain them in their products. The O/S kernel is kept small because the performance of the machine depends on large parts of it being in primary or secondary cache most of the time.
The features of XP that will be much more relevant to the embedded systems space are its multi-tasking and scheduling control. I don't expect any traditional UNIX kernel to do well there, the UNIX architecture was never designed for and is simply not up to RT tasks. Thats why the RT Linux varieties have major mods to the internals to support features such as guaranteed scheduling etc.
Looking for an Information Security student project suggestion?
Try http://dotcrimeManifesto.com/
Welcome to WinXP for ATM
Please wait.
Enter your card.
New hardware found! Installing card-reader, please wait.
Please remove card from ATM.
Rebooting...
Welcome to WinXP for ATM
Please wait.
GPF, press "1, Clear + Enter" to reboot.
Rebooting...
Welcome to WinXP for ATM
Please wait.
Scandisk found errors on card-reader.
Enter your card.
Errors on your card have been found. Would you like to create a recovery-card?
"No."
It looks like you have never used this ATM before, would you like to transfer your profile?
"How do you know that?? No!"
You have selected withdraw cash.
Access Denied. Only a user with administrative rights may perform this action.
"F***.. Gimme back my card!"
Unable to remove card, there has been a sharing violation. This card is in use by another user.
"WTF????"
My life is one big siesta in which I'm dreaming I wished my life was one big siesta.
What embedded systems do you work on ? Most embedded systems (controllers, switches etc etc) run a very very small RTOS, DOS is not an RTOS (Real Time Operating System).
DOS is not an RTOS, Linux is not an RTOS. These systems are not really talking about embedded stuff at all, they are talking about small PC architectures, which have their place. But embedded is about small footprint and 100% reliability. I wouldn't like to know that the medical controller my life relied upon was using DOS.
An Eye for an Eye will make the whole world blind - Gandhi
In Sweden, some ATMs are already running NT.
:)
And yes, they did *actually* get those "Low on Virtual Memory" errors (try to hit CTRL-ALT-DELETE to reboot on an ATM) and even a few bluescreens back then. I kid you not.
On the other hand after those child diseases, they are actully seeming to behave, and I know of noone that has actually lost (or gotten) money due to this.
The banks just needed two service packs, is my guess.
Well, so this product, after troubles unheard of in other systems, finally made it "stable" and "reliable".
I would not like to bet my money once again, just because I got the winning ticket once. Would you?