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.

Thread beginning with comment 648556
To read all comments associated with this story, please click here.
I think they do this the wrong way...
by Megol on Mon 4th Sep 2017 16:12 UTC
Member since:

Why not "simply" write a kernel+HAL (executive layer) compatible with a certain Windows version and then replace upper layers step by step?

Yes it is certainly against MS licenses however most of the things in those aren't valid and it would be hard for MS to complain when people with valid licenses replace parts of their own OS installation.

Reply Score: 2

yerverluvinunclebert Member since:

It has been discussed as a strategy - but it breaks the terms of your Windows licence, you cannot even take the task manager from Win 7 and transplant it to Win10 (well you can but you aren't supposed to).

However, ReactOS code is created and tested on Windows first then moved to ReactOS ensuring for certain it functions under Windows and does not break any compatibility.

Reply Parent Score: 1