public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter B. Steiger" <pbs-lists@12-254-66-125.client.attbi.com>
To: linux-msdos@vger.kernel.org
Subject: Re: DOSEMU-1.1.5 vs. DPMI
Date: Mon, 23 Jun 2003 01:02:32 -0500	[thread overview]
Message-ID: <3EF651A8.20606.222D92F2@localhost> (raw)

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



             reply	other threads:[~2003-06-23  6:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23  6:02 Peter B. Steiger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-12 23:28 DOSEMU-1.1.5 vs. DPMI Peter B. Steiger
2003-06-10 21:18 Stas Sergeev
2003-06-07  0:07 [ANNOUNCE] DOSEMU-1.1.5 Bart Oldeman
2003-06-10 20:43 ` DOSEMU-1.1.5 vs. DPMI Peter B. Steiger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3EF651A8.20606.222D92F2@localhost \
    --to=pbs-lists@12-254-66-125.client.attbi.com \
    --cc=linux-msdos@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox