Linked by Thom Holwerda on Sat 2nd Sep 2017 22:51 UTC
ReactOS

0.4.6 is a major step towards real hardware support. Several dual boot issues have been fixed and now partitions are managed in a safer way avoiding corruption of the partition list structures. ReactOS Loader can now load custom kernels and HALs.

Printing Subsystem is still greenish in 0.4.6, however Colin Finck has implemented a huge number of new APIs and fixed some of the bugs reported and detected by the ReactOS automated tests.

Regarding drivers, Pierre Schweitzer has added an NFS driver and started implementing RDBSS and RXCE, needed to enable SMB support in the future, Sylvain Petreolle has imported a Digital TV tuning device driver and the UDFS driver has been re-enabled in 0.4.6 after fixing several deadlocks and issues which was making it previously unusable. Critical bugs and leakages in CDFS, SCSI and HDAUDBUS have been also fixed.

That's some solid progress.

Thread beginning with comment 648545
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Good progress
by Darak on Mon 4th Sep 2017 07:58 UTC in reply to "Good progress"
Darak
Member since:
2009-10-16

Haiku is actually more advanced regarding actual hardware support, but it is true that the pace of development in Haiku is very slow nowadays.

The things ReactOS aims to do are a lot harder, though. The Windows APIs are incredibly complex, poorly designed, partially undocumented, and have been a moving target since day one. Microsoft likes to reinvent the whole application programming biosphere every few years, often implementing the new one on top of the old ones. In comparison, BeOS had a clean and simple API that obviously never changed.

In any case, hardware support remains an unsolved problem for niche or enthusiast operating systems. Haiku essentially has no graphic drivers and relies on VESA to even draw anything to the screen, for example. In an ideal world, there should be some kind of open device driver API allowing vendors to write drivers that could work reliably on any open source OS.

Reply Parent Score: 1

RE[2]: Good progress
by yerverluvinunclebert on Mon 4th Sep 2017 08:11 in reply to "RE: Good progress"
yerverluvinunclebert Member since:
2014-05-03

And Cadbury's chocolate tastes nice!

Reply Parent Score: 1

RE[2]: Good progress
by yahya on Mon 4th Sep 2017 09:18 in reply to "RE: Good progress"
yahya Member since:
2007-03-29

The things ReactOS aims to do are a lot harder, though. The Windows APIs are incredibly complex, poorly designed, partially undocumented, and have been a moving target since day one. Microsoft likes to reinvent the whole application programming biosphere every few years, often implementing the new one on top of the old ones. In comparison, BeOS had a clean and simple API that obviously never changed.


And Windows is a moving target, while BeOS development has ended over a decade ago.

That means that ReactOS if it ever reaches stability, it will be obsolete before it is released. Already now, a lot of software requires at least Vista to install and run, while ReactOS tries to recreate Win XP/2003. So while ReactOS might have limited use for some very old programmes or drivers, it is not going to be a viable desktop OS. And if you need a legacy windows version, then running a real Winxp in VirtualBox still works far better.

I am not saying that the devs should stop. It is their hobby, they have to decide what to spend their time on. But the idea that ReactOS is ever going to become something of use for the average end user is illusory.

Edited 2017-09-04 09:21 UTC

Reply Parent Score: 2

RE[3]: Good progress
by yerverluvinunclebert on Mon 4th Sep 2017 09:31 in reply to "RE[2]: Good progress"
yerverluvinunclebert Member since:
2014-05-03

You are talking rubbish.

ReactOS' goal is NT5 compatibility. That's it. At that point they have a Windows binary compatible o/s that can run the majority of software. A full virtual memory operating system. From that point they can add the NT6 (Vista) APIs and achive upward/downward compatibility - this work has already started. Microsoft spends most of its time (and thousands of developers) re-inventing the wheel. It does this to fool people like you.

ReactOS does not have to follow Microsoft and all its later Win 8 Metro/Windows shennanigens. It does not have to keep up! It simply has a very good o/s when it arrives at NT5 compatibility. An o/s that can be added to as required.

Keep up with those uninformed comments!

Reply Parent Score: 2