On Monday 24 February 2003 04:54 pm, Tim Wegner wrote:
I'm inclined to think that the virtual windows parameters should be settable even if the current mode is not a virtual mode. There could be words on the screen to the effect that these parameters only take effect in virtual mode.
And, I'm inclined not to do that. The only way a user would know if they could get into a virtual mode is to try it and see what happens. This would lead to many complaints when users try it in the standard svga modes and it doesn't work.
Summary. ATI video boards are OK, but Nvidia boards have problems. I believe the Diamond viper uses an Nvidia chipset.
I know the exact section of code causing the problem (VESAvirtscan). But, I don't know why (probably sxdots and sydots getting changed), and I don't know how to keep the video switch to text mode from getting into that section of code. If you have the time or energy you could put in jumps around sections of code in VESAvirtscan and see if it ever works on the Nvidia boards.
Since virtual=no works OK, I suggest you release this patch and let our loyal public help tabulate what works and what doesn't. We'll get
more feedback that way. Or at least, move the proposed patched version to a public area.
I'd like to release it the way it is just so I can move on. But, since it doesn't quite work, I know that won't happen. I'll take another look at the code. Maybe we can release it this weekend. Jonathan