Hi all,
As Gene suggested, I browsed vesamenu code and found nothing useful.
However, I figured out how to use the 640X480 mode in mode 12h. It turns out
that one pixel takes one bit place. Codes are:
//
void
2011/4/2 何闯 justhechu...@163.com:
Hi all,
As Gene suggested, I browsed vesamenu code and found nothing useful.
However, I figured out how to use the 640X480 mode in mode 12h. It turns out
that one pixel takes one bit place. Codes are:
Deal all,
I just tested int 0x10 BIOS interrupt to draw some pictures.
However, when I coded the follow to enter 640X480 video mode, it seems that the
actual video mode is 640X100,
I draw a rectangle with range(0,0, 640, 480) to verify, and it resulted in
range(0,0, 640,100), about a quarter
2011/4/1 何闯 justhechu...@163.com:
Deal all,
I just tested int 0x10 BIOS interrupt to draw some pictures.
However, when I coded the follow to enter 640X480 video mode, it seems that
the actual video mode is 640X100,
I draw a rectangle with range(0,0, 640, 480) to verify, and it resulted in
I'd suggest you find out how many bytes there are per pixel. I guess
you have 4 (not 1 you are using) and the resolution you think you see
is actually 640x120. You may also have limited video memory that makes
different resolutions use different pixel sizes
In Reply to:
2011/4/1 何闯
On Fri, Apr 1, 2011 at 15:15, Vaza gpxe vaza.g...@gmail.com wrote:
I'd suggest you find out how many bytes there are per pixel. I guess
you have 4 (not 1 you are using) and the resolution you think you see
is actually 640x120. You may also have limited video memory that makes
different
Thanks for the clue, I will check the code in vesamenu.c32 and find why. ：）
At 2011-04-02，Gene Cumm gene.c...@gmail.com wrote:
On Fri, Apr 1, 2011 at 15:15, Vaza gpxe vaza.g...@gmail.com wrote:
I'd suggest you find out how many bytes there are per pixel. I guess
you have 4 (not 1 you are
