Bochs/bochs
2006-05-31 17:20:52 +00:00
..
bios Removed file until permission from ASUS (again) 2006-05-14 17:42:06 +00:00
build iUpdate MSDEV workspaces 2006-02-24 18:36:31 +00:00
bx_debug Fixed segfault with bochs debugger but reported today 2006-05-31 17:20:52 +00:00
cpu Handle more fields memory management insie the bx_param_c. 2006-05-30 17:01: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 Memory access handling explanation by Brendan 2006-03-06 06:32:03 +00:00
dynamic
font
fpu Changes list made after CVS service crash: 2006-04-05 17:31:35 +00:00
gui - save state handling rewritten similar to the win32dialog behaviour 2006-05-30 18:01:51 +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 Now devices could be compiled separatelly from CPU 2006-03-06 22:03:16 +00:00
iodev Avoid doing strdup for param name field - most of the strdups elliminated ! 2006-05-29 22:33:38 +00:00
memory Fixed segfault with bochs debugger but reported today 2006-05-31 17:20:52 +00:00
misc - added "reserved" floppy types 160k, 180k and 320k 2005-11-20 20:26:35 +00:00
patches Remove the patch, it was successfully merged to CVS 2006-03-16 20:38:32 +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 - 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 Merge SAVE_RESTORE branch to CVS 2006-05-27 15:54:49 +00:00
.conf.linux - enabled USB in shortcut scripts for the most popular platforms 2005-12-26 16:47:51 +00:00
.conf.macos - enabled USB in shortcut scripts for the most popular platforms 2005-12-26 16:47:51 +00:00
.conf.macosx - enabled USB in shortcut scripts for the most popular platforms 2005-12-26 16:47:51 +00:00
.conf.sparc - enabled USB in shortcut scripts for the most popular platforms 2005-12-26 16:47:51 +00:00
.conf.win32
.conf.win32-cygwin Fixed printing of 64-bit values forma. When compiling with cygwin with -mno-cygwin option the format should be like in MSVC 2006-01-17 18:17:01 +00:00
.conf.win32-vcpp - enabled USB in shortcut scripts for the most popular platforms 2005-12-26 16:47:51 +00:00
aclocal.m4 - implemented GTK2+ detection for wxGTK (patch by Guillem Jover <guillem@debian.org>) 2006-03-13 17:18:33 +00:00
bochs.h Several x86-64 MSRs were not-initilized ! 2006-05-28 17:07:57 +00:00
bxversion.h.in
CHANGES Update CHANGES 2006-05-27 20:29:11 +00:00
config.cc Handle more fields memory management insie the bx_param_c. 2006-05-30 17:01:27 +00:00
config.guess
config.h.in Fixed segfault with bochs debugger but reported today 2006-05-31 17:20:52 +00:00
config.sub
configure Merge SAVE_RESTORE branch to CVS 2006-05-27 15:54:49 +00:00
configure.in Merge SAVE_RESTORE branch to CVS 2006-05-27 15:54:49 +00:00
COPYING
crc.cc This is cumulative patch for bochs debugger, it is only very first step towards working debugger supporting all new simulator functionalitieS. 2006-01-24 19:03:55 +00:00
extplugin.h
gdbstub.cc Enable show-param support in debugger. 2006-05-30 19:46:31 +00:00
install-sh
load32bitOShack.cc Preliminary implemntation of SMM save statei 2006-03-27 18:02:07 +00:00
logio.cc Handle more fields memory management insie the bx_param_c. 2006-05-30 17:01:27 +00:00
ltdl.c
ltdl.h
ltdlconf.h.in
ltmain.sh
main.cc Enable show-param support in debugger. 2006-05-30 19:46:31 +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 Remove redundant 0x from FMT_ADDRX macro for cygwin 2006-02-11 20:47:22 +00:00
PARAM_TREE.txt - remaining config options and special menus added to parameter tree 2006-03-05 10:24:29 +00:00
pc_system.cc Avoid doing strdup for param name field - most of the strdups elliminated ! 2006-05-29 22:33:38 +00:00
pc_system.h Merge SAVE_RESTORE branch to CVS 2006-05-27 15:54: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 Merge SAVE_RESTORE branch to CVS 2006-05-27 15:54:49 +00:00
plugin.h Merge SAVE_RESTORE branch to CVS 2006-05-27 15:54:49 +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 Do not allow to allocate more than 2048Mb of emulated memory. 2005-03-06 21:23:38 +00:00
TODO My update of TODO 2006-01-21 17:19:46 +00:00
win32res.rc - updated save/restore stuff in the win32 runtime dialog 2006-05-28 08:49:20 +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.