ReactOS 0.3.14 Released With Improved Networking Stack
An anonymous reader wrote in with news of the latest release of ReactOS, a project to create a complete reimplementation of Windows. The highlights of this release are the integration of a new network stack based upon lwIP, the ability to build using Microsoft's C compiler, and Wifi support. There are a few options for trying it out (emulator image and a livecd amongst others) and source code over at Sourceforge.
Ah, FOSS Windows 98 for the masses! How we've missed you...
I remember testing this out a few years ago, hopefully it's more stable than previously as well.. looking forward to trying it when I get home.
At this point I think it's time for me to upgrade from FreeDOS to ReactOS.
There are many possible reasons why people want a functioning clone of MS Windows that can use the same drivers etc.
If nothing else, it's an interesting project.
Why not Linux? Because drivers don't always work. Why not WINE? ReactOS and WINE share a lot of code, but WINE is aiming to solve a different problem. Why not just use old MS Windows? Because the source is not there, and neither is support.
People would find a use for a Free MS Windows clone the same way that people find a use for a Free MS DOS clone (FreeDOS).
I for one am excited about ReactOS. Here's hoping they continue the good work for many years
it's a joke, son
They almost finished getting the new USB stack up and running in a different branch, but it isn't reliable (or stable even in most virtual environments) to sync it into the main branch prior to release. That's fine in a virtual environment, but on real hardware it would be nice for a few different reasons (ReactOS on USB may be possible soon because of this, maybe even debug output over USB, to name a few).
I'll just keep building the USB branch until then.
ROS has fixed a lot of their issues this last release and I look forward to the upcoming years when it will be stable enough for daily use.
I can't help but think a number of talented people have wasted quite a lot of life on a project that is pretty much without value. Sometime the bazaar just really does produce chaos.
http://teasphere.wordpress.com - A little spot of tea
Best case: ReactOS remains a toy of little practical use.
Worst case: ReactOS succeeds, Microsoft sues either the devs or the users for infringing several thousand patents.
I really hope ReactOS is at 0.5 beta by then. It'll be a relief from having to choose between 50 linux distros, because there's no way I'm getting another Windows or Mac OS.
Then again there is PC-BSD :)
It's an interesting project, but I fear that its progress is too slow for it to be of any practical use. It's been under development since 1998, and is still in alpha and lacking core features. As a hobbyist project I'm sure it's great, and it's hugely ambitious, so I'm hardly surprised that progress has been slow. But I have no idea when it's going to achieve its aim of being 100% compatible with Windows, if ever.
The Random Joe who pulled that creaky old "waste of time" argument out of the toilet has absolutely ZERO say on what makes a good use of the developer's time. Only the developer himself has any say in that, because quite simply, his brain is inside his head and therefore his thoughts and conclusions belong exclusively to him, not Random Joe.
So Random Joe, get off your high horse and do something useful like the developers you speak of.
I've been hearing of this OS since the time I was a member of an Alpha-NT group. They've been taking all these years, and are not even on 1.x even now. These guys are giving Hurd strong competition on who takes forever to come up w/ an OS, particularly given all the FOSS OSs out there.
On the project itself, I think that it had a window of opportunity when MS abandoned the MIPS and Alpha versions of NT years ago. At that time, there were NT users for this platform worried about where it would leave them, and this would definitely have been a godsend. However, on the x86 platform, it's pretty much irrelevant - either people have Windows, and if that's not acceptable, they can run Linux. As it is, there are some things, like NTFS file system support that ReactOS doesn't/can't support, so it's not like even close to a complete substitute. The only people I can imgaine who might have (had) an use for it would be NT/RISC users, but that assumes that they never moved from NT to Linux or RISC to x64.
to see if they can they release version 1.0 of ReactOS before the X86 architecture becomes obsolete.
They can't even do a release that supports the Virtual Box Additions, I tried installing them and it bluescreened me.
Without support for modern file systems, It can not be taken seriously.
They should not dismiss suggestions to adopt use of fuse based filesystems such as ntfs3g, as this may likely be the most direct way to get support for popular file systems.
With projects like Qemu, then ReactOS will just grab a Virtual Terminal or XDisplay, so this way DRI drivers will become obsolete in favor of drivers deployed to a safe-standard NT architecture.
Transgaming WineX and CodeWeavers Wine and ReactOS have always had the reputation among Linux gamers as stealing the light from GNU/Linux in favor of another HAL and SAL.
I installed it on Parallels and I have to say I'm pretty impressed how far they have come sing last time I looked at it 5 years ago. I thought this was a dead project...
It is a very useful addition.
That was when I tested their last release.
I wonder whether they have integrated the WINE code enough so one could do stupid stuff, like trying out the only DirectX 4.0 or 5.0 game that must be out there, Chaos Overlords, on it?
I'm not sure that I would go these lengths though, I'd probably have to configure the downloaded VM image I use to try ReactOS.
Hey don't blame me, IANAB
VAX/VMS.
I heard you like old things, so I put a reverse-engineered Windows clone in your VM so you can simulate while you emulate.
Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
It's their time, they can do what the fuck they want.
I don't because my embedded system that uses it, boots from a section in the same flash chip as BIOS
Pardon me, but I was recently fascinated with the idea that something like that might be possible---Stuffing an INT13-reading bootloader, like GRUB4DOS or SYSLINUX, into an archive in the BIOS and then strapping it like any other option ROM.
:P
I was always fascinated with the idea of separating the initial boot program from the hard disk layout and into the board itself. Running a bootloader from the BIOS ROM would technically allow that to happen, I think, and I thought curiously about the idea of embedding a UEFI payload into it (that probably wouldn't fit, but I digress!)... essentially "converting" a board to UEFI by chainloading it from BIOS. Not practical, but I thought it would be pretty neat
Any links or info you could provide me on projects like yours?
Boot Windows, Linux, and ESX over the network for free.