Search:

Obviously I was being stupid again, it requires looping which we can accomplish:


[BITS 16]
[ORG 0]
;16-bit real mode

jmp start

msg db 'Booting a shitty program',13,10,0

No, they aren't, the BIOS simply looks for a valid bootsector on the disk which is in the process of being booted. That bootsector contains the code needed to continue booting the operating system.
...

That's what I did, rename it to command.com but it said it wasn't a command interpretenter.

You say

I know, but how does the computer know how to boot dos? (from a floppy that is).


huh?...

Yes, the virus example is good.
I firstly only want to display a simple string to make sure it actually works, then write a command interpretenter. But that's not the problem, I should technically...

Lol, I don't want to write some command line interpretenter that runs in dos or something.
The point is simply knowing how to write the most basic operating system.
My problem is simply not knowing...

Obviously, it thinks the command.com is corrupt here as I replaced it.

I don't want to do anything specific, I simply want to run a program without an operating system (making it an operating...

How does it know how to execute that command interpretenter then?
The thing I tried the second time is defintly not what I want to try.

I actually want to write an OS (well, actually a program...

Yes, I have tried (win98), that's were it hanged.
I tried something else now, I used 'sys' to make a bootdisk and replaced command.com with a copy of my own program (hello world). Now it booted but...

Why should it matter what OS I'm using?
I don't want to create a bootable floppy with dos on it.
I want to make a bootable floppy with my own program (call it operating system if you like).

I am trying to boot my own program from a floppy (like a MS-DOS bootdisk) so I write a little x86 assembly program (a .com file) and use a program rawrite to write it to a floppy.
I supposed this...