The High ASCII bug in v1.3.4, 1.3.5 persists
With my historic .dosemurc/dosemu.conf running on the same development system, dosemu 1.3.2 and 1.3.3 WILL display normal MS-DOS high ascii (border drawing, etc.) but not 1.3.4 or 1.3.5! I run dosemu on a Linux /dev/tty?, but same result on an X rxvt.
What changed in 1.3.4 and persited in 1.3.5 that could affect this?
And yes of course, I have used the cp437/850 character sets and tried several other HIASCII mapped shell fonts, with the same effect. Why would it be fine with 1.3.2/1.3.3 and broken 1.3.4/1.3.5?
What could I try to debug this!
The dosemu make config is the same in all version build:
#!/bin/sh
#
make distclean
./configure --prefix=/usr --sysconfdir=/etc \
--target=i486-pc-linux-gnu --with-target-cpu=i486 --without-x \
--disable-dlplugins --disable-mitshm --disable-aspi 2>&1 | \
tee cf.log
make 2>&1 | tee mk.log
Tony Borras
There are 10 types of people in this world, those that read binary and those who don't!
--
__ __ _ I N C. http://www.sysdev.org
/ __|\\// __|| \ __ __ / [email protected] \__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities |___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers
Quoted 3 lines · Tony Borras
With my historic
.dosemurc/dosemu.confrunning on the same development system, dosemu 1.3.2 and 1.3.3 WILL display normal MS-DOS high ascii (border drawing, etc.) but not 1.3.4 or 1.3.5!
So what is your historic .dosemurc/dosemu.conf? Esp the internal and external char set settings?
I did not receive any reply to my enquiries last time (@dosemu-devel) and it works for me so the terminal code hasn't changed from 1.3.4 to 1.3.5.
Quoted 1 line
What could I try to debug this!
The output of
locale charmap
and a debug log (~/.dosemu/boot.log) of
dosemu -D+v
would be helpful (both in rxvt and on the linux console)
Bart