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

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.

Permalink for comment 648551
To read all comments associated with this story, please click here.
RE[3]: Good progress
by yerverluvinunclebert on Mon 4th Sep 2017 09:31 UTC in reply to "RE[2]: Good progress"
Member since:

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