24x .FLC
How about that. A question and an answer (well, not exaclty) before you had
a chance of catching up your breath…
I found the "reboot" problem in Windows. Somebody (I mean by that, some
other application) installed a "device=monoumb2.386" in my system.ini. I
"grep'ed" all the hard disk looking for someone that made any refence to
that and I couldn't find "who did it". I did find what that is. It's there
to allow using 0B100h through 0B7FFh as high memory while running Windows.
Please note that, although I am running QEMM 6.12, I have all that area
excluded (B000-CFFF).
Apparently, your drivers don't like MONOUMB2.386. Great, what a nightmare.
DOS with its CONFIG.SYS and AUTOEXEC's wasn't messy enough. Now we have a
SYSTEM.INI with a billion entries to have fun with.
Any how, Windows is up and running. Not so fast, the same problems I had
with the "old" drivers for stealth are here again with this board.
Just something to try out and check to see if it can be reproduced or
maybe, they've even be fixed by now and a new driver is coming up soon!
640x480x24 – Can't run AAWIN. Slooooooow.
800x600x16 – Fast but AAWIN doesn't like it either.
1024x768x8(sf) – Fast. GP when runing CakeWalk Professional "Staff"
Window. (Same exactly problem with Stealth. Got fixed
with 2.0 drivers.)
1264x1024x4 – Problems with windowed DOS boxes. PCTools' SI locks up.
Norton's SI writes all over the place (outside it's
window).
Interesting fireworks when switching from windowed to full
screen!