Mail Archives: djgpp/1999/06/04/15:02:55
From: | "Christopher Nelson" <paradox AT gye DOT satnet DOT net>
|
To: | <djgpp AT delorie DOT com>
|
Subject: | Re: putpixel method
|
Date: | Thu, 3 Jun 1999 21:54:02 -0600
|
Message-ID: | <01beae3d$e22890e0$LocalHost@thendren>
|
MIME-Version: | 1.0
|
X-Priority: | 3
|
X-MSMail-Priority: | Normal
|
X-Mailer: | Microsoft Outlook Express 4.71.1712.3
|
X-MimeOLE: | Produced By Microsoft MimeOLE V4.71.1712.3
|
Reply-To: | djgpp AT delorie DOT com
|
>> 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.
only in real mode when you have the segment set at 0xa000. although, in
protected mode you could fool around with a selector and get 0xa000 to work,
but in truth, look at it this way:
0xa000: 40960 decimal. right smack at the bottom of low memory. since we
all know that video memory is NOT right smack at the bottom of low memory,
0xa0000: 655360, or right inside of BIOS space sounds much more likely. :-)
the address is linear starting at 0, by the way, so to find it's address you
multiply it by 0x10, then add in the offset, and it gives you the true
memory address.
-={C}=-
- Raw text -