Bochs/bochs
2005-04-13 18:39:26 +00:00
..
bios - APM support for 16 bit protected mode added (patch from Struan Bartlett) 2005-04-06 18:05:47 +00:00
build - updated win32 installer for NSIS 2.03 (Modern UI) 2005-03-20 14:29:23 +00:00
bx_debug Fixed logic bug caused SIGSEGV in debugger when gcc 3.4.0 is used. 2005-04-10 19:53:42 +00:00
cpu Fixed compilation problem in segment_ctrl.pro 2005-04-13 17:13:05 +00:00
disasm small optimization in disasm code 2004-12-15 17:15:43 +00:00
doc - updates from SF documenation request #1175567 by Alexander Schuch 2005-04-03 10:47:01 +00:00
docs-html - added new section "Building a Bochs release" in development.dbk and removed 2005-03-28 08:56:07 +00:00
dynamic
font
fpu Add CVS header for FPU files 2005-03-20 21:19:38 +00:00
gui - status bar text support added 2005-04-07 19:08:01 +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 Extend Bochs instrumentation 2005-03-17 20:50:57 +00:00
iodev - cpu-to-video transparent colorexpand function renamed and implementation completed 2005-04-13 18:39:26 +00:00
memory Separate pageWriteStamp from ICACHE. The pageWriteStamp has totally independant structure and could be used in future with icache structure. Also it could be significantly speeded up using BX_SMF analog constructions. 2005-04-10 19:42:48 +00:00
misc Feature request 2005-01-28 10:25:06 +00:00
patches Added CVS version header to all the files. 2005-03-19 20:44:01 +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 Fixed compilation problem in segment_ctrl.pro 2005-04-13 17:13:05 +00:00
.conf.AIX.4.3.1
.conf.amigaos
.conf.beos
.conf.everything .conf.everything should be platform independent 2005-03-21 19:14:40 +00:00
.conf.linux - use autodetection version of the SB16 configure option 2005-03-22 16:44:24 +00:00
.conf.macos - use autodetection version of the SB16 configure option 2005-03-22 16:44:24 +00:00
.conf.macosx - use autodetection version of the SB16 configure option 2005-03-22 16:44:24 +00:00
.conf.sparc
.conf.win32
.conf.win32-cygwin - use autodetection version of the SB16 configure option 2005-03-22 16:44:24 +00:00
.conf.win32-vcpp - removed obsolete configure option --with-win32-vcpp. The shortcut script 2005-03-28 10:26:14 +00:00
aclocal.m4 - changed wxWindows to wxWidgets (includes SF patch #1094407 by Alexander Schuch) 2005-01-05 19:54:32 +00:00
bochs.h - BX_GDBSTUB and BX_SUPPORT_X86_64 are always defined in config.h 2005-03-16 16:36:31 +00:00
bxversion.h.in
CHANGES Update changes 2005-03-30 21:50:24 +00:00
config.cc - parsing of comX, parportX and usbX options simplified similar to ataX options 2005-04-03 15:00:44 +00:00
config.guess
config.h.in Forgot to update config.h.in ... 2005-03-29 22:01:22 +00:00
config.sub
configure - the variable $cross_configure is now set to yes if $cross_compiling returns 2005-03-30 16:41:31 +00:00
configure.in - the variable $cross_configure is now set to yes if $cross_compiling returns 2005-03-30 16:41:31 +00:00
COPYING
extplugin.h
gdbstub.cc - BX_GDBSTUB and BX_SUPPORT_X86_64 are always defined in config.h 2005-03-16 16:36:31 +00:00
install-sh
load32bitOShack.cc Merged patch 2005-01-19 18:21:40 +00:00
logio.cc - removed old unused code designed for a save/restore feature 2004-12-13 19:10:38 +00:00
ltdl.c
ltdl.h
ltdlconf.h.in
ltmain.sh
main.cc Separate pageWriteStamp from ICACHE. The pageWriteStamp has totally independant structure and could be used in future with icache structure. Also it could be significantly speeded up using BX_SMF analog constructions. 2005-04-10 19:42:48 +00:00
Makefile.in - use 'install' instead of 'cp' during installation (based on SF patch #1152808 2005-03-05 21:02:59 +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 - Busmaster DMA fuction implemented, but disabled for now. BM-DMA works in Linux, 2005-02-08 18:32:27 +00:00
README - fixed typo 2005-03-31 16:57:32 +00:00
README-plugins
README-wxWindows
README.rfb - remove GPL'd rfbproto.h 2004-04-05 12:09:25 +00:00
TESTFORM.txt Do not allow to allocate more than 2048Mb of emulated memory. 2005-03-06 21:23:38 +00:00
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: Fri Mar 25 10:33:15 CET 2005
Version: 2.2.pre2

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, DOS,
Windows 95/98 and Windows NT/2000.  
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.