Bochs/bochs
Kevin Lawton 3fdba77f4e Fixes these files to comply with the new method of getting
and pinning user pages from the plex86 kernel module.  The
  guest physical memory array is no longer mmap()'d from kernel
  space where it used to be allocated.
2003-01-08 17:22:07 +00:00
..
bios - compile from rombios rev1.86 2003-01-06 02:03:57 +00:00
build - there are no longer any *.htm files, but the installer was still 2003-01-06 03:26:55 +00:00
cpu clean up of error messages 2002-12-30 18:51:09 +00:00
debug Added support for a PASS log level. This probably 2002-12-17 03:36:53 +00:00
disasm - regenerate makefile dependencies 2002-11-25 15:05:51 +00:00
doc - add cvs tags for 2.0s versions 2003-01-06 02:49:45 +00:00
docs-html - get rid of bochs-docs which didn't work anyway 2002-12-11 19:16:20 +00:00
dynamic - remove obsolete makefile 2002-10-26 13:19:06 +00:00
font - font char 0x00 is a blank, not a "@" 2002-05-25 14:22:53 +00:00
fpu - add msdos compatibility FPU exception support (irq 13). The IGNNE pin is no handled yet. 2003-01-06 02:20:47 +00:00
gui - fixed segfault in log action dialogs - the new log type "pass" was missing 2003-01-04 11:47:00 +00:00
instrument - change BX_SREG_CS to BX_SEG_REG_CS 2002-11-20 17:55:41 +00:00
iodev - remove read handler, on Volker advice 2003-01-07 08:17:15 +00:00
memory - regenerate makefile dependencies 2002-11-25 15:05:51 +00:00
misc - fix compile warning (patch from HJ) 2002-11-26 11:21:31 +00:00
patches - This patch adds msdos compatibility FPU exception support. (irq 13). The IGNNE pin is no handled yet. 2003-01-06 02:17:24 +00:00
plex86 Changed over from allocating the the guest physical memory area 2003-01-08 17:20:01 +00:00
.bochsrc - mention the PIT option in .bochsrc 2002-12-21 17:10:08 +00:00
.conf.AIX.4.3.1 Added a config file for AIX 4.3.1. 2001-04-11 09:07:55 +00:00
.conf.amigaos - commit patch.check-platform. For full details, pull up the patch itself 2002-03-07 16:00:39 +00:00
.conf.beos -Wno-multichar is already added by the configure script for beos, so 2002-12-21 14:28:24 +00:00
.conf.everything - add warning about this config enabling lots of experimental stuff 2002-11-21 20:57:34 +00:00
.conf.linux - I'm building releases with the plugins configuration these days. 2002-12-15 17:40:14 +00:00
.conf.macos - update to have macos compile. 2002-12-12 13:27:47 +00:00
.conf.macosx - remove "unset echo" at the end. That's the command that actually 2002-12-19 03:13:15 +00:00
.conf.sparc - get sparc conf file in sync with others 2002-11-23 00:52:05 +00:00
.conf.win32 - commit patch.check-platform. For full details, pull up the patch itself 2002-03-07 16:00:39 +00:00
.conf.win32-cygwin - remove --enable-dc2300-vlb-ide from all .conf files at Volker's suggestion. 2002-11-19 20:48:07 +00:00
.conf.win32-vcpp - remove --enable-dc2300-vlb-ide from all .conf files at Volker's suggestion. 2002-11-19 20:48:07 +00:00
aclocal.m4 Add plugin support to Bochs by merging all the changes from the 2002-10-24 21:07:56 +00:00
bochs.h - add msdos compatibility FPU exception support (irq 13). The IGNNE pin is no handled yet. 2003-01-06 02:20:47 +00:00
bxversion.h.in - I have tried to make the --prefix argument to configure control 2001-11-10 03:48:22 +00:00
CHANGES - update Changes with 2.0.1 Changelog 2003-01-04 23:08:53 +00:00
config.guess - commit patch.check-platform. For full details, pull up the patch itself 2002-03-07 16:00:39 +00:00
config.h.in - add msdos compatibility FPU exception support (irq 13). The IGNNE pin is no handled yet. 2003-01-06 02:20:47 +00:00
config.sub - commit patch.check-platform. For full details, pull up the patch itself 2002-03-07 16:00:39 +00:00
configure - show something reasonable in the version string, instead of showing 2.0.pre4. 2003-01-04 19:22:47 +00:00
configure.in - show something reasonable in the version string, instead of showing 2.0.pre4. 2003-01-04 19:22:47 +00:00
COPYING - entered original Bochs snapshot bochs-2000_0325a.tar.gz from 2001-04-10 01:04:59 +00:00
extplugin.h - update for macos compile 2002-12-12 15:29:45 +00:00
gdbstub.cc - add check for existence of sockaddr_in.sin_len in configure 2002-11-08 21:29:16 +00:00
install-sh - commit patch.check-platform. For full details, pull up the patch itself 2002-03-07 16:00:39 +00:00
install-x11-fonts.in - if the font is already there, do not restart the font server. Shap says 2002-11-18 19:30:34 +00:00
load32bitOShack.cc I merged the cpu/cpu.h and cpu64/cpu.h files as well as the 2002-09-13 00:15:23 +00:00
logio.cc Patch name: patch.carbon-startup 2002-12-17 05:58:45 +00:00
ltdl.c - add win32 specific print code, so that we can see the exact error that 2002-11-01 13:02:15 +00:00
ltdl.h Add plugin support to Bochs by merging all the changes from the 2002-10-24 21:07:56 +00:00
ltdlconf.h.in Add plugin support to Bochs by merging all the changes from the 2002-10-24 21:07:56 +00:00
ltmain.sh Add plugin support to Bochs by merging all the changes from the 2002-10-24 21:07:56 +00:00
main.cc - fix bug reported many times on irc and on the ml. The "pass" log was 2002-12-24 09:14:54 +00:00
Makefile.in - new application icon for the X11 gui using 'icon_bochs.xpm' 2002-12-30 13:17:39 +00:00
osdep.cc - update for macos compile 2002-12-12 15:29:45 +00:00
osdep.h - update for macos compile 2002-12-12 15:29:45 +00:00
pc_system.cc - Apply patch.replace-Boolean rev 1.3. Every "Boolean" is now changed to a 2002-10-25 11:44:41 +00:00
pc_system.h - due to multiple complaints of "register_timer: too many registered timers" 2002-12-15 16:00:41 +00:00
plex86-interface.cc Fixes these files to comply with the new method of getting 2003-01-08 17:22:07 +00:00
plex86-interface.h Fixes these files to comply with the new method of getting 2003-01-08 17:22:07 +00:00
plugin.cc - plugins are now called libbx_NAME.so for unix and bx_NAME.dll for win32. 2002-11-14 18:45:49 +00:00
plugin.h - add msdos compatibility FPU exception support (irq 13). The IGNNE pin is no handled yet. 2003-01-06 02:20:47 +00:00
README - update date for pre4 release 2002-12-14 21:26:44 +00:00
README-plugins - rewrite header to describe what's in this file. 2002-12-21 16:23:52 +00:00
README-wxWindows - update 2002-12-21 16:13:11 +00:00
state_file.cc - apply patch.memleaks-tominac from Darko Tominac <darko.tominac@zg.tel.hr> 2001-12-21 19:33:18 +00:00
state_file.h Add plugin support to Bochs by merging all the changes from the 2002-10-24 21:07:56 +00:00
test-x11-fonts - add a script that tests whether your vga font is installed. 2001-09-30 14:53:57 +00:00
TESTFORM.txt - just leave a blank for the version number. I'm never going to remember to 2002-12-17 21:31:03 +00:00
win32res.rc - new application icon for the win32 gui using 'bochs.ico' 2002-12-26 18:24:41 +00:00
wxbochs.rc - new application icon for wxMSW using 'bochs.ico' 2002-12-25 17:13:45 +00:00

Bochs x86 Pentium Emulator
Updated: Sat Dec 14 16:28:25 EST 2002
Version: 2.0.pre4

WHAT IS BOCHS?

Bochs is a highly portable open source IA-32 (x86) PC emulator
written in C++, that runs on most popular platforms.  It includes
emulation of the Intel x86 CPU, common I/O devices, and a custom
BIOS.  Currently, bochs can be compiled to emulate a 386, 486 or
Pentium CPU.  Bochs is capable of running most Operating Systems
inside the emulation including Linux, Windows 95, DOS, and 
Windows NT 4.  Bochs was written by Kevin Lawton and is currently 
maintained by the Bochs project at "http://bochs.sourceforge.net".

Bochs can be compiled and used in a variety of modes, some which are
still in development.  The 'typical' use of bochs is to provide
complete x86 PC emulation, including the x86 processor, hardware
devices, and memory.  This allows you to run OS's and software within
the emulator on your workstation, much like you have a machine
inside of a machine.  Bochs will allow you to run Win '95
applications on a Solaris machine with X11, for example.

Bochs is distributed under the GNU LGPL.  See COPYING for details.

GETTING CURRENT SOURCE CODE 

Source code for Bochs is available from the Bochs home page at
http://bochs.sourceforge.net.  You can download the most recent
release, use CVS to get the latest sources, or grab a CVS
snapshot which is updated nightly.  The releases contain the most
stable code, but if you want the very newest features try the
CVS version instead. 

WHERE ARE THE DOCS?

The Bochs documentation is written in Docbook.  Docbook is a text 
format that can be rendered to many popular browser formats such 
as HTML, PDF, and Postscript.  Each binary release contains the
HTML rendering of the documentation.  Also, you can view the
latest documentation on the web at
  http://bochs.sf.net/doc/docbook/index.html

Some information has not yet been transferred from the older
HTML docs.  These can be found at http://bochs.sf.net/docs-html

WHERE CAN I GET MORE INFORMATION?  HOW DO I REPORT PROBLEMS?

Both the documentation and the Bochs website have instructions on how 
to join the bochs-developers mailing list, which is the primary
forum for discussion of Bochs.  The main page of the website also
has links to bug reports and feature requests.  You can browse and
add to the content in these areas even if you do not have a (free)
SourceForge account.  We need your feedback so that we know what
parts of Bochs to improve.  

There is a patches section on the web site too, if you have made
some changes to Bochs that you want to share.

HOW CAN I HELP?

If you would like contribute to the Bochs project, a good first step
is to join the bochs-developers mailing list, and read the archive
of recent messages to see what's going on.  

If you are a technical person (can follow hardware specs, can write
C/C++) take a look at the list of open bug reports and feature
requests to see if you are interested in working on any of the
problems that are mentioned in them.  If you check out the CVS
sources, make some changes, and create a patch, one of the
developers will be very happy to apply it for you.  Developers who
frequently submit patches, or who embark on major changes in the
source can get write access to CVS.  Be sure to communicate with the
bochs-developers list to avoid several people working on the same
thing without realizing it.

If you are a Bochs user, not a hardware/C++ guru, there are still
many ways you could help out.  For example:
  - write instructions on how to install a particular operating system
  - writing/cleaning up documentation
  - testing out Bochs on every imaginable operating system and 
    reporting how it goes.