To quote the manual, "dosemu" is a user-level program which uses certain special features of the Linux kernel and the 80386 processor to run MS-DOS in what we in the biz call a `DOS box.' The DOS box, a combination of hardware and software trickery, has these capabilities:
o the ability to virtualize all input/output and processor control instructions
o the ability to support the word size and addressing modes of the iAPX86 processor family's "real mode," while still running within the full protected mode environment
o the ability to trap all DOS and BIOS system calls and emulate such calls as are necessary for proper operation and good performance
o the ability to simulate a hardware environment over which DOS programs are accustomed to having control.
o the ability to provide MS-DOS services through native Linux services; for example, dosemu can provide a virtual hard disk drive which is actually a Linux directory hierarchy."
(xx/yy/zz) means day zz in month yy in year xx(97/2/9).
winemu mean WinOS/2 running in dosemu(97/2/10).
Dosemu uses the same numbering scheme as the kernel. Uneven second numbers are for possible unstable developper releases, even second numbers are for releases considered stable. At the time of writing, 0.64.4 is the latest stable release, while 0.65.0.6 ist the latest developper's release. So if you want to use dosemu, get the latest stable release (97/02/28).
(xx/yy/zz) means day zz in month yy in year xx(97/2/9).
winemu mean WinOS/2 running in dosemu(97/2/10).
The newest version of dosemu as of (97/2/9) is dosemu0.64.4 and can be ftp'ed from:
tsx-11.mit.edu:/pub/linux/ALPHA/dosemu/
ftp.suse.com:/pub/dosemu/However, pre-release versions are also available for developers and ALPHA testers. They can be retrieved from:
http://www.ednet.ns.ca/auto/rddc
If you have problems regarding installing and running dosemu after reading the documentation, first try to help yourself: Your question has probably been asked and perhaps answered before. Try some search engine on the internet to retrieve that information. E.g. you can ask
http://www.dejanews.comto find all newsnet articles containing the keywords of your question. Helping yourself will probably be faster than asking a well known question. It too frees up the time of developpers from answering trivial question and so helps the further development of dosemu(97/2/9) .
If you want to ask questions and report bugs regarding dosemu, you should consider subscribing to the linux-msdos-digest mailing list. To subscribe, send mail to Majordomo@vger.rutgers.edu with the following command in the body of your email message:
subscribe linux-msdos-digest your_username@your.email.address
If you ever want to remove yourself from the mailing list, you can
send mail to
Majordomo@vger.rutgers.edu
with the following command in the body of your email message:
unsubscribe linux-msdos-digest your_username@your.email.address
(95/8/11). When you are subscribed to linux-msdos, you can send your
report as mail to linux-msdos@vger.rutgers.edu. There is a gate that
send mails to linux-msdos@vger.rutgers.edu as postings to the
newsgroup named linux.dev.msdos. If your News provider
doesn't carry that group, ask her(him) to add that group(97/2/10).
If you want to follow the development of dosemu, there is a mailing list for developpers. To subscribe, send mail to Majordomo@ednet.ns.ca with the following command in the body of your email message:
subscribe msdos-devel your_username@your.email.address
If you ever want to remove yourself from the mailing list, you can
send mail to
Majordomo@ednet.ns.ca
with the following command in the body of your email message:
unsubscribe dosemu-devel your_username@your.email.address
Please, don't use this list for the things
linux-dosemu-digest is thought for. Contributions to msdos-devel
should concern the further development of dosemu. Normal installation
problems shouldn't be reported here, and are normally ignored by those
reading that list(97/2/9).
The dosemu manual (dosemu.texinfo) written by Robert Sanders has not been updated in some time but is still a good source of information. It is distributed with dosemu.
The "dosemu Novice's Altering Guide" or DANG is a road map to the inner workings of dosemu. It is designed for the adventurous, those who wish to modify the source code themselves. The DANG is maintained by Alistair MacDonald ( alistair@slitesys.demon.co.uk) and is found in the doc-directory of the dosemu source tree.
The EMU failure list (EMUfailure.txt) is a list of all programs known not to work under dosemu.
And then, of course, there is the dosemu FAQ/HOWTO. But you already know about that, don't you. It is also posted once in a while to the mailing list and found in the doc-directory. The most recent version can be found in ftp.mathematik.th-darmstadt.de:/pub/linux/bonnes/(97/2/9).
First check, if the failure of your program is not caused by some of the fundamental incapabilities of dosemu, listed in EMUfailure. If you think you have something new, please report to linux-msdos@vger.rutgers.edu. Perhaps it can be made going with the help others. Give detailed information about your setup, tell the version of kernel, dosemu etc and name the observed errors. You can use xdos to cut and paste the error message into your report. But keep your report in a readable form. We know the content of ../etc/config.dist. So only send the active lines from your dosemu.conf. And scan through your debug output and at first only send those parts you think are relevant. Few people are willing to decode some long attachment to a mail, to do debugging for others. But keeps your logs at hand, if others ask detailed(97/2/10).
The preferred method is to edit the file dosemu-HOWTO-xx.x.sgml to incorporate the changes, create a diff file by typing something like
diff -uw original-file new-file
and send it to bon@elektron.ikp.physik.th-darmstadt.de. If you do not know SGML, that's ok. Changes or new information in any form will be accepted. Creating the diff file just makes it easier on the HOWTO maintainer. :-)(97/2/9)
Unless otherwise stated, Linux HOWTO documents are copyrighted by their respective authors. Linux HOWTO documents may be reproduced and distributed in whole or in part, in any medium physical or electronic, as long as this copyright notice is retained on all copies. Commercial redistribution is allowed and encouraged; however, the author would like to be notified of any such distributions.
All translations, derivative works, or aggregate works incorporating any Linux HOWTO documents must be covered under this copyright notice. That is, you may not produce a derivative work from a HOWTO and impose additional restrictions on its distribution. Exceptions to these rules may be granted under certain conditions; please contact the Linux HOWTO coordinator at the address given below.
In short, we wish to promote dissemination of this information through as many channels as possible. However, we do wish to retain copyright on the HOWTO documents, and would like to be notified of any plans to redistribute the HOWTOs.
If you have questions, please contact Tim Bynum, the Linux HOWTO coordinator, at linux-howto@sunsite.unc.edu.