For anyone interest, the biggest feature of this release is the Handbook, a complete guide to running, building and developing the OS. There's also a section on writing your own OS, with primers on the PC boot procedure and x86 assembly language:

I think this is an awesome feat. I'm going to crack open a beer in your honor. Maybe several.

Before that, I have question nagging at me and I can't wait to read the handbook to get to the answer: What was your rubric for the 1.0 release? Did you have a defined list of features going in that made you say, "I'll consider this my benchmark." Or did the rubric for 1.0 evolve as the project moved along?

Seriously, though, congrats on your 1.0 release.

Edit: I just realized I posted this one in the Announcements instead of the OtherOS. Whether you reply here or move me or ignore me is all up to you.

Cheers kilikopele, beerage is good! I started writing MikeOS as an experiment, playing around with x86 assembly and a small bootloader. After that I had some design ideas for loading programs and system calls, so I went ahead to satisfy my curiosity. A 16-bit real-mode OS is pretty archaic today -- I didn't have any major plans for it or list of must-have features.

However, a few months ago I was browsing the OSDev.org forums and someone recommended MikeOS 0.40 as a tool for learning basic OS design. At the time I was working on a GUI for MikeOS, but the code was getting overly complex so I ditched it. So I decided to set a goal for 1.0: make it a (hopefully!) useful mini OS for first-time OS developers and those learning x86 assembly, with complete documentation from start to finish.

So I tided up and re-commented a lot of the code, simplified the build scripts and wrote the mammoth handbook which should serve as a one-stop-shop for all things MikeOS.

I've already had some third-party input (someone has sent me an OS X build script), and I'll release 1.1 if I add new system calls or features. As for 2.0... well, maybe the old GUI code can be resurrected at some point

However, stick with me here because this makes a little sense. (Albeit, very little.) When I go through it, I really want to digest its contents and not give it just a cursory glance. To do that, I need some uninterrupted time--like when my son is in swimming and gymnastics and it's too damn cold to sit on my deck with a bourbon and a cigar. (Oh, and I do print marketing for real estate which really drops off in the "holiday" season, so I won't be putting in astronomical hours either.)

Yes, I even posted a small message to that effect in the sourceforge forum. As I mentioned there, for some reason GFXDEMO caused a lock-up the first time I ran 1.0, but not on any subsequent runs. All the other apps run just fine, except for Vlak quitting, which you already know about.
The html docs are nice and clearly laid out too. If only I understood them

I'd like to add my appreciation for MikeOS! I've tried it in qemu too.

I've haven't got round to digesting the handbook (and source code!) yet, but I have been thinking about learning x86 assembly language for a while, so that I can better understand the x86 architecture, so MikeOS will be a useful resource. The last assembly language programming I did was on a 6502 (BBC Master)...