On Sat, 28 Jul 2001, Stuffed Crust wrote:
> On Sat, Jul 28, 2001 at 11:00:39AM -0700, Matt wrote:
> > I agree. The end problem is that, in the crossblit_32 function,
> > priority_buffer is read beyond it's bounds because the loop is iterated
> > through too many times. That happens because yl is a larger value (for
> > some reason) in fullscreen mode.
>
> We allocate a 320x240(*scaling) screen when going fullscreen in Win32,
> because 320x200 doesn't seem to be a standard mode.
I removed that to eliminate that possibility. I think that was just a
problem on my NT laptop which had a crap video chipset.
--
http://www.clock.org/~matt
