On Monday 03 March 2003 08:00 pm, Tim Wegner wrote:
I tried skipping all the blocks, as well as changing bad_vesa to wedone as you suggested in a private email. Nothing helped.
I assume that in each case I should put a jmp where one of your numbered "jump obver next" were placed, and place the jmp target before the next numbered spot (just after the jne bad_vesa).
Any other requests?
Hmm, the first jump makes no sense, except if you jump from it to wedone, there should be no problems (as confirmed below). If you jump from the second jump to wedone (change 'jne badvesa' to 'jne wedone'), then the first bios call will be tested. I think part of the problem is that even if we fail all the tests, we try to set it anyway. We should bail out if the first test fails. Try these changes at the third and fourth jumps, also.
Keep in mind that even though I am using virtual=yes, I am not actually trying to use a virtual mode. I'm basically starting fractint thusly:
fractint virtual=yes video=sf4
and then pressing ESC. If I understand the virtscan routine (unlikely! :-), I may never be entering the code you wanted me to skip. Aren't sxdots and sydots equal to vesa xres and yres in my case? Apparently not, because if I skip all the way to wedone, everything is OK.
They could be equal (and are when you first start up). But, in a text mode, vesa_xres and vesa_yres could be set to much smaller values. This would cause the code to execute. That is why I've been trying to prevent the call to VESAvirtscan when we switch to text mode. As you can see, I haven't been successful. Jonathan