Slashdot Mirror


On Microsoft's Embedded DevCon Keynote

An anonymous reader writes "WindowsForDevices reports on the keynote talk at Microsoft's Windows Embedded DevCon (developer conference) taking place this week in San Diego. The story includes some interesting comments and highlights from the talk. Don't miss the cool bit about the ARM7-based 'SPOT' development platform that runs a tiny version of the .NET Compact Framework -- Microsoft is demoing a robot that's run by SPOT. There's also a pointer to an online video demo of a project to create a digital picture frame using Win CE."

15 of 106 comments (clear)

  1. SPOT by Anonymous Coward · · Score: 5, Funny

    M$ is demoing a robot that's run by SPOT. See SPOT run. Run SPOT, run!

  2. Windows XP Embedded by Dante · · Score: 4, Interesting
    I noticed a couple comments on Windows XP Embedded on that website, has anyone else had issues trying to keep embeded secure? You can't run windows update or SUS and service packs don't work. And Cannon won't support any anti-virus software.

    In my opinion Windows XP Embedded is the largest boondogle I've ever come across.

    Is there a way to keep these boxes(cancer) secure?

    --
    "think of it as evolution in action"
    1. Re:Windows XP Embedded by smithmc · · Score: 4, Funny

      I noticed a couple comments on Windows XP Embedded on that website, has anyone else had issues trying to keep embeded secure? You can't run windows update or SUS and service packs don't work. And Cannon won't support any anti-virus software.

      No biggie - just don't ever connect your device to, well, anything, and you'll have no problems!

      --
      Downmodding is the refuge of the weak. Don't downmod, make a better argument!
    2. Re:Windows XP Embedded by howlinmonkey · · Score: 5, Informative

      I don't know if you mean Cannon or Canon. If you do mean the EFI based RIPs for Canon ColorPASS controllers, you can run McAfee VirusScan 7.0 on their XPe based controllers.

      As for security updates, EFI has just started a program for keeping more up to date with Hotfixes and Service Packs. Just today I got an update from Canon with information on a forthcoming CD bundle with the latest patches for their entire Windows based product line. Granted, they will be a little behind because they have to do a full test suite to make sure their software functions with the patch or a modified version thereof. Your printers should be bedhind a firewall with all external access blocked to protect from the majority of these baddies, if possible.

      Contact your local servicing Canon dealer for additional information on the anti-virus and security update issues.

      Yes, I do work as an analyst for a Canon dealer ;)

    3. Re:Windows XP Embedded by mrpuffypants · · Score: 4, Informative

      The company that I work for right now is experiencing the EXACT problem that you are referring to: WinXPe forgoes all support from the OS maker (MS) and puts it right on the OEM/Embedded device maker.

      While this makes sense for many devices that could be loaded with WinXPe this is a bitch and a half for anybody using it in a pseudo-desktop system use. The people on-site can't run WindowsUpdate and just get the patches, they have to come directly from the maker and be customized for that version of that kernel on that hardware.

      In fact, right as I type this I'm watching a patch for Korgo/Sasser deploy to a fleet of about 1000 WinXPe powered devices. Thanks to office politics and people that have such a massive hard-on for Microsoft we are using XPe for a purpose that could be solved (LITERALLY) with a big hard drive, wget, and Apache.

      Instead, we have a box that has to have XPe on it which, of course, comes with all of its wonderful 'features' that we never need, should never have to deal with, and only cause us headaches.

      However, I DO get overtime for sitting here making sure that this update goes through, so cheers to that! Thanks Microsoft!

    4. Re:Windows XP Embedded by Brandybuck · · Score: 4, Interesting

      My company is using WXPe for an upcoming realtime embedded medical diagnostic system. We're solving this by basically rolling our own MSI/Installshield bundles for each and every patch, vulnerability and virus definition. We're in the third round of estimating this product and I made a note to the VP that the product WILL REQUIRE a full time employee to handle rolling out patches.

      My company really doesn't know what it's getting into. Our old product was LynxOS based, and we NEVER once had to issue an OS related patch, and I think we had a total of three critical patches for the ten year lifetime of the product.

      --
      Don't blame me, I didn't vote for either of them!
  3. Windows CE == POS by k4_pacific · · Score: 4, Interesting

    I work for a company that does Point of Sale software and we looked at Windows CE. The company that built some of our hardware (I won't give their name, let's just say its Not Columbia Records) sent us a CE image and a little boot utility that copied the image into memory off the hard disk and kicked it off. It booted up okay, and reminded me of a really bad version of Windows 95. (Heck, Windows 95 is a bad version of Windows 95, but this was worse). Particularly amusing was that apparently it had been expected to be used with flash memory rather than a real hard disk, so copying files took a long time as there was no head movement optimization.

    The disk goes Clcklklklklklklklklklklklklklk for about 3 minutes to copy the 6 MB image.

    Also, if there were bad sectors on the drive, it would corrupt the root directory and you'd have to reformat the drive and start over. This was especially bad for us as most of the hard disks on our customer's systems are inches away from a cash drawer that flies open then gets slammed shut constantly.

    Needless to say, the customer we were evaluating this for is still running MS-DOS.

    --
    Unknown host pong.
  4. Overkill ? Headed in wrong direction ? by phoxix · · Score: 4, Insightful

    Windows + .Net for a simple picture frame ?

    wtf ? do they not teach the concept of KISS in school anymore ?

    I think the likes of TRON will be around for quite sometime ...

    Sunny Dubey

  5. WinCE that bad? by nten · · Score: 5, Interesting

    I don't have any WinCE experience(VXworks, custom schedulers, and Integrity mostly), but one of my coworkers, whose opinion I generally respect uses CE for all his moonlighting contract jobs and he calls it rocksolid, easy to use, etc. etc. He's got lots of embedded experience, mostly safety critical, and he considers it a truly useful tool.

    I can't ignore it outright, because he really does know what he's doing, he's written his own schedulers and memory managers for projects for 8051s and whatnot, so he's not just saying "oh, this looks easy I'll use this". But I'm also hesitant to believe that M$ has made something reliable enough to run embedded hard real-time.

    Anyone want to enlighten me further?

    --
    refactor the law, its bloated, confusing and unmaintainable.
    1. Re:WinCE that bad? by Anonymous Coward · · Score: 4, Insightful


      Anyone want to enlighten me further?


      I can't imagine how one could praise WinCE so highly. It's not hard realtime. This isn't a negative, just a fact. It just means that it is not a flexible as some other alternatives. It has NO flexibility as far as scheduler and memory management are concerned. The API is loosely based on the Win32 API, which sucks especially for this purpose, and sucks doubly because 90% of the parameters to the bloated API calls are ignored anyway. IPC options suck: thread message queues (a la WPARAM/LPARAM) and shared memory. The scheduler is capable of only 32 processes (again I consider a bitmap scheduler great if it's an option, but when you realize that WinCE drivers and BSPs are built ASSUMING this is a constant it is quite bad). There is essentially no memory protection since it is trivial and plausible that any process will enter Ring 0 even by accident. The scheduler is dead nuts simple. This is not necessarily a bad thing, until you realize that changing it is not trivial without practically rewriting most of the kernel (as the device driver model assumes the scheduler and memory model) and furthermore the OS is such a bloated piece of shit considering how simplistic the components are.

      Oh yeah, there is NO standards compliance, and I'm not talking about any one in particular. I'm just looking for some basic ROAD MAP from Microsoft. It would be nice if Microsoft at least developed their own standard and abstractions that would mean that so many fundamental things wouldn't change from one release to the next. Couple this with the fact that even the basic C runtime support is sorely lacking.

      As for rock solid, you are at the mercy of whoever wrote your BSP. I have seen a number and the quality varies widely. The one constant thing is they all reinvent the wheel for missing facilities and interfaces. I have seen very few WinCE implementations that proved themselves to be rock solid.

      Let me just say that while WinCE may be OK for some limited uses, its no QNX or vxWorks and that's sad since Microsoft had the chance to develop something that would bring something new to the table.

      Your coworker is probably quite smart. If his customers do not know any better, then I say good for him!

  6. SPOT notes by Anonymous Coward · · Score: 5, Funny

    1) Term for a bug report is now "you missed a spot" report.

    2) Name was inspired by Microsoft's spotty security record.

    3) Virus writers are now hard at work at viruses that hit the SPOT.

    4) Geeks everywhere will deny the spot even exists.

    5) Locomotives will adapt this embedded technology through the TrainSPOTting initiative.

    6) The MONO folks will be creating a GNOME-based port. No word yet on what they'll call it but rumor has it that it'll start with a "G"

  7. Gates' Ideas by concordeonetwo · · Score: 4, Interesting

    I always wondered why Gates thinks certain technologies and products are going to be big. Tablet PCs for example while is a great concept, it is severly limited by todays technology (Poor handwriting reconition, short battery life, etc). And yet, Gates has put his money down on it 3 times (Pen Services for DOS, Pen Services for Windows 95, Windows XP Tablet Edition). Compare him to Steve Jobs, who has had good sucess since he has returned to Apple (iPod, iTunes, iPod Mini, Airport Express/Extreme and iMac) Its probably just their philosophies.

  8. WinCE, yesterdays technology - today! by Weaselmancer · · Score: 4, Funny

    Microsoft is demoing a robot that's run by SPOT.

    Wow! That's some cutting edge stuff. Thank Bill we have Windows CE.

    What? What's that you say? We've already done robots? Ah. *ahem*

    There's also a pointer to an online video demo of a project to create a digital picture frame using Win CE.

    Now there you go! Some real future tech. A picture...that hangs on the wall....that changes! Fantastic!

    What? They've already done that too? Without CE? You mean that's possible? *ahem*

    Ok, nevermind then.

    --
    Weaselmancer
    rediculous.
  9. Better have a good firewall in your garage... by MMHere · · Score: 5, Insightful
    All I can say about hearing that MS has a serious Windows Automotive department going is...

    You had better have a good firewall in your garage for those times when your car says to you we're home, would you like me to go online and fetch your calendar updates?

    It's one thing for an unfirewalled windoze 98 box to be hacked and compromised by a remote attacker. It's quite another to have your vehicle compromised unbeknownst to you--

    I don't think I want my car "crashing" its OS while I'm at the wheel, unrelated to any driving choices/mistakes I may have made. I can see it now--

    "Honest Officer! I think my car must have caught the Download.Ject virus this morning!" I didn't drive into that bridge abutment on my own! Honest!!" The officer replies--

    "Sir, didn't you listen to the latest Microsoft warning? You should never use your steering wheel / joystick to surf to 'unsafe' websites with IE! Now I have to write you a Stupid-Ticket."

    But seriously...

    How concerned are other developers about MS style code being let loose in a critical system like an automobile? I mean, running a PDA or a desktop printer is one thing. When they crash, people aren't so likely to DIE! A malfunctioning four ton Ford Excursion, on the other hand, is something I'd really rather not encounter.

  10. A sad WinCE story by ras · · Score: 5, Interesting

    My company was looking some embedded hardware with some specific capabilities. It took a while, but last year the hardware arrived. Since I was the first user, I was offered the choice of WinCE or Linux. I personally prefer to develop under Linux, but in this case I thought it was best to go with whichever one the hardware manufacturer was most comfortable with, and that was CE.

    They supplied prototype hardware. This was just the CPU manufacturers reference design, which they laid up and hand soldered. A contractor recommended by Microsoft then produced a "basic" CE image, and we were away. So far so good. The next step was design and delivery of produce production boards. These were just the reference design with unwanted bits removed, and the form factor adjusted accordingly. Again, they put a "basic" CE image on it, and it all worked.

    The final step was to put the "real" CE image on the device. The major differences between this and the basic seemed to me to be be little details, like persisting the registry to flash, making the CF card work, making the buttons work, making USB work with 2.0 devices, making power off work and so on. The job went to the same Microsoft contractor, who promised delivery in a week or so.

    That was in January. Lots of phone calls later, and me finally threating to cancel the deal forced them (the manufacturer) to take drastic steps: they made the contractor's staff work in their offices, so they could monitor the work being done and the progress being made.

    That was two months ago. Meanwhile the situation was explained to Microsoft, but they insisted the if their nominated contractor couldn't get CE going nobody could.

    More threats from me, and the manufacturer contacted another manufacturer in Germany who was using CE with the same reference design. They found who did their CE image, and ask them to do the same job. That was a month ago. Nobody has delivered. Nobody has raised any queries over the hardware design. And I, an embedded programmer by trade, and sitting here mystified by how hard it appears to be to get CE to go.

    At the same time I have written my own apps to run on this thing. It is written in C# (which is what Microsoft recommended). I prefer Java as it runs well under Linux - but Microsoft does not supply a Java VM for CE - surprise, surprise! The back end of these apps (the server part) runs on Linux. So I had to make C# run under Linux. I choose PNet (as opposed to Mono) for reasons I won't discuss here.

    The contrast between the two efforts could not be more stark. Microsoft CE.Net mostly worked from the start, although it wasn't obvious how to do some things and it did have one of two bugs. Moving beyond that point - figuring out how things work, and fixing the bugs ranged from very hard to impossible - for all the usual reasons. Microsoft's documentation was good, but when it fell short there is no backup - no source, no helpful online community, and no one willing to fix bugs. Granted I didn't go looking for someone looking to do these things for money.

    PNet, in contrast, didn't work well when I first got it. It took me a day just to figure out how to make the thing go. But progress after that was rapid. I found bugs, I fixed them and posted the patches. Not a lot of doco other than the source, but if I got stuck I asked what seems to be a thriving and friendly online community.

    It goes without saying that the PNet stuff is now rock solid for me. The Microsoft stuff is about where it was when we first started - very close but no cigar, and it seems no one has any idea how to make it progress beyond that.

    I now wonder if this experience is atypical, or if I just made the wrong choice at the beginning. I am sure I would of have got Linux going by now - at the cost of a lot more effort on my part. But a little voice inside my head keeps saying - if it is this hard to make CE go, why does everybody keep using it?