The Place to Start for Operating System Developers
https://f.osdev.org/
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
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
. Not like I can write a keyboard driver in my OS if one doesn't exist already. I am working on re-writing a lot of it, once I get my kernel where I want it, I will worry about self hosting. Self host now, find out I want major changes to my kernel later, need to re-compile all self-hosting tools again, and probably from another OS. I do use a real PC for testing, but there is no reason to do so if it crashes in bochs. Once it runs fine in bochs, then I write it to my HD and boot (I have a seperate partition just for my OS, and a custom MBR that allows me to choose a partition to boot that is only 512 bytes, and works with winxp and dos without issues, haven't tried linux but assume it will work the same).Nah, I wish, lol, not enough time to work on it though, once I get to a point where work on the actual kernel is done (well, not done, but functioning propely!) is when I will begin building tools for self hosting.Dex wrote:Sorry i thought this new kernel, was fever down the Dev path.
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.
. When I think about a useable OS, I think about an OS I can boot up, type some code, and make programs for, not something that requires me to boot into windows, link some specific lib's, compile, use another utility to copy files to the other Os's partition, reboot into that OS and test my app 
.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
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
. My OS will be multi-platform, and the pocket pc is one of my targets, I plan on being able to compile for my pocket pc from my OS on a PC, but I can definitely see why someone would not if it's a limited platform, but most people on here are developing for PC platforms primarily. Not all OS's need to be self hosting, for example, if you're writing a gaming OS, one wouldn't expect tools to be part of the OS, since the OS is mostly just a hardware abstraction layer, and the dev tools would more than likely be for linux or windows, etc. However, my dev tools will be compileable for my OS, and since my pocket pc will have a libc, there would be no reason why I couldn't compile the compiler for the pocket pc and have it run and compile stuff on the pocket pc, who knows, maybe someone wants to distribute source code rather than executeables, that way they could compile it on the pocket pc and a regular pc, etc without having to compile for each platform themselves, just provide the sources, and let the user compile it to their platform (would work really good if the compiler flags were set depending on CPU as well, so one could compile for a mmx, sse, sse2, etc or use regular instructions if they aren't available for example). All in all, you are correct, I was thinking in terms of an x86, but even then it's not 100% true, there are special cases (as with everything really), but in the majority of the cases, I would think someone would want their OS self hosted if they plan on it being 'useable', unless it's one of the aforementioned special cases .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.
. Of course, there are tons of ways to do stuff without self hosting, you could have your OS connected to a network or serial or parallel port, and upload/run the programs as you are writing them, so you won't have to reboot or copy a bunch of stuff around, or worry about file systems. As stated, there are special cases were it probably won't be worth it to self-host (for example, a console game system, most games are written on the PC platform and uplaod the data to the console for testing). Something like a palm or pocket pc, I would develop on windows/linux and use an emulator for testing until it was functioning properly, then install it on an actual device to verify operation, it'd be a pain to type code with a stylus .
])