Xref:	news-dnh.mv.net comp.os.msdos.djgpp:1880
Path:	news-dnh.mv.net!mv!news.sprintlink.net!in1.uu.net!panix!news.mathworks.com!gatech!swrinde!news.uh.edu!uuneo.neosoft.com!news!sandmann
From:	Charles Sandmann <sandmann AT praline DOT no DOT NeoSoft DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Graphics in v2.0
Date:	Fri, 01 Sep 1995 21:39:37 CDT
Organization:	NeoSoft Internet Services +1 713 968 5800
Lines:	18
References:	<427d38$8k0 AT cray DOT ap DOT utu DOT fi> <30478146 DOT sandmann AT praline DOT no DOT NeoSoft DOT com> <427g3j$5n0 AT krel DOT iea DOT com>
Reply-To:	sandmann AT praline DOT no DOT NeoSoft DOT com
Nntp-Posting-Host:	praline.no.neosoft.com
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway:	from newsgroup comp.os.msdos.djgpp

> >I don't do any of that, for both 1.6 and 2.0 I've used:
> >screen=(char*)0xa0000;
> >screen[x+y*320]=somecolor;
> How do you get this to work? Every time I try to do this I get a GPF!

This code has never worked and will never work under DJGPP, period.

> Here is the code for the simple test program I use (It doesn't work), am I 
> doing something wrong?

Yes.  You need to either use <sys/farptr.h> to access the video ram, or
if you are willing to live with reloading the pointer and limiting portability
you can use the new <sys/nearptr.h> setup in V2.  see tests/libc/pc_hw/nearptr

> Should I use INT86() rather than __asm()?

Actually you should use __dpmi_int() in v2 - int86 is big and slow, and 
primarily for compatibility. 

- Raw text -