Bochs/bochs
2017-03-23 19:09:37 +00:00
..
bios Recompiled after MP table fix. 2017-03-02 18:39:35 +00:00
build Added symbol VSIDE in the MSVC workspace files and and the manifest section 2017-03-19 12:22:27 +00:00
bx_debug Fixed compilation errors that occur with debugger enabled. 2016-12-06 18:07:05 +00:00
cpu Updated build test script and fixed compilation without FPU. 2017-03-19 09:50:16 +00:00
disasm extracted fetchdecode into separated folder under cpu and also out of BX_CPU_C class into stand-alone module. Next step: wrap it up nicely and define clear interace to CPU model to minimize dependencies. Ideally I need fetchdecode to not include CPU at all 2016-06-12 21:23:48 +00:00
doc Some cleanups in in the user documentation and the code (obsolete stuff). 2017-03-23 19:09:37 +00:00
docs-html
gui Some cleanups in in the user documentation and the code (obsolete stuff). 2017-03-23 19:09:37 +00:00
host/linux/pcidev
instrument fixed compliation err 2015-10-26 17:49:45 +00:00
iodev Fixed Cirrus VGA PCI save/restore when a standard VGA mode is active. The PCI 2017-03-22 21:24:30 +00:00
memory Simplified code for the "optromimage" and "optramimage" options stuff (saving 2017-02-14 20:11:58 +00:00
misc Documentation updates. 2017-03-19 19:08:15 +00:00
patches Updated user plugin example. 2017-01-28 20:31:18 +00:00
.bochsrc Some cleanups in in the user documentation and the code (obsolete stuff). 2017-03-23 19:09:37 +00:00
.conf.amigaos
.conf.everything The USB EHCI and xHCI emulations are now almost stable, so we can remove 2016-12-31 12:17:37 +00:00
.conf.linux The USB EHCI and xHCI emulations are now almost stable, so we can remove 2016-12-31 12:17:37 +00:00
.conf.macos The USB EHCI and xHCI emulations are now almost stable, so we can remove 2016-12-31 12:17:37 +00:00
.conf.macosx The USB EHCI and xHCI emulations are now almost stable, so we can remove 2016-12-31 12:17:37 +00:00
.conf.nothing
.conf.sparc
.conf.win32-cygwin The USB EHCI and xHCI emulations are now almost stable, so we can remove 2016-12-31 12:17:37 +00:00
.conf.win32-vcpp The USB EHCI and xHCI emulations are now almost stable, so we can remove 2016-12-31 12:17:37 +00:00
aclocal.m4
bochs.h Added macro BX_FATAL() that works like BX_PANIC(), but with hardcoded action 2016-12-30 10:04:06 +00:00
bxversion.h.in
bxversion.rc.in Fixed template for the win32 version information. 2014-05-15 21:19:54 +00:00
CHANGES Some release preparations: 2017-03-21 20:12:07 +00:00
config.cc Some cleanups in in the user documentation and the code (obsolete stuff). 2017-03-23 19:09:37 +00:00
config.guess
config.h.in Added ethernet module 'socket'. designed to connect two Bochs instances with 2017-02-27 22:26:43 +00:00
config.sub Added Android host platform support to Bochs based on SF patch #534. 2016-08-12 17:06:14 +00:00
configure Some release preparations: 2017-03-21 20:12:07 +00:00
configure.in Some release preparations: 2017-03-21 20:12:07 +00:00
COPYING
cpudb.h reorg of cpudb folder, added AMD Ryzen CPUID placeholder module (still not 100% correct) 2017-03-13 19:44:14 +00:00
crc.cc
extplugin.h Rewrite of the network driver plugin code. 2017-03-12 07:48:08 +00:00
gdbstub.cc For each WSAStartup() we have to call WSACleanup() on exit. 2017-03-06 21:30:05 +00:00
install-sh
LICENSE
load32bitOShack.cc fixed problems found by cppcheck tool (patch by Maxim Derbasov) 2015-01-03 13:53:52 +00:00
logio.cc Added macro BX_FATAL() that works like BX_PANIC(), but with hardcoded action 2016-12-30 10:04:06 +00:00
ltdl-bochs.h
ltdl.c fixed problems found by cppcheck tool (patch by Maxim Derbasov) 2015-01-03 13:53:52 +00:00
ltdlconf.h.in
ltmain.sh
main.cc Modified plugin system to support the new PLUGTYPE_GUI. 2017-02-18 16:28:04 +00:00
Makefile.in Reverted 'clean' target optimization. MinGW/MSYS uses targets without ".exe", 2017-03-18 09:27:48 +00:00
msrs.def
osdep.cc c++ better to use new/delete and not malloc 2016-12-05 19:05:31 +00:00
osdep.h Fixed some MSVC warnings in the debugger code. 2014-12-23 11:53:35 +00:00
param_names.h Simplified code for the "optromimage" and "optramimage" options stuff (saving 2017-02-14 20:11:58 +00:00
PARAM_TREE.txt Preparing Bochs release 2.6.8 2015-05-03 06:36:30 +00:00
pc_system.cc fixed %d->%u format found by cppcheck (patch by Maxim Derbasov) 2015-01-25 21:24:13 +00:00
pc_system.h Fixed OPL chip detection. 2014-12-31 12:27:32 +00:00
plugin.cc Implemented self-registering static objects in the lowlevel sound code similar 2017-03-14 18:21:05 +00:00
plugin.h Network and sound driver plugins are no devmodel devices. 2017-03-17 20:53:31 +00:00
qemu-queue.h Added QEMU queue macros (required for EHCI) as a separate file. Removed already 2016-01-08 18:58:27 +00:00
README Preparing Bochs release 2.6.8 2015-05-03 06:36:30 +00:00
README-plugins
README-wxWidgets
README.rfb
TESTFORM.txt
TODO Some release preparations: 2017-03-21 20:12:07 +00:00
win32_enh_dbg.rc Added capability to use the gui debugger output window as a log viewer 2014-01-13 21:31:14 +00:00
win32res.rc Added symbol VSIDE in the MSVC workspace files and and the manifest section 2017-03-19 12:22:27 +00:00
wxbochs.rc

Bochs - The cross platform IA-32 (x86) emulator
Updated: Sun May  3 08:36:00 CEST 2015
Version: 2.6.8

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. Bochs can be compiled to emulate many different x86 CPUs,
from early 386 to the most recent x86-64 Intel and AMD processors
which may even not reached the market yet. Bochs is capable of running
most Operating Systems inside the emulation, for example DOS,
Linux or Windows. 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 Windows
applications on a Solaris machine with X11, for example.

Bochs is distributed under the GNU LGPL. See LICENSE and 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 SVN to get the latest sources, or grab a SVN
snapshot which is updated frequently. The releases contain the most
stable code, but if you want the very newest features try the
SVN 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

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