10 Problems and fixes

(8/5/94)

Dosemu 0.52 is not compatible with kernels newer than 1.1.30. This problem will be fixed in dosemu 0.53.

Rob Janssen (rob@pe1chl.ampr.org) reported (7/11/94)

Don't forget to load the provided ems.sys from the config.sys file.

(8/11/94)

Grab and install klogd. Try

         sunsite.unc.edu:/pub/Linux/system/Daemons/sysklogd1.2.tgz

(7/9/94)

This is a known bug in dosemu 0.52. It will be fixed in dosemu 0.53.

James B. MacLean (jmaclean@fox.nstn.ns.ca) reported (7/8/94) that

Busmouse support is quite ALPHA at this time (as is DOSEMU :-)), and will be continually refined for a while :-). Look for better support in the upcoming releases.

Aldy Hernandez (aldy@sauron.cc.andrews.edu) reported (7/8/94) that

You should disable your video and/or bios caching.

James B. MacLean (jmaclean@fox.nstn.ns.ca) reported (6/19/94) that

At this time (as of 0.52 release) DOSEMU is still growing with respect to DPMI. It will run certain DPMI programs, but has a ways to go yet. As suggested there needs to be more of the calls implemented, etc. Please be patient :-), as it's bound to come in time.

(1/17/94)

This is a known bug. It will (hopefully) be fixed in an upcoming release. For now, you can simply exit dosemu and start it again.

JyiJiin Luo (jjluo@casbah.acns.nwu.edu) reported (4/19/94) that

I experienced exactly the same problem before. I figured out all the video shadow in my AMI BIOS must be disabled. Now dosemu runs fine on my system.

Mark Rejhon (mdrejhon@undergrad.math.uwaterloo.ca) reported (4/7/94) that

TIP: Speed up your DOS "dir" listings by about 25%-50% or so by typing break off at the DOS prompt or including it in autoexec.bat.

TIP: Use the nnansi.com ANSI driver to speed up the "dir" output even more at roughly 50%-100% more. It works properly in non-graphics mode, unlike turbo.com.

---------------------

Joel M. Hoffman (joel@rac1.wam.umd.edu) reported (4/23/94) that

Ironically, I've found that it's sometimes faster to run dosemu in an Emacs terminal emulator rather than directly to the console. Emacs's output optimization is what makes the difference here.

Put the following in your .emacs:

        (defun do-dos ()
          (interactive)
          (terminal-emulator "dos" "/usr/local/bin/dos" ()))

---------------------

Pete Heist (heistp@rpi.edu) reported (5/13/94) that

If you compile it with the "-funroll-all-loops" option you will get MUCH faster screen output. Some other parts of the emulator will run much faster as well. Realize that the consequence of this is a larger executable which eats a little more memory, even though it's demand loaded.

---------------------

Georg Wiegand (gw@gwcomp.e.open.de) reported (5/16/94) that

You also can use the keyword HogThreshold in /etc/dosemu.conf. The greater the following number the more calculating-time dosemu gets. For example, I use "HogThreshold 60000" on my 386/87-20 laptop.

Vinod G Kulkarni (vinod@cse.iitb.ernet.in) reported (4/7/94) that

When a CDROM is mounted from linux and used from within DOSEMU (mapped drive), there could be some problems. The cdrom driver (iso9660) in the kernel tries to find out the type of the file (i.e. binary or text). If it can't find, it tries to guess the type of the file using a heuristic. This heuristic fails under some circumstances when a (almost) text file is to be treated as binary. (I do not know if it is a bug or feature.)

The result of this is that if you copy such a file from cdrom (from linux itself, and not necessarily dosemu), the resulting file will be usually bigger than original file. (Blanks get added before ˆJ,ˆM.) So a program running in dosemu gives an error or hangs, which may be mistaken as problem of dosemu.

Rob Janssen (pe1chl@rabo.nl) reported (8/10/94) that

The way to solve this is to turn off conversion altogether. Pass the option "-o conv=binary" to the mount command mounting the CDROM, or use the following in /etc/fstab:

/dev/cdrom      /cdrom          iso9660 conv=binary,ro

As of dosemu0.49pl4, stderr is automatically redirected to /dev/null. Try "dos -D+a 2>debug" to turn on debugging information and redirect it to the file "debug".

(12/17/93)

You need to turn on the keyboard interrupt in the dosemu config file. Add a line to the config file:

   keybint on

Shouldn't be a problem in dosemu0.52.

Nick Holloway (alfie@dcs.warwick.ac.uk) reported (2/22/94) that

After running dos after playing with some stty settings, I was getting doubled key presses. I can now reveal what the reason is!

It only happens when dos is run on the console with 'istrip' set. This is (I think) because the raw scancodes are mutilated by the 'istrip', so that key release events look like key press events.

So, the input processing needs to be turned off when using the scan codes on a console (it wouldn't be a good idea to do it for tty lines).

Chris Kuehnke (Christian.Kuehnke@Informatik.Uni-Oldenburg.DE) reported (3/21/94) that

I think I've found a bug in dosemu0.50pl1; with a MDA card displayed characters > 128 automagically appeared as highlighted and blinking.

This patch fixed the problem for me [but on the other hand, maybe I'm totally wrong ;-)]:

--- video.c~    Sat Mar 19 00:50:25 1994
+++ video.c     Sat Mar 19 20:36:10 1994
@@ -721,7 +721,7 @@
   int x, y, i, tmp;
   unsigned int s;
   static int gfx_flag = 0;
-  char c;
+  u_char c;
   us *sm;
 
   if (d.video >= 3)