Ford to release cars with Microsoft operating system!
-
Giving new meaning to the words "System Crash".
Brad Australian -CAUTION- The previous statement may contain traces of PHP, and by reading this statement you negate the right to vote me down.
and Blue/Burgundy Screen of Death (BSOD) :doh: Steve
-
Giving new meaning to the words "System Crash".
Brad Australian -CAUTION- The previous statement may contain traces of PHP, and by reading this statement you negate the right to vote me down.
It is a win win situation for Microsoft. If the OS crashes, the user might not live to report it. Imagine an air bag with send/don't send dialog coming up. :) Or better still, a panel with open airbag/cancel coming up.
-
Giving new meaning to the words "System Crash".
Brad Australian -CAUTION- The previous statement may contain traces of PHP, and by reading this statement you negate the right to vote me down.
-
From arstechnica: As part of their partnership announced in September, Ford Motor Co. and Microsoft will be showing off (subscription required) one of their new technologies developed together in January when the Detroit automaker reveals a new system called "Sync." In short, Sync is a Microsoft operating system (OS) which includes built-in Bluetooth wireless technology. Specifically focusing on wireless capabilities, some examples of what the system will bring to Ford's automobiles include hands-free mobile phone communication, e-mail, and music downloads. The first two cars to utilize the Sync OS will be the Ford Focus and the Five Hundred sedans. According to the Wall Street Journal, Ford executives feel that Sync will give the company a competitive advantage over its competitors. By 2008, Ford hopes to add Sync as a possible option for their entire automobile lineup. That includes both the Lincoln and Mercury brands as well. Sync will be introduced at both the Detroit auto show and the Consumer Electronics Show (CES) at the beginning of January. The two companies plan to also discuss other technologies that they've been working on together. http://arstechnica.com/journals/microsoft.ars/2006/12/29/6427[^]
cue news break....... It has been reported that a Ford automobile using the new SyncOS decided that the user has violated the EULA. This has caused all SyncOS controlled systems to be shutdown while the user was driving down the freeway at 100mph. Microsoft and Ford deny any wrong doing as the SynOS was still running with the ability to login and reactivate the system.......... this is not a sig, i am too lazy to have a sig.
-
I strongly doubt that a car manufacturer would allow any type of consumer OS to be used to control critical systems. This OS is an add-on to, not a replacement for, the car's onboard electronics system.
Yes, but where's the controversy in that? (By the way, I feel that Windows CE would be perfectly suitable - using its minimal kernel-only template - for critical management systems. At least as suitable as VxWorks, and probably more so than Linux. The GUI is less reliable but there's no reason to include that component in a real-time system controller platform.) Also note that something around 70% of all Windows crashes reported to Microsoft are determined to be due to errors in third-party drivers. 15% of crash dumps were too badly corrupted to be analyzed and are therefore considered crashes for unknown reasons. 10% were due to hardware errors and only 5% due to errors in Microsoft code. These statistics were taken from Online Crash Analysis for Windows XP between release and April 2004, and are quoted in 'Windows Internals, Fourth Edition' by Mark Russinovich and David Solomon. Windows CE drivers are significantly easier to write than Windows XP drivers, because CE's driver model is much more synchronous and generally fewer demands are placed on drivers (XP's model is highly asynchronous). Microsoft are aiming to make 2000/XP/2003/Vista drivers easier to write with the Kernel-Mode Driver Framework[^], and to shift some drivers to user-mode (e.g. audio drivers in Vista) for which there is also a User-Mode Driver Framework[^].
Stability. What an interesting concept. -- Chris Maunder
-
Yes, but where's the controversy in that? (By the way, I feel that Windows CE would be perfectly suitable - using its minimal kernel-only template - for critical management systems. At least as suitable as VxWorks, and probably more so than Linux. The GUI is less reliable but there's no reason to include that component in a real-time system controller platform.) Also note that something around 70% of all Windows crashes reported to Microsoft are determined to be due to errors in third-party drivers. 15% of crash dumps were too badly corrupted to be analyzed and are therefore considered crashes for unknown reasons. 10% were due to hardware errors and only 5% due to errors in Microsoft code. These statistics were taken from Online Crash Analysis for Windows XP between release and April 2004, and are quoted in 'Windows Internals, Fourth Edition' by Mark Russinovich and David Solomon. Windows CE drivers are significantly easier to write than Windows XP drivers, because CE's driver model is much more synchronous and generally fewer demands are placed on drivers (XP's model is highly asynchronous). Microsoft are aiming to make 2000/XP/2003/Vista drivers easier to write with the Kernel-Mode Driver Framework[^], and to shift some drivers to user-mode (e.g. audio drivers in Vista) for which there is also a User-Mode Driver Framework[^].
Stability. What an interesting concept. -- Chris Maunder
instead of percentages, could you give the number of errors in MS code. I mean not as a fraction but as absolute number. I would not like to drive anything that crashes so regularly (Even twice a year would be too much for an automobile).
-
cue news break....... It has been reported that a Ford automobile using the new SyncOS decided that the user has violated the EULA. This has caused all SyncOS controlled systems to be shutdown while the user was driving down the freeway at 100mph. Microsoft and Ford deny any wrong doing as the SynOS was still running with the ability to login and reactivate the system.......... this is not a sig, i am too lazy to have a sig.
Don't worry, they can't use it for anything critical.
-
instead of percentages, could you give the number of errors in MS code. I mean not as a fraction but as absolute number. I would not like to drive anything that crashes so regularly (Even twice a year would be too much for an automobile).
Anand Vivek Srivastava wrote:
I would not like to drive anything that crashes so regularly (Even twice a year would be too much for an automobile).
So you won't be driving any US-manufactured automobile anytime soon, then? ;P Snarking aside, I honestly can't see how there is such a large market for an entertainment center built into a car. Can't complain if people really want it, though.
-
Yes, but where's the controversy in that? (By the way, I feel that Windows CE would be perfectly suitable - using its minimal kernel-only template - for critical management systems. At least as suitable as VxWorks, and probably more so than Linux. The GUI is less reliable but there's no reason to include that component in a real-time system controller platform.) Also note that something around 70% of all Windows crashes reported to Microsoft are determined to be due to errors in third-party drivers. 15% of crash dumps were too badly corrupted to be analyzed and are therefore considered crashes for unknown reasons. 10% were due to hardware errors and only 5% due to errors in Microsoft code. These statistics were taken from Online Crash Analysis for Windows XP between release and April 2004, and are quoted in 'Windows Internals, Fourth Edition' by Mark Russinovich and David Solomon. Windows CE drivers are significantly easier to write than Windows XP drivers, because CE's driver model is much more synchronous and generally fewer demands are placed on drivers (XP's model is highly asynchronous). Microsoft are aiming to make 2000/XP/2003/Vista drivers easier to write with the Kernel-Mode Driver Framework[^], and to shift some drivers to user-mode (e.g. audio drivers in Vista) for which there is also a User-Mode Driver Framework[^].
Stability. What an interesting concept. -- Chris Maunder
I'll have you know that I owned a CE phone for about 1 month before I threw it in my pool and bought a new nokia. Windows CE is not an OS... Its an abomination.
Brad Australian -CAUTION- The previous statement may contain traces of PHP, and by reading this statement you negate the right to vote me down.
-
Yes, but where's the controversy in that? (By the way, I feel that Windows CE would be perfectly suitable - using its minimal kernel-only template - for critical management systems. At least as suitable as VxWorks, and probably more so than Linux. The GUI is less reliable but there's no reason to include that component in a real-time system controller platform.) Also note that something around 70% of all Windows crashes reported to Microsoft are determined to be due to errors in third-party drivers. 15% of crash dumps were too badly corrupted to be analyzed and are therefore considered crashes for unknown reasons. 10% were due to hardware errors and only 5% due to errors in Microsoft code. These statistics were taken from Online Crash Analysis for Windows XP between release and April 2004, and are quoted in 'Windows Internals, Fourth Edition' by Mark Russinovich and David Solomon. Windows CE drivers are significantly easier to write than Windows XP drivers, because CE's driver model is much more synchronous and generally fewer demands are placed on drivers (XP's model is highly asynchronous). Microsoft are aiming to make 2000/XP/2003/Vista drivers easier to write with the Kernel-Mode Driver Framework[^], and to shift some drivers to user-mode (e.g. audio drivers in Vista) for which there is also a User-Mode Driver Framework[^].
Stability. What an interesting concept. -- Chris Maunder
Mike Dimmick wrote:
(By the way, I feel that Windows CE would be perfectly suitable - using its minimal kernel-only template - for critical management systems. At least as suitable as VxWorks, and probably more so than Linux. The GUI is less reliable but there's no reason to include that component in a real-time system controller platform.)
I would tend to agree with that assessment, but many people wouldn't. I think all of them would understand that if it's not used in a critical system, it should not be an issue, period - so I just mentioned that part.
-
From arstechnica: As part of their partnership announced in September, Ford Motor Co. and Microsoft will be showing off (subscription required) one of their new technologies developed together in January when the Detroit automaker reveals a new system called "Sync." In short, Sync is a Microsoft operating system (OS) which includes built-in Bluetooth wireless technology. Specifically focusing on wireless capabilities, some examples of what the system will bring to Ford's automobiles include hands-free mobile phone communication, e-mail, and music downloads. The first two cars to utilize the Sync OS will be the Ford Focus and the Five Hundred sedans. According to the Wall Street Journal, Ford executives feel that Sync will give the company a competitive advantage over its competitors. By 2008, Ford hopes to add Sync as a possible option for their entire automobile lineup. That includes both the Lincoln and Mercury brands as well. Sync will be introduced at both the Detroit auto show and the Consumer Electronics Show (CES) at the beginning of January. The two companies plan to also discuss other technologies that they've been working on together. http://arstechnica.com/journals/microsoft.ars/2006/12/29/6427[^]
I'm looking forward to being able to hack into the system in the slow car ahead of me with my Bluetooth-enabled phone and commanding it to go faster.:-D
"...a photo album is like Life, but flat and stuck to pages." - Shog9
-
From arstechnica: As part of their partnership announced in September, Ford Motor Co. and Microsoft will be showing off (subscription required) one of their new technologies developed together in January when the Detroit automaker reveals a new system called "Sync." In short, Sync is a Microsoft operating system (OS) which includes built-in Bluetooth wireless technology. Specifically focusing on wireless capabilities, some examples of what the system will bring to Ford's automobiles include hands-free mobile phone communication, e-mail, and music downloads. The first two cars to utilize the Sync OS will be the Ford Focus and the Five Hundred sedans. According to the Wall Street Journal, Ford executives feel that Sync will give the company a competitive advantage over its competitors. By 2008, Ford hopes to add Sync as a possible option for their entire automobile lineup. That includes both the Lincoln and Mercury brands as well. Sync will be introduced at both the Detroit auto show and the Consumer Electronics Show (CES) at the beginning of January. The two companies plan to also discuss other technologies that they've been working on together. http://arstechnica.com/journals/microsoft.ars/2006/12/29/6427[^]
I just imagined a dialogue between the driver and the car:
driver: start ze engine
car : LoadCursor(IDC_WAIT), fordinit.exe, fordlogon.exe, UACford.exe etc.
driver: start the f****n engine, NOW, you junk piece of *(&#@%@^%#^$@%^#@
car : microsoft ford is starting the microsoft ford car, version 10.gazillion
please sit back and relax while microsoft ford is installing in your microsoft seat of this microsoft car
driver: hand me the keys, you f****n c**ksucker (*)
car : 0x0000007B(* aka the "Keyser Soze asking") (Am I sick? Please, doctor, tell me the truth no matter what.)