Hi,
I've currently not a question directy about os
development, but what do you use for it?
Which compiler, os, ides?
How do you test your os?
Thanks in advance,
The Legend
OS Development Environment?
RE:OS Development Environment?
>On 2002-01-31 13:45:52, The Legend wrote:
>Hi,
>
>I've currently not a question directy about os
>development, but what do you use for it?
>
>Which compiler, os, ides?
>How do you test your os?
>
>Thanks in advance,
>The Legend
Sorry, I just wanted back to the index and
the board creates another thread ...
The Legend
>Hi,
>
>I've currently not a question directy about os
>development, but what do you use for it?
>
>Which compiler, os, ides?
>How do you test your os?
>
>Thanks in advance,
>The Legend
Sorry, I just wanted back to the index and
the board creates another thread ...
The Legend
RE:OS Development Environment?
>On 2002-01-31 13:47:44, Sorry wrote:
>>On 2002-01-31 13:45:52, The Legend wrote:
>>Hi,
>>
>>I've currently not a question directy about os
>>development, but what do you use for it?
>>
>>Which compiler, os, ides?
>>How do you test your os?
NASM (http://www.cryogen.com/Nasm) is a good,
free assembler. It doesn't really matter which
OS you use to develop in, because you're making
your own to use anyway, and there are lots of
tools for all of them (the common OSes, I mean).
There are different ways to test your OS. If
you are making a bootloader, you should use
RAWRITE or PARTCOPY to write your code to a
disk, then boot off of that. If you don't have
a bootloader, download LOADER.COM in the developer
guides section of this site and use that to
load your code.
>Sorry, I just wanted back to the index and
>the board creates another thread ...
N/p, I've done that too... Hope this helps!
>>On 2002-01-31 13:45:52, The Legend wrote:
>>Hi,
>>
>>I've currently not a question directy about os
>>development, but what do you use for it?
>>
>>Which compiler, os, ides?
>>How do you test your os?
NASM (http://www.cryogen.com/Nasm) is a good,
free assembler. It doesn't really matter which
OS you use to develop in, because you're making
your own to use anyway, and there are lots of
tools for all of them (the common OSes, I mean).
There are different ways to test your OS. If
you are making a bootloader, you should use
RAWRITE or PARTCOPY to write your code to a
disk, then boot off of that. If you don't have
a bootloader, download LOADER.COM in the developer
guides section of this site and use that to
load your code.
>Sorry, I just wanted back to the index and
>the board creates another thread ...
N/p, I've done that too... Hope this helps!
RE:OS Development Environment?
>On 2002-02-01 11:20:49, Khumba wrote:
>>On 2002-01-31 13:47:44, Sorry wrote:
>>>On 2002-01-31 13:45:52, The Legend wrote:
>>>Hi,
>>>
>>>I've currently not a question directy about os
>>>development, but what do you use for it?
>>>
>>>Which compiler, os, ides?
>>>How do you test your os?
>
>NASM (http://www.cryogen.com/Nasm) is a good,
>free assembler. It doesn't really matter which
>OS you use to develop in, because you're making
>your own to use anyway, and there are lots of
>tools for all of them (the common OSes, I mean).
>
>There are different ways to test your OS. If
>you are making a bootloader, you should use
>RAWRITE or PARTCOPY to write your code to a
>disk, then boot off of that. If you don't have
>a bootloader, download LOADER.COM in the developer
>guides section of this site and use that to
>load your code.
Personally I am trying to do a C or perhaps C++
Kernel, but this seems to limit me to gcc but
basically I miss a good GUI for it like VS6.
What about PC-Emulators?
>>On 2002-01-31 13:47:44, Sorry wrote:
>>>On 2002-01-31 13:45:52, The Legend wrote:
>>>Hi,
>>>
>>>I've currently not a question directy about os
>>>development, but what do you use for it?
>>>
>>>Which compiler, os, ides?
>>>How do you test your os?
>
>NASM (http://www.cryogen.com/Nasm) is a good,
>free assembler. It doesn't really matter which
>OS you use to develop in, because you're making
>your own to use anyway, and there are lots of
>tools for all of them (the common OSes, I mean).
>
>There are different ways to test your OS. If
>you are making a bootloader, you should use
>RAWRITE or PARTCOPY to write your code to a
>disk, then boot off of that. If you don't have
>a bootloader, download LOADER.COM in the developer
>guides section of this site and use that to
>load your code.
Personally I am trying to do a C or perhaps C++
Kernel, but this seems to limit me to gcc but
basically I miss a good GUI for it like VS6.
What about PC-Emulators?
RE:OS Development Environment?
>On 2002-01-31 13:47:44, Sorry wrote:
>>On 2002-01-31 13:45:52, The Legend wrote:
>>Hi,
>>
>>I've currently not a question directy about os
>>development, but what do you use for it?
>>
>>Which compiler, os, ides?
>>How do you test your os?
DJGPP and Nasm, it's also really helpfull if you have
a system that runs Dos or Win9x. When writing your
pmode code it's nice to have a real mode OS to use as
a loader.
>>Thanks in advance,
>>The Legend
>Sorry, I just wanted back to the index and
>the board creates another thread ...
I'm going to fix that really soon...
>>On 2002-01-31 13:45:52, The Legend wrote:
>>Hi,
>>
>>I've currently not a question directy about os
>>development, but what do you use for it?
>>
>>Which compiler, os, ides?
>>How do you test your os?
DJGPP and Nasm, it's also really helpfull if you have
a system that runs Dos or Win9x. When writing your
pmode code it's nice to have a real mode OS to use as
a loader.
>>Thanks in advance,
>>The Legend
>Sorry, I just wanted back to the index and
>the board creates another thread ...
I'm going to fix that really soon...
RE:OS Development Environment?
>On 2002-02-01 22:18:23, Chase wrote:
>>On 2002-01-31 13:47:44, Sorry wrote:
>>>On 2002-01-31 13:45:52, The Legend wrote:
For testing your OS you may use Bochs (bochs.sourceforge.com,
so you don't have to reboot your computer every time
you want to test your OS.
>>On 2002-01-31 13:47:44, Sorry wrote:
>>>On 2002-01-31 13:45:52, The Legend wrote:
For testing your OS you may use Bochs (bochs.sourceforge.com,
so you don't have to reboot your computer every time
you want to test your OS.