what to do now
Re:what to do now
Well, I have no idea what you have just asked...is it "What should I do now?" or "Can anyone give me a project I can work on?" is one of those right?
Re:what to do now
Well, I see you're from Portugal.
I suggest you retype your message in Portugese and leave the translation to us, or go to http://www.altavista.com and translate it.
I suggest you retype your message in Portugese and leave the translation to us, or go to http://www.altavista.com and translate it.
- Pype.Clicker
- Member
- Posts: 5964
- Joined: Wed Oct 18, 2006 2:31 am
- Location: In a galaxy, far, far away
- Contact:
Re:what to do now
well, maybe you might wish to let your kernel support multiasking, or implement disk access ... or modules loading & management ...
Re:what to do now
How can i do that?Pype.Clicker wrote: well, maybe you might wish to let your kernel support multiasking, or implement disk access ... or modules loading & management ...
- Pype.Clicker
- Member
- Posts: 5964
- Joined: Wed Oct 18, 2006 2:31 am
- Location: In a galaxy, far, far away
- Contact:
Re:what to do now
with the usual development cycle : google for tutorial, grab some books, upload documentation to your brain, analyze, design, test, design again, implement ...
multitasking: learn about what it is (process, threads, etc.), how it roughly works in Windows or Posix threads or Unix processes. Learn about scheduler algorithms, learn about task switching techniques (intel TSS, software stack-switching, etc.)
disk access: learn about the IDE interface, what is a sector, a cylinder, etc. Learn how a trivial filesystem (FAT) is made and how it works. try to see how you could improve its performance or possibilities, then give yourself a try through more evoluted FS like EXT2 or NTFS ...
modules: learn how modules work in Linux, and how DLL works under windows. Then read binary executable formats specs and try to understand how they work. Finally, see how you could load some code from a file and make it be a part of your kernel ...
multitasking: learn about what it is (process, threads, etc.), how it roughly works in Windows or Posix threads or Unix processes. Learn about scheduler algorithms, learn about task switching techniques (intel TSS, software stack-switching, etc.)
disk access: learn about the IDE interface, what is a sector, a cylinder, etc. Learn how a trivial filesystem (FAT) is made and how it works. try to see how you could improve its performance or possibilities, then give yourself a try through more evoluted FS like EXT2 or NTFS ...
modules: learn how modules work in Linux, and how DLL works under windows. Then read binary executable formats specs and try to understand how they work. Finally, see how you could load some code from a file and make it be a part of your kernel ...
-
- Member
- Posts: 1600
- Joined: Wed Oct 18, 2006 11:59 am
- Location: Vienna/Austria
- Contact:
Re:what to do now
i'd also suggest to learn when and how to ask questions .. *gg* there is an huge link about this topic on the very head of the main list of threadses of this forum.
Mr. Nuno You are a daring one to try to meddle with the affairs of wizardses *gg* In the early stage of development and knowledge that I have reached, I am glad not to meet their harsh and sudden anger. *gg*
Stay safe gosh
Mr. Nuno You are a daring one to try to meddle with the affairs of wizardses *gg* In the early stage of development and knowledge that I have reached, I am glad not to meet their harsh and sudden anger. *gg*
Stay safe gosh
... the osdever formerly known as beyond infinity ...
BlueillusionOS iso image
BlueillusionOS iso image