Bochs/bochs
Christophe Bothamy 3104ba6bea - fix [ 625878 ] reset doesn't reset something(?)
In bx_cpu_c::reset method I set bx_cpu->async_event to 2
  so execution in the cpu_loop gets stopped early.

  Previously, async_event was set to 0, and with repeatable
  instructions, after reset, eip was incremented by the instruction
  length, so execution would resume at 0xffffX (X being >0, the current
  instruction length).

  In halt state I check now for reset with async_event is 2, so
  reset works also when the cpu is halted. (update to Peter change)

  I hope I fixed this the right way, please report any strange behaviour.
2002-11-21 08:08:29 +00:00
..
bios *** empty log message *** 2002-11-21 06:41:39 +00:00
build - rename bochsrc.txt to bochsrc.bxrc, and remove the .bat file so that 2002-11-21 08:01:54 +00:00
cpu - fix [ 625878 ] reset doesn't reset something(?) 2002-11-21 08:08:29 +00:00
debug - move call to update_drive_status_buttons until after hardware init. 2002-11-20 19:34:51 +00:00
disasm
doc Added the first Method for Installing Windows 98 as a guest OS. 2002-11-21 03:34:15 +00:00
docs-html
dynamic
font
fpu
gui - change to nmake compatible lines (from Psyon) 2002-11-20 20:36:05 +00:00
instrument - change BX_SREG_CS to BX_SEG_REG_CS 2002-11-20 17:55:41 +00:00
iodev - change to nmake compatible lines (from Psyon) 2002-11-20 20:36:05 +00:00
memory
misc - on WIN32 wait for a key, whether we exit with an error or not. 2002-11-21 06:36:22 +00:00
patches - add SVGAlib patch from Igor Popik <igipop@wsfiz.edu.pl> 2002-11-21 01:31:12 +00:00
.bochsrc
.conf.AIX.4.3.1
.conf.amigaos
.conf.beos
.conf.everything - everything now includes --enable-instrumentation 2002-11-20 23:31:45 +00:00
.conf.linux
.conf.macos
.conf.macosx
.conf.sparc
.conf.win32
.conf.win32-cygwin
.conf.win32-vcpp
aclocal.m4
bochs.h
bochs.rsrc.hqx
bxversion.h.in
CHANGES
config.guess
config.h.in
config.sub
configure - add NSIS makefile 2002-11-21 03:50:59 +00:00
configure.in - add NSIS makefile 2002-11-21 03:50:59 +00:00
COPYING
extplugin.h
gdbstub.cc
install-sh
install-x11-fonts.in
load32bitOShack.cc
logio.cc
ltdl.c
ltdl.h
ltdlconf.h.in
ltmain.sh
macintosh.txt
main.cc - move call to update_drive_status_buttons until after hardware init. 2002-11-20 19:34:51 +00:00
Makefile.in - rename VGABIOS-lgpl-README to .txt as well 2002-11-21 06:38:56 +00:00
osdep.cc
osdep.h
pc_system.cc
pc_system.h
plugin.cc
plugin.h - fix args of DEV_ne2k_print_info (there should be 4, not 0) 2002-11-20 19:44:05 +00:00
README
README-plugins
README-wxWindows
state_file.cc
state_file.h
test-x11-fonts
TESTFORM.txt
win32.txt
wxbochs.rc

Bochs x86 Pentium Emulator
Updated: Tue Nov 19 11:13:15 EST 2002
Version: 2.0.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 or
Pentium CPU.  Bochs is capable of running most Operating Systems
inside the emulation including Linux, Windows 95, DOS, and 
Windows NT 4.  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 Win '95
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 in transition between the old documentation
written in HTML and the new documentation written in Docbook format.
The new documentation is online at
  http://bochs.sf.net/doc/docbook/alldocs.html
and it is the most current.  Some information has not yet been
transferred from the old HTML docs.  This 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:
  - improving win32 binary releases
  - building up a set of useful tools to include in those releases
  - writing/cleaning up documentation
  - testing out Bochs on every imaginable operating system and 
    reporting how it goes.