Stas, I wrote those example EXEs for my own testing and then like an idiot I didn't clean them up for anyone else to make sense of... I uploaded a new pair of tests (dpmiok.exe and dpmibad.exe) and their corresponding logs with -D9+M debug options as you requested. Unfortunately that won't tell you much more than the previous log files did... my dpmibad.log stops where it does because it halts with the exception error 06 before any output appears.
I see from your comments on the bug report that you did get correct output from dpmibad.exe... that tells me that the fault lies not in dosemu or the dpmi handling routines, but my own build or my configuration... probably my build, since the same configuration works with the older prebuilt binary. configure options are: --prefix=/usr --datadir=/usr/share --disable-use-svgalib --enable-mitshm -- enable-experimental --enable-dodebug --enable-debug --enable-aspi --disable- cpuemu --with-syshdimagedir=/usr/share/dosemu --with-fdtarball=none compiling with gcc 3.2.2 on kernel 2.4.20. Anything in the above you did differently which might affect the DPMI performance? pbs -------- Peter B. Steiger Cheyenne, WY - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
