Charlie,
if the setup fails, the sx/ydots should differ from the videoentry sx/y*, as it does for the not-enough-vram-cut-down (that i've put a message for in) (somewhere after setvideomode() in framain2.c)
but, with vesa 1.x, what is wrong there? if any vesa call fails, it should disable the scrolling.. all those checks for vesa returned values, not enough? ..sigh..
The problem occurred with a VESA 3.0 bios which doesn't support scrolling. It didn't like having subfunction 3 called at all and that was the first test you had. I changed it to subfunction 1, and then had to add the subfunction 3 call back in later to make things work on a 2.0 bios which does support scrolling. Yes, the scrolling is disabled, but the user can't tell this (yet). I will modify the view window menu so that the user can tell that virtual screen's are not supported by his/her graphics card. Jonathan