In that case talk of switching between 32-bit and 16-bit, and Virtual 8086 mode, is irrelevant isn't it?omarrx024 wrote:Because he wants a DOS-like OS, which probably means it would be 16-bit.iansjack wrote:Rather than all the kludging with 16-bit and/or Virtual 8086 mode, why not just write a proper disk driver?
Weevil (planned)
Re: Weevil (planned)
- BrightLight
- Member
- Posts: 901
- Joined: Sat Dec 27, 2014 9:11 am
- Location: Maadi, Cairo, Egypt
- Contact:
Re: Weevil (planned)
Yes, but a 32-bit DOS would be pretty cool in my opinion. It's also odd he's using GRUB to boot a 16-bit kernel.iansjack wrote:In that case talk of switching between 32-bit and 16-bit, and Virtual 8086 mode, is irrelevant isn't it?omarrx024 wrote:Because he wants a DOS-like OS, which probably means it would be 16-bit.iansjack wrote:Rather than all the kludging with 16-bit and/or Virtual 8086 mode, why not just write a proper disk driver?
You know your OS is advanced when you stop using the Intel programming guide as a reference.
Re: Weevil (planned)
Ahem, I was following the Bare Bones tutorial (found on the wiki) when I got the idea of writing something like MS DOS. So I didn't really care about the bootloader, but went straight into OS development.omarrx024 wrote:It's also odd he's using GRUB to boot a 16-bit kernel.
P. S. Is there something wrong with using GRUB for this task? Or is it better to write my own bootloader? (I'd have to somehow parse ELF format and load it into the memory )
My own MS-DOS like OS
https://github.com/Vik2015/weevil/
https://github.com/Vik2015/weevil/
http://bestsoft.azurewebsites.net/ wrote: With Bestsoft Space you can write operating system eaven if it your first software.
Re: Weevil (planned)
In which case we're back to "write a proper driver".omarrx024 wrote: Yes, but a 32-bit DOS would be pretty cool in my opinion.
Re: Weevil (planned)
As I said I want to try to use no (or minimal) BIOS calls . Thought that means implementing keyboard driver, etc. Again, that's the fun!iansjack wrote:In which case we're back to "write a proper driver".omarrx024 wrote: Yes, but a 32-bit DOS would be pretty cool in my opinion.
My own MS-DOS like OS
https://github.com/Vik2015/weevil/
https://github.com/Vik2015/weevil/
http://bestsoft.azurewebsites.net/ wrote: With Bestsoft Space you can write operating system eaven if it your first software.
Re: Weevil (planned)
That doesn't make a lot of sense. Why would you restrict yourself to Real Mode if you're not even using the BIOS, which is probably the only thing in RM that could possibly be seen as an advantage?omarrx024 wrote:I am also gonna *try* to write it using only real mode (64kb memory should be enough I guess?) but without using any BIOS calls (or just minimal amount of them).
And being 16 bit isn't the defining property of DOS, in my opinion. You can probably still be quite DOS-like in Protected Mode. You wouldn't make any use of the protection features, of course, but having a much larger address space would definitely be worth it.
Re: Weevil (planned)
Hmm. I guess you are right. Going to Protected Mode isn't going to hurt . Gonna implement it after I finish reading meaty skele.Kevin wrote:That doesn't make a lot of sense. Why would you restrict yourself to Real Mode if you're not even using the BIOS, which is probably the only thing in RM that could possibly be seen as an advantage?omarrx024 wrote:I am also gonna *try* to write it using only real mode (64kb memory should be enough I guess?) but without using any BIOS calls (or just minimal amount of them).
And being 16 bit isn't the defining property of DOS, in my opinion. You can probably still be quite DOS-like in Protected Mode. You wouldn't make any use of the protection features, of course, but having a much larger address space would definitely be worth it.
My own MS-DOS like OS
https://github.com/Vik2015/weevil/
https://github.com/Vik2015/weevil/
http://bestsoft.azurewebsites.net/ wrote: With Bestsoft Space you can write operating system eaven if it your first software.
Re: Weevil (planned)
Multiboot kernels are always started in Protected Mode by the bootloader. So unless you switch back to Real Mode (and I don't see any code to do that in your repository), you're automatically in PM.
Re: Weevil (planned)
Oh. That's why QEMU was going crazy when I tried to use interruptsKevin wrote:Multiboot kernels are always started in Protected Mode by the bootloader. So unless you switch back to Real Mode (and I don't see any code to do that in your repository), you're automatically in PM.
I guess all that stuff is on the wiki... Gonna read more.
P. S. @Sortie, thanks for the tutorial! It really helped alot in organizing my project and developing some kind of libc for my kernel!
My own MS-DOS like OS
https://github.com/Vik2015/weevil/
https://github.com/Vik2015/weevil/
http://bestsoft.azurewebsites.net/ wrote: With Bestsoft Space you can write operating system eaven if it your first software.
Re: Weevil (planned)
Storing the address of the repo in your signature is a good idea, what do you think?Vik2015 wrote:Gitrepo is here https://github.com/Vik2015/weevil/.
User Control Panel -> Profile -> Edit signature
Re: Weevil (planned)
Indeed. Added it to the signatureExeTwezz wrote:Storing the address of the repo in your signature is a good idea, what do you think?Vik2015 wrote:Gitrepo is here https://github.com/Vik2015/weevil/.
User Control Panel -> Profile -> Edit signature
My own MS-DOS like OS
https://github.com/Vik2015/weevil/
https://github.com/Vik2015/weevil/
http://bestsoft.azurewebsites.net/ wrote: With Bestsoft Space you can write operating system eaven if it your first software.