From: "Chewbaklava" Newsgroups: comp.os.msdos.djgpp Subject: Graphics Lines: 32 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Message-ID: Date: Wed, 12 Apr 2000 20:30:18 -0400 NNTP-Posting-Host: 209.222.102.61 X-Trace: harpo 955586009 209.222.102.61 (Wed, 12 Apr 2000 20:33:29 EDT) NNTP-Posting-Date: Wed, 12 Apr 2000 20:33:29 EDT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com I was starting work on my own graphics library, not to compete with anything like Allegro, because it surely can't hold up, but just to see how it all works. My question is this, I see people set mode 13h 2 ways, both work fine. is there any differance between saying (and I'm doing this from memory, so if the syntax is a little wrong...) union REGS regs; regs.x.ax = 0x13; int86(0x10, ®, ®s); and __dpmi_regs r; r.x.ax = 0x13; __dpmi_int(0x10, &r); Both of these methods work, and as far as I can see do absolutly the same thing. Also, plotting a pixel. I've seen a method with a char * that points to the video memory (0xA0000 right?) and I've seen it done with farpokew, farpokel and farpokeb (the w, l and b stand for word, long and byte, right??). This is speed sensitive, so I would like to know, what does farpokeb do exactly??? If there are other methods here, I would also like to know because I want to get this cleared up before I move on to mode-x. - Dogansmoobs The grape moos hotly Manly loser snaps at beach Screwdrivers are green