ah, thanks. I can see that now. They talk about including their Xen^H^H^H Microsoft based hypervisor in the next Windows server in late 2007 and will ship the Xen VM image support 180 days after that. And with this late date, they don't know if it'll be called Vista Server 2007 or Vista Server 2008. Longhorn Server covers that til they can figure it out.
Again, thanks for pointing this out. I should have seen this.
I think they'll interfere with how Linux works under Windows from the get-go. As long as Linux is kept out of the Windows shops, Microsoft software will prevail. There's nothing like a good 'get the facts' campaign to show that Linux is slower than Windows and that Windows VMs are all the rage while Linux VMs are poor and difficult to run. FUD. But they have to make sure there is an 'option' to run other VMs under Windows because Virtualization is happening on Windows and they MUST keep their customers using Microsoft VM formats. IMO.
actually, there are WAY too many Windows sites where the employees don't know anything else and will ALWAYS go to Microsoft first. I've seen this a couple times recently. When I told them of VMware, showed them how it worked, and explained why it's better to run a trimmed down Linux as the host, they went to Microsoft instead. Their first reaction was to find out what the Microsoft solution was( I told them they had something ) and then they'd install it from their MSDN CD on a new computer running Windows XP. And then they start asking me questions about it.
It's like they are baffled by Linux and run to what they are comfortable with.... In a couple of cases, I could atleast move them to VMware on the Windows host but that's as far as I could get.
So Microsoft already has a leg up on the competition and ANYTHING they can do to keep their customers from 'finding' Linux means they'll keep purchasing Microsoft products above all others. IMO, Linux VM appliances are a threat to Windows and if Microsoft can control the virtualization foundation those VM run in, they can make those 'unwieldy' to operate or operate with reduced performance to make them less attractive than a Windows solution. IMO.
This is Microsoft we are talking about here so the excercise is to figure out how this will be played out.
Will Microsoft take what they learn from 'working' with Xen and use it in their own product( Sybase SQL, Wang DDE, Sun JAVA, etc )?
Will Microsoft find ways to break Xen or cripple it so that the Microsoft product works better?
Or, is Faust making snowballs and Microsoft is really working to make a competing technology work better when at the same time they are working to release their own product which supports only Windows as the Host and only recently stated they'd support Linux as a client VM?
My guess is that it's going to be a mix of the 1st and 2nd actions. And what's with them calling the Server "Longhorn"? Have they not already announced the product is called Vista? Is this a trick to separate how they 'work' with Xen now but release something different in Vista Server? Will it be used to manipulate the public/press perception? Or do they really not have a name for the product yet and still use "Longhorn" in press releases?
That is most likely what they'll let RECHARGEABLE Li batteries onboard but not full capacity non-rechargeable Li batteries. With all the ways the batteries can be damaged before they're put on the planes, there's too much of a risk of fire from latent fires due to damaged cells.
This is also why there aren't lots of fires in the backrooms of computer stores. All those laptops not only don't have charged batteries but they've probably already been inspected for damaged packaging.
In related news: The Musick Industry finds that since their products have been used for thousands of years, they believe The Circle is going unlicensed. The Musick Industry believes that in the distributing of music used over the years, one can always find The Circle and so it is going unlicensed and may start charging extra for its use. The Musick Industries Circle can be traced back to its use in singing around a campfire, the Victrola, reel-to-reel, albums, cassette tapes, compact discs, and on the circuit board of flash-based music players. Therefore, any use of The Circle associated with music is the property of the Musick Industry and unauthorized use is prohibited. Any persons found shaping their lips to the form of The Circle while singing a song will be held libel and could be prosecuted.
In and interesting turn, the Musick Industry has recently invested billions in prison systems operations around the world in anticipation of the imprisoning of all persons worldwide as it starts protecting its property, The Circle.;)
...on their face. Most laptops with ATI Mobility Express chipsets can't use the onboard video memory. ATI broke this a year ago and has not fixed it.
So don't trust ATI for Linux capabilities on notebooks.
Maybe Toms Hardware can do a notebook comparison since they've already done the desktop. I'm pretty sure that would expose this failure to far more than the few who already are aware of this. And just maybe, it'll get ATI to fix this.
The VMPlayer will only PLAY VMs, VMserver, as you stated, let's you create VMs. The other difference is that the VMplayer runs one VM instance where the VMserver is designed to run multiple VMs all managed from a common( tabbed ) UI. I've seen it said here that there are preformance differences between the VMplayer and VMserver. I don't know about that but I do know that if you don't load up the VMWareTools for each VM, they will run quite slow.
I think the advantage of the VMplayer is that it's an easier install and easier to run a VM from. And therefore, it makes an easy platform for the VirtualAppliances VMWare has been promoting.
It looks like the plan was to NOT letting this get too popular. The fact that customers have to pay more for this power AND the plan is to pay the farmers more than the current rate is the exact technique I'd use if I didn't want too many customers picking this option. Who's going to make the choice to pay about 30% more for energy?
This looks like a scam to make this look like the "green" thing to do when in fact, the result is going to make very little difference in how their energy is produced. Sounds just like Bush's hydrogen vs hybrid strategies.
There's tons of information on this but I'll fill you in, you don't need to worry about that. The wing sail can be 'trimmed' to a symetric shape and weather vaned in high winds if needed. It turns out that one of the first Walker Wing Sail ships to cross the Atlantic went through a Category 3 hurricane without any problems besides some frightened crew members.
This question seems to get asked of the wing sail system as much as Prius owners get asked "How do you plug in it". And like the Prius hybrid system, it's not a concern due to the design of the system.
winds change and change often, a para-sail out on a tether might make a good picture but over a few thousand miles, I wonder how many times it's going to either get wet or need to be pulled in quickly.
I saw 30% possible fuel savings mentioned but didn't see any real world data whereas the Walker system has been deployed and saw a 15-20% savings on the one ship it was installed on in the late 80's.
BTW, I figured just looking at the two designs might be a clue as to why one might be better than the other. If you want more, there's google for ya.
The Walker Wing Sail system was designed in the 70s when fuel was 'expensive' and the idea was to outfit freighters with the Wing Sails to help reduce fuel costs. Unfortunately, once the fuel 'shortages' of the 70's went away, Mr Walker found it very difficult to sell his systems. He started making his own Trimarans when no boat builders would license his design and build boats using it. But finacially solid orders were too few and only a handful of his boats were made utilizing the Wing Sail design. Some are still afloat today.
Bull sh1t, what I said was that you will NOT be able to add Microsofts proprietary extensions to its plugin and they are not going to put their proprietary code, or conversion for such, in this open source project.
Anybody would be far better off helping with one of the other plugins since the goal of THOSE projects will be compatibility and not showing how bad ODF document conversions can be and why MS OpenXML is supposedly better than ODF.
wow, there's so much wrong with your reply I don't know where to start. Let's start with the ECMA, they allow proprietary/patented material in their 'standards' and Microsoft has this in their MS OpenXML. And that FAQ link was just too funny. I loved the question: "How open or closed will the Ecma International process be for the OpenXML formats?". Shouldn't that have been 'How open or closed with the Ecma standard be for the MS OpenXML formats'? Oh, and Microsoft has been 'talking' about open standard for over 6 years now and yet, none of it is really open. They use the work "open" alot though.
Next, where do you get that a menu item to download a plugin means the conversion is right to ODF? And I could be wrong with regards to other versions of MS Office working with this but surely stating that Microsoft is working on MS OpenXML capabilities for some previous version of MS Office does not mean this plugin will work with it. It goes more to say that converting to MS OpenXML is going to be a requirement before converting to ODF.
over 20 years of Microsoft history tells me that what they SAY and what they DO are VERY different unless you look at what they SAY from a marketing perspective. Then, when the resulting product is thrown out there, you'll not be surprised. IMO
If "your buddy" only needs to read your document, then export to PDF and send him the PDF. Atleast that way, it's less likely your document will get changed and mis-interpreted from how you intended it AND everyone can read it.
But if you must send him/her an editable document, I would trust a 3rd pary plugin for MS Office over one backed by MSFT any day. There's alredy one being deliverd to that State of Massachusetts from the OpenDocument Foundation: http://www.crn.com/sections/breakingnews/breakingn ews.jhtml?articleId=187201009 But I don't know if it's been released to the public yet or not. And if people really think there'll be anything better in Microsofts plugin over the others, just think about how well Microsoft has supported competing products in the past. And if MSopen XML is really open, there's nothing stopping a 3rd party from doing as good a job, or better, than Microsoft since ODF is completely public.
And not everyone is going to jump on the ODF bandwagon right away. It'll first happen at the State, Local, and Federal levels of government since they are the ones creating public documents without owning or controlling the rights for access to the documents. The rest will follow this lead. And considering MSFT gets over 30% of its profits from MS Office, there's no reason to believe they will go quietly.
you forget, MSopen XML was submitted to the ECMA. The ECMA allows patented materials in formats submitted to it for a public standardization. Microsofts.Net stuff is the same way. So, just how much of Microsofts patented MSopen XML format is going to be in this BSD-like licensed plugin? If Microsoft patented how they put a PageBreak in MSopen XML, you won't see it in the ODF plugin. And if you go and reverse engineer their MSopen XML and add that PageBreak code to the plugin, don't even think about releasing THAT to the public without a license from Microsoft.
This is Microsoft we are talking about, so don't think there is any way this can be used for anything but directing people to use Microsoft products and Microsoft proprietary formats on Microsfot Windows. It's just the way the marketing company called Microsoft works. History shows this. IMO.
Well, since the project is BSD licensed, what's to stop you from fixing it?
And what would be the purpose of doing that? You know darn well that ODF format/structures will not be translated to the same proprietary format/structures of MSopen XML.
This 'plug-in' is only going go convert from ODF to MSopen XML initially and supposedly, it'll eventually go the other way. If you'd like to convert your existing proprietary formatted MS-word document formats then you'll have to move them to MSopen XML first and THEN to ODF. And if you want MSopen XML then you'll have to get a future version of MS Office( 2007 ) and it's likely you'll also need another version of Microsoft Windows to run that, and you'll probably need a new computer to run that.
So good luck trying to fix any of this without reverse engineering Microsofts patented structures, purchasing all that new software, and hardware to do this and still be doing this with possible legal threats from MSFT. And then, you'd be doing this when the whole purpose of this Microsoft plugin is not to provide something that'll be useful but instead, to provide something to show how bad ODF is.
If they can make things work fairly seemlessly between the two formats, I expect that Microsoft can do at least as well.
What makes you think Microsoft WANTS to do good conversions between their proprietary format and the public ODF format?
Surely there is absolutely no history of this. You've got some 'inside' information?;-)
except every other imported ODF word will be reversed because of a mismatch between ODF and MSopenXML. Well, that's what they'll say.
Sure it's on Sourceforge.net and we could 'fix' these issues but then again, we really don't think there'll be anything there which handles the 'patented' and 'proprietary' parts of the MS Office file formats( old or new ) do we? I hope not.
top that off with the fact that 'their' plugin will only convert some future MSopen-XML file format to ODF and what you get is any requirement for ODF means you have to have the next version of MS Office( which will probably require a new OS ). So, if you have any existing MS Office files, you'll have to convert them to MSopen-XML and then convert that to ODF.
And Microsoft is claiming that they are doning this to make sure of an accurate conversion to ODF. Yeah, right. But rest assured, those who maintain use of Microsoft products, to point of exclusion to almost all other software, will use this and complain of the poor conversion. I wonder how much they'll pay the press to publish lies about the ability to use ODF in an MS Windows office.
not successful? It got them $125 cool million from Microsoft to stop all that Linux stuff. Without Corel LinuxOS and the bucks MSFT paid them to dump it, Corel might be in worst shape today. IMO.
Sounds like there's some tight coupling with the next version of the rewritten-from-the-ground-up operating system having the best security of any OS on the market. Maybe they should stop charging extra for this and ship it with the computer and tie the pricing to the hardware so that you can't update the computer without asking permission.
or are they just having a difficult time figuring out how to read the ODF specs?
that'll happen only if there's a Linux LiveCD that'll migrate their existing data, use their hard drive for a persistent HOME and SETTINGS location and provide the option of bringing their 'old' operating system back up in a virtual machine.
Otherwise, people will pay the Redmond Ransome just to get their data and settings back. But there still will be a goog number of Linux people getting calls asking about 'that thing called Linux' and asking if it'll run on their computer. Hey, the viruses and spyware are already doing that now so having their OS shutdown by its manufacturer and owner isn't going to make them any happier.
I don't yet know about the Nokia 770 but I think you might have run into the PXA255 fiasco. A PXA250 running at 206MHz ran circles around the PXA255 running at 400MHz. Intel screwed up that chip so bad that cache had to be turned off in many cases and I think there was one other bug in it which also greatly reduced its speed.
Simply amazing how Intel has blown not only the desktop CPU market but also the handheld/etc market.
Slashdot Mirror
ah, thanks. I can see that now. They talk about including their Xen^H^H^H Microsoft based hypervisor in the next Windows server in late 2007 and will ship the Xen VM image support 180 days after that. And with this late date, they don't know if it'll be called Vista Server 2007 or Vista Server 2008. Longhorn Server covers that til they can figure it out.
Again, thanks for pointing this out. I should have seen this.
LoB
I think they'll interfere with how Linux works under Windows from the get-go. As long as Linux is kept out of the Windows shops, Microsoft software will prevail. There's nothing like a good 'get the facts' campaign to show that Linux is slower than Windows and that Windows VMs are all the rage while Linux VMs are poor and difficult to run. FUD. But they have to make sure there is an 'option' to run other VMs under Windows because Virtualization is happening on Windows and they MUST keep their customers using Microsoft VM formats. IMO.
LoB
actually, there are WAY too many Windows sites where the employees don't know anything else and will ALWAYS go to Microsoft first. I've seen this a couple times recently. When I told them of VMware, showed them how it worked, and explained why it's better to run a trimmed down Linux as the host, they went to Microsoft instead. Their first reaction was to find out what the Microsoft solution was( I told them they had something ) and then they'd install it from their MSDN CD on a new computer running Windows XP. And then they start asking me questions about it.
It's like they are baffled by Linux and run to what they are comfortable with.... In a couple of cases, I could atleast move them to VMware on the Windows host but that's as far as I could get.
So Microsoft already has a leg up on the competition and ANYTHING they can do to keep their customers from 'finding' Linux means they'll keep purchasing Microsoft products above all others. IMO, Linux VM appliances are a threat to Windows and if Microsoft can control the virtualization foundation those VM run in, they can make those 'unwieldy' to operate or operate with reduced performance to make them less attractive than a Windows solution. IMO.
LoB
This is Microsoft we are talking about here so the excercise is to figure out how this will be played out.
Will Microsoft take what they learn from 'working' with Xen and use it in their own product( Sybase SQL, Wang DDE, Sun JAVA, etc )?
Will Microsoft find ways to break Xen or cripple it so that the Microsoft product works better?
Or, is Faust making snowballs and Microsoft is really working to make a competing technology work better when at the same time they are working to release their own product which supports only Windows as the Host and only recently stated they'd support Linux as a client VM?
My guess is that it's going to be a mix of the 1st and 2nd actions. And what's with them calling the Server "Longhorn"? Have they not already announced the product is called Vista? Is this a trick to separate how they 'work' with Xen now but release something different in Vista Server? Will it be used to manipulate the public/press perception? Or do they really not have a name for the product yet and still use "Longhorn" in press releases?
LoB
That is most likely what they'll let RECHARGEABLE Li batteries onboard but not full capacity non-rechargeable Li batteries. With all the ways the batteries can be damaged before they're put on the planes, there's too much of a risk of fire from latent fires due to damaged cells.
This is also why there aren't lots of fires in the backrooms of computer stores. All those laptops not only don't have charged batteries but they've probably already been inspected for damaged packaging.
Atleast that's my theory.
LoB
In related news: The Musick Industry finds that since their products have been used for thousands of years, they believe The Circle is going unlicensed. The Musick Industry believes that in the distributing of music used over the years, one can always find The Circle and so it is going unlicensed and may start charging extra for its use. The Musick Industries Circle can be traced back to its use in singing around a campfire, the Victrola, reel-to-reel, albums, cassette tapes, compact discs, and on the circuit board of flash-based music players. Therefore, any use of The Circle associated with music is the property of the Musick Industry and unauthorized use is prohibited. Any persons found shaping their lips to the form of The Circle while singing a song will be held libel and could be prosecuted.
;)
In and interesting turn, the Musick Industry has recently invested billions in prison systems operations around the world in anticipation of the imprisoning of all persons worldwide as it starts protecting its property, The Circle.
LoB
...on their face. Most laptops with ATI Mobility Express chipsets can't use the onboard video memory. ATI broke this a year ago and has not fixed it.
So don't trust ATI for Linux capabilities on notebooks.
Maybe Toms Hardware can do a notebook comparison since they've already done the desktop. I'm pretty sure that would expose this failure to far more than the few who already are aware of this. And just maybe, it'll get ATI to fix this.
LoB
The VMPlayer will only PLAY VMs, VMserver, as you stated, let's you create VMs. The other difference is that the VMplayer runs one VM instance where the VMserver is designed to run multiple VMs all managed from a common( tabbed ) UI. I've seen it said here that there are preformance differences between the VMplayer and VMserver. I don't know about that but I do know that if you don't load up the VMWareTools for each VM, they will run quite slow.
I think the advantage of the VMplayer is that it's an easier install and easier to run a VM from. And therefore, it makes an easy platform for the VirtualAppliances VMWare has been promoting.
LoB
It looks like the plan was to NOT letting this get too popular. The fact that customers have to pay more for this power AND the plan is to pay the farmers more than the current rate is the exact technique I'd use if I didn't want too many customers picking this option. Who's going to make the choice to pay about 30% more for energy?
This looks like a scam to make this look like the "green" thing to do when in fact, the result is going to make very little difference in how their energy is produced. Sounds just like Bush's hydrogen vs hybrid strategies.
LoB
There's tons of information on this but I'll fill you in, you don't need to worry about that. The wing sail can be 'trimmed' to a symetric shape and weather vaned in high winds if needed. It turns out that one of the first Walker Wing Sail ships to cross the Atlantic went through a Category 3 hurricane without any problems besides some frightened crew members.
This question seems to get asked of the wing sail system as much as Prius owners get asked "How do you plug in it". And like the Prius hybrid system, it's not a concern due to the design of the system.
LoB
winds change and change often, a para-sail out on a tether might make a good picture but over a few thousand miles, I wonder how many times it's going to either get wet or need to be pulled in quickly.
I saw 30% possible fuel savings mentioned but didn't see any real world data whereas the Walker system has been deployed and saw a 15-20% savings on the one ship it was installed on in the late 80's.
BTW, I figured just looking at the two designs might be a clue as to why one might be better than the other. If you want more, there's google for ya.
LoB
The Walker Wing Sail system was designed in the 70s when fuel was 'expensive' and the idea was to outfit freighters with the Wing Sails to help reduce fuel costs. Unfortunately, once the fuel 'shortages' of the 70's went away, Mr Walker found it very difficult to sell his systems. He started making his own Trimarans when no boat builders would license his design and build boats using it. But finacially solid orders were too few and only a handful of his boats were made utilizing the Wing Sail design. Some are still afloat today.
http://www.lusas.com/case/composite/wingsail.html
So I think the Walker Wing Sail makes more sense than this para-sail system.
LoB
Bull sh1t, what I said was that you will NOT be able to add Microsofts proprietary extensions to its plugin and they are not going to put their proprietary code, or conversion for such, in this open source project.
Anybody would be far better off helping with one of the other plugins since the goal of THOSE projects will be compatibility and not showing how bad ODF document conversions can be and why MS OpenXML is supposedly better than ODF.
LoB
wow, there's so much wrong with your reply I don't know where to start. Let's start with the ECMA, they allow proprietary/patented material in their 'standards' and Microsoft has this in their MS OpenXML. And that FAQ link was just too funny. I loved the question: "How open or closed will the Ecma International process be for the OpenXML formats?". Shouldn't that have been 'How open or closed with the Ecma standard be for the MS OpenXML formats'? Oh, and Microsoft has been 'talking' about open standard for over 6 years now and yet, none of it is really open. They use the work "open" alot though.
Next, where do you get that a menu item to download a plugin means the conversion is right to ODF? And I could be wrong with regards to other versions of MS Office working with this but surely stating that Microsoft is working on MS OpenXML capabilities for some previous version of MS Office does not mean this plugin will work with it. It goes more to say that converting to MS OpenXML is going to be a requirement before converting to ODF.
over 20 years of Microsoft history tells me that what they SAY and what they DO are VERY different unless you look at what they SAY from a marketing perspective. Then, when the resulting product is thrown out there, you'll not be surprised. IMO
LoB
If "your buddy" only needs to read your document, then export to PDF and send him the PDF. Atleast that way, it's less likely your document will get changed and mis-interpreted from how you intended it AND everyone can read it.
n ews.jhtml?articleId=187201009
But if you must send him/her an editable document, I would trust a 3rd pary plugin for MS Office over one backed by MSFT any day. There's alredy one being deliverd to that State of Massachusetts from the OpenDocument Foundation:
http://www.crn.com/sections/breakingnews/breaking
But I don't know if it's been released to the public yet or not. And if people really think there'll be anything better in Microsofts plugin over the others, just think about how well Microsoft has supported competing products in the past. And if MSopen XML is really open, there's nothing stopping a 3rd party from doing as good a job, or better, than Microsoft since ODF is completely public.
And not everyone is going to jump on the ODF bandwagon right away. It'll first happen at the State, Local, and Federal levels of government since they are the ones creating public documents without owning or controlling the rights for access to the documents. The rest will follow this lead. And considering MSFT gets over 30% of its profits from MS Office, there's no reason to believe they will go quietly.
LoB
you forget, MSopen XML was submitted to the ECMA. The ECMA allows patented materials in formats submitted to it for a public standardization. Microsofts .Net stuff is the same way. So, just how much of Microsofts patented MSopen XML format is going to be in this BSD-like licensed plugin? If Microsoft patented how they put a PageBreak in MSopen XML, you won't see it in the ODF plugin. And if you go and reverse engineer their MSopen XML and add that PageBreak code to the plugin, don't even think about releasing THAT to the public without a license from Microsoft.
This is Microsoft we are talking about, so don't think there is any way this can be used for anything but directing people to use Microsoft products and Microsoft proprietary formats on Microsfot Windows. It's just the way the marketing company called Microsoft works. History shows this. IMO.
LoB
And what would be the purpose of doing that? You know darn well that ODF format/structures will not be translated to the same proprietary format/structures of MSopen XML.
This 'plug-in' is only going go convert from ODF to MSopen XML initially and supposedly, it'll eventually go the other way. If you'd like to convert your existing proprietary formatted MS-word document formats then you'll have to move them to MSopen XML first and THEN to ODF. And if you want MSopen XML then you'll have to get a future version of MS Office( 2007 ) and it's likely you'll also need another version of Microsoft Windows to run that, and you'll probably need a new computer to run that.
So good luck trying to fix any of this without reverse engineering Microsofts patented structures, purchasing all that new software, and hardware to do this and still be doing this with possible legal threats from MSFT. And then, you'd be doing this when the whole purpose of this Microsoft plugin is not to provide something that'll be useful but instead, to provide something to show how bad ODF is.
Good luck with THAT.
LoB
What makes you think Microsoft WANTS to do good conversions between their proprietary format and the public ODF format? Surely there is absolutely no history of this. You've got some 'inside' information? ;-)
LoB
except every other imported ODF word will be reversed because of a mismatch between ODF and MSopenXML. Well, that's what they'll say.
Sure it's on Sourceforge.net and we could 'fix' these issues but then again, we really don't think there'll be anything there which handles the 'patented' and 'proprietary' parts of the MS Office file formats( old or new ) do we? I hope not.
LoB
top that off with the fact that 'their' plugin will only convert some future MSopen-XML file format to ODF and what you get is any requirement for ODF means you have to have the next version of MS Office( which will probably require a new OS ). So, if you have any existing MS Office files, you'll have to convert them to MSopen-XML and then convert that to ODF.
And Microsoft is claiming that they are doning this to make sure of an accurate conversion to ODF. Yeah, right. But rest assured, those who maintain use of Microsoft products, to point of exclusion to almost all other software, will use this and complain of the poor conversion. I wonder how much they'll pay the press to publish lies about the ability to use ODF in an MS Windows office.
LoB
not successful? It got them $125 cool million from Microsoft to stop all that Linux stuff. Without Corel LinuxOS and the bucks MSFT paid them to dump it, Corel might be in worst shape today. IMO.
LoB
Sounds like there's some tight coupling with the next version of the rewritten-from-the-ground-up operating system having the best security of any OS on the market. Maybe they should stop charging extra for this and ship it with the computer and tie the pricing to the hardware so that you can't update the computer without asking permission.
or are they just having a difficult time figuring out how to read the ODF specs?
is there a train wreck coming or what.
LoB
that'll happen only if there's a Linux LiveCD that'll migrate their existing data, use their hard drive for a persistent HOME and SETTINGS location and provide the option of bringing their 'old' operating system back up in a virtual machine.
Otherwise, people will pay the Redmond Ransome just to get their data and settings back. But there still will be a goog number of Linux people getting calls asking about 'that thing called Linux' and asking if it'll run on their computer. Hey, the viruses and spyware are already doing that now so having their OS shutdown by its manufacturer and owner isn't going to make them any happier.
LoB
That's what I ment alright. Thanks.
LoB
I don't yet know about the Nokia 770 but I think you might have run into the PXA255 fiasco. A PXA250 running at 206MHz ran circles around the PXA255 running at 400MHz. Intel screwed up that chip so bad that cache had to be turned off in many cases and I think there was one other bug in it which also greatly reduced its speed.
Simply amazing how Intel has blown not only the desktop CPU market but also the handheld/etc market.
LoB