And, I'm inclined not to do that.
OK. The point was only that I have no way to set the virtual mode parameters since I can't get to the text screen. Maybe viewwindows command line parameters?
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.
Please give me more details on what to try.
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.
Consider at least making your version public so more people can try it. That's not the same as releasing. Tim