Hey,
just wanted to give a quick shout to kylebell to let ya know I didn''t mean to come across as such an ass in my first couple posts....Guess you shouldn''t post to bulliten boards when the pressures on ya from your own programming. Anyway things have eased up(finally figured out my problem actually) so all the power to ya....Thank god I am not in my newbie days anymore...don''t get me wrong, far from being good but at least I know what I am doing now...I remember those long hours trying to figure out what the hell everything meant..you will get there soon enough, just keep wacking a way at it and it will be fine..I don''t really need to go into much detail because other posters have done a good job so have fun and good luck

Later
OME

ODD...I am registered....either its time to kick the message board or learn to type my password

OME

To Anonymous Poster - No problem.

WHAT A SUBJECT...actually admitting to being a retard!
320x200 graphics in C...make sure your going to compile a DOS program:

#include

void main()
{
// Set screen mode
union REGS r;
r.h.ah = 0;
r.h.al = 0x13;
int86(0x10, &regs, &regs);

// Get Pointer to screen
unsigned char far *ScreenArray =
(unsigned char far*)0xa000000;

// Put pixel at 10, 10 index 7
ScreenArray[(10*320)+10] = 7;


// Set back to text mode
union REGS r;
r.h.ah = 0;
r.h.al = 0x03;
int86(0x10, &regs, &regs);
}


The only thing is I haven''t done this for a long time in C so it could be wrong but its something like that

So from what I gather, VC++ 6 a rather strict compiler. Would I be well advised to go purchase a different one? Does anyone here use Borland? Would that be a good choice? Or should I go find a copy of VC++ 5 or possibly 4? Or should I stick it out and go purchase a book on VC++ 6


Edited by - kylebell on 2/8/00 2:43:09 PM

You''re not a retard, but it strikes me that part of your difficulty is learning several things at once: the C++ language; the Windows API; DirectX / games programming, and even the nuances of your compiler.

All of these things have a steep learning curve, but if you''re going to practice, try not to do more than one thing at once. Concentrate on building up skills in one area, then once you start encountering problems you''ll soon know whether it''s due to the compiler, the language or just a simple mistake.

Btw, another post mentioned that the MSDN CD and the F1 key is your best friend - I second that!

--- Marlow