I CANT FIND A FSCKING PEICE OF SHITE COMPLILER THAT WILL FSCKING COMPILE THIS

#include <stdlib.h>
#include <dos.h>

int main(int argc, char *argv[])
{
union REGS regs;

return 0;
}

WTF STUPID WINDOWS STUPID MSVC++ STUPID DEVC++ STUPID GCC AND LINUX AND FAISAL.

Ps. Edited marginally by sphinX for censoring purposes ;-)

IT GIVES ME SOME FSCKEN ERROR ON LINE 5

DEVC++'s <bad> COMPILER GAVE ME THIS CRAP:
aggregate `union REGS regs' has incomplete type and cannot be initialized

WTF.

THIS IS THE SAME FOR BORLAND AND MSVC++ AND FAISAL

Ps. Edited marginally by sphinX for censoring purposes ;-)

If you really NEED that struct, just build your own. That is only a STRUCT!!!

You are laughable... I suggest you keep on living 10 years ago and stick with Turbo C++ if you are not smart enough to understand what you are doing.

Thank you, Next please.

(^^^wtf is that supposed to mean)

Why do you need to use that struct? It's just a struct that is suppose to hold registers to call interrupts. Since you can't call interrupts under Windows or Linux, there are no good reasons for you to use this.

And no Linux/Windows/BeOS or any other modern compiler will support the DOS.H header file. This is just waaaay outdated. Don't use this.

If you really need to use this structure, redefine it manually in your program.

I suggest you explain us what you are trying to do with Dev-C++, MSVC or whatever and we may show you a better and more up-do-date to do it.

Try an old version of Borland, I think you can get them free online

DJGPP compiles that just fine.

I'd only be that angry if it where an actual program of use that wouldn't compile..

Even then I doubt that sort of anger is warranted. Being angry due to one's own ignorance may be motivation to learn, by Faisal has not asked any intelligent questions yet.

I don't think he's angry with his ignorance, more with not having a magical compiler.

what if it was a really really really big program and the dealine was in 2 seconds and the problem wasn't your fault?

Something makes me doupt that faisal's program was really big and due in 2 seconds though.

Well, when he finds the magical compiler, perhaps he'll be kind enough to share it with us.

Perhaps it's voice controlled? "Oh almighty magical compiler, make me a multi-million copy selling first person shooter that will make me lots of money" and voila it's done....

I like the sound of that. If it was truly magical it mightn't work for him though. It might demand he be calm, pleasnt and mannerly. We all know how fussy computers can be, especially compilers.

Any good magical compiler comes with the "edit user"-feature.

pah, I have a magic lantern to do that for me.

Faisal, do you mind maybe not plastering this board with violent cursing over a very simple problem?

My final words: Laugh out Loud.

ps: i cant find the magical compiler, what kind of a joke is this?

Faisal, we could help you if you were a little more precise about what you are trying to do using it!

okay, I WANT TO Use Dos Interrupts, heck i want to use BIOS interrupts. Now how shall i do this... hmmm its only been my #1 confusion for THE PAST 2 FUCKING YEARS OF MY LIFE.

and all i get is some stupid assholes like you and people on irc that ramble on about stupid bullshit like magical compilers.

they probably cant give me an answer so they try to please others by sounding intelligent

now im going to wait for the next intelligent response or some admin is going to talk to me about rules of cussing or whatever admins love doing to people

You can't use BIOS interrupts nor in Windows, nor in Linux. If you could only tell us what you want to do using those BIOS interrupts, we could tell you about a more elegant way to do it using Win32 API or anything else...

LMFAO, I TOLD YOU AN OLDER VERSION OF BORLAND CAN DO THAT, I've used code like that before, I think it was when I trying to get into svga graphics modes under DOS

Faisal, if you are trying to use Mode 13h, then I would recommend using Allegro and DJGPP, which is basically just a slightly more sophisticated implementation of it.

May I also suggest that next time you want some help, you don't insult the people you want to help you. It can often lead to people getting this idea about you being arrogant and ungrateful.

try Qbasic

*And out of nowhere comes mop with a nonsensical suggestion*

Now, I'm not easily offended, but using the qb*sic word on a forum available to minors is considered anti-social behavior.

If you absolutly need to learn bios interrupt functions, search for "The VGA trainer program" from Denthor of ASPHYXIA. It's a good introduction to VGA graphics and demonstrates how to use the bios interrupts. It doesn't cover the other interrupts but it's a start.

Yes, I am an asshole.

Thanks for the help. how am I supposed compile a program with bios interrupts?

You shouldn't be able to run them in a modern OS. Welcome to the year 2002. =)

You compile them like any other C source. All the functions are in the standard C lib. Last time I used these was with Borland C (really old 16bit compiler, but available for free at borlands site in their software museum).

This runs in dos, might run in win'95/98 and probably won't run in any newer windows.

"BIOS interrupts" would not be in a standard C library. Standard C doesn't require you have a BIOS, a computer that has registers, etc.. :P

The functions you use to acces the interrupts are in the C lib ( inp(), outp() and those register variables ).

There's a difference between "the C library" for a compiler and "the standard C library."

modern os's use bios interrupts. modern os's dont allow me to use them. I want to.

After a quick search on MSDN, I can confirm that there is no way to call interrupts from application level in Win32 (thank god!)...

Now, get used to it or stick with third-world 16 bits applications in MS-DOS....

In fact, there is no need to call interrupts. Just tell me something you do using BIOS interrupts in DOS and everybody will prove you here that you can do it more safely using Win32 or a third party API.

Faisal, there is no need for you to use BIOS interrupts. Unless you are trying to write a virus or something, in which case it should not be platform specific and you shouldn't be using BIOS interrupts!
It was like when I started trying to do some graphics programming, I tried using Mode 13h to do it, and I was baffled by the fact that no compiler would let me use the "char far" that was featured in so many examples on 13h. Later on I discovered the marvels of Allegro! Usually if only a 16-bit compiler can do something, then there is bound to be a better way of doing it with a 32-bit compiler.

sorry to interupt this forum... but what are BIOS interrupts, what do they do, and are they only for windows?

Neumann: You think you can do this w/o bios interrupts?

Make me a simple unix-like OS.

Exactly. Im not going to only use windows just because of there stupid monopoly. Im glad im finding out these things as soon as I can, it's becoming rare to find anyone that knows anything about it.

I like consoles and simple OS's not these graphics intense peices of crap.

I suppose you are joking and your are trying to fool me...

...you expect to make a "simple unix-like OS" using a 32 bit Windows compiler? mingwin32? Visual C++? Borland C++?...

this is laughable :P

Do you realize that you tried Windows-only compilers?

yea, so what compilers do i use? WTF man.

I bet you could make a simple unix like OS in Qbasic.

Okay, I really REALLY need sleep now.

yeah, and STOP MENTIONING QBASIC

Besides, most Unices are 32-bit these days.

Faisal, constructing an OS is an incredibly complex task, let alone a UNIX-like OS!! It involves a lot of assembly, lot of low level hardware knowledge, and a LOT of reading through things like CPU Specification documents to get where you want to be. Firstly, I would suggest you learn assembly and use something like NASM or MASM to assemble a boot loader or something. Then I would suggest you read the Intel 386 processor specification (ALL OF IT!) to understand the difference between 16bit Real Mode and 32bit Protected Mode. That document will also explain how you can get from RM to 32bit PM by setting up your Global Descriptor Table and Interrupt Descriptor Table. Then you need to learn about paging and 4K mode. And that's only to get the computer to boot!!!! Then you need to read hardware specifications to find out how to access the keyboard/hard disk/graphics card.

As for compilers, something as simple as GCC or DJGPP's GCC (which WILL compile the code you posted originally) will do fine, but you'll need to write your own C API (or parts of it) because when the computer boots on your code, you will not be able to use the normal C library.

Then you can actually start thinking about how your OS will function --- monolithic or micro kernel? GUI or console? If you want to run concurrent processes then you'll need to learn about time sharing and implement your own fork() function.

This should get you started. (still want to write an OS?)

The BIOS interrupts are functions implented in hardware (like to set the VGA card to a particular mode, or to control the disk drives without the os). They were used in old dos based graphical programs. These functions aren't available under windows, you'll have to use the API's instead of them.

sphinX: What you wrote inspires me.

Faisal: Good, because I've tried before, and it's hard. So instead of posting useless code and cussing at everyone, I suggest you go and DAFGS for OS development tutorials. Get onto the OS dev newsgroups like alt.os.development etc. I would suggest you read a great deal, get some good books (which are often easier to navigate than online tutorials), such as Tananbaum's "Operating Systems: Design and Implementation", and architecture books such as Englander's "The Architecture of Computer Hardware and Systems Software", both of which I've read and I highly recommend.

Thanks.

Oh boy.

Sorry, this just looked like a fun thread to post in.

Forum whore....

this is some good irony

Shut up mister "How do I get rid of PM's" *rolleyes*

irony?

Faisal, if you are not wanting to support a Microsoft monopoly bla bla bla (we've heard it before... it is usually a sign of a very immature person rebelling just because they can. If you don't like Microsoft, don't use their stuff instead of whinging about it) then why not just use GNU/* (Linux, Hurd... whatever)?

Well, they can't all rebel against homework, can they?

@gain you have the wrong image. its not that i dont want to support them, im not rebeling, its that the reason i program to begin with is dealing directly with the machine. And besides im to stupid to figure out how to use linux. i will soon though so WATCH OUT.

There is far more documentation on how to use Linux than there is on developing an operating system.

Yes. I can't possibly see how you expect to be able to develop an entire unix-like operating system if you can't even work out how to use a unix-like operating system.

I know why i do the things i do now go fuck off. you don't need to know how to use linux to beable to fucking program your computer. Thank You for your time. Never talk to me again bye.

What a truly strange individual.

Yea, how am I strange.

You seem incapable of seeing anything beyond your own nose (refer to my PM).

Ok...

i dont have to use gcc for linux you silly man. i can use djgpp...

"I know why i do the things i do now go fuck off. you don't need to know how to use linux to beable to fucking program your computer. Thank You for your time. Never talk to me again bye"

Do you enjoy embarassing yourself? That was the most immature comment I have heard in a long time. You'll find you get a lot more respect if you intelligently support your arguement rather than swearing at everyone and having a temper tantrum.

djgpp cannot create ELF binaries, as you would probably want to when creating a Unix-like OS.

Why does everyone want to make an OS? Don't people realize that it is one of the most difficult and time consuming excercises in programming? Real operating systems are written by large teams of people over months or even years, people with decades of experience in the programming field. It requires advance programming concepts that most teen programmers just don't have knowledge of. If you cannot make a binary search tree using a recursive algorithm, if you don't know about linked lists, stacks or ques(sp), or if you don't have a competent knowledge of assembly language programming, you might as well not even bother trying.

Add to that that noone is waiting for yet another OS. Why don't you join one of the open source OS developers instead?
You'll do better by picking a project that you're capable of handling. If you thing you can handle development of an OS then prove this to yourself by writting a design document. If you have never heard of a design document or don't know how to start it you should reconsider your OS building plans.

(notice how I avoid using a name to prevent a religous forum war about what OS is best)

http://atheos.cx ... it was written by one person. Is there anything really wrong with writing your own ToyOS? It can't really hurt anything. Remember, the Linux kernel started out as a toy project as see where it is now. But that isn't really the point; writing your own kernel and a few basic tools to get something like a shell running on your own toy OS is a useful exercise--you'll learn a bit of assembly (to do stuff like switching into protected mode), how your system boots, and how to read filesystems and whatnot (if you choose to do them). There is a interesting system written entirely in x86 assembly at http://menuetos.org . It has experimental ELF support that; if someone writes a libc for it, enables it to run binaries written for GNU/Linux, FreeBSD, GNU, and other ELF based operating systems. It doesn't hurt anyone if you want to spend your time writing another operating system or kernel--who knows, maybe everyone will be using it in 10 years. The worst thing that can happen is that you'll learn something.

CodeRed: Everyone wants to make an OS because its fun. At least i think its fun.

unknown_lamer: thanks

Frustration is fun for you? It's more than likely over your head. But, Lamer made some good points, the only harm it can do is in wasted time and you might just learn some things in the process.

ok

" Remember, the Linux kernel started out as a toy project as see where it is now."

But even Linux wasn't written from scratch, it was based on the Minix kernel.

This is by far the most lengthy and interresting thread I've read in a long time. Maybe we should get Fasial to stay around a little longer to provide us with yet more amusement. :)

Just kidding, I've always wanted to write my own OS, but at this point in time I don't have the time or determination to write one. What age are you Fasial, if you've been working on this thing for two years you've gotta be determined

No, Linux had no Minix code in it.

regretfuldaydreamer: lol, im 15, your standard screwed up teenager

Ive decided that i need to learn asm, but the problem is that i cant find a decent tutorial on nasm. I found some nice tutorials on a86 but i cant figure out why it only compiles to a .com. I've search usenet and found people with the same problem and there was never a solution. Can anyone help the guy that insulted you and looks like an idiot?

sphinx: Linux was inspired by Minix, but it was written from scratch.

Faisal: Go read http://gaztek.sf.net/ for some OSDev information and links.

Gian, stop double posting

[edited by buzgub so it wasn't a double post]

Stupid Linkers.

a86 is stupid for compiling to .com files. it also lets you make a .obj then you can use a linker to make it a binary. but i cant find a fscking peice of shite linker that will fscking do it.

WTF stupid x, stupid y, stupid z, and faisal

Ps. Edited marginally by Faisal because i knew someone would edit it anyway purposes ;-)

Did you try the borland linker? It should come with the free borland C compiler. I believe I suggested it to you on IRC.

hmm it worked(i thought i tried it).. why doesn't LD work though?

as86 is producing 16-bit binaries. which is why you have to use ld86 with as86 on GNU/Linux at least...(as86 is a 16-bit real mode assembler, not the best to learn assembly with). If you want to learn assembly, you should download "The Art of Assembly Programming" from http://webster.cs.ucr.edu/

wooow... this is the longest thread I have ever seen at TPU

You should have seen the one where AngelOD, me, and infryq were using the board like a chat room LOL, well over 100 posts

heh, lol. i wonder why, probably because i annoy everyone and they feel like saying something to me.

You? annoying us? No way?!

Yea, so you want me to annoy you some more?

so faisal... have you come to ne conclusions as to what u are going to do with that stupid compiler?

Kick it out the window, thats what I did to my cat.... Muahahaha

"Kick it out the window, thats what I did to my cat.... Muahahaha"

Didn't you learn anything from the Flinstones? In a moment your cat is going to jump in through the window and kick you out.

Faisal, maybe I should inform you what happens with annoying people. They get a free trip to the Kakabolochichi tribe in the Central African Jungle. This tribe really likes people (well done, with salt, peper, some vegetables and a beer).

"Didn't you learn anything from the Flinstones? In a moment your cat is going to jump in through the window and kick you out"

LMFAO, didn't even think about that

I stand corrected on the Linux/Minix thing.

Faisal: There are stacks of x86 assembly resources available. Google turned up a mass of results. Also, there is a book available online entitled "The Art of Assembly Language Programming", which you can find here: http://webster.cs.ucr.edu/Page_asm/ArtofAssembly/pdf/0_AoAPDF.html

Read it. Learn it. You will benefit.

is that real assembly.. its confusing, the writein fuction that i found in it. ive never used it because i keep thinking its not real assembly.

Real x86 assembly looks like the following:

mov ax, 5
mul bx
shl ax, 2
jmp 0x355

Or, once you actually get into 32-bit protected mode you can use the extended, 32-bit registers:

mov eax, 0xFFFF
mul ebx

etc etc...

Note: The above code is not meant to do anything and is purely example.

The assembly in AoA is "High Level Assembly." Basically, it is a bit pascal-ish, but still assembly. It contains a large standard library that make it much easier to start assembly programming. Eventually you stop using any of the HLA features and should have the skills to implement the HLA standard library. I think it is better to have a few higher level constructs at first so that the learning curve for assembly is lowered (what I mean is that you can do real things more quickly than you can when doing "pure" assembly). No one wants to spend a few weeks learning how to do I/O or (worse) not being able to write programs that have any output at all for a while why you learn the basics of assembly neccesary to do things like I/O.

I didn't like that Art of Assembly book, it was far too heavy going and got way to far into the theory of hexadeimal and mats. Then it moved on to how the circuits work in the second chapter. It was far too complicated, so I put it down and haven't looked at it since(I printed it out for tose who are wondering how you can put down an e-book, I find reading long amount of texts off the screen annoying, you can never take any of it in

Wait a minute

Yay, This is the 101th message on this thread, and i posted it, Muhahahahahahahahaha. (It was meant to be the 100th, but I posted 1 premessage too many.

:)

I'm not looking forward to the backlash

@Gian is gonna hate me, cause I invented Quadruple posting.

And the rest of you's are gonna hate me cause I've introduced the idea of adding even more posts into his mind.

Hehehehehe ... World War III

that is so lame....

"Quadruple posting" another PC term for spam?

I must inform you about the new law I just made up: Frequent spammer will be forced to eat their keyboard (including the cable). Severe cases will be provided mandatory help to shove the keyboard (including cable) down the offenders throat.
(This is ofcourse the clean version, for the original replace throat with ass, and adjust grammar where needed).

I know its lame.

And RedX, which country does this so called "law" of yours apply in?

Everywhere in the federation of planets.

darn.

Darn. Still I suppose it doesn't apply to me, I'm not a frequent spammer

http://www.phys.uu.nl/~takken/Assembly.htm