Microsoft Corp. “dropped the other shoe” today, as it were, announcing the first source code sharing program for its Windows CE embedded operating system that allows developers and manufacturers to actually redistribute modified OS code in real products. Read the report at WindowsForDevices.
Microsoft Grants “full access” to Windows CE Source
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Will be see any benefit from windows ce code in other projects, like ReactOS or WINE?
Will be see any benefit from windows ce code in other projects, like ReactOS or WINE?
Nope
Will be see any benefit from windows ce code in other projects, like ReactOS or WINE?
nope
The OSS people better not look at the source code because MS might hammer them for stealing.
No, Microsoft are not stupid (unethical bullies yes, stupid no) the chances of them letting another operating system compete with their monopoly on terms of the OS rather than the apps it runs are small to negligable. It looks like there going to let the hardware developers start adding stuff to WinCE that hooks directly into their hardware at an OS level rather than just drivers. I guess they figure that it is better this and get OS sales than let Linux or Java get the sales. This will also make it harder for the hardware vendors to change OS’s later as they will have invested in a software team that specialises in WinCE as well as a hardware team for intergrating WinCE in their product.
If any of the Wine people even look at the WinCE source, they’ll become totally corrupted. That is, Microsoft might have reason to suspect they’re stealing ideas from WinCE.
Don’t worry, there’s no chance anyone would ever want to copy anything from Windows CE.
…tar.gz or tar.bz2 file with the source code…or rpm…
Will it compile with gcc 3.2.2 or should I use the old 2.95.4 ??? How can I start WindowsCE desktop from linux? Do I have to edit .xinitrc??? Or does it com with install.sh???
If someone could give me an asnwer I’ll be glad:)
Thank ya in advance:)
PS: does it support NPTL???
because that license is evil, so if i check it I cant later
work on similar projects. Evil!
How is this going to help BeOS though? I cant wait until the OpenBeOS guys incorporate the ideas in WinCE. Then BeOS will certainly claims it’s rightfull place in the computing world as the ultimate embeded and micro and mini and main-frame operating system.
(And I was already waiting for the obligatory BeOS post. I’m getting nervous without routine.)
> How is this going to help BeOS though?
BeOS doesn’t need to rip ideas from Windoze, better take them where M$ originaly stole them and implement them correctly instead than in a POS
> (And I was already waiting for the obligatory BeOS post. I’m getting nervous without routine.)
Hmm, gonna fix this…
– 1 pill of BFS every day at wake up,
– 1 spoon of pervasive multithreading per week (that thing is dangerous for ppl not used to it
).
How many embedded OS vendors allow you to modify OS source code for your product anyway? QNX? VxWorks?
Are Linux, Symbian and WinCE the only three at this point?
Interview with Craig Mundie
http://www.microsoft.com/presspass/features/2003/Apr03/04-09wince.a…
The original Microsoft press release
http://www.microsoft.com/presspass/press/2003/Apr03/04-09PremiumSou…
Are Linux, Symbian and WinCE the only three at this point?
No, Palm is another big vendor that allows access to the code for vendors/licensees and allow modification (like Sony, Handspring, etc have done).
As an embedded FIRMWARE developer, I’m curious as to WHY THE HELL ANYONE WOULD USE THIS LICENSE OR WIN CE IN GENERAL:
I’m left to 1 conclusion: Project Managers are receiving kickbacks, or managers really AREN’T USING WIN CE, AND THIS IS FREE PUBLICITY.
If embedded linux is safe enough to be used in nearly all parts of aircraft why the hell would you NOT want to use it for a “time-waster” PDA? RTEMS QNX, there’s a TON of excellent, well documented and easy to use proprietary (but OPEN SOURCE) RTOS out there. RTEMS used to be used for missile guidance systems. Now that’s what I call “Trust-worthy computing.”
To those of you fellow engineers out there, tell your bosses to stop subscribing to “Java Developer, or Embedded Computer Daily, etc.”
Boss: I just read about WinCE, I want you to put it in our fire-alarm product.
Engineer: Do you even know what WinCE is useful for, or its limitations and platform requirements?
Boss: No, I just know that I need it, and as soon as possible.
I get the feeling the WinCE push is a Top-Down one.
I work for a company that produces software that is licensed and ported by various platform vendors. Our WinCE code is licensed more often than our Linux code. This is not a scientific study, but there are apparently WinCE vendors out there.
WinCE uses a completely different codebase from any other version of Windows. Using WinCE only lets you copy WinCE. If this had been WinXP embedded (which is totally different) this would be something big.
I’m too lazy to do the research. So does this apply to current and future PocketPC devices or just the old WinCE devices? There’s a huge difference. Since PDA manufacturers seem abaondon software development for their products before they even hit the shelf, being able to modify old WinCE 3.x stuff is kind of pointless.