Linked by Thom Holwerda on Wed 9th Apr 2008 17:16 UTC, submitted by M-Saunders
Permalink for comment 308888
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
More News »
Sponsored Links



Member since:
2007-09-17
I guess by paragraphs you're referring to segments. Yes, segments are horrible in real mode, but it doesn't affect MikeOS because the kernel (and loaded programs) reside in a single 64K segment. So that isn't a problem.
Regarding 32-bit, please see the FAQ section of the Handbook. In summary: 32-bit is naturally better if you want to write a full, serious, general-purpose OS. But when you're learning x86 assembly and want to piece together your own OS, 16-bit real mode is much better, because you have access to the BIOS.
This means that you can focus on doing interesting stuff (loading programs, making new system calls) instead of spending the first few months writing tedious keyboard and floppy drivers.