•
•
•
•
What is DaniWeb IT Discussion Community?
You're currently browsing the C section within the Software Development category of DaniWeb, a massive community of 403,519 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 3,798 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.
Please support our C advertiser: Programming Forums
Views: 622 | Replies: 10
![]() |
•
•
Join Date: Oct 2006
Posts: 90
Reputation:
Rep Power: 2
Solved Threads: 1
Wow. It's kinda strange to even consider that I am taking part in the creation of an operating system... It really wasn't that long ago that I wasn't even capable of writing a functional program... I owe a good portion of my achievements to you posters here on DANIWEB (especially Ancient Dragon).
Now on to my question(s):
1) A couple of friends and I have taken on the challenge of creating our very own OS. I still have much to learn, so I get a little bit lost every now and then, but for the most part, I pull through. Our 'team leader' has assigned me the task of rewriting the standard c libraries, and I was wondering if this is really a necessary task (I plan on doing it either way, as it will be good practice). -- He has told me that the more important functions include memory, and output functions. What is your input on this matter?
2) Regarding #1, how would I go about recreating malloc, and printf?
-- Please keep all of your answers exclusive of asm, unless that is the absolute only way to do it.
3) Are there any other things that I may need to know before I get too into this?
--
Please forgive any mistake I make. I admit that I am by far no professional, and have an immense amount to learn before I even become close to that. If you see a mistake, please tell me, so that I do not make a mistake in the future.
Thanks again, you have helped me come a long way.
Now on to my question(s):
1) A couple of friends and I have taken on the challenge of creating our very own OS. I still have much to learn, so I get a little bit lost every now and then, but for the most part, I pull through. Our 'team leader' has assigned me the task of rewriting the standard c libraries, and I was wondering if this is really a necessary task (I plan on doing it either way, as it will be good practice). -- He has told me that the more important functions include memory, and output functions. What is your input on this matter?
2) Regarding #1, how would I go about recreating malloc, and printf?
-- Please keep all of your answers exclusive of asm, unless that is the absolute only way to do it.
3) Are there any other things that I may need to know before I get too into this?
--
Please forgive any mistake I make. I admit that I am by far no professional, and have an immense amount to learn before I even become close to that. If you see a mistake, please tell me, so that I do not make a mistake in the future.
Thanks again, you have helped me come a long way.
•
•
Join Date: Oct 2006
Posts: 90
Reputation:
Rep Power: 2
Solved Threads: 1
Would this work to output a character?
I found this while searching, and it looks useful.
c Syntax (Toggle Plain Text)
void output(int c) { *(unsigned short *)0xB8000 = 0x0F00 | c; }
Last edited by Brent.tc : Jun 29th, 2008 at 1:49 am. Reason: forgot to close [code]
•
•
Join Date: Aug 2006
Location: Noida, India
Posts: 157
Reputation:
Rep Power: 3
Solved Threads: 16
hey 0xB8000 is the starting address of VDU memory. If u write any thing on this memory location it will be displayed on the screen.
But one thing I want to know what is ur operating system's specification, i mean 8-bit, 16-bit...
And u should know what is ur target hardware(uProccessor). before proceeding.
But one thing I want to know what is ur operating system's specification, i mean 8-bit, 16-bit...
And u should know what is ur target hardware(uProccessor). before proceeding.
When you think you have done a lot, then be ready for YOUR downfall.
•
•
•
•
And u should know what is ur target hardware(uProccessor). before proceeding.
Exactly. Work out those details before commencing this big a task.
"You know you're a computer geek when you try to shoo a fly away from the monitor screen with your cursor. That just happened to me. It was scary." - Juuso Heimonen.
"The only truly secure computer is one buried in concrete, with the power turned off and the network cable cut." - Anonymous.
"The only truly secure computer is one buried in concrete, with the power turned off and the network cable cut." - Anonymous.
•
•
Join Date: May 2008
Location: Infinite Castle, below Beltline
Posts: 282
Reputation:
Rep Power: 1
Solved Threads: 22
Sorry for stealing others thread.
<<And u should know what is ur target hardware(uProccessor). before proceeding
What does this mean? I am so dumb that I don't understand.
EDIT:
I ask this because I know very little about OS. WinXP works well with various hardware configuration, So is not an OS hardware independent
<<And u should know what is ur target hardware(uProccessor). before proceeding
What does this mean? I am so dumb that I don't understand.
EDIT:
I ask this because I know very little about OS. WinXP works well with various hardware configuration, So is not an OS hardware independent
Last edited by Prabakar : Jul 3rd, 2008 at 1:57 pm.
•
•
•
•
Sorry for stealing others thread.
Then don't do it in the first place.
"You know you're a computer geek when you try to shoo a fly away from the monitor screen with your cursor. That just happened to me. It was scary." - Juuso Heimonen.
"The only truly secure computer is one buried in concrete, with the power turned off and the network cable cut." - Anonymous.
"The only truly secure computer is one buried in concrete, with the power turned off and the network cable cut." - Anonymous.
•
•
Join Date: Aug 2006
Location: Noida, India
Posts: 157
Reputation:
Rep Power: 3
Solved Threads: 16
OS is like a layer between ur hardware and ur application program. OS is very close to hardware. So it is not wrong to say that OS is hardware dependent.
As far as WinXp is concerned it is developed in such way to work with uProccessors which are dominating the market like: intel, AMD etc.
But still it will not work with 8-bit uprocessors.
As far as WinXp is concerned it is developed in such way to work with uProccessors which are dominating the market like: intel, AMD etc.
But still it will not work with 8-bit uprocessors.
When you think you have done a lot, then be ready for YOUR downfall.
•
•
Join Date: May 2008
Location: Infinite Castle, below Beltline
Posts: 282
Reputation:
Rep Power: 1
Solved Threads: 22
•
•
•
•
To make the OS independent of hardware is in the hands of the programmers.
More true would be, "To make the OS compatible with maximum amount of uPs that are being used in the target market."
"You know you're a computer geek when you try to shoo a fly away from the monitor screen with your cursor. That just happened to me. It was scary." - Juuso Heimonen.
"The only truly secure computer is one buried in concrete, with the power turned off and the network cable cut." - Anonymous.
"The only truly secure computer is one buried in concrete, with the power turned off and the network cable cut." - Anonymous.
![]() |
•
•
•
•
•
•
•
•
DaniWeb C Marketplace
•
•
•
•
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
Other Threads in the C Forum
- Previous Thread: Passing a pointer to an array.
- Next Thread: Help!!!


Linear Mode