Bochs/bochs
2019-10-14 14:54:07 +00:00
..
bios Some work on the i440BX chipset AGP support in the Bochs BIOS. 2018-05-03 17:55:17 +00:00
build Updated both MSVC workspace files for current SVN (added DDC files). 2018-05-04 21:21:51 +00:00
bx_debug fixed dbg message when stop/continue watchpoints 2018-10-16 18:08:44 +00:00
cpu more faststring cleanup 2019-10-14 14:54:07 +00:00
disasm disasm updates 2019-02-08 16:28:51 +00:00
doc Documentation updates (i440BX chipset / Voodoo AGP adapters). 2018-05-06 16:31:56 +00:00
docs-html
gui Check if Xrandr extension is present. 2019-04-21 20:08:32 +00:00
host/linux/pcidev
instrument
iodev Added ATAPI command "get event status notification" (patch by Ben Lunt). 2019-04-22 18:54:04 +00:00
memory Some fixes for MSVC. 2018-05-21 16:11:46 +00:00
misc Added sector size option in bximage for creating flat, sparse and growing mode 2018-03-30 21:04:04 +00:00
patches Updated user plugin example. 2017-01-28 20:31:18 +00:00
.bochsrc Fixed Banshee status reading via MMIO (unaligned access is allowed). 2018-05-03 19:46:12 +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 Continued release preparations: 2017-03-24 18:23:07 +00:00
.conf.macos Continued release preparations: 2017-03-24 18:23:07 +00:00
.conf.macosx Continued release preparations: 2017-03-24 18:23:07 +00:00
.conf.nothing
.conf.sparc
.conf.win32-cygwin Continued release preparations: 2017-03-24 18:23:07 +00:00
.conf.win32-vcpp Continued release preparations: 2017-03-24 18:23:07 +00:00
aclocal.m4
bochs.h Moved all Bochs multi-threading definitions from bochs.h and osdep.h to a new 2017-09-10 15:55:13 +00:00
bxdisasm_new.cc added compilation instructions for bxdisasm_new.cc 2017-12-13 20:27:02 +00:00
bxdisasm_old.cc distinguish between vzeroupper/vzeroall in old legacy disasm 2017-12-28 20:20:13 +00:00
bxthread.cc Added SDL / SDL2 specific multi-threading support. If one of these guis is 2017-09-16 22:01:49 +00:00
bxthread.h Added SDL / SDL2 specific multi-threading support. If one of these guis is 2017-09-16 22:01:49 +00:00
bxversion.h.in
bxversion.rc.in
CHANGES add Icelake-U model to CPUDB database. TODO: verify its VMX features 2019-09-24 20:26:14 +00:00
config.cc Added support for unlocking disk images (locks leftover from previous Bochs 2018-05-11 07:44:49 +00:00
config.guess
config.h.in Check if Xrandr extension is present. 2019-04-21 20:08:32 +00:00
config.sub
configure Check if Xrandr extension is present. 2019-04-21 20:08:32 +00:00
configure.in Check if Xrandr extension is present. 2019-04-21 20:08:32 +00:00
COPYING
cpudb.h add Icelake-U model to CPUDB database. TODO: verify its VMX features 2019-09-24 20:26:14 +00:00
crc.cc
extplugin.h Preparing improved VGA extension support and some VGA / Cirrus cleanups. 2017-10-10 18:06:16 +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 Added symbol BX_LOAD32BITOSHACK to disable this legacy feature. With the 2017-04-17 13:26:44 +00:00
logio.cc Moved all Bochs multi-threading definitions from bochs.h and osdep.h to a new 2017-09-10 15:55:13 +00:00
ltdl-bochs.h
ltdl.c
ltdlconf.h.in
ltmain.sh
main.cc patch by Luigu.B - significantly speedup multi-threaded guest simulation 2019-08-09 19:57:13 +00:00
Makefile.in small change to extract ia_opcodes.h from instr.h to dedicated file. this would remove compilation dep of all files on ia_opcodes.h (now called ia_opcdes.def). regenerating dep ober all files in Makefiles.in 2017-10-19 21:27:25 +00:00
msrs.def
osdep.cc Moved all Bochs event / wait functions required for multi-threading to a new 2017-09-14 16:18:12 +00:00
osdep.h Some fixes for MSVC. 2018-05-21 16:11:46 +00:00
param_names.h Added support for unlocking disk images (locks leftover from previous Bochs 2018-05-11 07:44:49 +00:00
PARAM_TREE.txt Prepared config interface for a hard disk sector size option. 2018-03-13 20:35:56 +00:00
pc_system.cc Prepared devices and timer code for HPET support 2017-04-15 20:31:07 +00:00
pc_system.h Prepared devices and timer code for HPET support 2017-04-15 20:31:07 +00:00
plugin.cc Preparing improved VGA extension support and some VGA / Cirrus cleanups. 2017-10-10 18:06:16 +00:00
plugin.h Added support for driving the speaker line directly with the speaker gate, but 2018-05-10 10:50:42 +00:00
qemu-queue.h
README Preparing release 2.6.9 2017-04-09 06:45:39 +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
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 Apr  9 08:45:00 CEST 2017
Version: 2.6.9

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.