Is your OS self-hosting? Or is it one of your goals?
When the FAT12 driver is done, i will try to port FASM under PortixOS and make at least some programming environment

And when IRQs are done too - well, I will make some applications for real mode kernel and after all that I will try to switch under "blessed Protected Mode" and make some kernel in C++.
inflater


And when IRQs are done too - well, I will make some applications for real mode kernel and after all that I will try to switch under "blessed Protected Mode" and make some kernel in C++.

inflater
My web site: http://inflater.wz.cz (Slovak)
Derrick operating system: http://derrick.xf.cz (Slovak and English
)
Derrick operating system: http://derrick.xf.cz (Slovak and English

Yes, that is a goal of mine, but not until after I have it to a point where it is as easy to program in as my current setup is. No point in self hosting with a crappy line editor that takes me 5x as long to write programs, and even longer to reboot and test, when I can just run bochs to test changes and get it right before attempting the real machine. Also, if I can type faster here than some crappy editor (like, cut/paste, very simple to see my project files with the nice expandable tree's, etc), why would I want to self host? I will start porting compilers and editors over to my OS once I get my GUI finished up, and at least some version of text editors running within my GUI. I will even port bochs or Open86 (if it supports 32-bit mode and other stuff by then?), that way I can test my OS within my OS, but that is a far time off into the future.
@Ready4Dis, i disagree with you, to me thats a copout, running something in bochs is like running a windows program in wine. Do not fall into the trap, YOU ARE CODING A OS, not a user program, it needs to be tested on a real PC.
You need to use it, from the beginning as a user would.
The gui stuff is just eyecandy, you can convert a good written editor from CLI to GUI in less than a week.
Also why do you need to do all that:
Like this: http://jas2o.forthworks.com/dexforum/in ... attach=135
You need to use it, from the beginning as a user would.
The gui stuff is just eyecandy, you can convert a good written editor from CLI to GUI in less than a week.
Also why do you need to do all that:
to test your program, when you can write and assemble and run from you OS's IDEwrite programs, and even longer to reboot and test
Like this: http://jas2o.forthworks.com/dexforum/in ... attach=135
Heh, well, I am still working on kernel mode stuff, so it would require a reboot, or at least a reload of the kernel and/or modules. Once I get to that point, I will start working on self hosting. I do want to self host, but don't see a reason to until it is actually useableDex wrote:@Ready4Dis, i disagree with you, to me thats a copout, running something in bochs is like running a windows program in wine. Do not fall into the trap, YOU ARE CODING A OS, not a user program, it needs to be tested on a real PC.
You need to use it, from the beginning as a user would.
The gui stuff is just eyecandy, you can convert a good written editor from CLI to GUI in less than a week.
Also why do you need to do all that:to test your program, when you can write and assemble and run from you OS's IDEwrite programs, and even longer to reboot and test
Like this: http://jas2o.forthworks.com/dexforum/in ... attach=135

If it's useable, then it should be self-hostingEdwin wrote:I don't think it should be a goal for my OS to be self-hosting, although it would be nice to be self-hosting. My main goal is to make a usable OS.


lol, this is probably truespix wrote:That depends on the type of OS it is. I doubt the guys at Palm develop their OS with s stylus.If it's useable, then it should be self-hosting


DexOS was designed to be one of thoughs special cases, (as in it was designed to run 1 program, all day long eg: a dedicated m3p player, robotic, etc).
So the original idea was to code for it on a desktop like windows/linux.
But i had a lot of people saying, i do not want to keep having to reboot to test programs and as its a good demo of what the OS can do, i added it.
So the original idea was to code for it on a desktop like windows/linux.
But i had a lot of people saying, i do not want to keep having to reboot to test programs and as its a good demo of what the OS can do, i added it.
Heh, see, told you it gets tiring rebooting to test programsDex wrote:DexOS was designed to be one of thoughs special cases, (as in it was designed to run 1 program, all day long eg: a dedicated m3p player, robotic, etc).
So the original idea was to code for it on a desktop like windows/linux.
But i had a lot of people saying, i do not want to keep having to reboot to test programs and as its a good demo of what the OS can do, i added it.


Reincarnation of a old topic:
It is now

(Actually PortixOS doesn't operate in [un]real mode from now.)
Thanks to:
myself (programming, testing)
DexOS Team (for releasing source code of DexOS [No, PortixOS and DexOS aren't clones and they are incompatible between each other
])
inflater
It is now

(Actually PortixOS doesn't operate in [un]real mode from now.)
Thanks to:
myself (programming, testing)
DexOS Team (for releasing source code of DexOS [No, PortixOS and DexOS aren't clones and they are incompatible between each other

inflater
My web site: http://inflater.wz.cz (Slovak)
Derrick operating system: http://derrick.xf.cz (Slovak and English
)
Derrick operating system: http://derrick.xf.cz (Slovak and English
