OSDev.org

I would love to enter.

Anyone else?

EDIT: or spice it up? 16bit realmode OS?

Nobody stops you from starting one.

Right you are.

So be it.

Looking for interest: which is preferred?

512b os challenge?

Or

Full blown 16bit real mode os?

Or

Enter idea here?

And it should support full HTML5.

OSwhatever wrote:And it should support full HTML5.

funny guy =]

I guess it depends on how long you want it to run for. If you want it to be a 2 week project, I would say 512 bytes. If you want 2 months, a real-mode OS would be cool, but what use would it serve?

Hi,

Ready4Dis wrote:..., but what use would it serve?

I can think of many.

• Could be released into public domain for newcomers to study and see how not to do things.
• Could give the winner some money - so that means competition (fun!).
• Could perhaps turn into something useful, some great idea or something.
• For the beginners, they could learn a lot.

Regards,
Shikhin

I'd say, make up some rules. If I've got time, I'll enter.

It could be a C64 look/act alike OS in 512 bytes.

GAT wrote:It could be a C64 look/act alike OS in 512 bytes.

That's so cool idea, that I've created a first draft in 30 minutes. So, here you are
Only look and feel for now, but if we are allowed to load 64k this could actually do something really funny Files:
c64in512.asm - source in fasm dialect
stage1.bin - precompiled binary
bochsrc - config file for bochs
Makefile - type "make" to compile, and "make test" to run in bochs

Edit: Oh, and I don't want to be rude with windows people:

I like it!
Maybe you could strip down the BASIC interpreter from mike OS and use it to actually run BASIC software!
(btw, it works on my 386 testbed fine.)

I will create a new topic when it's time to open it up, will just flesh out the specifics here.

So, I'm thinking we could do an extended time contest (2mos?) for a 16 bit real mode os. Since I have done work on MikeOS, and am familiar with it, I am going to base some of the rules around it. (As I think it's a sane way to play in 16 bit RM world)

So, rule the first!:

You must live within a single segment in 16bit real mode. How you do it? I don't care. MikeOS' Memory Map for reference:

0 - 24575 (0h - 5FFFh): 24k Kernel Executable Code

24576 - 32767 (6000h - 7FFFh): 8k Kernel Disk Operation Buffer

32768 - 65535 (8000h - FFFFh): 32k Space for external programs.

Rule the second:

It must boot via Bochs (since these are BIOS drivers, should not be an issue.)

Rule the Third:

It must be open source. Source must be provided. I want beginners to be able to learn from this.

Rule the Fourth:

Use of pre-existing code is OK, as long as the license allows for it, and you abide by the stipulations of any such licenses (provide copyright notices, cite in submission what its based on etc) - It must be somewhat original though. a copy of MikeOS with a couple new user apps will not suffice.

--

Thinking of more at the moment -- Any to add? (aside from obviously the end date, which im deciding on)

If anyone wants to help out, please let me know.

As far as prizes go, not sure, but will see what we can figure out.

Can we use pre-existing code?

I would say yes, as long as we don't get MikeOS back bit for bit, I don't see why not. It IS open source. I would stipulate that all uses of code be cited and copyright notices kept with the finished product, in keeping with the respective license agreements.

I see a bunch of rules but how will this be judged?