<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: ReactOS Reviewed: The Next Windows?</title>
	<atom:link href="http://neosmart.net/blog/2006/reactos-the-next-windows/feed/" rel="self" type="application/rss+xml" />
	<link>http://neosmart.net/blog/2006/reactos-the-next-windows/</link>
	<description>Connecting Ideas</description>
	<pubDate>Thu, 15 May 2008 20:05:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6-bleeding</generator>
		<item>
		<title>By: Daniel Breidegam</title>
		<link>http://neosmart.net/blog/2006/reactos-the-next-windows/#comment-158470</link>
		<dc:creator>Daniel Breidegam</dc:creator>
		<pubDate>Thu, 15 May 2008 02:01:20 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/archives/220#comment-158470</guid>
		<description>I've actually used this before on one of my spare machines, booted into 64mb of ram where most other OS's failed to do so. The absolute best feature of this OS is not the open source, free, ect. but that it is so much more damn efficient. Kind of makes me wonder why the microsoft corporation doesnt notice public unrest and try to develop a more effecient and STABLE OS instead of slapping us with something like Vista. I made a point of using vista for about a month, i found that not only did everything become slower and lag, but that i was getting hit left and right by viruses. Luckily i thought enough to install nod32. Linux ftw.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve actually used this before on one of my spare machines, booted into 64mb of ram where most other OS&#8217;s failed to do so. The absolute best feature of this OS is not the open source, free, ect. but that it is so much more damn efficient. Kind of makes me wonder why the microsoft corporation doesnt notice public unrest and try to develop a more effecient and STABLE OS instead of slapping us with something like Vista. I made a point of using vista for about a month, i found that not only did everything become slower and lag, but that i was getting hit left and right by viruses. Luckily i thought enough to install nod32. Linux ftw.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mahmoud Al-Qudsi</title>
		<link>http://neosmart.net/blog/2006/reactos-the-next-windows/#comment-117466</link>
		<dc:creator>Mahmoud Al-Qudsi</dc:creator>
		<pubDate>Tue, 18 Mar 2008 20:32:02 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/archives/220#comment-117466</guid>
		<description>Well, both VirtualBox and VirtualPC aren't the "optimal" virtualization softwares. The only one's I'd dare recommend would be VMware (Workstation - which is paid; and Server - which is *free*) and Parallels *only if* you have a good reason not to use VMware.</description>
		<content:encoded><![CDATA[<p>Well, both VirtualBox and VirtualPC aren&#8217;t the &#8220;optimal&#8221; virtualization softwares. The only one&#8217;s I&#8217;d dare recommend would be VMware (Workstation - which is paid; and Server - which is *free*) and Parallels *only if* you have a good reason not to use VMware.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sam wilke</title>
		<link>http://neosmart.net/blog/2006/reactos-the-next-windows/#comment-117438</link>
		<dc:creator>sam wilke</dc:creator>
		<pubDate>Tue, 18 Mar 2008 18:07:32 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/archives/220#comment-117438</guid>
		<description>reactOS always just gives me a Blue screen when I try to emulate it in VirtualPC or VirtualBox

The Qemu emulation works, and I'm waaay to cheap to buy VMWare</description>
		<content:encoded><![CDATA[<p>reactOS always just gives me a Blue screen when I try to emulate it in VirtualPC or VirtualBox</p>
<p>The Qemu emulation works, and I&#8217;m waaay to cheap to buy VMWare</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Benfield</title>
		<link>http://neosmart.net/blog/2006/reactos-the-next-windows/#comment-76447</link>
		<dc:creator>John Benfield</dc:creator>
		<pubDate>Wed, 12 Dec 2007 16:25:22 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/archives/220#comment-76447</guid>
		<description>&#62;But look at it like this: if you're going to be using it to run virtualized operating systems, why all the bother with MS-compatibilties in the first place? After all, a highly stripped-down Linux distribution with VMware or Xen installed will do the same thing.

Politics mostly. A "Windows compatible" operating system is an easier sell than "Switch to Linux".&#160;

VMWare and Xen are certainly viable options for some situations. But the footprint and hardware requirements are relatively large. If you can run Windows in VMWare, you can certainly run it natively right on the client.

If an app virtualization&#160;client like Thinstall or Softgrid could be made to work, you could package up your existing Windows apps so that there's no loss in functionality at the client. You'd reduce your IT support costs since the apps are all isolated in packages, centralized on a server and there's no issue with people farting around with configurations locally. You also do away with a lot of compatibility and integration testing since the packages are somewhat isolated from the client OS and each other. The advantage over a VMWare solution is that you aren't packaging the entire OS and operating environment with each app. Only&#160;the bare minimum to run the app is included and ReactOS continues to&#160;provides the core services. You can do the same with Linux, Wine and a lot of brute-force, but it's multiple layers of emulation and abstraction where something like ReactOS would be a single layer (or maybe 2).

As for the embedded options, I just realized that I have a few "appliances" that I've built using Win2K. (It's faster than WinXP and recovers better from brute force power on/off situations) I'll have to see if ReactOS would be a viable replacement. I could also see ReactOS as a viable option where WindowsCE is being used today.

Maybe I just look at it differently than the dissenters. I don't see the future of it as a replacement for gamers or power users. The real power and viability is where you need core Windows compatibility, speed&#160;and a small footprint. The geek running 64-bit with 8GB of RAM, dual-SLI and a 1TB disk array to speed up level loads isn't going to be the beneficiary. Someone in a call center that runs one app or a Windows-based cash register in Walmart or the guy running a dedicate MAME system&#160;on a Centrino with 256MB of RAM are far more likely candidates.

It's pretty exciting and I hope that the recent attention gets ReactOS some funding and supporters. There's a lot of potential. I just hope that the timing is right to really exploit it.
</description>
		<content:encoded><![CDATA[<p>&gt;But look at it like this: if you&#8217;re going to be using it to run virtualized operating systems, why all the bother with MS-compatibilties in the first place? After all, a highly stripped-down Linux distribution with VMware or Xen installed will do the same thing.</p>
<p>Politics mostly. A &#8220;Windows compatible&#8221; operating system is an easier sell than &#8220;Switch to Linux&#8221;.&nbsp;</p>
<p>VMWare and Xen are certainly viable options for some situations. But the footprint and hardware requirements are relatively large. If you can run Windows in VMWare, you can certainly run it natively right on the client.</p>
<p>If an app virtualization&nbsp;client like Thinstall or Softgrid could be made to work, you could package up your existing Windows apps so that there&#8217;s no loss in functionality at the client. You&#8217;d reduce your IT support costs since the apps are all isolated in packages, centralized on a server and there&#8217;s no issue with people farting around with configurations locally. You also do away with a lot of compatibility and integration testing since the packages are somewhat isolated from the client OS and each other. The advantage over a VMWare solution is that you aren&#8217;t packaging the entire OS and operating environment with each app. Only&nbsp;the bare minimum to run the app is included and ReactOS continues to&nbsp;provides the core services. You can do the same with Linux, Wine and a lot of brute-force, but it&#8217;s multiple layers of emulation and abstraction where something like ReactOS would be a single layer (or maybe 2).</p>
<p>As for the embedded options, I just realized that I have a few &#8220;appliances&#8221; that I&#8217;ve built using Win2K. (It&#8217;s faster than WinXP and recovers better from brute force power on/off situations) I&#8217;ll have to see if ReactOS would be a viable replacement. I could also see ReactOS as a viable option where WindowsCE is being used today.</p>
<p>Maybe I just look at it differently than the dissenters. I don&#8217;t see the future of it as a replacement for gamers or power users. The real power and viability is where you need core Windows compatibility, speed&nbsp;and a small footprint. The geek running 64-bit with 8GB of RAM, dual-SLI and a 1TB disk array to speed up level loads isn&#8217;t going to be the beneficiary. Someone in a call center that runs one app or a Windows-based cash register in Walmart or the guy running a dedicate MAME system&nbsp;on a Centrino with 256MB of RAM are far more likely candidates.</p>
<p>It&#8217;s pretty exciting and I hope that the recent attention gets ReactOS some funding and supporters. There&#8217;s a lot of potential. I just hope that the timing is right to really exploit it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Computer Guru</title>
		<link>http://neosmart.net/blog/2006/reactos-the-next-windows/#comment-74557</link>
		<dc:creator>Computer Guru</dc:creator>
		<pubDate>Tue, 04 Dec 2007 14:59:47 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/archives/220#comment-74557</guid>
		<description>Well, that certainly is an interesting idea.

But look at it like this: if you're going to be using it to run virtualized operating systems, why all the bother with MS-compatibilties in the first place? After all, a highly stripped-down Linux distribution with VMware or Xen installed will do the same thing.

However, running Windows-based (probably built for Windows Embedded) thin-clients... &lt;em&gt;that&lt;/em&gt; sounds like an idea that could be expanded on!

I don't know about the Vista compatibility, but I'll certainly do my best to find out and post back :)</description>
		<content:encoded><![CDATA[<p>Well, that certainly is an interesting idea.</p>
<p>But look at it like this: if you&#8217;re going to be using it to run virtualized operating systems, why all the bother with MS-compatibilties in the first place? After all, a highly stripped-down Linux distribution with VMware or Xen installed will do the same thing.</p>
<p>However, running Windows-based (probably built for Windows Embedded) thin-clients&#8230; <em>that</em> sounds like an idea that could be expanded on!</p>
<p>I don&#8217;t know about the Vista compatibility, but I&#8217;ll certainly do my best to find out and post back <img src='http://neosmart.net/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Benfield</title>
		<link>http://neosmart.net/blog/2006/reactos-the-next-windows/#comment-74554</link>
		<dc:creator>John Benfield</dc:creator>
		<pubDate>Tue, 04 Dec 2007 14:48:16 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/archives/220#comment-74554</guid>
		<description>It's really unfortunate that it's been in development for so long. Being in alpha for 11 years is one of those stigmas that's going to haunt ReactOS. It's a remarkable achievement. But it's really a shame that some corporate monolith didn't jump on board to throw some&#160;cash and resources at it. There could have been a ton of money in consulting, support and enterprise licensing while promoting a "free" alternative for the masses.

Just out of curiosity, is ReactOS going to jump on the Vista bandwagon and try to&#160;build the Vista kernel changes? (UMDF, ASLR, all of the UAC and session 0 isolation, etc.) I don't know that anything would be lost by ignoring the changes, apart from compatibility. But I'm just curious how ReactOS is going to position itself now that Microsoft is getting more aggressive and scheduling more frequent kernel-level changes.

Finally, is there anyone looking at ReactOS as a thin/thick-client OS? With desktop virtualization becoming a hot topic in the enterprise, I would think that a sleek fast OS that could&#160;run a&#160;VNC or RDP client would be pretty well received. If it could&#160;stream and run&#160;Softgrid or Thinstall images as well, it would certainly be in a good place. Since Microsoft's VECD licensing is so restrictive (ie: expensive as hell for large mixed deployments), there's a pretty nice niche there that could be exploited. Add ReactOS on a bootable CF card to an old desktop and get a brand new high-speed thin-client with ultra-low maintenance costs. Linux and Wine has been a popular alternative, but it's certainly higher maintenance and a larger footprint. Plus it has the "Linux Geek" stigma in the enterprise. A lot of executives roll their eyes and groan whenever you mention Linux because of the wild promises that they've been hearing for years. ReactOS would be something "new" without any of the baggage. It would be a pretty nice coup to see ReactOS as an embedded OS in a client appliance.
</description>
		<content:encoded><![CDATA[<p>It&#8217;s really unfortunate that it&#8217;s been in development for so long. Being in alpha for 11 years is one of those stigmas that&#8217;s going to haunt ReactOS. It&#8217;s a remarkable achievement. But it&#8217;s really a shame that some corporate monolith didn&#8217;t jump on board to throw some&nbsp;cash and resources at it. There could have been a ton of money in consulting, support and enterprise licensing while promoting a &#8220;free&#8221; alternative for the masses.</p>
<p>Just out of curiosity, is ReactOS going to jump on the Vista bandwagon and try to&nbsp;build the Vista kernel changes? (UMDF, ASLR, all of the UAC and session 0 isolation, etc.) I don&#8217;t know that anything would be lost by ignoring the changes, apart from compatibility. But I&#8217;m just curious how ReactOS is going to position itself now that Microsoft is getting more aggressive and scheduling more frequent kernel-level changes.</p>
<p>Finally, is there anyone looking at ReactOS as a thin/thick-client OS? With desktop virtualization becoming a hot topic in the enterprise, I would think that a sleek fast OS that could&nbsp;run a&nbsp;VNC or RDP client would be pretty well received. If it could&nbsp;stream and run&nbsp;Softgrid or Thinstall images as well, it would certainly be in a good place. Since Microsoft&#8217;s VECD licensing is so restrictive (ie: expensive as hell for large mixed deployments), there&#8217;s a pretty nice niche there that could be exploited. Add ReactOS on a bootable CF card to an old desktop and get a brand new high-speed thin-client with ultra-low maintenance costs. Linux and Wine has been a popular alternative, but it&#8217;s certainly higher maintenance and a larger footprint. Plus it has the &#8220;Linux Geek&#8221; stigma in the enterprise. A lot of executives roll their eyes and groan whenever you mention Linux because of the wild promises that they&#8217;ve been hearing for years. ReactOS would be something &#8220;new&#8221; without any of the baggage. It would be a pretty nice coup to see ReactOS as an embedded OS in a client appliance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Computer Guru</title>
		<link>http://neosmart.net/blog/2006/reactos-the-next-windows/#comment-74545</link>
		<dc:creator>Computer Guru</dc:creator>
		<pubDate>Tue, 04 Dec 2007 14:05:04 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/archives/220#comment-74545</guid>
		<description>Well, they'll probably still poke fun at it on Slashdot anyway - if it's not Linux, it's not worthy :P

But all joking aside, ReactOS has actually been "in the works" since the early 90s &#8211; it's only recently getting the attention it deserves.</description>
		<content:encoded><![CDATA[<p>Well, they&#8217;ll probably still poke fun at it on Slashdot anyway - if it&#8217;s not Linux, it&#8217;s not worthy <img src='http://neosmart.net/blog/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> </p>
<p>But all joking aside, ReactOS has actually been &#8220;in the works&#8221; since the early 90s &ndash; it&#8217;s only recently getting the attention it deserves.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Delibert0</title>
		<link>http://neosmart.net/blog/2006/reactos-the-next-windows/#comment-74533</link>
		<dc:creator>Mike Delibert0</dc:creator>
		<pubDate>Tue, 04 Dec 2007 12:46:25 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/archives/220#comment-74533</guid>
		<description>Its funny, a few years ago I remember being mocked for mentioning something like this, rewriting windows to make it more efficient, etc, look what happened. Its somewhere on slash dot, I'll have to look</description>
		<content:encoded><![CDATA[<p>Its funny, a few years ago I remember being mocked for mentioning something like this, rewriting windows to make it more efficient, etc, look what happened. Its somewhere on slash dot, I&#8217;ll have to look</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Walker</title>
		<link>http://neosmart.net/blog/2006/reactos-the-next-windows/#comment-58547</link>
		<dc:creator>Robert Walker</dc:creator>
		<pubDate>Thu, 18 Oct 2007 20:18:42 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/archives/220#comment-58547</guid>
		<description>This is the perfect time to be working on a clone of Windows. When Windows XP is frozen at SP2 and Windows Vista sinks like a stone... OK ReactOS has been a work in progress for a while :-) But Rome wasn't built in a day :-)
  

&#160;Problem is reverse engineering the entire Windows OS would frankly drive me insane...

I presume most of the people posting crap about ReactOS couldn't even reverse engineer &lt;a href="http://www.google.co.uk/search?hl=en&#38;client=firefox-a&#38;rls=org.mozilla:en-US:official&#38;hs=0db&#38;sa=X&#38;oi=spell&#38;resnum=0&#38;ct=result&#38;cd=1&#38;q=PROPRIETARY+&#38;spell=1"&gt;&lt;strong&gt;&lt;em&gt;ONE PROPRIETARY&lt;/em&gt;&lt;/strong&gt; &lt;/a&gt;Windows hardware device driver...&#160; You bunch of brainless lameos... The OS is at the alpha stage and there isn't hundreds of paid programmers working on it like M$...
  

&#160;Imagine having a decent OS for gaming on that wouldn't get kicked off on-line servers for not being the 'correct' Windows. Or an OS that supported Windows drivers that Linux doesn't (a lot from what I keep finding when I try to install the latest distros - bloody hardware/chipset manufacturers)... An OS that fixes real bugs rather than constantly have security fixes released (bullshit)
  &#160;

&#160;ReactOS team rock on!!

&#160;

Bob Wya


  
  &#160;
</description>
		<content:encoded><![CDATA[<p>This is the perfect time to be working on a clone of Windows. When Windows XP is frozen at SP2 and Windows Vista sinks like a stone&#8230; OK ReactOS has been a work in progress for a while <img src='http://neosmart.net/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> But Rome wasn&#8217;t built in a day <img src='http://neosmart.net/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>&nbsp;Problem is reverse engineering the entire Windows OS would frankly drive me insane&#8230;</p>
<p>I presume most of the people posting crap about ReactOS couldn&#8217;t even reverse engineer <a href="http://www.google.co.uk/search?hl=en&amp;client=firefox-a&amp;rls=org.mozilla:en-US:official&amp;hs=0db&amp;sa=X&amp;oi=spell&amp;resnum=0&amp;ct=result&amp;cd=1&amp;q=PROPRIETARY+&amp;spell=1"><strong><em>ONE PROPRIETARY</em></strong> </a>Windows hardware device driver&#8230;&nbsp; You bunch of brainless lameos&#8230; The OS is at the alpha stage and there isn&#8217;t hundreds of paid programmers working on it like M$&#8230;</p>
<p>&nbsp;Imagine having a decent OS for gaming on that wouldn&#8217;t get kicked off on-line servers for not being the &#8216;correct&#8217; Windows. Or an OS that supported Windows drivers that Linux doesn&#8217;t (a lot from what I keep finding when I try to install the latest distros - bloody hardware/chipset manufacturers)&#8230; An OS that fixes real bugs rather than constantly have security fixes released (bullshit)<br />
  &nbsp;</p>
<p>&nbsp;ReactOS team rock on!!</p>
<p>&nbsp;</p>
<p>Bob Wya</p>
<p>  &nbsp;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nightfox</title>
		<link>http://neosmart.net/blog/2006/reactos-the-next-windows/#comment-55572</link>
		<dc:creator>Nightfox</dc:creator>
		<pubDate>Sun, 30 Sep 2007 20:42:17 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/archives/220#comment-55572</guid>
		<description>I am really interested in ReactOS and look forward to possibly replacing Windows XP with it on my computers some day.&#160; However, I am somewhat skeptical about whether it can achieve 100% compatibility with Windows applications.

For one thing, I've heard that the Windows API is not totally documented, and in some cases, the documentation may be incorrect, which happens sometimes when the code is updated but the documentation is not.&#160; I seem to remember reading that this is a problem for the Wine developers.&#160; Also, I've heard that there may be special "hidden" APIs within Windows that Microsoft uses for their own apps to make them run faster or work better with Windows than another company's app.&#160; That was one of the arguments I heard back when the antitrust case against Microsoft was in full swing.

Another problem is the fact that the ReactOS team will always be a little behind in keeping up with the changes that Microsoft puts out in their service packs, patches, etc..&#160; If Microsoft makes any significant additions to Windows with their service packs, the ReactOS team would have to take some time to release the equivalent changes in ReactOS.

I am excited about ReactOS though.&#160; It looks like it has come along fairly well, and it would be nice to have a GPL alternative to Windows so that if I build my own PC, I won't have to spend an arm and a leg on an OS to install on it.&#160; If I had more experience with OS development, I might even join the ReactOS team and contribute to it.
  
</description>
		<content:encoded><![CDATA[<p>I am really interested in ReactOS and look forward to possibly replacing Windows XP with it on my computers some day.&nbsp; However, I am somewhat skeptical about whether it can achieve 100% compatibility with Windows applications.</p>
<p>For one thing, I&#8217;ve heard that the Windows API is not totally documented, and in some cases, the documentation may be incorrect, which happens sometimes when the code is updated but the documentation is not.&nbsp; I seem to remember reading that this is a problem for the Wine developers.&nbsp; Also, I&#8217;ve heard that there may be special &#8220;hidden&#8221; APIs within Windows that Microsoft uses for their own apps to make them run faster or work better with Windows than another company&#8217;s app.&nbsp; That was one of the arguments I heard back when the antitrust case against Microsoft was in full swing.</p>
<p>Another problem is the fact that the ReactOS team will always be a little behind in keeping up with the changes that Microsoft puts out in their service packs, patches, etc..&nbsp; If Microsoft makes any significant additions to Windows with their service packs, the ReactOS team would have to take some time to release the equivalent changes in ReactOS.</p>
<p>I am excited about ReactOS though.&nbsp; It looks like it has come along fairly well, and it would be nice to have a GPL alternative to Windows so that if I build my own PC, I won&#8217;t have to spend an arm and a leg on an OS to install on it.&nbsp; If I had more experience with OS development, I might even join the ReactOS team and contribute to it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: betaluva</title>
		<link>http://neosmart.net/blog/2006/reactos-the-next-windows/#comment-54736</link>
		<dc:creator>betaluva</dc:creator>
		<pubDate>Wed, 26 Sep 2007 23:03:40 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/archives/220#comment-54736</guid>
		<description>hi, i like you review of reactos, maybe its time to do another review,a lot of things have improved in the last&#160;12 months.</description>
		<content:encoded><![CDATA[<p>hi, i like you review of reactos, maybe its time to do another review,a lot of things have improved in the last&nbsp;12 months.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Ando</title>
		<link>http://neosmart.net/blog/2006/reactos-the-next-windows/#comment-52746</link>
		<dc:creator>Tim Ando</dc:creator>
		<pubDate>Mon, 24 Sep 2007 01:23:03 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/archives/220#comment-52746</guid>
		<description>I have tried it on a real machine but it was a pain in the neck to install (the install disk doesn't work. neither does the live cd) first i had to convert the virtual hard disk to raw format then copy the partition over with parted. it doesnt like my usb mouse or serial mice though
</description>
		<content:encoded><![CDATA[<p>I have tried it on a real machine but it was a pain in the neck to install (the install disk doesn&#8217;t work. neither does the live cd) first i had to convert the virtual hard disk to raw format then copy the partition over with parted. it doesnt like my usb mouse or serial mice though</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tsetso Neshev</title>
		<link>http://neosmart.net/blog/2006/reactos-the-next-windows/#comment-47272</link>
		<dc:creator>Tsetso Neshev</dc:creator>
		<pubDate>Fri, 07 Sep 2007 20:49:36 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/archives/220#comment-47272</guid>
		<description>nice very nice :)</description>
		<content:encoded><![CDATA[<p>nice very nice <img src='http://neosmart.net/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leon</title>
		<link>http://neosmart.net/blog/2006/reactos-the-next-windows/#comment-41109</link>
		<dc:creator>Leon</dc:creator>
		<pubDate>Thu, 23 Aug 2007 18:13:56 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/archives/220#comment-41109</guid>
		<description>stolennomenclature, there's no need to run lots of proprietary Windows software on it.&#160; There are good, functional equivalents to a lot of MS software--with one major exception being the operating system itself.
  

Office - OpenOffice, AbiWord (both work stably in Windows now)

Internet Explorer - Firefox (arguably better anyway)

Media Player - VLC

Windows' (laughably bad) built-in CD burner - CDBurnerXP Pro
  
</description>
		<content:encoded><![CDATA[<p>stolennomenclature, there&#8217;s no need to run lots of proprietary Windows software on it.&nbsp; There are good, functional equivalents to a lot of MS software&#8211;with one major exception being the operating system itself.</p>
<p>Office - OpenOffice, AbiWord (both work stably in Windows now)</p>
<p>Internet Explorer - Firefox (arguably better anyway)</p>
<p>Media Player - VLC</p>
<p>Windows&#8217; (laughably bad) built-in CD burner - CDBurnerXP Pro</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Open Directory - Computers: Software: Operating Systems: Microkernel: ReactOS</title>
		<link>http://neosmart.net/blog/2006/reactos-the-next-windows/#comment-37694</link>
		<dc:creator>Open Directory - Computers: Software: Operating Systems: Microkernel: ReactOS</dc:creator>
		<pubDate>Sun, 12 Aug 2007 09:21:26 +0000</pubDate>
		<guid isPermaLink="false">http://neosmart.net/blog/archives/220#comment-37694</guid>
		<description>[...] ReactOS Reviewed: The Next Windows? - Detailed review of ReactOS. [...]</description>
		<content:encoded><![CDATA[<p>[...] ReactOS Reviewed: The Next Windows? - Detailed review of ReactOS. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
