AUTISTIC PRIDE

When I get bored, instead of watching TV or playing vidya games, i start writing operating systems. Its just a hobby of mine. The first operating system I wrote used a monolithic kernel which unitasked and used 16bit protected segmentation. Over the years I began to write increasingly complicated operating systems, and the latest one I wrote includes a paging memory manager with support for PAE, a ring-one driver framework, custom executable format (dynamic library support too), custom filesystem with ACL's and a Realtek RTL8100 ethernet driver (did I mention the TCP/IPv4 stack and web browser?). When I look back at all the time I could have spent playing vidya games and watching the same TV shows over and over again, I realise why it takes some people years or even decades to learn what I have mastered within only two years. Popular media is the greatest threat to mankind

So /prog/,
WHERE'S YOUR OPERATING SYSTEM? HUH? HUH?

>>1-6
Running modern x86-64 CPUs in 32-bit exclusive protected mode is considered deprecated. It's like how running x86 in 16-bit real mode was considered deprecated back in the late 90s. It's time to abandon 32-bit x86.

Current x86-64 CPUs from AMD and Intel support 48-bits of hard addressing internally (the top 16-bits of the address lines are currently unused, but can be expanded upon when the time comes).

And if you really need to run a specific process in 32-bit mode, you can thunk down to 32-bit mode as needed.

There's no reason to limit yourself to the 32-bits.