Previous Next Contents

11. Problems and fixes

11.1 Dosemu crashed and now I can't type anything.

Daniel Barlow(jo95004@sable.ox.ac.uk) reported (4/8/95) that

If you have no terminal or network access that you can use to log in, you may have to press the reset button. If you can still get a usable shell somehow, run "kbd_mode -a" to switch the keyboard out of raw mode, and/or "stty sane" on the console so that you can see what you're typing.

A useful thing to do is to use a script to run dosemu, and run "kbd_mode -a" automatically right after dosemu. When dosemu crashes, the script usually will resume running, and execute the "kbd_mode -a" command.

11.2 I've enabled EMS memory in dosemu.conf but it does not help.

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

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

11.3 How do I get rid of all those annoying "disk change" messages?

(8/11/94)

Grab and install klogd. Try

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

11.4 Why won't dosemu run a second time after exiting in console mode?

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

You should disable your video and/or BIOS caching.

11.5 Why will dosemu run in a term but not in the console?

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.

11.6 How can I speed up dosemu?

In some cases it is useful to play with the value of the HogThreshold variable in your dosemu.conf file.

Daniel Barlow(jo95004@sable.ox.ac.uk) reported (4/8/95) that

HogThreshold should now be set to approximately half of the BogoMips value that the system reports on boot.

11.7 My CDROM drive has problems reading some files under dosemu.

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 CD-ROM 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 CD-ROM (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 CD-ROM, or use the following in /etc/fstab:

/dev/cdrom      /cdrom          iso9660 conv=binary,ro
No patches to the kernel are necessary.

11.8 How do I see debugging output?

Daniel Barlow(jo95004@sable.ox.ac.uk) reported (4/8/95) that

As of dosemu 0.60, debugging output is redirected to a file specified on the command line. Use "dos -D+a -o /tmp/debug" to log all debug output to /tmp/debug. There should no longer be any need to redirect stderr.

11.9 Why are my keystrokes echoed ttwwiiccee??

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).


Previous Next Contents