~ [ source navigation ] ~ [ identifier search ] ~ [ freetext search ] ~ [ file search ] ~

Bochs x86 Emulator
bochs/

Version: ~ [ 2.3.5 ] ~ [ 2.3 ] ~
Name Size Last modified (GMT) Description
Folder CVS/ 2008-08-09 05:19:52
Folder bios/ 2008-08-09 05:19:53
Folder build/ 2008-08-09 05:19:53
Folder bx_debug/ 2008-08-09 05:19:56
Folder cpu/ 2008-08-09 05:19:58
Folder disasm/ 2008-08-09 05:19:58
Folder doc/ 2008-08-09 05:19:34
Folder docs-html/ 2008-08-09 05:20:00
Folder dynamic/ 2008-08-09 05:20:00
Folder font/ 2008-08-09 05:20:00
Folder fpu/ 2008-08-09 05:20:02
Folder gui/ 2008-08-09 05:20:04
Folder host/ 2008-08-09 05:19:39
Folder instrument/ 2008-08-09 05:20:07
Folder iodev/ 2008-08-09 05:20:11
Folder memory/ 2008-08-09 05:20:12
Folder misc/ 2008-08-09 05:20:12
Folder patches/ 2008-08-09 05:20:13
Folder plex86/ 2008-08-09 05:20:13
File CHANGES 121705 bytes 2006-08-27 07:06:01
File COPYING 26428 bytes 2001-04-10 01:04:08
File Makefile.in 30649 bytes 2006-04-09 13:55:53
File PARAM_TREE.txt 9196 bytes 2006-03-05 10:24:27
File README 3799 bytes 2006-08-27 07:18:30
File README-plugins 19128 bytes 2002-12-21 16:23:52
File README-wxWindows 13193 bytes 2002-12-21 16:13:11
File README.rfb 198 bytes 2004-04-05 12:09:25
File TESTFORM.txt 4231 bytes 2005-03-06 21:23:38
File TODO 12490 bytes 2006-08-25 11:58:55
File aclocal.m4 232561 bytes 2006-03-13 17:17:38
C file bochs.h 18190 bytes 2006-05-28 17:07:56
File bxversion.h.in 335 bytes 2001-11-10 03:45:53
C++ file config.cc 125412 bytes 2006-06-21 20:42:26
File config.guess 38470 bytes 2003-08-28 00:09:21
File config.h.in 29915 bytes 2006-06-21 20:42:26
File config.sub 29027 bytes 2003-08-28 00:09:21
File configure 1255137 bytes 2006-08-27 07:20:06
File configure.in 78484 bytes 2006-08-27 07:18:30
C++ file crc.cc 2431 bytes 2006-01-24 19:03:53
C file extplugin.h 1309 bytes 2002-12-12 15:28:37
C++ file gdbstub.cc 23008 bytes 2006-06-21 16:30:14
File install-sh 5598 bytes 2002-03-07 16:00:39
C++ file load32bitOShack.cc 9418 bytes 2006-03-27 18:02:06
C++ file logio.cc 15867 bytes 2006-06-12 19:51:31
C file ltdl.c 87739 bytes 2002-11-01 13:02:15
C file ltdl.h 12565 bytes 2002-10-24 21:04:37
File ltdlconf.h.in 4366 bytes 2002-10-24 21:04:38
File ltmain.sh 181013 bytes 2003-08-28 00:09:21
C++ file main.cc 40634 bytes 2006-07-21 18:26:53
C++ file osdep.cc 9538 bytes 2006-08-07 17:59:15
C file osdep.h 6278 bytes 2006-02-11 20:47:22
C++ file pc_system.cc 16621 bytes 2006-05-29 22:33:38
C file pc_system.h 6650 bytes 2006-05-27 15:54:47
C++ file plex86-interface.cc 15180 bytes 2006-05-21 20:41:48
C file plex86-interface.h 1649 bytes 2003-01-09 04:03:36
C++ file plugin.cc 19848 bytes 2006-05-27 15:54:47
C file plugin.h 18687 bytes 2006-05-27 15:54:47
File win32res.rc 6551 bytes 2006-06-08 17:02:51
File wxbochs.rc 141 bytes 2003-07-13 23:30:55 
  1 Bochs x86 Pentium+ Emulator
  2 Updated: Sun Aug 27 09:18:00 CEST 2006
  3 Version: 2.3
  4 
  5 WHAT IS BOCHS?
  6 
  7 Bochs is a highly portable open source IA-32 (x86) PC emulator
  8 written in C++, that runs on most popular platforms.  It includes
  9 emulation of the Intel x86 CPU, common I/O devices, and a custom
 10 BIOS.  Currently, Bochs can be compiled to emulate a 386, 486,
 11 Pentium, Pentium Pro or x86-64 CPU, including optional MMX, 
 12 SSE/SSE2/SSE3 and 3DNow! instructions.  Bochs is capable of running
 13 most Operating Systems inside the emulation including Linux, DOS,
 14 Windows 95/98 and Windows NT/2000/XP.
 15 Bochs was written by Kevin Lawton and is currently maintained by 
 16 the Bochs project at "http://bochs.sourceforge.net".
 17 
 18 Bochs can be compiled and used in a variety of modes, some which are
 19 still in development.  The 'typical' use of bochs is to provide
 20 complete x86 PC emulation, including the x86 processor, hardware
 21 devices, and memory.  This allows you to run OS's and software within
 22 the emulator on your workstation, much like you have a machine
 23 inside of a machine.  Bochs will allow you to run Windows
 24 applications on a Solaris machine with X11, for example.
 25 
 26 Bochs is distributed under the GNU LGPL.  See COPYING for details.
 27 
 28 GETTING CURRENT SOURCE CODE 
 29 
 30 Source code for Bochs is available from the Bochs home page at
 31 http://bochs.sourceforge.net.  You can download the most recent
 32 release, use CVS to get the latest sources, or grab a CVS
 33 snapshot which is updated nightly.  The releases contain the most
 34 stable code, but if you want the very newest features try the
 35 CVS version instead. 
 36 
 37 WHERE ARE THE DOCS?
 38 
 39 The Bochs documentation is written in Docbook.  Docbook is a text 
 40 format that can be rendered to many popular browser formats such 
 41 as HTML, PDF, and Postscript.  Each binary release contains the
 42 HTML rendering of the documentation.  Also, you can view the
 43 latest documentation on the web at
 44   http://bochs.sf.net/doc/docbook/index.html
 45 
 46 Some information has not yet been transferred from the older
 47 HTML docs.  These can be found at http://bochs.sf.net/docs-html
 48 
 49 WHERE CAN I GET MORE INFORMATION?  HOW DO I REPORT PROBLEMS?
 50 
 51 Both the documentation and the Bochs website have instructions on how 
 52 to join the bochs-developers mailing list, which is the primary
 53 forum for discussion of Bochs.  The main page of the website also
 54 has links to bug reports and feature requests.  You can browse and
 55 add to the content in these areas even if you do not have a (free)
 56 SourceForge account.  We need your feedback so that we know what
 57 parts of Bochs to improve.  
 58 
 59 There is a patches section on the web site too, if you have made
 60 some changes to Bochs that you want to share.
 61 
 62 HOW CAN I HELP?
 63 
 64 If you would like contribute to the Bochs project, a good first step
 65 is to join the bochs-developers mailing list, and read the archive
 66 of recent messages to see what's going on.  
 67 
 68 If you are a technical person (can follow hardware specs, can write
 69 C/C++) take a look at the list of open bug reports and feature
 70 requests to see if you are interested in working on any of the
 71 problems that are mentioned in them.  If you check out the CVS
 72 sources, make some changes, and create a patch, one of the
 73 developers will be very happy to apply it for you.  Developers who
 74 frequently submit patches, or who embark on major changes in the
 75 source can get write access to CVS.  Be sure to communicate with the
 76 bochs-developers list to avoid several people working on the same
 77 thing without realizing it.
 78 
 79 If you are a Bochs user, not a hardware/C++ guru, there are still
 80 many ways you could help out.  For example:
 81   - write instructions on how to install a particular operating system
 82   - writing/cleaning up documentation
 83   - testing out Bochs on every imaginable operating system and 
 84     reporting how it goes.
~ [ source navigation ] ~ [ identifier search ] ~ [ freetext search ] ~ [ file search ] ~
This page was automatically generated by the LXR engine.
Visit the LXR main site for more information.