Linked by David Adams on Fri 5th Aug 2011 16:56 UTC, submitted by fran
Permalink for comment 483911
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2005-07-06
Anyone remember the original BeOS design. Have a hybrid kernel, with a bunch of servers / kits which can be used as required instead of being initialised all at once. Sounds exactly like what MinWin is trying to accomplish. To use a quote from the internet:
MinWin contains the bootloader, HAL (processor & chipset initialization, memory manager, etc), scheduler, most of the kernel infrastructure (sans most drivers, filesystems, etc) and some of the core Win32 subsystem upon which essential apps can be run.
To MinWin you can then configure an OS build by choosing which OS components you want to include from a catalog of items - NTFS, (ex)FAT, etc., TCP/IP & NETBIOS, SCSI/RAID, video, audio, printers, .NET, etc.