Dont care
Re: Dont care
I know stop being rude to me please ok. I tryed cmd for nasm but it chashed the .pf file is corrupt apperently but it also is not. Anyways thanks neon theat tutorial was great i can lin the files and make a kernal now.
Re: Dont care
Focus on the tutorial and learning. If you are not a troll, then this is what you should be doing. If you need any help with the tutorial, feel free to let us know however keep in mind that we will not do the work for you.Screw you troll windows worm linux trojan.
Enough with comments like "screw you" and the like already. These types of comments do not create a good impression of you and only make you look bad.
NASM uses Intel-style assembly language syntax. Use an editor to type the code in and run NASM through command line (I personally use a batch script on Windows). If you dont know what these are, then you need to first learn your environment better before OS development.how do i use nasm?
Then, again, stop being rude to us.I know stop being rude to me please ok.
Post errors if you are having problems. Im glad you are getting it to work thoughI tryed cmd for nasm but it chashed the .pf file is corrupt apperently but it also is not. Anyways thanks neon theat tutorial was great i can lin the files and make a kernal now.
OS Development Series | Wiki | os | ncc
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
Re: Dont care
Ok i am sorry but how do i get it to work with cmd?
Re: Dont care
What is cmd? Don't use acronyms unless they're well known. If you mean the windows command prompt, either say that, or say cmd.exe (implying cmd isn't an acronym and is a windows executable). If you don't know how to use the command prompt, learn that first (and no, we won't tell you how to use the command prompt; that's not related to operating system development).
Re: Dont care
The tutorial has this:Ok i am sorry but how do i get it to work with cmd?
Code: Select all
nasm -f elf -o loader.o loader.sHow much experience do you have with NASM? If not too much experience with it, I highly recommend learning how to use NASM first before going any further.
OS Development Series | Wiki | os | ncc
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
Re: Dont care
Yes compand promt and there is no cmd.exe. I think i know how heres the command that should work. c:\nasm\assembler.c code here command here
Re: Dont care
The problem do i use a text file for the code use that comand then itwill produce the results?
Re: Dont care
Er... cmd.exe is the Windows command prompt.Yes compand promt and there is no cmd.exe.
No. It would be this (assuming Windows):I think i know how heres the command that should work. c:\nasm\assembler.c code here command here
Code: Select all
cd c:\nasm\
nasm -f elf -o c:\outputdir\loader.o c:\outputdir\loader.sCode: Select all
cd c:\outputdir\
nasm -f elf -o loader.o loader.sUse any basic text editor to write the code in (Like notepad). Will it produce what results?The problem do i use a text file for the code use that comand then itwill produce the results?
Last edited by neon on Sat Nov 15, 2008 7:27 pm, edited 1 time in total.
OS Development Series | Wiki | os | ncc
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
Re: Dont care
Yes there is cmd.exe, that's what is run when you type "cmd" in the prompt.Yes compand promt and there is no cmd.exe.
"I think I know how here's the command that should work." is not a sentence. "I think I know how the command should work" and "Here's the command that should work" are. Besides, that's not how you use nasm, so that's not how it works at all.I think i know how heres the command that should work. c:\nasm\assembler.c code here command here
You sure you aren't a foreigner? You're just as illiterate as they usually are.
-
pcmattman
- Member
- Posts: 2566
- Joined: Sun Jan 14, 2007 9:15 pm
- Libera.chat IRC: miselin
- Location: Sydney, Australia (I come from a land down under!)
- Contact:
Re: Dont care
I think you're clearly not ready to develop an operating system.
Go learn assembly and C, learn how to use a compiler and an assembler (which is part of using assembly and C), and learn how to ask smart questions. Then, when you have the basic required knowledge, you can come back and understand what you're doing.
Go learn assembly and C, learn how to use a compiler and an assembler (which is part of using assembly and C), and learn how to ask smart questions. Then, when you have the basic required knowledge, you can come back and understand what you're doing.
Re: Dont care
I will not ok i barly know batch yet i am making tones of batch files.
Re: Dont care
pcmattman wrote:I think you're clearly not ready to develop an operating system.
Go learn assembly and C, learn how to use a compiler and an assembler (which is part of using assembly and C), and learn how to ask smart questions. Then, when you have the basic required knowledge, you can come back and understand what you're doing.
I dont care thats your opinion so dont spam that.
Re: Dont care
That is not spam nor opinion and is very correct what he posted. They are required prior knowledge... (Technically C is only required if you plan to use C for OS dev (Although knowing it is still recommended) ).cotton509 wrote:pcmattman wrote:I think you're clearly not ready to develop an operating system.
Go learn assembly and C, learn how to use a compiler and an assembler (which is part of using assembly and C), and learn how to ask smart questions. Then, when you have the basic required knowledge, you can come back and understand what you're doing.
I dont care thats your opinion so dont spam that.
OS development is not easy and requires alot of technical knowledge and the ability to search and find the information needed. You need to know: Assembly language, System architecture, your primary language inside and out, and your host operating system. These are the basics required in order to understand OS development. If you dont know any one of these, you are not ready and should learn it. Not doing so you will be running into problems and your project will never be close to complete.
Last edited by neon on Sat Nov 15, 2008 7:37 pm, edited 1 time in total.
OS Development Series | Wiki | os | ncc
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
-
pcmattman
- Member
- Posts: 2566
- Joined: Sun Jan 14, 2007 9:15 pm
- Libera.chat IRC: miselin
- Location: Sydney, Australia (I come from a land down under!)
- Contact:
Re: Dont care
You've made far too many Beginner_Mistakes, you need to learn how to ask a smart question, and you clearly hardly know how to use the command interpreter of your host operating system.
You aren't cut out for this, go and learn how to program something simpler. Maybe try developing a program to convert temperatures and compile and link on the command line rather than in an IDE.
You aren't cut out for this, go and learn how to program something simpler. Maybe try developing a program to convert temperatures and compile and link on the command line rather than in an IDE.
I'm sorry, it's not my opinion. It's the cold, hard, truth, and as neon says - they are required prior knowledge. If you don't know that, you shouldn't be thinking about writing an OS. It's that simple.I dont care thats your opinion so dont spam that.
Re: Dont care
It's not just an opinion, it's informed advice. You aren't ready. Learn C and assembly, make some games with allegro or SDL (or some other programs, whatever), and come back when you're done and can ask intelligent questions. He's not insulting you, he's telling you how this sort of thing works. You can't just dive into kernel development with no prior experience.