Scratch

32 bit. 32 or 64 bit.
The backgrounds and cursors don't come with the computer, those are files that are customisable by the user.

ZeroLuck wrote:

That's why there's the power of Scratch!

You can't write an OS in Scratch.

Making an OS doesn't mean creating some cursors/backgrounds and managing windows...
You have to schedule tasks and threads, writing (very much) drivers, manage the memory, and much more. You can't even use the standard C-Lib...

(I know that because I wrote a little OS myself)

I don't mean IN scratch, I mean any scratchers are welcome to help. I mean some scratchers code, some make graphics...

I'll go research for an hour, code for 2 hours, come back and research for a month, code for two months, come back and research for 5 years, and code till i'm 21. 

Ok.
I'm not going to help but I'll clear a few things up.
There are different kinds of assembly (x86 assembly, mac assembly, ARM assembly, 64bit assembly...)

When I get my RPi, I'm going to learn ARM assembly.

Assembly is hard. If you've never used anything other than Scratch, don't use assembly.

Graphics are hard in assembly. If you must make an operating system, make a DOS. Every OS with a GUI started as a DOS.

Now, the MOST important thing:

PROGRAMMING IS NOT LIKE SCRATCH.

With scratch, you start with graphics.

With REAL PROGRAMMING you start with basic code. With an OS, it would be the bootloader.

Don't do graphics until the VERY END.

Behind every GUI OS is a command line. The buttons are just triggers for commands. Start with a DOS. Then make the window manager.

Also, (Just making sure you know this), the rules DON'T bend for you. You can't ignore something and do it your own way which you've never tried before and expect it to work like in Scratch where everything is simple and easy and there are no typos.

Yet again, if you don't know Assembly or C, START WITH BASIC STUFF LIKE "HELLO WORLD."

You are not an exception, and you will not make an OS without prior knowledge of a programming language like C or Assembly.

That said, if you DO know enough C or Assembly, good for you. However, I get the feeling you haven't learnt much. You can't build an OS off a few tutorials.

Someone made a computer in The Powder Toy and I think it uses assembly although I haven't really done anything except use the example program. 

Dinoclor wrote:

Ok.
I'm not going to help but I'll clear a few things up.
There are different kinds of assembly (x86 assembly, mac assembly, ARM assembly, 64bit assembly...)

When I get my RPi, I'm going to learn ARM assembly.

Assembly is hard. If you've never used anything other than Scratch, don't use assembly.

Graphics are hard in assembly. If you must make an operating system, make a DOS. Every OS with a GUI started as a DOS.

Now, the MOST important thing:

PROGRAMMING IS NOT LIKE SCRATCH.

With scratch, you start with graphics.

With REAL PROGRAMMING you start with basic code. With an OS, it would be the bootloader.

Don't do graphics until the VERY END.

Behind every GUI OS is a command line. The buttons are just triggers for commands. Start with a DOS. Then make the window manager.

Also, (Just making sure you know this), the rules DON'T bend for you. You can't ignore something and do it your own way which you've never tried before and expect it to work like in Scratch where everything is simple and easy and there are no typos.

Yet again, if you don't know Assembly or C, START WITH BASIC STUFF LIKE "HELLO WORLD."

You are not an exception, and you will not make an OS without prior knowledge of a programming language like C or Assembly.

That said, if you DO know enough C or Assembly, good for you. However, I get the feeling you haven't learnt much. You can't build an OS off a few tutorials.

Thanks. I knew some of these. Btw: That's not a few 

echs wrote:

I hate to say this, but it's nigh impossible to make a full operating system by yourself, let alone as a minor.

But don't let me discourage you. The small attempts you make now will give you a better background for computer programming in the future.

Thanks! Whoever can answer this question gets TEN free mp3 files(please help): How do you display text in assembly?

poemon1 wrote:

How do you display text in assembly?

That's the point!
If you don't have an OS because you are the OS you have to query the video-card.
And this is very hard because there are thousands of different cards.
If you are in 16-bit Real-Mode you can use the BIOS-functions to write 8x8 pixel letters on the screen.( But you can't write a real OS in 16-bit Real-Mode so you have to use the 32 Protected-Mode (or 64 bit Long-Mode). And then you can't use the BIOS-functions anymore... )

In Real-Mode you can do that: (using the BIOS-functions)

print_str:
    push ebp
    mov ebp, esp
    
    mov eax, [ebp + 8]

    mov esi, eax
    mov ah, 0x0E 
    .loop:   
        lodsb
        test al, al 
        jz .done 
        int 0x10 
        jmp .loop
    .done:
        pop ebp
        pop eax
        ret

Last edited by ZeroLuck (2012-04-12 14:45:14)

poemon1 wrote:

ZeroLuck wrote:

poemon1 wrote:

How do you display text in assembly?

That's the point!
If you don't have an OS because you are the OS you have to query the video-card.
And this is very hard because there are thousands of different cards.
If you are in 16-bit Real-Mode you can use the BIOS-functions to write 8x8 pixel letters on the screen.( But you can't write a real OS in 16-bit Real-Mode so you have to use the 32 Protected-Mode (or 64 bit Long-Mode). And then you can't use the BIOS-functions anymore... )

In Real-Mode you can do that: (using the BIOS-functions)

Code:

print_str:
    push ebp
    mov ebp, esp
    
    mov eax, [ebp + 8]

    mov esi, eax
    mov ah, 0x0E 
    .loop:   
        lodsb
        test al, al 
        jz .done 
        int 0x10 
        jmp .loop
    .done:
        pop ebp
        pop eax
        ret

I'll Test It!

poemon1 wrote:

  http://i42.tinypic.com/33nkfut.jpg

Are you using the GNU-Assembler?
The code is X86 NASM.
The code works just in Real-Mode. (usually in the boot-code).
If you want to write in DOS-Windows to the screen you have to call a syscall.

org 100h
 start:
  mov dx, hello_world
  mov ah, 09h
  int 21h
  mov al, 0
  mov ah, 4Ch
  int 21h
 section .data
  hello_world: db 'hello, world', 13, 10, '$'

If you compile this with nasm.exe you will get a ".com" file.
You can execute it in the Windows-DOS prompt.

poopo wrote:

If you don't already know assembly I doubt you'll be able to make one. Make it in C instead.

You cannot. You must have Assembly somewhere in the code.

Maybe the osDev wiki can help?

Also, it takes years just to make a non-gui version. Longer if you are making your own GUI.

slinger wrote:

Haha, it depends on what you want to do 
It doesn't take years to make an os that turns on then prints "Press enter to shut down" to the screen ;P

That can take anything from a day to a week. Depending on your skill level.

You may be better off modding ReactOS or something.