Bochs/bochs
Volker Ruppert 1073eaf524 - sending data to printer causes a BX_ERROR when offline
- untrigger_irq() seems to be necessary, so I add it again
2002-01-18 16:33:07 +00:00
..
bios - romscan routine from plex86 BIOS integrated 2002-01-15 21:22:00 +00:00
build - add entry for 1.3 2001-12-10 19:59:10 +00:00
cpu - clarify panic message. It panics if HLT is executed from segment 0xf000, 2001-11-18 16:32:40 +00:00
debug added the trace-reg-on and trace-reg-off commands 2001-11-28 18:40:02 +00:00
disasm - use @CPP_SUFFIX@ substitution to get the dependencies right for nmake too 2001-10-07 20:19:04 +00:00
doc . Added a keyboard_type option in the conf file 2001-12-12 10:38:39 +00:00
docs-html - eliminate top level list so that I can put <a name=""> anchors 2001-12-10 14:53:27 +00:00
dynamic - apply VPATH patch from Edouard G. Parmelan, posted to list on September 1 2001-09-14 04:19:08 +00:00
font - add RCS Id to header of every file. This makes it easier to know what's 2001-10-03 13:10:38 +00:00
fpu - use @CPP_SUFFIX@ substitution to get the dependencies right for nmake too 2001-10-07 20:19:04 +00:00
gui - clean up comment 2002-01-07 16:30:43 +00:00
instrument - add RCS Id to header of every file. This makes it easier to know what's 2001-10-03 13:10:38 +00:00
iodev - sending data to printer causes a BX_ERROR when offline 2002-01-18 16:33:07 +00:00
memory - apply patch.pci from Volker Ruppert. See 2001-11-14 01:39:22 +00:00
misc - use floating point when computing # of cylinders. The expression 2001-12-08 17:46:02 +00:00
patches - patch is checked in 2002-01-16 16:43:57 +00:00
.bochsrc - .bochsrc said "keymap" instead of "map" which didn't match main.cc 2002-01-08 15:38:28 +00:00
.conf.AIX.4.3.1 Added a config file for AIX 4.3.1. 2001-04-11 09:07:55 +00:00
.conf.amigaos - I was stupid and wrote "enable-amigaos" instead of "with-amigaos". Fixed. 2001-12-12 03:48:48 +00:00
.conf.beos-x86-preR4 - entered original Bochs snapshot bochs-2000_0325a.tar.gz from 2001-04-10 01:04:59 +00:00
.conf.beos-x86-R4 - entered original Bochs snapshot bochs-2000_0325a.tar.gz from 2001-04-10 01:04:59 +00:00
.conf.linux - use gcc instead of egcs, since gcc is much more standard. Using a 2001-10-07 21:23:00 +00:00
.conf.macos - use gcc instead of egcs, since gcc is much more standard. Using a 2001-10-07 21:23:00 +00:00
.conf.macosx - fix obsolete, incorrect comment 2001-12-11 13:42:23 +00:00
.conf.sparc - entered original Bochs snapshot bochs-2000_0325a.tar.gz from 2001-04-10 01:04:59 +00:00
.conf.win32 - entered original Bochs snapshot bochs-2000_0325a.tar.gz from 2001-04-10 01:04:59 +00:00
.conf.win32-cygwin - add cdrom and sb16 since .conf.win32-vcpp has those too 2001-11-16 14:23:17 +00:00
.conf.win32-vcpp - explictly turn off readline. Then if you add --enable-debugger, it will 2001-11-21 00:16:17 +00:00
.conf.x86 - use gcc instead of egcs, since gcc is much more standard. Using a 2001-10-07 21:23:00 +00:00
bochs.h - Added XFree86 keyboard mapping (us, fr, de) 2001-12-14 17:56:37 +00:00
Bochs.proj.hqx - entered original Bochs snapshot bochs-2000_0325a.tar.gz from 2001-04-10 01:04:59 +00:00
bochs.rsrc.hqx - entered original Bochs snapshot bochs-2000_0325a.tar.gz from 2001-04-10 01:04:59 +00:00
bxversion.h.in - I have tried to make the --prefix argument to configure control 2001-11-10 03:48:22 +00:00
CHANGES - update for 1.3 2001-12-10 21:53:21 +00:00
config.h.in - Dave enabled the E9 hack in config.h.in, but it had no effect. The correct 2001-12-05 16:25:24 +00:00
configure - apparantly freebsd works with linux sound code. Now you can type 2002-01-16 19:52:28 +00:00
configure.in - apparantly freebsd works with linux sound code. Now you can type 2002-01-16 19:52:28 +00:00
COPYING - entered original Bochs snapshot bochs-2000_0325a.tar.gz from 2001-04-10 01:04:59 +00:00
install-x11-fonts.in - install as vga.pcf.gz, without first copying to vga.pcf and gzipping. 2001-12-08 15:18:28 +00:00
load32bitOShack.cc - add RCS Id to header of every file. This makes it easier to know what's 2001-10-03 13:10:38 +00:00
logio.cc - remove broken code that deletes the "io" object. Since all logfunctions 2002-01-07 16:10:11 +00:00
macintosh.txt - added strdup replacement function to osdep 2001-04-10 02:02:05 +00:00
main.cc - bx_init_hardware(): don't update the log actions if control panel is enabled 2002-01-02 09:57:58 +00:00
Makefile.in - include niclist and bochsdbg (debug enabled version) 2001-12-10 21:31:20 +00:00
osdep.cc - add RCS Id to header of every file. This makes it easier to know what's 2001-10-03 13:10:38 +00:00
osdep.h - remove my ill-conceived configure test for wsprintf. It really is 2001-10-05 13:52:25 +00:00
pc_system.cc - implementation of transfer type 0 (verify) - dma write without writing to memory 2001-12-26 14:56:15 +00:00
pc_system.h - implementation of transfer type 0 (verify) - dma write without writing to memory 2001-12-26 14:56:15 +00:00
README - update for 1.3 2001-12-10 21:53:21 +00:00
state_file.cc - apply patch.memleaks-tominac from Darko Tominac <darko.tominac@zg.tel.hr> 2001-12-21 19:33:18 +00:00
state_file.h - add RCS Id to header of every file. This makes it easier to know what's 2001-10-03 13:10:38 +00:00
test-x11-fonts - add a script that tests whether your vga font is installed. 2001-09-30 14:53:57 +00:00
TESTFORM.txt - add keyboard 2001-06-04 23:06:33 +00:00
win32.txt - updated instructions for compiling under win32 2001-05-30 18:24:48 +00:00

Bochs x86 Pentium Emulator
Upated: Mon Dec 10 16:54:43 PDT 2001
Version: 1.3

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 has been overhauled, and it is now
distributed in a separate package called bochsdoc-VERSION.tar.gz.
A copy is also online at 
  http://bochs.sf.net/doc/docbook/alldocs.html
For now, the old documentation can still 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.