From: Endlisnis Newsgroups: comp.os.msdos.djgpp Subject: Re: Why protected mode. Date: Wed, 02 Sep 1998 18:59:29 -0300 Organization: NBTel Internet Lines: 23 Message-ID: <35EDBFC1.D159FEC6@unb.ca> References: <01bdd69b$a8b74560$4f47f482 AT s-64584> NNTP-Posting-Host: fctnts09c21.nbnet.nb.ca Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk Tarad wrote: > > Started to use djgpp a few weeks ago and I really like it. It's free, not > to complcated and so on. Now I'm just wondering why is djgpp using > protected mode (no real knowledge about protected mode). Does it protect my > programs from crashing? I ask this beacause I'm writing a tiny game library > to djgpp in nasm and to me it's more complicate when you can't use > interrupts (no, I don't use all the slow graphic interrupts). > I know you can do it without interrupts but it seams like unneccesary work > to me. Excuse my bad english. It was done in PMode for 2 main reasons: Programs are more stable and crashes produce important information. Also, you can easily access (idealy) up to 2 Gigs of RAM (some of it may be virtual). Interrupts were still slow in 16-bit mode, they are just slower now. Besides, there is really only one interrupt you shouldn't use when doing graphics, which is the bank-switching interrupt. All the rest are perfectly fast enough. -- (\/) Endlisnis (\/) s257m AT unb DOT ca Endlisnis AT GeoCities DOT com Endlis AT nbnet DOT nb DOT ca hen passed char pointers or 'other' pointers. My guess is that when given the 'other' (void) pointer, it prints it's address in hex. -- (\/) Endlisnis (\/) s257m AT unb DOT ca Endlisnis AT GeoCities DOT com Endlis AT nbnet DOT nb DOT ca