What do you prefer???
Ok, vote, this is just an opinion, I want to know what everyone wants :)

I voted for a rewrite, as i know many good ASM programmers take a look at menuet kernel and run a mile, these are good programmers. The basic of menuet are great, but it let down by, not bad coding, but code that as been patched, as things have been adder-ed over the years, so it not a total rewrite, but more a reorganisation of the code. And to simplify thingsa bit. PS: May some one should ask the Russians, if they mind, as they have been treated pretty badly by some parts of the the menuet32 community, eg: they did 90% of the coding work , but were never allowed to be in charge.

....i voted for KolibriOS ... as many have said, KolibriOS is M32 but much more improved ... why rewriting? ... well ... we have reasons ... but ... WHO WILL DO IT? 8)

Kolibri. Although i prefer Menuet, there is no denying that Kolibri is currently more advanced.

Ok, I'm one of the guys against the rewrite, but if the comunity wants to rewritte most of the code then I will support it anyway, of course. But for example, tell me about anyone who is interested on that job...

hey ... why not doing a new OS ? ... :P

Its simple ASM programmer need a desktop OS, menuet OS was as far as i was concerned that OS, this is no longer the case. It looks like most people want to go with KolibriOS, which is great. But i see this as negative, when your get knock down, it should make you stronger, more determine, to show the person who did, that you will show him. So maybe it time to build a ASM desktop OS :shock: . And yes it got to be a differant OS with the best bits of menuet, if not your going to get s**t down the road, as someone does not want menuet to survive.

I agree with Dex. First up I think after seeing both here and at the Russian meos forum a common view that a closer relationship is preferred, that what we do here is instead of continuing the Menuet32 theme, we instead rename this forum, to a name independent of any particular asm OS and support all efforts. Does that mean we need to reregister? no big deal if so. Set up a list of goals to aim for. It seems to me Kolibri should aim for a rewrite with new code solely for the purposes of releasing the ties to Menuet32 license, baggage etc. At this forum, our goals should include the bringing together of all asm OSes (there are several out there) as well as attracting people like Brendan from places like Mega Tokyo OS Development forum. It seems strange to argue about what's the most efficient way for task switching as maybe a small framework kernel should be developed as the official distro and if you can improve on task switching etc, great. In the mean time why not develop all the gui/file/network etc independent, that can drop into any kernel. Drawing code for instant doesn't need to know how the buffer was created, it just needs a buffer and screen dimensions to fill the buffer with magic pixels :) There are many things on the horizon, virtualisation, now even IO virtualisation - http://devforums.amd.com/lofiversion/index.php/t470.html Looks like 64 bit, multicore, IO virtualisation etc etc development is on the way for all of us, so lets work towards it. So how about it, lets start talking about the big picture, support all efforts. Who agrees in a name change and a distancing from any one project in favour of support for all? BTW, Babelfish Russian to English translation of meos.sysbin.com forum - http://babelfish.altavista.com/babelfish/trurl_pagecontent?lp=ru_en&trurl=http%3a%2f%2fmeos.sysbin.com%2findex.php%3f Difficult but not impossible to get a vague understanding of what they are meaning. I extend a warm hand of friendship to all no matter what your first language is.

A name change is a must and the reason is this, the person who started menuet OS went open source, but this he thinks was a mistake, as he thinks that he can make some money out of this OS, but he can not make any money if it open source, so when 64bit came along, he saw this as a chance to re-code menuet and keep it closed source. But its nogood there being a open and closed source OS both called menuet. So he basically wants the name back. So if you keep the name you will find, more problems down the line. So i vote we make a OS called Menuet64, that is a recoding of menuet32 for 64bit cpu, fully open source. Just a joke :wink: .

Hello, I've never been one to talk about direction, but many points have been made that I agree with. I think that most of you can say without a doubt, that MenuetOS blew you away when you learnt that the entire system comprised of about ~150k of data. I was too and I still am. I agree with Dex about the rewrite and the rename. I only care about the vision of menuet. The Desktop in Assembly. I, over the holidays, have come to appreciate what was done and I studied what worked and what was confusing in many assembly operating systems. I started my own, for experimental and learning reasons, and respect what others have done. I voted for a rewrite. But I think that if it was to be undertaken, a solid model would have to be decided on. Advantages and Disadvantages weighed via polling (not forum polling, but me stating my choice, and just my choice polling). I've seen in other projects that heirachy kiils a project, so what to do there. Do we support old hardware? 386+ with 8 Mb of memory and a 1Mb SVGA video adaptor. Bleeding Edge only? Extensive use of SIMD extentions, Nvidia and ATI drivers, USB2.0. How many possible and committed developers are there? How many would be enough for anything to get done? I hope this is not the death of MenuetOS (or the paradigm behind it). Solidus.

Solidus117 your right, we both have seen many OS fail because no one can agree about a direction, i think the best thing to do is let everyone have there say, but instead of arguing about which way is best, the people who can code like your self, should start to code it how you want it to be, may be some one else will go in a differant direction, but thats OK, as the one that does the best job and works best will win in the end. And that the one that will become the "new menuet". Let the code do the talking, too many projects are directed by people who can not code, the noncode say is important, but its the coders that have to do the work.

No doubt, rewrite from the scratch. Sorry guys, but MenuetOS has an absurdly bad design. Admit it: it's a shame of Ville and other contributors (among them me). Kolibri might be a bit better but definitely not good. As you may remember I suggested once that it would be well advised changing to C. Then I was put down... T.

ok, now you convinced me hehehe and I think that Dex opinion on the last post is completely right but it's the same old situation... we don't have anyone starting the code... and Ireally would like to know how to start and develop this kind of project, but I can't... obviously I don't have the knowledge, but also, I don't have the time

First we need to find out what people think was wrong (if any thing) with menuet, then we need to know what people thing we can do to fix it. This should take a week, than any coders who want to do a rewrite etc, should put forward what they are going to do ( a plan of action ). Form here small groups of people, will be formed who want to it a certan way. From here will come a team that gets the most and best job done. Eg: Theorizer, thinks rewriting it in C is a good idea, fine anyone who thinks the same can form a group and show the rest of us, how much better it would be. I think that menuet should only be coded in ASM, so will not join that group. These groups should not fight with each other, but let there code do the fighting.