(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
James B. MacLean (jmaclean@fox.nstn.ns.ca
) reported
(1/16/94) that
If you have Linux networking turned on for your card, it is not accessible to DOSEMU at this time. It is also true that the default dosemu will not get interrupts from the kernel. That said, if you'd like to give your NIC to dosemu for it to control, maybe for access to Netware on the network through a NETX client, I do have a driver (Silly Interrupt Generator) to put in the kernel that any program, like dosemu can use to get at the interrupt for your NIC. I use it in DOSEMU to access a Novell Lite network. Speed is not it's high point, but it does seem to work :-).
Any interested parties should E-mail me
(jmaclean@fox.nstn.ns.ca
) and I'll pass along some
directions.
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).
(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.
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".
James MacLean (jmaclean@fox.nstn.ns.ca
) reported (3/10/94)
that
For everyone suffering from seg faults, please try these 2 things:
1) In emu.c, function video_config_init()
, add *(u_char *)0x462=0;
after the switch statement ends.
2) In emu.c, function emulate()
, move video_config_init()
to
just after memory_setup()
in the same function emulate()
.
[
Note: this applies only to dosemu0.50]
<
128 highlighted and blinking? 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)
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" ()))and then "emacs -f do-dos" will run the dosemu inside the buffer. Make sure you emacs window is 25x80, of course.
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 error or
hangs, which you may mistaken as problem of dosemu.
I could verify that this kind of heuristic is not used when the cdrom is used from DEC ALPHA system. (I nfs mounted the exported cdrom drive and used under dosemu as a drive.)
To correct the behaviour, you can force the iso9660 file system not to use heuristic at all. Make the following change and then recompile your kernel.
File: /usr/src/linux/fs/isofs/file.c In Function: static int isofs_file_read () ... if (inode->u.isofs_i.i_file_format == ISOFS_FILE_UNKNOWN) { inode->u.isofs_i.i_file_format = ISOFS_FILE_BINARY ; /* ORIGINAL: isofs_determine_filetype(inode); */ } ...
Next Chapter, Previous Chapter
Table of contents of this chapter, General table of contents
Top of the document, Beginning of this Chapter