Bochs/bochs
2006-05-22 21:17:27 +00:00
..
bios Removed file until permission from ASUS (again) 2006-05-14 17:42:06 +00:00
build
bx_debug Fix 'instrument stop' command 2006-05-21 16:48:05 +00:00
cpu Fix amount of XMM registers in non-x86-64 mode 2006-05-22 21:17:27 +00:00
disasm - Code cleanup, remove x86-64 code from functions which cannot be called from x86-64 2006-05-12 17:04:19 +00:00
doc - updated CVS server name (new SF CVS infrastructure) 2006-05-14 09:16:29 +00:00
docs-html
dynamic
font
fpu Changes list made after CVS service crash: 2006-04-05 17:31:35 +00:00
gui - unicode fixes in the wx debugger 2006-05-22 16:35:03 +00:00
host/linux/pcidev
instrument
iodev Wow, I forgot to commit this change for NullTimer fixes ! 2006-05-18 19:57:11 +00:00
memory Veto direct write to the 0x000C0000 to 0x000EFFFF area 2006-04-29 16:55:22 +00:00
misc
patches Remove the patch, it was successfully merged to CVS 2006-03-16 20:38:32 +00:00
plex86
.bochsrc - Code cleanup, remove x86-64 code from functions which cannot be called from x86-64 2006-05-12 17:04:19 +00:00
.conf.AIX.4.3.1
.conf.amigaos
.conf.beos
.conf.everything Prepare configure support for SSE4 implemntation (coming soon) 2006-04-05 18:49:35 +00:00
.conf.linux
.conf.macos
.conf.macosx
.conf.sparc
.conf.win32
.conf.win32-cygwin
.conf.win32-vcpp
aclocal.m4 - implemented GTK2+ detection for wxGTK (patch by Guillem Jover <guillem@debian.org>) 2006-03-13 17:18:33 +00:00
bochs.h - get rid of the unused description field of shadow bool and data parameters 2006-05-14 15:47:37 +00:00
bxversion.h.in
CHANGES Update recent CPU CHANGES 2006-05-07 19:19:55 +00:00
config.cc Fix compilation 2006-04-25 15:59:20 +00:00
config.guess
config.h.in Removed icount guard for debugger. Implement STEPN debugger command using CPU_LOOP method capabilities 2006-04-29 09:27:49 +00:00
config.sub
configure Enable SEP by default for PII processor (P6+MMX) 2006-05-15 17:40:16 +00:00
configure.in Enable SEP by default for PII processor (P6+MMX) 2006-05-15 17:40:16 +00:00
COPYING
crc.cc
extplugin.h
gdbstub.cc I want to replace debugger ICOUNT guard by existent cpu_loop funtionality, first step to do that ... 2006-04-29 07:12:13 +00:00
install-sh
load32bitOShack.cc Preliminary implemntation of SMM save statei 2006-03-27 18:02:07 +00:00
logio.cc Update dependencies for iodev and root project folders. 2006-03-06 22:32:03 +00:00
ltdl.c
ltdl.h
ltdlconf.h.in
ltmain.sh
main.cc - get rid of the unused description field of shadow bool and data parameters 2006-05-14 15:47:37 +00:00
Makefile.in - save state function now supported on win32 in the runtime dialog 2006-04-09 13:55:55 +00:00
osdep.cc
osdep.h
PARAM_TREE.txt
pc_system.cc revert last change in pc_system.cc 2006-05-18 18:08:30 +00:00
pc_system.h Flush TLB for all CPUs when memory mapping information changed by system (A20 change, PAM write or similar events) 2006-04-29 17:21:49 +00:00
plex86-interface.cc Merge tss286 and tss386 segment descriptor cache fields to one structure 2006-05-21 20:41:48 +00:00
plex86-interface.h
plugin.cc - some more work for the save/restore feature in the plugins and devices code 2006-04-15 17:03:59 +00:00
plugin.h - some more work for the save/restore feature in the plugins and devices code 2006-04-15 17:03:59 +00:00
README Prepare configure support for SSE4 implemntation (coming soon) 2006-04-05 18:49:35 +00:00
README-plugins
README-wxWindows
README.rfb
TESTFORM.txt
TODO
win32res.rc - save state function now supported on win32 in the runtime dialog 2006-04-09 13:55:55 +00:00
wxbochs.rc

Bochs x86 Pentium+ Emulator
Updated: Sun Jan 29 09:48:00 CET 2006
Version: 2.2.6

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 x86-64 CPU, including optional MMX, 
SSE/SSE2/SSE3 and 3DNow! instructions.  Bochs is capable of running
most Operating Systems inside the emulation including Linux, DOS,
Windows 95/98 and Windows NT/2000/XP.
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 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.