CVS solves a lot of problem about cursor shape and 43
lines but it still has problems.
I found that in int10c, function set_video_mode(mode)
there is a command set_text_scanlines(400); just
before the end. It is odd to force 400 scan-lines after
calculating everything!
I removed it and fixed these problems:
1) if I set 43 lines and call Borland C 3.1 IDE, it
expands to 50 lines.
2) in 43 line mode, NDN 2.15 4000 editor gets confused
and has a few "bellow the end of the screen" lines.
3) if I call xdosemu without the option "-v 18" and
then switch to 43 lines, in Borland C 3.1 IDE the
cursor disapears.
Why is this line there? Is it a reminicense of some
debug? Am I breaking something?
Diff file attached, if nescessary.
Alain M.
Logged In: YES
user_id=501371
Logged In: YES
user_id=1132071
Originator: NO
I couldn't reproduce this -
1) AFAIKT in borland C 3.1 it sets 43 lines if it detects EGA and 50 if it detects VGA, you can't choose.
2) 43 lines seems ok in xdosemu, however if you cycle through the modes with shift f10, eventually it seems to crash with
ERROR: Fault in dosemu code, in_dpmi=1
ERROR: cpu exception in dosemu code outside of DPMI client!
trapno: 0x0e errorcode: 0x00000006 cr2: 0xb4b98000
eip: 0x08060d0e esp: 0xbfb84e90 eflags: 0x00210202
cs: 0x0073 ds: 0x007b es: 0x007b ss: 0x007b
Page fault: write instruction to linear address: 0xb4b98000
CPU was in user mode
Exception was caused by non-available page
3) Works for me (TM) -- (can change to 43 line mode with mode co80,43, but bc changes back when back from the dos shell)
Logged In: YES
user_id=1132071
Originator: NO
Just tried this in the console (seems to be fb console) and the freedos edit looks all borked (trying to run in 25 lines)
mode co80,43 tells me I can only run in 25 lines is this known?
Patch to fix 43 lines behaviour
I just attached a patch fo fix the 43 lines behaviour in dosemu.
I have been using tis for many years, it works very well (the original post is from 2005, by myself).
Another patch
I can reproduce this, and I've also found that
the attached (different) patch fixes this too.
I have no idea which one is correct though, if
any.