From: "Michael Stewart" Newsgroups: comp.os.msdos.djgpp Subject: Re: putpixel method Date: Tue, 1 Jun 1999 08:58:31 +0100 Organization: (Posted via) Netcom Internet Ltd. Lines: 28 Message-ID: <7j03kl$7ef$1@taliesin.netcom.net.uk> References: <12907576 DOT 928170590243 DOT JavaMail DOT w-epost AT localhost> <375331E2 DOT 65A7180A AT cartsys DOT com> <37533712 DOT 2CB224D2 AT hitech DOT net DOT au> NNTP-Posting-Host: hgty.capgemini.co.uk X-Trace: taliesin.netcom.net.uk 928223701 7631 194.42.240.2 (1 Jun 1999 07:55:01 GMT) X-Complaints-To: abuse AT corp DOT netcom DOT net DOT uk NNTP-Posting-Date: 1 Jun 1999 07:55:01 GMT X-Newsreader: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com leroy wrote in message <37533712 DOT 2CB224D2 AT hitech DOT net DOT au>... >Nate Eldredge wrote: > >> Writing to video memory is not risky per se; the risk comes if you miss >> and write to some other kind of memory :) In the above example, it >> might be wise (while debugging) to check that y < 200 and x < 320, and >> that you have the right number of zeros in 0xA0000. >> -- > >Isn't it 0xA000, only 3 zero's. Thats the address I always write to and it >works. It is 0xa0000 In a real mode program you would access segment 0xa000 offset 0x0000, but to convert that value to a pmode offset (?) you would do this offset = segment * 16 + offset Which in the above example is 0xa0000. I think this is documented in the FAQ. >The irony of it is pretty funny though. > >Cheers, > >leroy.