We talk to the developers behind MenuetOS: an operating system written entirely in assembly language

MenuetOS is an operating system that is super-fast and can fit on a single floppy disk (remember them?)

Why a monolithic kernel?

Ville: When you look at process execution at a more detailed level, Menuet kernel has features from both micro- and monolithic scheduling. For example, applications graphics access is implemented monolithic style and networking is implemented like in microkernels. Monolithic kernel is a reliable backbone for all the other features.

Why a real-time OS? That seems unusual for something with a GUI.

Ville: Menuet task-switching is a combination of pre-emptive and event-based scheduling. Every process has a maximum execution time which is interrupted by the timer scheduler. With a built-in GUI, this doesn't have any down-sides, since the amount of processing doesn't really change whether the multitasking is real-time or something else. So it really comes down to the actual GUI design, not that much to the scheduling type.


One of the main hassles of writing an operating system is the driver support. How did you pick the devices you support?

Ville: In general, we try to support the most popular device types first. For example, we support USB video, storage and printer device classes, which gives us the widest range of support. But more drivers are needed before hitting the 1.0 mark. Currently we just have a minimal set of drivers to add network applications, for example.

How well does Menuet deal with multi-core systems, given they seem increasingly common?

Madis: MenuetOS is still using a single core or a thread of a multicore system. There have been tests to enable the additional cores and threads, but this needs some work with the kernel before we get it working.

Menuet has Ring 3 support. What exactly is running in Ring 3? Just applications?

Ville: Only applications are running in Ring 3. Kernel and drivers are running at Ring 0.

How do you debug when working on Menuet?

Madis: My personal favourite is QEMU, which runs MenuetOS nicely. For single applications there are some approaches. One is IPC, in which case the other program listens to the debug-strings or numbers sent. Another possibility is to halt the program's execution (jmp $) at the interested spot and use QEMU to inspect the registers and memory at that time.

Tags software developmentoperating systems

Keep up with the latest tech news, reviews and previews by subscribing to the Good Gear Guide newsletter.
Rohan Pearce

Rohan Pearce

Good Gear Guide




Good read

Thanks for the interview, nice OS.



Amazing. Extremely impressive what some people can do.



Did you guys ever see the QNX demo?

It came out back in the Pentium days. It fit on a floppy; had web, mail, and IRC clients; it had a PPP dial; and it made my 486 run faster than my Quadra. Not sure if it's available any more.



Marvelous!! but needs posix support to survive beyond toy state

Hats off to you guys - very well done but without posix layer (or even a plan for it) this will run out of steam and that would be a sad day considering the excellent work.



POSIX not needed at all

posix is an api intended to talk to the Unix kernel and do things the Unix way. Why hamstring this exciting new project with that bloated pile of baggage when the goal is to make smaller, less resource hungry platform?



Is assembly only available for ONE processor architecture?

One might assume that the processors that this OS is written for are x86 32 bit and 64 bit, but notice how it's not mentioned ONCE in the article.

There are other processors, and people do code in assembly for them, too.

John Klos




>One might assume that the processors that this OS is >written for are x86 32 bit and 64 bit, but notice how it's >not mentioned ONCE in the article.

It is mentioned in the article, I suggest you read it again.




hey, you rock! :)
so what new features are planned for the 1.0 release? any chance to be compatible with windows drivers :)?




comments are poop



It would be enormously advantageous.

There's a huge amount of existing software that makes use of POSIX. Just because the basic core of the operating system may be written entirely in assembly, doesn't mean it should be shoved into the corner of having everything available to it being written only in assembly. A noted embedded real-time linux kernel, which is heavily based on a hardware abstraction layer with direct assembly interfaces implementing multi-level task switching (and so on), eCos, provides a POSIX abstraction layer. As an embedded software developer, this made it an extremely appealing, light-weight, customizable, kernel, that I could readily port a huge amount of already written Unix compatible software to.



Give menuet a try!

I played with menuet a few years ago and was really impressed. Would rock on my netbook if they had a driver for my wireless.

QNX is still developed and popular. You can get a free non-comercial version at qnx.com or go for the open source version at openqnx.com



Salute the Inspiration

Salute the team of developers that make this operating system.
I worked with almost every version of MS windows
including various Linux Distro's and Unix varient

I prefer only BSD / Redhat Linux
But this seems promising for me to check out the issues with the said operating system and possiblities.

Once again keep the good work. and give developers the vision to build speedy code.

Some body



The original premise of Linux revisited!

Back in 1990/91 when Linux first started coming out, Linus Torvald's original premise was to create an OS that entirely supported the assembly language substructure of x86 Protected Mode, unlike any OS that existed before that or since. Once the Linux 1.x kernel came out, they quickly abandoned the entire assembly language idea, which I thought was a shame. Though going towards C/C++ made it more portable, and increased its commercial appeal but it did bloat out like a pregnant mom in her third trimester. I think the developers of MenuetOS understand how open source development creates this flight towards lowest-common-denominator mentality, and have done the right thing to not go fully towards open-source. This way if Menuet develops more fully within the assembly framework, it will become less likely for open-source authors to come in and ruin it by translating it to an inefficient portable language. They can release the 64-bit version as open-source later when it's got more momentum on its own. Afterall, open-source itself doesn't have a problem with assembly language, it's just open-source developers that have a problem.



Good post overall. Enjoyed reading it. <a rel="follow" href="http://www.clickingsubmit.info">William</a>



I am very impressed especialy with the GUI in such a small size. It's looks seem even better than puppy linux or dsl



It's amazing what you can do with 759KB (zipped)!
I hope this project stays alive - it currently lacks polish but the time to boot a GUI is incredible.



Well DUH. Up until about 1998 (recent, in my memory), ALL operating systems were written in assembly. It went without saying that high-level languages were too slow and inefficient for the job. Subsequent code bloat proves this to be true; it's only the enormous increases in processor speeds that have allowed y'all the illusion that software hasn't slowed down by about 1000% in the intervening years. I cry to think how fast today's computers would run, say, OpenVMS, if only the processor architectures could handle the interrupt structure, response-time guarantees, etc. etc. And OpenVMS -- known originally as VAX/VMS -- was written in the 1970s. I've been sneering at "modern" OS architecture since at least 1988, myself...

Oh, and for what it's worth, QNX still exists, though it's not clear whether that boot-floppy demo, per se, is still available. My guess would be "probably not," but, as it happens, I am in a position to ASK. I was *just* talking to someone the other day who was with QNX when that demo came out.




"Well DUH" yourself. UNIX-style OSes have been written in C since the early 70s.




@Andrew and Chris

Unix-schumix, the first OSes written in High Level Languages appeared in the 1960s: Burroughs' MCP and the great, never-bettered, sadly-missed Multics, the greatest OS in history (written in PL/1).

Bloat is *not* a necessary concomitant of using HLLs.

While I teach an assembler/architecture course, I wouldn't even contemplate writing an OS in assembler (I did once write a timesharing executive in assembler, 30+ years ago).

The arguments against are even stronger today, with our aster hardware, than they were 30-40 years ago. Development times, maintainability, etc, etc.

And, of course, portability. If Linus T had implement the whole of the linux kernel in assembler, we'd be lucky to have it on one other architecture by now.

"Those who cannot remember the past are condemned to repeat it"
George Santayana

umair jalal


HY........ every one...im having a presentation on MENEUTOS...nd i cannot find the Process state model, PCB, Process creation and Inter process communication of MENEUTOS....can any one tell me about them.

Kelly Smith


It is fantastic that an OS has been written in - mainly Assembly. What make me concerned is that the 'new' version 64 bit is 'closed source'. I don't have any interest in closed source software. In fact I would prefer to pay for it than to download some dodgy 'free' files from the net. The closed source nature of this project should set off alarm bells for many many people out there.

I won't touch this with a barge pole.

Comments are now closed.

Most Popular Reviews

Follow Us

Best Deals on GoodGearGuide


Latest News Articles


GGG Evaluation Team

Kathy Cassidy


First impression on unpacking the Q702 test unit was the solid feel and clean, minimalist styling.

Anthony Grifoni


For work use, Microsoft Word and Excel programs pre-installed on the device are adequate for preparing short documents.

Steph Mundell


The Fujitsu LifeBook UH574 allowed for great mobility without being obnoxiously heavy or clunky. Its twelve hours of battery life did not disappoint.

Andrew Mitsi


The screen was particularly good. It is bright and visible from most angles, however heat is an issue, particularly around the Windows button on the front, and on the back where the battery housing is located.

Simon Harriott


My first impression after unboxing the Q702 is that it is a nice looking unit. Styling is somewhat minimalist but very effective. The tablet part, once detached, has a nice weight, and no buttons or switches are located in awkward or intrusive positions.

Latest Jobs


Don’t have an account? Sign up here

Don't have an account? Sign up now

Forgot password?