🚀 go-pugleaf

>Like is it impossible to access each plane in turn?

	Kinda sorta - there's only one plane. After much arguing with
one person i think we arrived at that you only use one plane to get
the linear video mapping feel (packed pixels). So you dont' get 
another plane.

>Can you use the set_address_high and set_address_low to pan the screen
>around?
>
	Don't know - have you tried? You have no spare memory area to
scroll onto the screen, but anything can be done (and  cause an error)
in assembler. But you shouldn't be able to get anything usefull 
out of this.

>Can you use page flipping?
>
	Uh, not that i know of. 320x200x1 = 64k, and since only one
plane gets used, you use all available memory. So i doubt you can get
more. If anyone has a tweak to get to other planes for more linear
pages i'd love to see it.

>I have the feeling that the answer to all these questions. If so then
>why would anyone want to use this mode? My current scrolly is so
>processor consuming that I can't do anything else!! 
>
	1) It's the only official 256 color mode. The others are hidden
or our inventions.
	2) I've seen really good things done with it. In sprites
(pascal source on garbo) they use a virtual page by defining an
array [1..64000] of byte. All changes and masking is done to that,
wait for a vertical retrace then you can use a movsw (movsd works
too on 386s, right?).

>Should I use Mode X from now on? I believe you can do the above
>questions with  this mode, right?

	I guess if you know it already. I kinda hate doing bit/pixel
masking and using all the silly registers - you can use mode 13
without any usage of vga registers. But i guess once you write the
masking routines and all the pain is past.
	And plenty of people have written routines to help out.

						- baylor