Bochs/bochs
Volker Ruppert eebdc22a1c - applied patches included in SF documentation requests by Alexander Schuch
#1061680: added more configure options, changed wxWindows to wxWidgets,
            fixed some typo's
  #1062638: added more description to "The Bochs headerbar"
2004-11-18 19:35:23 +00:00
..
bios - boot sequence with up to 3 boot devices inplemented. The sequence is stored 2004-10-15 15:37:01 +00:00
build - the user documentation has replaced this file in release packages 2004-08-23 08:39:12 +00:00
bx_debug debugger help text typo fix 2004-11-15 10:43:39 +00:00
cpu Fix CS.base register after #RESET 2004-11-16 19:19:13 +00:00
disasm everal fixes in disasm 2004-10-22 22:56:59 +00:00
doc - applied patches included in SF documentation requests by Alexander Schuch 2004-11-18 19:35:23 +00:00
docs-html Fixed incompatibility with gcc3.3, I think. 2003-11-28 15:07:29 +00:00
dynamic
font
fpu Fixed compilation warnings (g++, -Wall) 2004-11-04 22:41:24 +00:00
gui - vbe update code now uses the new graphics API 2004-11-06 17:03:44 +00:00
host/linux/pcidev - fixed possible memory leaks and compilation warnings (patch by Frank Cornelis) 2004-11-16 20:44:48 +00:00
instrument
iodev Fix CS.base register after #RESET 2004-11-16 19:19:13 +00:00
memory Fix CS.base register after #RESET 2004-11-16 19:19:13 +00:00
misc - looks like <sys/io.h> isn't standardised. Now check for glibc-based systems 2004-09-07 18:31:38 +00:00
patches Merge and commit patch.apic-zwane from CVS patches directory. 2004-09-15 21:48:57 +00:00
plex86 - support for GNU/kFreeBSD and GNU/kNetBSD added in lowlevel iodev code (cdrom, 2004-09-11 15:39:53 +00:00
.bochsrc - gdbstub support turned into a runtime option (SF patch #1021740 by Charles Duffy) 2004-11-06 10:50:03 +00:00
.conf.AIX.4.3.1
.conf.amigaos
.conf.beos
.conf.everything added new option --enable-show-ips to configure -> allow to enable BX_SHOW_IPS through configure script 2004-10-16 21:17:44 +00:00
.conf.linux Increased optimization from -O2 to -O3. 2004-01-15 03:17:37 +00:00
.conf.macos Added Brian Huffman's Sound for OSX code with a couple of tweaks. 2004-02-09 22:59:22 +00:00
.conf.macosx workaround autoconf bug 2004-02-22 04:14:10 +00:00
.conf.sparc
.conf.win32
.conf.win32-cygwin Merge softfloat-fpu-implementation_ver4_branch branch 2004-06-18 14:11:11 +00:00
.conf.win32-vcpp - applied SF patch #867045 from m_suzu_abc@yahoo.co.jp 2004-08-18 11:52:25 +00:00
aclocal.m4
bochs.h - gdbstub support turned into a runtime option (SF patch #1021740 by Charles Duffy) 2004-11-06 10:50:03 +00:00
bxversion.h.in
CHANGES Fix CS.base register after #RESET 2004-11-16 19:19:13 +00:00
config.cc - gdbstub support turned into a runtime option (SF patch #1021740 by Charles Duffy) 2004-11-06 10:50:03 +00:00
config.guess
config.h.in - the PCI Pseudo-NIC is now independent from the NE2000 NIC stuff. New symbol 2004-10-03 20:06:12 +00:00
config.sub
configure Fix typo 2004-10-23 19:31:13 +00:00
configure.in Fix typo 2004-10-23 19:31:13 +00:00
COPYING
extplugin.h
gdbstub.cc - gdbstub support for MinGW toolchains (SF patch #970929 by Muranaka Masaki) 2004-11-01 17:14:02 +00:00
install-sh
load32bitOShack.cc Speed up compilation process. 2004-06-19 15:20:15 +00:00
logio.cc Fix compilation problem caused by 2004-10-05 18:59:20 +00:00
ltdl.c
ltdl.h
ltdlconf.h.in
ltmain.sh
main.cc - gdbstub support turned into a runtime option (SF patch #1021740 by Charles Duffy) 2004-11-06 10:50:03 +00:00
Makefile.in - gdbstub support for MinGW toolchains (SF patch #970929 by Muranaka Masaki) 2004-11-01 17:14:02 +00:00
osdep.cc - add check for vsnprintf availability and emulate with vsprintf if not found 2004-02-08 10:22:29 +00:00
osdep.h - fixed crash after debugger command 'show "call"' (mingw doesn't like %ll and 2004-09-19 18:38:09 +00:00
PARAM_TREE.txt
pc_system.cc - level sensitive irq mode prepared 2004-07-06 19:59:10 +00:00
pc_system.h - level sensitive irq mode prepared 2004-07-06 19:59:10 +00:00
plex86-interface.cc
plex86-interface.h
plugin.cc - configure / compile fixes for Solaris SunPro (patch from Robin Kay) 2004-08-11 11:09:01 +00:00
plugin.h - temporary pci irq initialisation removed from pci devices (now done in the 2004-09-25 22:15:02 +00:00
README - update to 2.1.1 version 2004-02-15 14:21:19 +00:00
README-plugins
README-wxWindows
README.rfb - remove GPL'd rfbproto.h 2004-04-05 12:09:25 +00:00
state_file.cc
state_file.h
TESTFORM.txt
TODO - commit long due "roadmap/todo", from my post and comments in the ml 2004-03-15 13:20:15 +00:00
win32res.rc - SB16 options dmatimer and loglevel now available at runtime (wx and win32) 2004-05-23 10:47:00 +00:00
wxbochs.rc

Bochs x86 Pentium+ Emulator
Updated: : Sun Feb  8 17:22:07 CET 2004
Version: 2.1.1

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,
Pentium, Pentium Pro or AMD64 CPU, including optional MMX, SSE, 
SSE2 and 3DNow instructions.  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.