Tim Wegner wrote:
Good news is that the SVGA modes work without problems, recent bad symptoms are gone.
That was what I wanted.
Bad news is that with virtual=yes, the text screens get messed up. I'll try to give you more details later, but basically, start with virtual=yes, goto a virtual mode, generate a fractal, and go back to a text screen.
Occurs to me that I have a houseful of computers, I'll try some of the other ones.
I wonder if stack is running out? Some VESA bioses use more stack than others. (cheking ...) debug=1000 shows 8444 stack bytes free at startup.
The switch between graphics modes changes the contents in the VESA buffer area we are using. If you take a look at the bottom of the <v> screen (with virtual=y) you will probably see that the resolution of the screen corresponds to a text mode. I can fix this by saving the x and y values to different variables and then using them. But, it breaks other things. The switch to the <t> screen, for instance. Jonathan