mirror of https://github.com/bochs-emu/Bochs
sfsite moved to another git repo which can be found at (#5)
https://sourceforge.net/p/bochs/Bochs-sfsite/ci/master/tree/ Co-authored-by: Stanislav Shwartsman <sshwarts@users.sourceforge.net>
This commit is contained in:
Stanislav Shwartsman
GitHub
parent
658fd9e51f
commit
aee0529304
|
|
@ -1,2 +0,0 @@
|
|||
AddHandler server-parsed .html
|
||||
AddHandler server-parsed .txt
|
||||
Binary file not shown.
|
|
@ -1,32 +0,0 @@
|
|||
###################################################################
|
||||
# Makefile
|
||||
# $Id: Makefile,v 1.10 2004-01-12 21:33:23 cbothamy Exp $
|
||||
#
|
||||
# Runs a cvs update on the source forge shell account.
|
||||
# This will only work if you are a developer on the Bochs
|
||||
# project, and have set up secure shell correctly.
|
||||
#
|
||||
###################################################################
|
||||
|
||||
SSH=ssh -x
|
||||
REMOTE_HOST=shell.sf.net
|
||||
BOCHS_PATH=/home/groups/b/bo/bochs
|
||||
HTDOCS=$(BOCHS_PATH)/htdocs
|
||||
|
||||
remote_update::
|
||||
sfuser=`whoami`; \
|
||||
if test "`whoami`" = bryce; then sfuser=bdenney; fi; \
|
||||
if test "`whoami`" = tbutler; then sfuser=uninet; fi; \
|
||||
if test "`whoami`" = chris; then sfuser=cbothamy; fi; \
|
||||
$(SSH) $$sfuser@$(REMOTE_HOST) "cd $(HTDOCS) && cvs update -Ad"
|
||||
|
||||
do_commit::
|
||||
cvs commit
|
||||
|
||||
commit:: update do_commit remote_update
|
||||
|
||||
update::
|
||||
cvs update -A -d
|
||||
|
||||
diff:
|
||||
cvs diff
|
||||
|
|
@ -1,25 +0,0 @@
|
|||
Sun Jun 17 00:30:54 EDT 2001
|
||||
|
||||
I checked in most parts of the Bochs web site. Some subdirs are omitted
|
||||
for various reasons. For example the "data" directory (collection of
|
||||
tech specs) and guestos directory (disk images) are not checked into
|
||||
CVS because they are so large. If the files are big, binary, and
|
||||
are hardly ever revised, what's the point of version control on them?
|
||||
It will just clog up SF server and make updates take longer!
|
||||
|
||||
Directories included in CVS:
|
||||
- docs-html (actually a checkout of bochs/docs-html)
|
||||
- images
|
||||
- includes
|
||||
- networking
|
||||
- testing-forms
|
||||
|
||||
|
||||
Directories not included in CVS:
|
||||
- xcf (what's that)
|
||||
- doc (updated by Michael when he does make webinst)
|
||||
- screenshot (contains screen shots)
|
||||
- tmp (misc stuff)
|
||||
- data (tech spcs)
|
||||
- images/.pics (not sure)
|
||||
- images/.xvpics (not sure)
|
||||
Binary file not shown.
Binary file not shown.
File diff suppressed because it is too large
Load Diff
|
|
@ -1,39 +0,0 @@
|
|||
DATELINE JUNE 4, 2001
|
||||
|
||||
FOR IMMEDIATE RELEASE
|
||||
|
||||
BOCHS PROJECT UNVEILS BOCHS x86 EMULATOR 1.2
|
||||
"Release aims to make Bochs accessible to end users"
|
||||
|
||||
June 3, 2001 (The INTERNET) - The Bochs IA-32 Emulator Project unveiled a new
|
||||
version of the popular Bochs emulator to the public today, coming on the heels
|
||||
of Bochs 1.1.2 released May 17, 2001.
|
||||
Bochs 1.2 includes many usability improvements such as improved control over
|
||||
error handling, binaries for RPM-based Linux(R) distributions and Windows(R),
|
||||
and improved error output messages. Other new features include an easy to use
|
||||
interactive disk image creator, multiple processor emulation (SMP), vastly
|
||||
improved documentation (including man pages), VNC remote viewer support using
|
||||
Bochs-RFB, dual virtual hard drive support, and a text mode interface. You can
|
||||
find Bochs binaries for Windows and Linux (along with the source code for UNIX,
|
||||
Linux, Windows, and Mac OS) at http://bochs.sourceforge.net .
|
||||
|
||||
ABOUT BOCHS
|
||||
|
||||
Bochs is one of the oldest and most popular x86 emulators available. Bochs
|
||||
compiles on a number of platforms including UNIX(R) and UNIX-like systems,
|
||||
Windows, and MacOS.
|
||||
Bochs can be used for many purposes such as running Windows on other
|
||||
platforms, trying a new operating system without repartitioning your system, and
|
||||
operating system debugging. You can learn more about Bochs at
|
||||
http://bochs.sourceforge.net.
|
||||
|
||||
---
|
||||
PRESS CONTACT:
|
||||
Timothy R. Butler
|
||||
tbutler@uninetsolutions.com
|
||||
|
||||
----
|
||||
Trademarks Notices: Windows is a trademark of Microsoft Corp. Linux is a
|
||||
registered trademark of Linus Torvalds. UNIX is a registered trademark of The
|
||||
Open Group. All other trademarks and copyrights referred to in this announcement
|
||||
are the property of their respective owners.
|
||||
|
|
@ -1,39 +0,0 @@
|
|||
DATELINE DECEMBER 10, 2001
|
||||
|
||||
FOR IMMEDIATE RELEASE
|
||||
|
||||
BOCHS PROJECT RELEASES USABILITY ENHANCED EMULATOR
|
||||
"Release adds easy to use configuration and networking support"
|
||||
|
||||
December 10, 2001 (The INTERNET) - The Bochs IA-32 Emulator Project unveiled a new
|
||||
version of the popular Bochs emulator to the public today, improving on the
|
||||
stability and ground breaking improvements of Bochs 1.2.
|
||||
Bochs 1.3 includes many major enhancements including a powerful menu-based
|
||||
configuration system and networking support for Linux and Windows NT/2000. Other
|
||||
additions in this release include support for ISO-format disk images, improved
|
||||
mouse performance, physical CD-ROM support for all versions of Windows, parallel
|
||||
port emulation, enhanced debugger, and many cpu and device model improvements. Bochs
|
||||
1.3 also adds native support for Mac OS X and Amiga MorphOS, along with improved
|
||||
support for BeOS. You can find Bochs binaries for Windows and Linux (along with the
|
||||
source code for UNIX, Linux, Windows, and Mac OS) at http://bochs.sourceforge.net .
|
||||
|
||||
ABOUT BOCHS
|
||||
|
||||
Bochs is the most popular open source x86 emulator available today. Bochs
|
||||
compiles on a number of platforms including UNIX(R) and UNIX-like systems, Windows,
|
||||
and MacOS.
|
||||
Bochs can be used for many purposes such as running Windows on other
|
||||
platforms, trying a new operating system without repartitioning your system, and
|
||||
operating system debugging. You can learn more about Bochs at
|
||||
http://bochs.sourceforge.net.
|
||||
|
||||
---
|
||||
PRESS CONTACT:
|
||||
Timothy R. Butler
|
||||
tbutler@uninetsolutions.com
|
||||
|
||||
----
|
||||
Trademarks Notices: Windows is a trademark of Microsoft Corp. Linux is a
|
||||
registered trademark of Linus Torvalds. UNIX is a registered trademark of The
|
||||
Open Group. All other trademarks and copyrights referred to in this announcement
|
||||
are the property of their respective owners.
|
||||
|
|
@ -1,69 +0,0 @@
|
|||
<?php
|
||||
// Default Web Page for groups that haven't setup their page yet
|
||||
// Please replace this file with your own website
|
||||
//
|
||||
// $Id: default_page.php,v 1.1 2001-06-17 04:14:28 bdenney Exp $
|
||||
//
|
||||
$headers = getallheaders();
|
||||
?>
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>SourceForge: Welcome</TITLE>
|
||||
<LINK rel="stylesheet" href="http://sourceforge.net/sourceforge.css" type="text/css">
|
||||
</HEAD>
|
||||
|
||||
<BODY bgcolor=#FFFFFF topmargin="0" bottommargin="0" leftmargin="0" rightmargin="0" marginheight="0" marginwidth="0">
|
||||
|
||||
<!-- top strip -->
|
||||
<TABLE width="100%" border=0 cellspacing=0 cellpadding=2 bgcolor="737b9c">
|
||||
<TR>
|
||||
<TD><SPAN class=maintitlebar>
|
||||
<A class=maintitlebar href="http://sourceforge.net/"><B>Home</B></A> |
|
||||
<A class=maintitlebar href="http://sourceforge.net/about.php"><B>About</B></A> |
|
||||
<A class=maintitlebar href="http://sourceforge.net/partners.php"><B>Partners</B></a> |
|
||||
<A class=maintitlebar href="http://sourceforge.net/contact.php"><B>Contact Us</B></A></SPAN></TD>
|
||||
</TD>
|
||||
</TR>
|
||||
</TABLE>
|
||||
<!-- end top strip -->
|
||||
|
||||
<!-- top title table -->
|
||||
<TABLE width="100%" border=0 cellspacing=0 cellpadding=0 bgcolor="" valign="center">
|
||||
<TR valign="top" bgcolor="#eeeef8">
|
||||
<TD>
|
||||
<A href="http://sourceforge.net/"><IMG src="http://sourceforge.net/images/sflogo2-steel.png" vspace="0" border=0 width="143" height="70"></A>
|
||||
</TD>
|
||||
<TD width="99%"><!-- right of logo -->
|
||||
<a href="http://www.valinux.com"><IMG src="http://sourceforge.net/images/valogo3.png" align="right" alt="VA Linux Systems" hspace="5" vspace="0" border=0 width="117" height="70"></A>
|
||||
</TD><!-- right of logo -->
|
||||
</TR>
|
||||
<TR><TD bgcolor="#543a48" colspan=2><IMG src="http://sourceforge.net/images/blank.gif" height=2 vspace=0></TD></TR>
|
||||
</TABLE>
|
||||
<!-- end top title table -->
|
||||
|
||||
<!-- center table -->
|
||||
<TABLE width="100%" border="0" cellspacing="0" cellpadding="2" bgcolor="#FFFFFF" align="center">
|
||||
<TR>
|
||||
<TD>
|
||||
<CENTER><BR>
|
||||
<H1>Welcome to http://<?php print $headers[Host]; ?>/</H1>
|
||||
<P>We're Sorry but this Project hasn't yet uploaded their personal webpage yet.<BR>
|
||||
Please check back soon for updates or visit <A href="http://sourceforge.net/">SourceForge</A></P><BR>
|
||||
</CENTER>
|
||||
</TD>
|
||||
</TR>
|
||||
</TABLE>
|
||||
<!-- end center table -->
|
||||
|
||||
<!-- footer table -->
|
||||
<TABLE width="100%" border="0" cellspacing="0" cellpadding="2" bgcolor="737b9c">
|
||||
<TR>
|
||||
<TD align="center"><FONT color="#ffffff"><SPAN class="titlebar">
|
||||
All trademarks and copyrights on this page are properties of their respective owners. Forum comments are owned by the poster. The rest is copyright ©1999-2000 VA Linux Systems, Inc.</SPAN></FONT>
|
||||
</TD>
|
||||
</TR>
|
||||
</TABLE>
|
||||
|
||||
<!-- end footer table -->
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -1,59 +0,0 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>bochs: The Open Source IA-32 Emulation Project (Get Involved)</TITLE>
|
||||
|
||||
<!--#include virtual="includes/header.txt" -->
|
||||
|
||||
<img src="images/logo.png" alt="A Window, Tux, and the BSD Daemon" width="160" height="175" align="right">
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Disk Images with Pre-installed Systems</b></font><BR><BR>
|
||||
|
||||
|
||||
We are trying to collect a minimal hard disk or floppy disk image for all
|
||||
free supported operating systems that Bochs can run.
|
||||
<A HREF="http://bochs.sourceforge.net/cgi-bin/topper.pl?name=Disk+Images+README&url=http://bochs.sourceforge.net/guestos/README.txt">More info...</A><P>
|
||||
Other disk images are available from the
|
||||
<a href="http://bochs.sourceforge.net/cgi-bin/topper.pl?name=Disk+Images&url=http://sourceforge.net/projects/bochs/files/Disk Images">
|
||||
files section of the Bochs project page
|
||||
on SourceForge</a>
|
||||
|
||||
<ul>
|
||||
<li><IMG SRC="/icons/compressed.gif" ALT="[ ]"> <A HREF="guestos/freedos-img.tar.gz">FreeDOS</A><BR>
|
||||
10-meg hard disk image which boots into FreeDOS.<BR><BR>
|
||||
<li><IMG SRC="/icons/compressed.gif" ALT="[ ]"> <A HREF="guestos/linux-img.tar.gz">Linux</A><BR>
|
||||
4-meg hard disk image which boots into Linux.<BR><BR>
|
||||
<li><IMG SRC="/icons/compressed.gif" ALT="[ ]"> <A HREF="guestos/dlxlinux4.tar.gz">DLX Linux</A><BR>
|
||||
A 10-meg disk that boots DLX Linux (1.3.x kernel).<BR><BR>
|
||||
<li><IMG SRC="/icons/compressed.gif" ALT="[ ]"> <A HREF="guestos/openbsd-img.tar.gz">OpenBSD</A><BR>
|
||||
Bootable floppy image.<BR><BR>
|
||||
<li><IMG SRC="/icons/compressed.gif" ALT="[ ]"> <A HREF="guestos/pragmalinux-img.tar.gz">Pragma Linux</A><BR>
|
||||
Floppy image that boots Pragma Linux.<BR><BR>
|
||||
</ul>
|
||||
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Other Images</b></font><BR>
|
||||
<ul>
|
||||
<li><A HREF="guestos/linux.x86-64.bzImage">Linux kernel image for x86-64</a> from Andi Kleen at SuSE, which can be used as a boot floppy. <a href="guestos/linux.x86-64.bzImage.System.map.txt">Here</a> is the System.map file for it, which can be useful for debugging.<BR><BR>
|
||||
</ul>
|
||||
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>SF Disk Image Links</b></font><BR>
|
||||
<ul>
|
||||
<li><img src="/icons/compressed.gif" ALT="[ ]"> <A HREF="http://sourceforge.net/projects/bochs/files/Disk Images/GNU Hurd/gnupre0_3.tar.gz/download">GNU pre0.3 (89 MB)</a><BR>Also known as <A HREF="http://www.gnu.org/software/hurd/faq.en.html#q1-2">GNU/Hurd</a>.
|
||||
<li><img src="/icons/compressed.gif" ALT="[ ]"> <A HREF="http://sourceforge.net/projects/bochs/files/Disk Images/Debian Linux/debian-3.0r0.tar.gz/download">Debian 3.0r0 Image (86 MB download)</a><BR>contributed by Robert Millan.
|
||||
</ul>
|
||||
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Other Disk Image Links</b></font><BR>
|
||||
<ul>
|
||||
<li><img src="/icons/compressed.gif" ALT="[ ]"> <A
|
||||
HREF="http://www.knopper.net/knoppix/">KNOPPIX</a><BR>Hardware auto-detecting Debian-based Live CD.
|
||||
<li><img src="/icons/compressed.gif" ALT="[ ]"> <A
|
||||
HREF="http://www4.informatik.uni-erlangen.de/Projects/JX/">JX OS Demo Floppy</a>
|
||||
</ul>
|
||||
|
||||
<!--#include virtual="includes/footer.txt" -->
|
||||
|
||||
|
||||
Last Modified on <!--#flastmod file="diskimages.html" -->.<BR>
|
||||
|
||||
<!--#include virtual="includes/cright.txt" -->
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 766 B |
|
|
@ -1,135 +0,0 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>bochs: The Open Source IA-32 Emulation Project (Download Current Release)</TITLE>
|
||||
|
||||
<!--#include virtual="includes/header.txt" -->
|
||||
|
||||
<!--content starts here-->
|
||||
<img src="images/logo.png" alt="A Window, Tux, and the BSD Daemon" width="160" height="175" align="right">
|
||||
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Latest release:</b> Bochs 2.7</font><BR><BR>
|
||||
|
||||
Bochs 2.7 is the latest major release. Here is the brief summary of changes :
|
||||
|
||||
<ul>
|
||||
<li>Bugfixes for CPU emulation correctness (CPUID/VMX/SVM fixes to support Windows Hyper-V as guest in Bochs)
|
||||
<li>Improvements for the plugin handling to simplify Bochs extensions
|
||||
<li>Added "multiple NICs" support to the NE2000 and E1000 devices
|
||||
<li>Added experimental FTP service for networking modules 'vnet' and 'socket'
|
||||
<li>Fixes and improvements for all supported Voodoo graphics adapters
|
||||
<li>Added USB keyboard emulation with most of the keys supported
|
||||
<li>GUI "cmdmode": create a headerbar event with key combo starting with F7
|
||||
<li>LGPL'd VGABIOS updated to version 0.8a (new VGABIOS for Voodoo Banshee)
|
||||
</ul>
|
||||
|
||||
The binary packages for Linux and Windows are built with these features :
|
||||
<ul>
|
||||
<li> x86-64 emulation with all optimizations enabled
|
||||
<li> devices:
|
||||
<ul>
|
||||
<li> chipset: PCI (i430FX / i440FX / i440BX), ACPI
|
||||
<li> video: Bochs VBE, Cirrus SVGA and 4 Voodoo models
|
||||
<li> sound: SB16 (ISA) and ES1370 (PCI)
|
||||
<li> network: NE2000 (ISA/PCI) and E1000 (PCI)
|
||||
<li> USB: OHCI, UHCI, EHCI, xHCI and 8 pluggable device types
|
||||
<li> other: game port, bus mouse
|
||||
</ul>
|
||||
<li> Display libraries:
|
||||
<ul>
|
||||
<li> Linux: nogui, rfb, sdl2, term, vncsrv, wx, x
|
||||
<li> Windows: nogui, rfb, win32
|
||||
</ul>
|
||||
</ul>
|
||||
|
||||
<a href="https://svn.code.sf.net/p/bochs/code/tags/REL_2_7_FINAL/bochs/CHANGES">
|
||||
Details on what has changed since version 2.6.11
|
||||
</a>
|
||||
|
||||
<BR/><BR/>
|
||||
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Previous release:</b> Bochs 2.6.11</font><BR><BR>
|
||||
|
||||
Bochs 2.6.11 is a bugfix release. Here is the summary of changes :
|
||||
|
||||
<ul>
|
||||
<li>General
|
||||
<ul>
|
||||
<li>Added 64-bit support to the NSIS installer script
|
||||
<li>Several fixes in the build system based on Debian patches
|
||||
</ul>
|
||||
<li>CPU / CPUDB
|
||||
<ul>
|
||||
<li>Bugfixes for CPU emulation correctness
|
||||
<li>Many critical bugfixes for Protection Keys, AVX512*, VMX/SVM, SHA, GFNI emulation
|
||||
<li>! Implemented CET (Control Flow Enforcement Technology) emulation according to Intel SDM rev071
|
||||
</ul>
|
||||
<li>I/O Devices
|
||||
<ul>
|
||||
<li>Added missing Cirrus SVGA bitblt feature "transparent color compare"
|
||||
<li>Some fixes in HPET emulation (patch by Oleg)
|
||||
<li>Fixed disk image lock mechanism in the USB MSD case
|
||||
</ul>
|
||||
<li>BIOS / VGABIOS
|
||||
<ul>
|
||||
<li>LGPL'd VGABIOS updated to version 0.7b (Fixed VESA extension 'read EDID' for Bochs VBE and Cirrus)
|
||||
<li>Updated SeaBIOS ROM image to current version 1.13.0
|
||||
<li>Added SeaVGABIOS ROM image for the Cirrus adapter
|
||||
<li>Bochs BIOS built to work with CPU level 5 again
|
||||
</ul>
|
||||
</ul>
|
||||
|
||||
<BR>
|
||||
|
||||
<a href="https://svn.code.sf.net/p/bochs/code/tags/REL_2_6_11_FINAL/bochs/CHANGES">
|
||||
Details on what has changed since version 2.6.10
|
||||
</a>
|
||||
|
||||
<BR><BR>
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Bochs Binary and Source Releases</b></font><BR><BR>
|
||||
The latest release of Bochs is available in these file formats :<BR>
|
||||
<ul>
|
||||
<li> Win64 binary NSIS installer package (EXE)
|
||||
<li> Linux binary RPM (64 bit)
|
||||
<li> Platform independant source package (TAR.GZ)
|
||||
<li> Win32 specific source package prepared for VS2019 (ZIP)
|
||||
<li> Linux source RPM
|
||||
</ul>
|
||||
You can download any release since March 2001 on the
|
||||
<a href="https://sourceforge.net/projects/bochs/files/bochs/">Files Page on SF</a>.
|
||||
|
||||
|
||||
<BR><BR>
|
||||
|
||||
<a name="cvssnap"><BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Download SVN
|
||||
Snapshot</b></font><BR><BR></a>
|
||||
|
||||
<b>SVN Snapshot:</b>
|
||||
Bochs, like many other open source projects, uses SVN (Subversion) to keep
|
||||
track of source code. Unlike the current release, the SVN version of the
|
||||
sources contains everything the developers have written to this date, and it
|
||||
can change daily (or even hourly). As a result, the SVN version of Bochs will
|
||||
have more features and bug fixes than the release, but also it may be somewhat
|
||||
less stable. You can decide if you prefer to go exploring and try out our
|
||||
newest code, or stick with the better-tested release.
|
||||
<BR><BR>
|
||||
|
||||
<!--#include virtual="svn-snapshot/bochs-snapshot-links.html" -->
|
||||
|
||||
The SVN snapshots are provided as a convenience only. Of course, you could
|
||||
also get the same information using SVN itself. Some of the benefits of
|
||||
using SVN directly are: you can get any release or version, view the log
|
||||
messages that say what files were changed, and make patches very easily
|
||||
with "svn diff -u".
|
||||
|
||||
<!--content ends here -->
|
||||
|
||||
|
||||
<!--#include virtual="includes/footer.txt" -->
|
||||
|
||||
|
||||
Last Modified on <!--#flastmod file="getcurrent.html" -->.<BR>
|
||||
|
||||
<!--#include virtual="includes/cright.txt" -->
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -1,54 +0,0 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>bochs: The Open Source IA-32 Emulation Project (Get Involved)</TITLE>
|
||||
|
||||
<!--#include virtual="includes/header.txt" -->
|
||||
|
||||
<img src="images/logo.png" alt="A Window, Tux, and the BSD Daemon" width="160" height="175" align="right">
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Get Involved with Bochs</b></font><BR>
|
||||
If you enjoy using Bochs, please consider joining our development team to
|
||||
assist in improving and extending Bochs. Open source projects depend on people like you to keep them
|
||||
going, so your help is needed!<BR><BR>
|
||||
|
||||
The <a href="mailinglists.html">bochs-developers mailing list</a> is the forum
|
||||
for all sorts of Bochs discussions, so reading over the mailing list archives
|
||||
and joining the list is a good way to get involved. To find out what features
|
||||
and fixes are under consideration, check out the bug reports, patches,
|
||||
and feature requests on the SourceForge project page. Even if you
|
||||
don't have a SourceForge account, you can add to our collection of good
|
||||
ideas by submitting your own.
|
||||
<br><br>
|
||||
If you are familiar with PC hardware such as IDE controllers,
|
||||
8259 interrupt controller, or the PS/2 mouse protocol, we can always use
|
||||
some help in improving the device models. Or, if your favorite operating
|
||||
system or GUI is not supported, you might want to port Bochs to your
|
||||
platform.
|
||||
Another way to contribute is to test Bochs on new platforms.
|
||||
The testing status page shows a table of host platforms and guest operating
|
||||
systems. Fill out a testing form (or several!) for the configurations that
|
||||
you have tried. For free operating systems, you could donate a disk
|
||||
image to save other users the trouble of installing.
|
||||
<br><br>
|
||||
With anonymous CVS access (available to everyone), you can make changes to
|
||||
the Bochs source code and submit patches on SourceForge that allow other
|
||||
people to try out your improvements. If you are submitting frequent
|
||||
patches, ask Bryce or Greg for CVS write access.
|
||||
<br><br>
|
||||
For more ideas, contact the bochs-developers mailing list or one of the developers:
|
||||
<ul>
|
||||
<li><a href="http://bochs.sourceforge.net/cgi-bin/topper.pl?name=Email+Bryce+Denney&url=http://sourceforge.net/sendmessage.phpqmrktousereq185114">Bryce Denney</a>
|
||||
<li><a href="http://bochs.sourceforge.net/cgi-bin/topper.pl?name=Email+Greg+Alexander&url=http://sourceforge.net/sendmessage.phpqmrktousereq125806">Greg Alexander</a>
|
||||
<li><a href="http://bochs.sourceforge.net/cgi-bin/topper.pl?name=Email+Todd+Fries&url=http://sourceforge.net/sendmessage.phpqmrktousereq22083">Todd Fries</a>
|
||||
<li><a href="http://bochs.sourceforge.net/cgi-bin/topper.pl?name=Email+Donald+Becker&url=http://sourceforge.net/sendmessage.phpqmrktousereq33082">Donald Becker</a>
|
||||
<li><a href="http://bochs.sourceforge.net/cgi-bin/topper.pl?name=Email+Tim+Butler&url=http://sourceforge.net/sendmessage.phpqmrktousereq44230">Tim Butler</a>
|
||||
</ul>
|
||||
|
||||
<!--#include virtual="includes/footer.txt" -->
|
||||
|
||||
|
||||
Last Modified on <!--#flastmod file="getinvolved.html" -->.<BR>
|
||||
|
||||
<!--#include virtual="includes/cright.txt" -->
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -1,39 +0,0 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<style TYPE="text/CSS">
|
||||
<!--
|
||||
A:link {color: blue; text-decoration: none}
|
||||
A:visited {color: blue; text-decoration: none}
|
||||
A:active {color: blue; text-decoration: none}
|
||||
A:hover {color: blue; text-decoration: underline}
|
||||
|
||||
|
||||
.sidebar {font-family:Verdana, Arial, Helvetica; color: #000000}
|
||||
A.sidebar:link {color: #000000; font-style: normal; text-decoration: none}
|
||||
A.sidebar:visited {color: #000000; font-style: normal; text-decoration: none}
|
||||
A.sidebar:active {color: #000000; font-style: normal; text-decoration: none}
|
||||
A.sidebar:hover {color: blue; text-decoration: underline}
|
||||
-->
|
||||
</style>
|
||||
|
||||
<META NAME="resource-type" CONTENT="document">
|
||||
<META NAME="distribution" CONTENT="GLOBAL">
|
||||
<META NAME="description" CONTENT="Bochs IA-32 Emulator provides a virtual PC that can run operating systems such as Windows, Linux, and BSD.">
|
||||
<META NAME="copyright" CONTENT="Copyright 2001 The Bochs Project.">
|
||||
<META NAME="keywords" CONTENT="pc emulation, vmware, win4lin, netraverse, trelos, x86 emulation, emulator,insignia, softpc, connectix, virtualpc, fx!32, freemware, dynamic translation,open source, gnu, linux, windows, bsd">
|
||||
<META NAME="Author" CONTENT="Timothy R. Butler">
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;CHARSET=iso-8859-1">
|
||||
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#FFFFFF" TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0">
|
||||
<table width="100%" border="0" cellspacing="0" cellpadding="0">
|
||||
<tr><td width="140" height="12" bgcolor="#aacbff"><font size="1"> </font></td><td bgcolor="#6d95d7" width="400"><font size="1"> </font></td><td width="100%"><table border="0" cellspacing="0" cellpadding="0" width="100%" height="12"><tr><td bgcolor="#4079d6" width="50%"><font size="1"> </font></td><td bgcolor="#1e029a" width="50%"><font size="1"> </font></td></tr></table></td></tr>
|
||||
<tr><td width="140" bgcolor="#6d95d7">
|
||||
<font face="arial, helvetica" size="1">
|
||||
<br><nobr> <b>-</b> <a href="https://bochs.sourceforge.net" target="_top" class="sidebar">Home Page</a></nobr>
|
||||
<br><nobr> <b>-</b> <a href="<!--#include virtual="includes/release.txt" -->" target="_top" class="sidebar">Download Latest</a></nobr>
|
||||
</font></center></td><td width="240" height="76"><a href="https://bochs.sourceforge.io" target="_top"><img src="https://bochs.sourceforge.io/images/smban.png" width="240" height="76" border="0" alt="bochs: think inside the bochs."></a></td><td> </td></tr>
|
||||
<tr><td bgcolor="#4079d6" height="1"><img src="https://bochs.sourceforge.io/images/smblue.png" width="140" height="1"></td><td colspan="2" bgcolor="#4079d6" height="1"><img src="https://bochs.sourceforge.io/images/smblue.png" width="100%" height="1"></td></tr>
|
||||
</table>
|
||||
</BODY>
|
||||
</HTML>
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 10 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.2 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.9 KiB |
Binary file not shown.
Binary file not shown.
|
Before Width: | Height: | Size: 32 KiB |
Binary file not shown.
Binary file not shown.
|
Before Width: | Height: | Size: 6.9 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 17 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 14 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.4 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 14 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 16 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 11 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 383 B |
Binary file not shown.
|
Before Width: | Height: | Size: 6.6 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 410 B |
|
|
@ -1,2 +0,0 @@
|
|||
© 2001-2021 The Bochs Project. See the project <a href="https://sourceforge.net/projects/bochs/files/stats/timeline">statistics</a> here.</font></td></tr>
|
||||
</table>
|
||||
|
|
@ -1,13 +0,0 @@
|
|||
</td></tr></table>
|
||||
</td></tr>
|
||||
<tr><td colspan="3" bgcolor="#4079d6" height="1"><img src="images/sm.png" width="1" height="1"></td></tr>
|
||||
<tr><td width="140" bgcolor="#aacbff"> </td><td bgcolor="#6d95d7" width="400"> </td><td width="100%"><table border="0" cellspacing="0" cellpadding="0" width="100%"><tr><td bgcolor="#4079d6" width="50%"> </td><td bgcolor="#1e029a" width="50%"> </td></tr></table></td></tr>
|
||||
<tr><td>
|
||||
<center>
|
||||
<A href="https://sourceforge.net">
|
||||
<IMG src="https://sourceforge.net/sflogo.php?group_id=12580&type=1" width="88" height="31" border="0" alt="SourceForge Logo">
|
||||
</A>
|
||||
</center>
|
||||
</td>
|
||||
<td colspan="2"><font size="2" face="arial, helvetica">Please send comments and questions concerning the site to <a href="mailto:vruppert@users.sourceforge.net">Volker Ruppert</a>.<BR>
|
||||
Web site feature requests and bug reports should be added to the <a href="https://sourceforge.net/p/bochs/web-site-requests/">Web site tracker</a>.<BR>
|
||||
|
|
@ -1,95 +0,0 @@
|
|||
<style TYPE="text/CSS">
|
||||
<!--
|
||||
A:link {color: blue; text-decoration: none}
|
||||
A:visited {color: blue; text-decoration: none}
|
||||
A:active {color: blue; text-decoration: none}
|
||||
A:hover {color: blue; text-decoration: underline}
|
||||
INPUT {border-bottom:thin solid black;border-right:thin solid black;border-top:thin solid black;border-left:thin solid black; font-size: 7pt; font-family:Verdana, Arial Helvetica}
|
||||
|
||||
|
||||
.sidebar {font-family:Verdana, Arial, Helvetica; color: #000000}
|
||||
A.sidebar:link {color: #000000; font-style: normal; text-decoration: none}
|
||||
A.sidebar:visited {color: #000000; font-style: normal; text-decoration: none}
|
||||
A.sidebar:active {color: #000000; font-style: normal; text-decoration: none}
|
||||
A.sidebar:hover {color: blue; text-decoration: underline}
|
||||
-->
|
||||
</style>
|
||||
|
||||
<META NAME="resource-type" CONTENT="document">
|
||||
<META NAME="distribution" CONTENT="GLOBAL">
|
||||
<META NAME="description" CONTENT="Bochs IA-32 Emulator provides a virtual PC that can run operating systems such as Windows, Linux, and BSD.">
|
||||
<META NAME="copyright" CONTENT="Copyright 2001-2021 The Bochs Project.">
|
||||
<META NAME="keywords" CONTENT="pc emulation, vmware, win4lin, netraverse, trelos, x86 emulation, emulator,insignia, softpc, connectix, virtualpc, fx!32, freemware, plex86, dynamic translation,open source, gnu, linux, windows, bsd">
|
||||
<META NAME="Author" CONTENT="Timothy R. Butler">
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;CHARSET=iso-8859-1">
|
||||
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#FFFFFF" VLINK="#000000" ALINK="#000000" LINK="#000000" TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0">
|
||||
<table width="100%" border="0" cellspacing="0" cellpadding="0">
|
||||
<tr><td width="140" bgcolor="#aacbff"> </td><td bgcolor="#6d95d7" width="400"><font face="arial, helvetica" size="2" color="#1e029a"><center><b>T H E C R O S S P L A T F O R M I A - 3 2 E M U L A T O R</b></center></font></td><td width="100%"><table border="0" cellspacing="0" cellpadding="0" width="100%"><tr><td bgcolor="#4079d6" width="50%"> </td><td bgcolor="#1e029a" width="50%"> </td></tr></table></td></tr>
|
||||
<tr><td width="140" bgcolor="#6d95d7"><font face="arial, helvetica"><center><b>Current Release:</b><BR><a href="<!--#include virtual="release.txt" -->" class="sidebar"><i><u>Bochs 2.7</u></i></a></font></center></td><td width="400" height="130"><img src="https://bochs.sourceforge.io/images/lgban.png" width="400" height="130" alt="bochs: think inside the bochs."></td><td> </td></tr>
|
||||
<tr><td colspan="3" bgcolor="#4079d6" height="1">
|
||||
<img src="https://bochs.sourceforge.io/images/smblue.png" width="1" height="1"></td></tr>
|
||||
<tr><td bgcolor="#4079d6" width="140" valign="top">
|
||||
<font face="arial, helvetica" size="-1">
|
||||
<img src="https://bochs.sourceforge.io/images/smblue.png" width="140" height="1">
|
||||
<br> <b>-</b> <a href="https://bochs.sourceforge.io" class="sidebar">Home Page</a>
|
||||
<br> <b>-</b> <a href="https://sourceforge.net/projects/bochs" class="sidebar">SF Project Page</a>
|
||||
|
||||
<br><br><center><b>Search</b></center>
|
||||
<center><form method=GET action="https://bochs.sourceforge.io/cgi-bin/eglimpse.pl/search">
|
||||
<input type=hidden name="title" value="Bochs">
|
||||
<input type=hidden name="file_base" value="/home/groups/b/bo/bochs/htdocs">
|
||||
<input type=hidden name="url_base" value="https://bochs.sourceforge.io">
|
||||
<input type=hidden name="output_format" value="standard">
|
||||
<input type=hidden name="case_sensitive" value="no">
|
||||
<input type=hidden name="words_only" value="yes">
|
||||
<input type=hidden name="misspellings" value="0">
|
||||
<input type=hidden name="file_pattern" value="">
|
||||
<input type=hidden name="date_filter" value="">
|
||||
<input name=query size=18>
|
||||
</form></center>
|
||||
|
||||
<br><center><b>Get Bochs</b></center>
|
||||
|
||||
<br> <b>-</b> <a href="<!--#include virtual="release.txt" -->" class="sidebar">Download Current</a>
|
||||
<br> <b>-</b> <a href="https://sourceforge.net/projects/bochs/files/bochs" class="sidebar">See All Releases</a>
|
||||
<br> <b>-</b> <a href="https://bochs.sourceforge.io/diskimages.html" class="sidebar">Disk Images</a>
|
||||
<br> <b>-</b> <a href="https://sourceforge.net/p/forge/documentation/svn/" class="sidebar">Anonymous SVN</a>
|
||||
|
||||
|
||||
<br><br><center><b>Support</b></center>
|
||||
|
||||
<br> <b>-</b> <a href="https://sourceforge.net/p/bochs/wiki/Home" class="sidebar">Bochs Wiki</a>
|
||||
<br> <b>-</b> <a href="https://bochs.sourceforge.io/cgi-bin/topper.pl?name=Bochs+FAQ&url=https://bochs.sourceforge.io/doc/docbook/user/faq.html" class="sidebar">Bochs FAQ</a>
|
||||
<br> <b>-</b> <a href="https://bochs.sourceforge.io/cgi-bin/topper.pl?name=New+Bochs+Documentation&url=https://bochs.sourceforge.io/doc/docbook/" class="sidebar">Documentation</a>
|
||||
<br> <b>-</b> <a href="https://bochs.sourceforge.io/cgi-bin/topper.pl?name=New+Bochs+Documentation&url=https://bochs.sourceforge.io/doc/docbook/user/index.html" class="sidebar">User Guide</a>
|
||||
<br> <b>-</b> <a href="https://bochs.sourceforge.io/cgi-bin/topper.pl?name=New+Bochs+Documentation&url=https://bochs.sourceforge.io/doc/docbook/development/index.html" class="sidebar">Devel. Guide</a>
|
||||
<br> <b>-</b> <a href="https://bochs.sourceforge.io/cgi-bin/topper.pl?name=New+Bochs+Documentation&url=https://bochs.sourceforge.io/doc/docbook/documentation/index.html" class="sidebar">Doc. Guide</a>
|
||||
<br> <b>-</b> <a href="https://bochs.sourceforge.io/mailinglists.html" class="sidebar">Mailing Lists</a>
|
||||
<br> <b>-</b> <a href="https://sourceforge.io/p/bochs/discussion/" class="sidebar">Discussion Boards</a>
|
||||
<br> <b>-</b> <a href="https://sourceforge.net/p/forge/documentation/Docs Home" class="sidebar">SF Site Docs</a>
|
||||
|
||||
<br><br><center><b>Feedback</b></center>
|
||||
|
||||
<br> <b>-</b> <a href="https://sourceforge.net/p/bochs/bugs/" class="sidebar">Bug Reports</a>
|
||||
<br> <b>-</b> <a href="https://sourceforge.net/p/bochs/feature-requests/" class="sidebar">Feature Requests</a>
|
||||
|
||||
|
||||
<br><br><center><b>Development</b></center>
|
||||
|
||||
<br> <b>-</b> <a href="https://bochs.sourceforge.io/getinvolved.html" class="sidebar">Get Involved</a>
|
||||
<br> <b>-</b> <a href="https://sourceforge.net/p/bochs/code/HEAD/tree/" class="sidebar">View the Source</a>
|
||||
<br> <b>-</b> <a href="https://sourceforge.net/p/bochs/patches/" class="sidebar">Patches</a>
|
||||
<br> <b>-</b> <a href="https://bochs.sourceforge.io/techdata.html" class="sidebar">Tech Specs Pages</a>
|
||||
|
||||
<br><br><center><b>Resources</b></center>
|
||||
|
||||
<br> <b>-</b> <a href="https://bochs.sourceforge.io/news.html" class="sidebar">Bochs History</a>
|
||||
<br> <b>-</b> <a href="https://bochs.sourceforge.io/links.html" class="sidebar">Bochs Links</a>
|
||||
<br> <b>-</b> <a href="https://bochs.sourceforge.io/related.html" class="sidebar">Related Links</a>
|
||||
<br> <b>-</b> <a href="https://bochs.sourceforge.io/screenshots.html" class="sidebar">Screen Shots</a>
|
||||
|
||||
</font>
|
||||
</td><td colspan="2" valign="top">
|
||||
<table width="100%" border="0"><tr><td>
|
||||
|
|
@ -1 +0,0 @@
|
|||
https://bochs.sourceforge.io/getcurrent.html
|
||||
|
|
@ -1,106 +0,0 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>bochs: The Open Source IA-32 Emulation Project (Home Page)</TITLE>
|
||||
|
||||
<!--#include virtual="includes/header.txt" -->
|
||||
|
||||
<img src="images/logo.png" alt="A Window, Tux, and the BSD Daemon" width="160" height="175" align="right">
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Welcome to the Bochs IA-32 Emulator Project</b></font><BR>
|
||||
|
||||
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. Bochs can be compiled to emulate
|
||||
many different x86 CPUs, from early 386 to the most recent x86-64 Intel and AMD processors
|
||||
which may even not reached the market yet. <BR>
|
||||
Bochs is capable of running most Operating Systems inside the emulation including Linux, DOS or
|
||||
Microsoft Windows. Bochs was originally written by Kevin Lawton and is currently maintained by
|
||||
this project.<BR>
|
||||
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. For instance, let's say your workstation is a Unix/X11 workstation, but you want to run
|
||||
Win'95 applications. Bochs will allow you to run Win 95 and associated software on your Unix/X11
|
||||
workstation, displaying a window on your workstation, simulating a monitor on a PC.
|
||||
|
||||
<BR><BR><BR>
|
||||
<hr>
|
||||
<table border=0>
|
||||
<tr>
|
||||
<td> <img src="images/bochs2_7.png" alt="Bochs 2.7"></td>
|
||||
<td>
|
||||
<font face="arial, helvetica" color="#1e029a" size="4"><b>Bochs 2.7 released on August 1, 2021 !</b></font><BR>
|
||||
The final release of the new Bochs version is now available. You can download
|
||||
it from the <a href="https://sourceforge.net/projects/bochs/files/bochs/2.7">Bochs project page on SourceForge</a>.
|
||||
See the <a href="https://svn.code.sf.net/p/bochs/code/tags/REL_2_7_FINAL/bochs/CHANGES">
|
||||
CHANGES</a> file for details on what has changed since release 2.6.11<BR>
|
||||
</td></tr></table><hr>
|
||||
|
||||
<BR><BR>
|
||||
<font face="arial, helvetica" color="#1e029a" size="4"><b>Bochs IRC Chat Transcripts</b></font><BR>
|
||||
The Bochs community held an IRC open discussion chat on Sunday, February 1, 2004.
|
||||
We talked about current and future developments (<a href="irc-20040201.html">Transcript</a>). Here are some transcripts of earlier conversations:
|
||||
<a href="irc-20020407.html">October 13, 2002</a>,
|
||||
<a href="irc-20020407.html">April 7, 2002</a>,
|
||||
<a href="irc-20010619.html">June 19, 2001</a>,
|
||||
<a href="irc-20010530.html">May 30, 2001</a>.
|
||||
|
||||
<BR><BR><BR>
|
||||
<font face="arial, helvetica" color="#1e029a" size="4"><b>Bochs at ISCA-35</b></font><BR>
|
||||
Bochs was presented at ISCA-35 in Beijing, China at
|
||||
"The 1st Workshop on Architectural and Microarchitectural Support for Binary Translation" by a paper
|
||||
<br><font face="arial, helvetica" color="#1e029a" size="2"><b>
|
||||
"Virtualization without direct execution - designing a portable VM".</b></font>
|
||||
<br>Download <a href="https://bochs.sourceforge.io/Virtualization_Without_Hardware_Final.pdf">paper</a> and <a href="http://bochs.sourceforge.net/VirtNoJit.pdf">presentation</a> slides.
|
||||
|
||||
<BR><BR><BR>
|
||||
Want to know more about Bochs architecture ? <a href="https://bochs.sourceforge.io/How the Bochs works under the hood 2nd edition.pdf">How the Bochs works under the hood (2nd edition)</a>
|
||||
|
||||
<BR><BR><BR>
|
||||
<font face="arial, helvetica" color="#1e029a" size="4"><b>Help Wanted</b></font><BR>
|
||||
<i>We currently need help with the following tasks:</i>
|
||||
<ul>
|
||||
<li><a href="https://bochs.sourceforge.io/cgi-bin/topper.pl?name=Bugs+Waiting+to+be+Fixed&url=https://sourceforge.net/p/bochs/bugs">
|
||||
Bug Reports</a>:
|
||||
Mouse, interrupt controller,
|
||||
timer, IDE controller, network card, keyboard, VGA... Most of our bug
|
||||
reports and feature requests are due to incomplete C++ models of the
|
||||
various PC devices. To improve this, we need PC Hardware Gurus who know
|
||||
where to find the specs for this stuff and improve the hardware models for
|
||||
Bochs. Working on models is a fun way to learn how things work, and unlike
|
||||
designing a real hard disk, you can test out your changes on a real operating
|
||||
system immediately!
|
||||
<li><a href="https://bochs.sourceforge.io/diskimages.html">Disk Images</a>: Our collection of disk images is getting out of date. It would be great to have small or large images of a variety of free operating systems.
|
||||
<li>Documentation: Adding installation help and other useful information into the docs.
|
||||
</ul>
|
||||
To help with one of these tasks, please contact <a href="https://sourceforge.net/sendmessage.php?touser=376477">Volker Ruppert</a>
|
||||
or <a href="https://sourceforge.net/sendmessage.php?touser=487634">Stanislav Shwartsman</a>.
|
||||
<BR><BR>
|
||||
<font face="arial, helvetica" color="#1e029a" size="4"><b>Older News</b></font><BR>
|
||||
<ul>
|
||||
<li><b>January 5, 2020:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6.11/">Bochs 2.6.11</a> is now available.
|
||||
<li><b>December 1, 2019:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6.10/">Bochs 2.6.10</a> is now available.
|
||||
<li><b>April 9, 2017:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6.9/">Bochs 2.6.9</a> is now available.
|
||||
<li><b>May 3, 2015:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6.8/">Bochs 2.6.8</a> is now available.
|
||||
<li><b>November 2, 2014:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6.7/">Bochs 2.6.7</a> is now available.
|
||||
<li><b>June 15, 2014:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6.6/">Bochs 2.6.6</a> is now available.
|
||||
<li><b>June 1, 2014:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6.5/">Bochs 2.6.5</a> is now available.
|
||||
<li><b>May 26, 2013:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6.2/">Bochs 2.6.2</a> is now available.
|
||||
<li><b>April 7, 2013:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6.1/">Bochs 2.6.1</a> is now available.
|
||||
<li><b>September 2, 2012:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6/">Bochs 2.6</a> is now available.
|
||||
<li><b>January 6, 2012:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.5.1/">Bochs 2.5.1</a> is now available.
|
||||
<li><b>November 27, 2011:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.5/">Bochs 2.5</a> is now available (first release from SVN).
|
||||
</ul>
|
||||
<BR><BR>
|
||||
<a href="news.html"><i>More News...</i></a>
|
||||
|
||||
|
||||
<!--#include virtual="includes/footer.txt" -->
|
||||
|
||||
|
||||
Last Modified on <!--#flastmod file="index.html" --> TRB.<BR>
|
||||
|
||||
<!--#include virtual="includes/cright.txt" -->
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
|
|
@ -1,474 +0,0 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>bochs: The Open Source IA-32 Emulation Project (IRC Chat Transcript)</TITLE>
|
||||
|
||||
<!--#include virtual="includes/header.txt" -->
|
||||
|
||||
<!--content starts here-->
|
||||
<img src="images/logo.png" alt="A Window, Tux, and the BSD Daemon" width="160" height="175" align="right">
|
||||
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Transcript of Bochs Chat from October 13, 2002</b></font><BR><BR>
|
||||
|
||||
<pre>
|
||||
(19:00:56) bryce: Oct. 13, 2002, 19:00:39 Universal Time
|
||||
(19:01:02) astaroth: sandos: i was thinking more along the lines of seeing how many bochs sessions running simultaniously it would take to make a linux Beowulf cluster that a commodore c64 could easily out perform
|
||||
(19:01:27) sandos: =)
|
||||
(19:01:35) bryce: I have written a web page about release 2.0 at http://bochs.sourceforge.net/release2_0.html
|
||||
(19:02:25) bryce: I figured we'd probably spend a lot of this time talking about what's new and how we are moving toward getting a release out the door.
|
||||
(19:04:07) bryce: It's been a very productive month, and it's been great to see Kevin Lawton working on Bochs again.
|
||||
(19:04:40) astaroth: bryce: i mentioned to sandos that i have some potentially helpful documentation for various bits of hardware. I will try to compile good list of what i have, but as an example, i have full docs on a couple of complete pc chipsets and various other tidbits
|
||||
(19:05:16) bryce: astaroth: that's great. We have a place to put such things (Tech Specs Pages) and it would be good to add your stuff.
|
||||
(19:06:04) bryce: astaroth: you can email me documents, or send me the urls of them
|
||||
(19:06:26) astaroth: i don't have the foggiest clue about any potential copyright infringements, but i figure that for stuff that used to be on the web, it should be safe
|
||||
(19:06:35) bryce: :)
|
||||
(19:07:29) astaroth: the original ibm pc Technical Reference complete with schematics and full bios source code might be a slightly different matter, though
|
||||
(19:08:30) bryce: yes
|
||||
(19:09:08) bryce: I assume a number of people have been using Kevin's optimized CPU code?
|
||||
(19:09:21) bryce: by doing configure --enable-all-optimizations, or configure --enable-icache, etc.?
|
||||
(19:09:45) sandos: all the time. =)
|
||||
(19:09:52) sandos: almost atleast.
|
||||
(19:10:13) bryce: unfortunately Kevin said he couldn't be here this afternoon. He had a conflict.
|
||||
(19:10:29) bryce: yeah, it seems reliable to me
|
||||
(19:10:47) bryce: At first I found a few segfaults, but the ones I've found have been fixed now.
|
||||
(19:11:33) bryce: any comments or questions about other new stuff?
|
||||
(19:12:58) japj: goodevening
|
||||
(19:13:04) bryce: For a group of 12 we're pretty quiet ;)
|
||||
(19:13:05) sandos: evening
|
||||
(19:13:07) bryce: Hi japj
|
||||
(19:13:16) japj: hello bryce
|
||||
(19:13:36) cbothamy: hi
|
||||
(19:13:42) japj: is someone logging this channel?
|
||||
(19:14:50) sandos: you flooder, you
|
||||
(19:14:55) bryce: oops!
|
||||
(19:15:08) bryce: I tried to send a log to japj
|
||||
(19:15:13) bryce: and I got booted off ;)
|
||||
(19:15:39) bryce: oh well
|
||||
(19:16:39) bryce: Has anybody tried out the GDB stub?
|
||||
(19:17:00) sandos: I never got to that.
|
||||
(19:17:06) bryce: You can get gdb to control Bochs, so you can do source level debug on a kernel compiled with -g.
|
||||
(19:17:16) bryce: It's pretty nice.
|
||||
(19:17:33) sandos: since Im only trying to install XP, and for some weird reason I dont have the debug symbols for that. :)
|
||||
(19:17:42) bryce: let us know if you do ;)
|
||||
(19:17:45) sandos: hehe
|
||||
(19:18:04) bryce: well it doesn't help all the time
|
||||
(19:18:39) bryce: but one advantage is that you can use any of the many interfaces to GDB that you want
|
||||
(19:19:01) bryce: There are some nice ones.
|
||||
(19:19:19) sandos: hmm
|
||||
(19:19:36) bryce: But not all of the bochs debugger features are available because they are not standard, like "break when you switch to protected mode"
|
||||
(19:19:55) sandos: is that part of the bochs debugger??
|
||||
(19:20:04) bryce: I think so
|
||||
(19:20:48) sandos: I could use that.
|
||||
(19:20:58) bryce: :)
|
||||
(19:21:25) bryce: Also, sshwarts added MMX emulation, and he's working on SSE/SSE2 right now.
|
||||
(19:22:42) bryce: sshwarts: I thought that would be mostly used to speed up performance on some multimedia tasks, but I think it turned out to fix a few windows boot bugs.
|
||||
(19:22:49) astaroth: wow, this is much faster
|
||||
(19:23:13) sandos: Lets hope it fixes XP
|
||||
(19:23:13) sandos: =)
|
||||
(19:23:15) bryce: (he must have tried Kevin's code)
|
||||
(19:24:17) sandos: kevins code?
|
||||
(19:24:37) bryce: (I'm guessing astaroth just did configure --enable-all-optimizations)
|
||||
(19:24:44) astaroth: also enabled the timer stuff, so now the screen saver isn't kicking in every 5 seconds :) (although, if had tweaked the IPS setting, i suppose that would have helped aswell)
|
||||
(19:24:58) sandos: ah
|
||||
(19:25:24) astaroth: this is MUCH faster. You guys rock
|
||||
(19:25:25) sandos: "the timer stuff" being "real-time pit" (which is going to get another name or?)
|
||||
(19:25:32) sandos: ?
|
||||
(19:25:34) sshwarts: BTW, about SSE ... Somebody knows a good ieee754 floating point emulation library ?
|
||||
(19:26:25) sshwarts: I could write my own one but it will take much more time
|
||||
(19:26:54) bryce: does the fpu directory have a complete library?
|
||||
(19:27:22) bryce: I don't know of one, but I'd be surprised if there wasn't one on the web somewhere.
|
||||
(19:27:42) sshwarts: fpu directory not ieee754 compatible
|
||||
(19:28:03) sshwarts: and also have a bugs ;)
|
||||
(19:28:07) bryce: :)
|
||||
(19:28:13) sandos: what is ieee754?
|
||||
(19:28:16) bryce: I believe it.
|
||||
(19:28:25) bryce: standard for floating point calculations
|
||||
(19:29:02) sandos: http://oss.software.ibm.com/mathlib/
|
||||
(19:29:09) sandos: maybe
|
||||
(19:30:14) astaroth: the project is a mips emulator, but they do say that they "include an IEEE754-compliant FPA instruction emulator"
|
||||
(19:30:16) astaroth: at
|
||||
(19:30:33) bryce: sshwarts: how does Java do it? Does it depend on the host processor's FPU?
|
||||
(19:30:34) astaroth: http://www.algor.co.uk/algor/info/sde-benefits.html
|
||||
(19:30:51) sandos: bryce: I think so
|
||||
(19:32:28) sandos: that mathlib from ibm isnt complete, but accurate and LGPL as I can see
|
||||
(19:32:51) bryce: sshwarts: why don't you ask on the mailing list? Maybe someone else has heard of one.
|
||||
(19:33:13) bryce: I don't think it's worth the time to consider writing one
|
||||
(19:33:24) bryce: even though I know you can work fast :)
|
||||
(19:33:58) sshwarts: I asked, may be you not seen ?
|
||||
(19:34:28) sshwarts: The best library that I found now doesn't have complete support of NaNs and
|
||||
(19:34:37) sshwarts: doesn't have sqrt and reciprocals
|
||||
(19:34:43) bryce: I spent about 6 months doing floating point verification on a 64bit processor... not enough to know everything but enough to know that there are many many details to get right, like denorms and stuff.
|
||||
(19:36:19) bryce: Maybe you should ask on list again. :)
|
||||
(19:36:44) sshwarts: bryce: Ok, I'll ask and you'll answer ;)
|
||||
(19:36:50) bryce: haha if I can
|
||||
(19:37:41) japj: btw, does anyone know how some bios'es can boot from the network?
|
||||
(19:38:05) japj: (I'm assuming there is some 'standard' ?)
|
||||
(19:39:50) sshwarts: and about bioses ... anyone know where I can find VESA VBE display driver for Win98 that will work with Bochs ?
|
||||
(19:40:12) sandos: japj: there are standars. One from intel I think, cant remember the name of it.
|
||||
(19:40:38) sshwarts: name of what ?
|
||||
(19:40:40) japj: sshwarts : maybe the scitech display doctor can?
|
||||
(19:41:22) sshwarts: May be there is a bug in VBE inmplementation but SDD also failed.
|
||||
(19:41:41) japj: japj : the windows version of SDD?
|
||||
(19:42:13) sshwarts: SDD 6.53 for Windows. It succefully switched video mode but
|
||||
(19:42:19) japj: sshwarts: I have never tried SDD with windows under Bochs (since I couldn't get Windows installed, but that might be fixed)
|
||||
(19:44:55) bryce: Christophe and I have been working on plugins for devices and for guis.
|
||||
(19:45:18) bryce: Bochs plugin = shared library that can be selected and loaded at run time
|
||||
(19:45:23) cbothamy: right ;-)
|
||||
(19:45:34) sandos: sounds really nice
|
||||
(19:45:48) bryce: We're working in a cvs branch called BRANCH_PLUGINS
|
||||
(19:45:56) japj: sshwarts : btw, I don't think SDD 6.53 will do, version 7 (http://www.scitechsoft.com/products/enterprise/enterprise_download/sdd_win_download.html)
|
||||
(19:46:06) sshwarts: could you try SDD in Windows ?
|
||||
(19:46:08) bryce: and it's not ready to go into the main trunk yet, but it is getting close.
|
||||
(19:46:31) sshwarts: On scitechsoft website there is a list of supported card
|
||||
(19:46:35) japj: sshwarts: should have support for a display driver using Vesa VBE
|
||||
(19:46:54) sandos: japj: ah, yeah, the intel thing is called PXE. I think netboot/etherboot is more common to boot linux though.
|
||||
(19:46:57) sandos: I tried
|
||||
(19:47:18) sandos: PXE with my 3com, never got it going Im afraid since Im on a campus where I cant freely set up bootp/dhcp servers.
|
||||
(19:47:48) bryce: One of the big benefits of the plugins is that I think we will be able to put a lot more features into a release binary package, without increasing the download size by a huge amount.
|
||||
(19:48:03) sshwarts: all supported cards from the their list has a 3D and thought that SDD7 already not supports old VGA cards ...
|
||||
(19:49:12) japj: sshwarts : yeah, but if I remember correctly they also have a 'generic' windows display driver that can use an existing VESA VBE to display windows graphics
|
||||
(19:49:49) bryce: Has anybody noticed that most of our disk images on the web site are out of date and don't work anymore?
|
||||
(19:50:03) bryce: (e.g. bochsrc invalid, roms fail)
|
||||
(19:50:15) japj: bryce: how often does anyone download them?
|
||||
(19:50:26) sshwarts: I not found it, may you know the filename ?
|
||||
(19:50:45) bryce: not sure. but they are there to save people time, not waste people's time ;)
|
||||
(19:50:48) japj: bryce: I would suggest to split the image files and their config files
|
||||
(19:51:07) japj: bryce: although you might get people complaining that there isn't a config file present :)
|
||||
(19:51:15) bryce: bochs.sf.net seems to be down right now
|
||||
(19:51:28) sandos: entire sf.net seems down actually
|
||||
(19:51:28) japj: bryce: sf was having several problems today
|
||||
(19:51:40) bryce: japj: I think it is important to include a bochsrc, because you have to guess the disk geometry otherwise.
|
||||
(19:51:43) sandos: both netboot and etherboot homepages was down :(
|
||||
(19:52:25) bryce: japj: the bochsrc is reasonably stable across versions, but the ROM frequenly needs to be changed. Maybe we should include disk images, bochsrc, but not ROMs.
|
||||
(19:52:32) sshwarts: somebody tryed SSE branch in last time ?
|
||||
(19:52:51) bryce: japj: I like having a TAR that people can install and use without much guessing/hacking
|
||||
(19:53:02) bryce: sshwarts: I tested that it compiled a few days ago when adding configure options
|
||||
(19:53:11) japj: bryce : yes, but you can have a tar with the latest rom images seperately
|
||||
(19:53:28) bryce: sshwarts: from past experience with branches, almost nobody will try it until it gets into the main CVS trunk
|
||||
(19:54:04) bryce: japj: yes
|
||||
(19:54:48) sshwarts: I mean with x86-64. I tested that it not brokes MMX results, but I don't know if it not fails with x86-64
|
||||
(19:55:11) bryce: japj: it would be nice if we could make some sort of "standard" for what goes into our disk image packages. they are all different now. some have bochsrc's, some don't. some have roms, some don't. some are just a gzipped image, while some are TARs or ZIPs with other stuff included.
|
||||
(19:55:50) sandos: can bochsrc "#include" eachothers ?
|
||||
(19:56:11) japj: bryce : I think the best thing would to seperate the images from files that can change frequently, you don't want to upload/download a new file each time a change is made to the bios/etc
|
||||
(19:56:34) bryce: sshwarts: I don't know, sorry. I think as soon as soon as you think adding SSE to the main branch will not damage anything when it is turned off, you may want to go ahead and bring it into the main branch.
|
||||
(19:57:03) bryce: japj: I agree
|
||||
(19:57:58) bryce: japj: I hope I can find someone with good internet connection to download all the images, make the packages consistent with each other, and upload them again.
|
||||
(19:58:13) bryce: japj: not a good use of my time, when I have 20 bugs to fix
|
||||
(19:58:16) bryce: ;)
|
||||
(19:58:37) japj: btw. <offtopic>I found myself a new appartment last week (still need to 'officially' call in the decision tomorrow, but it looks ok).. result is that I'll probably be more busy with preparing to move in, then with something else</offtopic>
|
||||
(19:59:15) japj: + I'll probably switch from cable (lousy upload speed) to ADSL (but with less download speed)
|
||||
(19:59:20) bryce: sandos: I think #include works now... based on what I see in main.cc
|
||||
(19:59:46) bryce: japj: not targeting you in particular, but I hope someone can do it
|
||||
(19:59:51) sshwarts: somebody, who logging this discussion, can mail the complete log to me ?
|
||||
(20:00:10) bryce: I will put it on bochs web page afterward.
|
||||
(20:00:16) japj: bryce : I understand
|
||||
(20:00:40) bryce: Anybody had a chance to try wxWindows? I know sandos has been.
|
||||
(20:00:55) japj: bryce : I would gladly do it, if my upload speed wasn't so lousy
|
||||
(20:01:30) SnitraM: Perhaps this has already been covered as I'm late: Why should we jump to 2.0 instead of 1.5 or 1.6?
|
||||
(20:01:45) bryce: snitra: because so much has been added since 1.4
|
||||
(20:01:56) bryce: it's somewhat arbitrary as you know
|
||||
(20:01:58) SnitraM: So make it 1.5...
|
||||
(20:02:15) bryce: then 1.9, 1.15, 1.22, when do you switch?
|
||||
(20:02:23) bryce: :)
|
||||
(20:02:28) SnitraM: After 1.9 of course.
|
||||
(20:02:31) sshwarts: 1.5 is also very "round" number ;)
|
||||
(20:02:47) bryce: those numbers are not base 10
|
||||
(20:03:09) bryce: but anyway it's just to indicate that there have been major upgrades to lots of things
|
||||
(20:03:31) sandos: bryce: shouldnt we just then include a "snippet" of a bochsrc that only includes the disk-image specific things, and let the user #include that from another bochsrc? maybe thats too much work for just easily testing images though.
|
||||
(20:03:40) bryce: and it's partly for the dramatic effect as well ;)
|
||||
(20:04:59) bryce: sandos: I just want a user to be able to download it, do a MINIMUM of steps, and boot the image. But since bios changes regularly, let's not package the bioses.
|
||||
(20:06:00) bryce: Anybody had a chance to try wxWindows? So far my goal has been to get it stabilized so that it can do everything that the old text config interface and the other GUIs can do.
|
||||
(20:06:25) japj: bryce: what is the currently expected ATA of 2.0? (since there is still some work to do, are we aiming for Oct/Nov/Dec?)
|
||||
(20:06:26) sshwarts: zwane: what about SMP ? it able to boot something other than smpdemo image ? WinNT for example ?
|
||||
(20:06:44) SnitraM: I see that at least one of my suggestions for making bochs compile with DJGPP hasn't found its way into CVS (<http://marc.theaimsgroup.com/?l=bochs-dev&m=102898262110890&w=2>). I humbly suggest you merge parts 1 and 4, and perhaps 3.
|
||||
(20:07:01) bryce: But the reason I'm so interested in it is that we can do a LOT more that other guis in terms of dialog boxes, help screen, drag and drop, whatever we want, without having to reimplement all the same features in 10 other gui libraries.
|
||||
(20:09:54) bryce: SnitraM: when SF comes back online I will add a bug report with that URL in it.
|
||||
(20:10:08) japj: bryce : you mean it's a multiplatform gui library?
|
||||
(20:10:12) bryce: yes
|
||||
(20:10:21) SnitraM: bryce: Thanks!
|
||||
(20:10:36) japj: that's always better then to reinvent the wheel for every platform.
|
||||
(20:10:44) bryce: wxWindows works on windows, X11, macos, beos, etc.
|
||||
(20:10:50) japj: (but does it support fullscreen? :)
|
||||
(20:11:02) bryce: it has a very good selection of text boxes, buttons, etc that are portable.
|
||||
(20:11:34) bryce: not sure. SDL does support fullscreen. Maybe you would want wxWindows dialogs and menus but an SDL fullscreen display?
|
||||
(20:11:51) japj: that means you need to be able to switch at runtime
|
||||
(20:11:54) ***SnitraM has to go. Will see you some other time.
|
||||
(20:12:02) bryce: japj: probably if you make a black window that is big enough, it could
|
||||
(20:12:15) bryce: thanks SnitraM :)
|
||||
(20:12:39) bryce: japj: could be done. Just wait until you see our plugins. :)
|
||||
(20:13:08) bryce: japj: but I'm not going to promise it
|
||||
(20:13:12) japj: do they resemble the plex86 plugins?
|
||||
(20:13:19) bryce: very closely, yes
|
||||
(20:14:06) bryce: I hope the device code can be almost 100% shared between the two
|
||||
(20:14:14) bryce: eventually
|
||||
(20:14:33) japj: it would be nice if you could put a bochs plugin into plex86 (and vice versa)
|
||||
(20:14:38) japj: yep
|
||||
(20:15:10) cbothamy: actually there are differences so the vga devices can't be the same
|
||||
(20:15:34) bryce: nothing that an ifdef can't handle, right ? :)
|
||||
(20:15:39) cbothamy: sure
|
||||
(20:15:41) bryce: or maybe a few
|
||||
(20:16:02) bryce: having them united would save both projects some work, even if there are occasional ifdefs
|
||||
(20:16:25) bryce: I unsubscribed from plex86 lists a while ago. Are they still moving, or still talking?
|
||||
(20:16:28) japj: :) well... maybe if the plex86 project becomes more active they see the light
|
||||
(20:16:30) cbothamy: sure, that would be a benefit for everybody
|
||||
(20:17:12) japj: ... anyway, gotta go.. (I got a three day course at work tomorrow and I need the sleep badly :)
|
||||
(20:17:30) cbothamy: hum... don't know, I will propose to port Bochs2 devices to plex86 when we're ready
|
||||
(20:17:36) bryce: japj: glad you could join us
|
||||
(20:17:46) japj: bryce : I
|
||||
(20:17:48) japj: 'll
|
||||
(20:18:25) japj: probably try to do some 'leftover' work for the Vesa stuff for bochs 2.0
|
||||
(20:18:38) bryce: japj: you asked about a target date
|
||||
(20:18:55) japj: yes
|
||||
(20:18:59) bryce: target date is something like Nov 1 for release
|
||||
(20:19:15) bryce: but it will probably slip a bit when we look more closely at our bug list :)
|
||||
(20:19:31) japj: bryce : the feature list also needs a cleanup :)
|
||||
(20:19:37) bryce: that too
|
||||
(20:19:43) bryce: please mark things for v2.0 if appropriate
|
||||
(20:20:00) bryce: or mark them "long term goal" or close them
|
||||
(20:20:19) sshwarts: Release will not have complete SSE/SSE2 but its integer part will be ready
|
||||
(20:20:53) japj: anyway, good night (or good morning wherever you are) - I'm heading to bed...
|
||||
(20:21:18) bryce: sshwarts: cool. I think just having a decode of all instructions is the most important thing, because then people can discover which instructions are actually needed.
|
||||
(20:21:32) bryce: but we will take whatever you have :)
|
||||
(20:21:54) sshwarts: just decoding already is
|
||||
(20:23:37) bryce: One of the things I've been struggling with in wxWindows is when to load
|
||||
the bochsrc. The wxWindows app starts up with a menubar, toolbar, and a
|
||||
big black rectangle for the VGA screen. The menus let you change the
|
||||
configuration and start simulating. Then you can also stop simulating,
|
||||
change parameters and start it up again.
|
||||
(20:24:00) bryce: Do you think it should always load a bochsrc when you start the application?
|
||||
(20:26:23) bryce: This was an issue for the text mode version as well. If it loads a bochsrc instantly, then you don't have an opportunity to say, "I want to load this other bochsrc instead." But if it doesn't load a bochsrc at the start, then have to click on more things before you can start running.
|
||||
(20:27:49) sshwarts: bryce: merging SMP fixes is panned for the release ?
|
||||
(20:29:06) sshwarts: I mean planned ...
|
||||
(20:29:27) bryce: sshwarts: yes, if we can decide which fixes to merge. If you know of any in particular, talk to zwane and check them in on the SMP branch
|
||||
(20:30:27) sshwarts: zwane: you are here ?
|
||||
(20:30:52) bryce: sshwarts: zwane is always logged in, but may be away from his machine now
|
||||
(20:30:55) d_Eric: has anyone been successful in getting Windows (any version) running in > 640x480x4bit mode inside bochs?
|
||||
(20:34:02) bryce: not sure
|
||||
(20:34:15) bryce: 4 bit mode? 16 colors?
|
||||
(20:35:18) d_Eric: it would be great if Bochs could include a Windows display driver for its super-vga interface, but it looks like you need M$ compiler to produce drivers
|
||||
(20:35:51) bryce: if we know of one, we can just give people the url
|
||||
(20:36:01) sshwarts: I asked about it, people says to try SDD7 as display driver, I am downloading it now ;)
|
||||
(20:36:54) d_Eric: that would be super-slick if the simulated h/w was close enough to a real board that someone else's driver would work
|
||||
(20:37:53) bryce: Anybody know how hard it would be? Do some video cards provide adequate specs to write a model of them?
|
||||
(20:38:03) sshwarts: S3 for example ...
|
||||
(20:38:34) cbothamy: Yes, I post about this in the ml. We settled down on a voodoo3 card, if I remember right
|
||||
(20:38:44) d_Eric: I have the specs for the old ATI Mach64 graphics engines
|
||||
(20:39:22) bryce: It might help to hack an xfree86 server that talks to that card, and log everything that goes between the cpu and the video card, for reference. Then in Bochs we could run the same xfree86 server and see how it compares.
|
||||
(20:40:51) d_Eric: cbothamy: do you know where the docs for voodoo3 could be downloaded?
|
||||
(20:41:09) cbothamy: yes, specs are freely available. Wait a sec
|
||||
(20:42:58) cbothamy: my post about video cards in the ml: http://marc.theaimsgroup.com/?l=bochs-dev&m=103062757300695&w=2
|
||||
(20:43:21) cbothamy: voodoo3 specs : http://ftp.yars.free.net/pub/doc/Hardware/Video/voodoo3_spec.zip
|
||||
(20:43:28) bryce: nice
|
||||
(20:44:09) sandos: "- the "virtual to real display" rendering architecture" <- what is that?
|
||||
(20:44:14) d_Eric: thanks
|
||||
(20:44:36) sandos: I mean, is anything done on that today?
|
||||
(20:45:01) cbothamy: No, I would really like to be able to zoom in and out in the virtual bochs screen
|
||||
(20:45:16) cbothamy: That means virtualize the monitor
|
||||
(20:45:28) sandos: ok
|
||||
(20:45:38) bryce: by integer factors, I assume
|
||||
(20:46:10) bryce: probably useful to have separate x,y scale factors to fix aspect ratio differences
|
||||
(20:46:15) cbothamy: performances-wise yes.
|
||||
(20:47:47) bryce: A few weeks ago I made a binary snapshot for several platforms. For each platform I made about 20 binaries with different configuration options like these: bochs.normal, bochs.dbg, bochs.sdl, bochs.rfb, bochs.smp2, bochs.icache, bochs.wx... With all the binaries built like this, it was easy to run each binary on a disk image to verify that it started up and booted ok.
|
||||
(20:48:29) bryce: So my question is, if I build these binaries as the release gets closer, would some people be willing to download them and try them out? In the Oct 2 snapshot I did this and the TARs with 20 binaries were over 5 meg. Would it help if each could be downloaded separately, or does that make it even more labor intensive?
|
||||
(20:49:01) sandos: I could test them, and I dont mind large files.
|
||||
(20:49:10) cbothamy: same for me
|
||||
(20:49:23) bryce: do you prefer a massive tar file full of binaries
|
||||
(20:49:31) bryce: rather than ability to download just a few?
|
||||
(20:49:44) bryce: like 5-10meg
|
||||
(20:49:55) sandos: I do
|
||||
(20:50:20) cbothamy: one big tar file is fine
|
||||
(20:50:21) d_Eric: perhaps there should be 1 with just "standard" configurations (all defaults, all optimizations on), and then another one with the 20ish binaries
|
||||
(20:50:28) bryce: yes
|
||||
(20:50:46) bryce: that makes sense
|
||||
(20:50:55) d_Eric: but I don't think it would be necessary to have more mix-and-match than just those 2 options
|
||||
(20:51:18) bryce: I might make these once a week or so
|
||||
(20:51:37) bryce: The other component for testing is Disk Images
|
||||
(20:51:45) bryce: everybody has a few, and it's great to try them
|
||||
(20:52:08) bryce: let's also find some volunteer to clean up the disk images on the web page
|
||||
(20:52:25) bryce: or else I should remove links to ones that have invalid configs
|
||||
(20:52:32) d_Eric: what would be involved in such cleanup?
|
||||
(20:52:32) bryce: until they are fixed
|
||||
(20:52:37) bryce: not much really
|
||||
(20:52:59) bryce: just download them, get them all into a "standard package"
|
||||
(20:53:19) bryce: for example I think we decided that roms should NOT be included, but a working bochsrc that works for current cvs SHOULD be.
|
||||
(20:53:33) bryce: then tar them back up and send to me or to SF
|
||||
(20:53:36) d_Eric: the package would be a tar/zip containing the disk image & the bochsrc ?
|
||||
(20:53:57) bryce: yes, and a README that tells a little about it is nice
|
||||
(20:54:17) bryce: e.g. what is the root password? :) what packages are installed
|
||||
(20:54:40) d_Eric: lol, yes that would be useful. I could give that a shot
|
||||
(20:55:04) bryce: that would be great
|
||||
(20:55:13) bryce: hope you have a good net connection :)
|
||||
(20:55:52) d_Eric: well, I'm about to find out ;)
|
||||
(20:56:00) bryce: I think TAR.GZ is good and standard
|
||||
(20:56:11) bryce: I like bz2 but I'm not sure if winzip will understand it
|
||||
(20:56:30) d_Eric: can Mac's deal with tar.gz ?
|
||||
(20:56:42) bryce: macosx certainly can
|
||||
(20:56:52) d_Eric: good point
|
||||
(20:57:02) cbothamy: legacy macos can with the right tool
|
||||
(20:57:17) bryce: there seems to be zero interest in bochs on macos9, among mac developers at least
|
||||
(20:57:52) cbothamy: well, i've tried to recompile bochs on macos. Did not work at all.
|
||||
(20:58:07) d_Eric: VirtualPC is a lot faster than bochs, too
|
||||
(20:58:28) bryce: d_eric: wonder what their budget it... :)
|
||||
(20:58:32) cbothamy: but is not open source AFAIK
|
||||
(20:58:38) bryce: d_eric: wonder what their budget is...
|
||||
(20:58:44) sshwarts: VirualPC, VmWare and etc has a direct execution of instructions
|
||||
(20:58:49) sandos: winzip doesnt do bz2, too bad.
|
||||
(20:58:55) sshwarts: it DEFINITLY faster
|
||||
(20:59:23) cbothamy: VirtualPC for mac has not
|
||||
(20:59:33) d_Eric: definitely not open source - they got access to the windows source, and then tuned + optimized for it
|
||||
(20:59:56) bryce: cbothamy I think they translate into native code though
|
||||
(21:00:00) cbothamy: that's right. Never tried to boot linux under virtual PC for mac
|
||||
(21:00:12) cbothamy: dynamic translation you mean ?
|
||||
(21:00:21) bryce: cbothamy: I am not sure, but I think so.
|
||||
(21:00:47) bryce: maybe that will be for v3.0 ;)
|
||||
(21:01:20) bryce: if we have 2x speed improvement for 2.0, then we'll have to work hard for the next major version!
|
||||
(21:01:40) bryce: Has anybody been thinking about bochs regression testing?
|
||||
(21:02:02) cbothamy: yes
|
||||
(21:02:08) bryce: like comparing the simulation results of one version of Bochs against another, while replaying the exact I/O reads and writes?
|
||||
(21:02:46) cbothamy: It might not be possible to replay exact IO
|
||||
(21:03:00) bryce: why not, I'm willing to log it to a file. :)
|
||||
(21:03:22) cbothamy: I was thinking about logging the execution path in a file
|
||||
(21:03:33) sandos: cbothamy: like every branch?
|
||||
(21:03:36) bryce: what about memory activity?
|
||||
(21:04:22) d_Eric: what about booting a certain disk image with *no* k/b or mouse input, and take screenshots at predefined instruction counts
|
||||
(21:04:39) cbothamy: I'm not sure what you mean by memory actvity
|
||||
(21:04:41) sandos: d_Eric: well, sometimes you need/want to use keyboard to get further etc
|
||||
(21:04:53) bryce: There are several different levels you might want to test. One of them is to verify that two simulations are absolutely identical, and if there are any differences you want to know exactly where the simulations diverge.
|
||||
(21:06:12) bryce: This would be needed to test new experiments on the CPU emulation, especially if we attempt to do dynamic translation or take advantage of x86-on-x86 speedups.
|
||||
(21:06:55) bryce: memory activity = checking that the contents of memory are the same for two runs, or checking that all reads and writes produced the same values on two runs.
|
||||
(21:07:06) sshwarts: what is dynamic translation ?
|
||||
(21:07:47) bryce: if bochs could read x86 instructions and generate the equivalent implementation in assembly on the computer it's running on
|
||||
(21:08:09) bryce: as opposed to calling a function pointer for each instruction that we see
|
||||
(21:08:36) d_Eric: it can sometimes be even more sophisticated -- you can do all the standard compiler optimizations on the input machine code, like constant
|
||||
(21:08:47) d_Eric: folding, etc
|
||||
(21:10:20) bryce: One approach that we've talked about is micro-ops. Each x86 instruction is translated into a series of simple operations, we can do some kind of optimizations on the micro-ops as d_eric says, and then a code generator to turn micro ops into machine code for that platform.
|
||||
(21:10:48) bryce: You'd get the most benefit if you can translate a whole basic block at a time
|
||||
(21:11:01) d_Eric: the difficult part is that, you will have some intermediate representation (trees, stack-based language, small RISC instructions, etc). and you need to express __every__ x86 operation in that representation
|
||||
(21:11:08) bryce: (basic block = series of instructions that end at a branch)
|
||||
(21:11:40) bryce: d_eric: not every, doing just the common ones will help.
|
||||
(21:12:10) d_Eric: oh, so uncommon ones would just trap back to the interpreter
|
||||
(21:12:12) bryce: d_eric: uncommon ones can be implemented as function calls
|
||||
(21:12:29) bryce: yes
|
||||
(21:13:18) bryce: it would be a fun project, but quite a challenge. Basically it's like writing a JIT compiler.
|
||||
(21:13:34) d_Eric: one nifty consequence of that would be that you could have several different front ends for machine-code -> micro-op, one for x86, ppc, alpha, and they would all use the same infrastructure. sounds like a 3.0 (4.0) feature though . . .
|
||||
(21:13:47) bryce: I REALLY wish we could get Julian Seward, who wrote Valgrind, interested in helping.
|
||||
(21:14:19) bryce: Valgrind is a memory checking tool for linux only, but it's implemented exactly like that: translate to micro-ops, optimize, and generate x86 code.
|
||||
(21:14:31) bryce: but he is just doing user level code
|
||||
(21:18:26) bryce: Christophe, how long do you think it will take us to get plugins ready for main branch? A week?
|
||||
(21:20:47) bryce: Plugins don't quite work on any platform other than linux. Shared libraries seem completely different on each platform, even though I'm using libtool which helps to hide the differences.
|
||||
(21:20:57) cbothamy: one week sounds ok.
|
||||
(21:21:35) d_Eric: i never quite understood what plugins were supposed to do... is there any documentation on that?
|
||||
(21:21:41) bryce: no, they are very new
|
||||
(21:21:51) bryce: here's what I wrote on the web page (sorry web site is down):
|
||||
(21:22:05) bryce: Christophe and Bryce are working on plugin support, so that you can compile in support for many more options and enable them at runtime. For example, you could compile in support for 4 different gui libraries (X11, SDL, RFB, wxWindows) and select between them in your bochsrc.
|
||||
(21:22:44) d_Eric: oooh! very cool
|
||||
(21:22:49) bryce: A plugin is a shared library (.so on unix, .dll on win32) that can be loaded at runtime
|
||||
(21:23:02) bryce: In our plugin branch, we can build it so that you can
|
||||
(21:23:17) bryce: compile all guis into plugins
|
||||
(21:23:27) bryce: (the ones that your platform supports at least)
|
||||
(21:23:34) bryce: and then at run time you can say "I want SDL this time"
|
||||
(21:23:43) bryce: or "I want to use Term GUI"
|
||||
(21:24:04) bryce: For devices, we can make it so that bochs only loads the devices that you have enabled in bochsrc.
|
||||
(21:24:33) bryce: And I hope that it's possible to make libcpu_fast.so and libcpu_debug.so and libsmp_debug.so
|
||||
(21:25:27) astaroth: bryce: would plugins be strictly for user interface stuff or will there be a hardware devices? or would there be 2 separate plugin api's?
|
||||
(21:25:29) bryce: instead of having to reconfigure and recompile when you change any options.
|
||||
(21:25:46) bryce: astaroth: right now there are 2 kinds of plugins: hardware device and gui.
|
||||
(21:26:16) d_Eric: is the plugin model that each plugin implements a C++ class derived from common base type?
|
||||
(21:26:25) astaroth: got it.
|
||||
(21:26:28) bryce: :)
|
||||
(21:26:57) bryce: we have two possible ways to do it. I think Christophe and I prefer what you just said.
|
||||
(21:27:16) astaroth: be neat if the hardware device plugin could be done in an os-independant bytecode or something
|
||||
(21:27:26) bryce: the other way is a bunch of C function pointers, and macros that call them.
|
||||
(21:27:54) osmaker|hereish: astaroth: u could interface to it with .NET maybe
|
||||
(21:28:03) bryce: d_eric: one problem we have run into is that on some systems you cannot be sure if C++ constructors in a shared library module will ever be called! :(
|
||||
(21:28:33) astaroth: osmaker|hereish: ack
|
||||
(21:28:45) bryce: d_eric: so it's possible that platform limitations might cause us to use the C function pointer method, but I hope the C++ class method will work out.
|
||||
(21:29:05) d_Eric: even if you explicitly (sp?) call the constructor?
|
||||
(21:30:12) bryce: if you explicitly call it, it's fine. But if you write "bx_floppy_c the_floppy;" as a global variable inside the plugin code, I've seen cases where it didn't ever get called.
|
||||
(21:30:56) d_Eric: yes, I have seen that. C++ shared objects require more programming dicipline than static C++ programs
|
||||
(21:30:58) bryce: Christophe, plex86 uses C++ devices now, right? I bet they could use our virtual functions too.
|
||||
(21:31:44) cbothamy: Not so sure, because the wrapper is C code, not C++. I'll check
|
||||
(21:31:59) bryce: Hmm.
|
||||
(21:32:38) bryce: Anyway, hopefully in the next week we can get the plugin code cleaned up and merged into CVS main trunk.
|
||||
(21:33:34) bryce: I want to get SSE in there too, and then it sounds like a good time to start the "feature freeze"
|
||||
(21:34:27) d_Eric: all of SSE, or just decoding + stubs ?
|
||||
(21:34:37) bryce: not all will be ready
|
||||
(21:35:01) bryce: stanslav says decoding is already ready, and he's working on the integer part
|
||||
(21:35:08) bryce: stanislav
|
||||
(21:35:37) bryce: Maybe the release should just be deoding & stubs as you said, rather than a brand new implementation of part of SSE
|
||||
(21:36:45) bryce: although bugs inside #if BX_SUPPORT_SSE ... #endif are not going to hurt anybody, in general
|
||||
(21:39:21) osmaker|hereish: will the device plugin stuff allow ppl to make gfx card devices for bochs?
|
||||
(21:39:35) bryce: you can do that, with plugins, or without
|
||||
(21:40:10) bryce: device plugin just means that the devices can be loaded at runtime.
|
||||
(21:44:07) bryce: Any win32 DLL experts out here?
|
||||
(21:44:42) bryce: With libtool I can build bochs plugin DLLs in cygwin, but so far I cannot load them and install them.
|
||||
(21:45:13) bryce: I'm trying to make it work using libtool and its little library call libltdl, which is supposed to support windows LoadLibrary/GetProcAddress interface
|
||||
(21:45:30) bryce: ...little library called libltdl, ....
|
||||
(21:47:28) bryce: guess not. :)
|
||||
(21:48:21) bryce: Any patches that are sitting around, with nobody looking at them?
|
||||
(21:49:09) bryce: If so, you should probably write a reminder to the mailing list, saying that we should apply this or that patch and why.
|
||||
(21:49:22) cbothamy: yes, there is the block device patch for linux from Phil Marek
|
||||
(21:51:06) bryce: looks reasonable
|
||||
(21:51:16) bryce: you can check it in if you want :)
|
||||
(21:51:29) cbothamy: ok fine
|
||||
(21:51:55) bryce: We have 37 patches sitting there.....
|
||||
(21:52:11) bryce: 904k of patches
|
||||
(21:52:16) cbothamy: yes, some must be outdated
|
||||
(21:52:42) bryce: Often I look at one and say, "I don't know anything about this. Maybe someone else will." and then it sits around.
|
||||
(21:54:06) bryce: Volker suggested that we add a "status" line or something for each patch, to help keep track of why the patch is still there. They don't very often get thrown away.
|
||||
(21:54:11) d_Eric: bryce: I have to go now. where should I send cleaned-up packages?
|
||||
(21:54:22) bryce: they are simply ignored instead.
|
||||
(21:54:35) bryce: d_eric: less than 5 meg, you can email it to me
|
||||
(21:55:05) d_Eric: ok. for bigger ones, I can put the package on my web page and send a link?
|
||||
(21:55:08) bryce: do you have any web site you can put big images on?
|
||||
(21:55:10) bryce: yes that would be ideal
|
||||
(21:55:17) d_Eric: ok
|
||||
(21:55:42) bryce: if you have a web page, why don't you do it for all of them :)
|
||||
(21:56:02) bryce: you can delete as soon as I copy them to SF
|
||||
(21:56:05) d_Eric: ok, but my web server is pretty wussy, so they have to end up back on sourceforge
|
||||
(21:56:10) bryce: definitely
|
||||
(21:56:15) d_Eric: ok
|
||||
(21:56:18) d_Eric: sounds like a plan
|
||||
(21:56:51) d_Eric: bye all
|
||||
(21:57:03) osmaker|hereish: see ya d_Eric
|
||||
(21:57:56) bryce: I was hoping that I could make wxwindows so good that it could be the default for 2.0, but I doubt that it is there yet.
|
||||
(21:58:17) bryce: Sandos, do you have an opinion on that?
|
||||
(21:59:17) bryce: I think it looks a lot more like a modern application than the text mode menus plus the native GUI window.
|
||||
(21:59:42) bryce: (sandos has been using wx a lot)
|
||||
(22:00:21) bryce: When I make binary snapshots, I will make wx binaries that are easy for people to play around with.
|
||||
(22:00:38) osmaker|hereish: can the wxwindows option be compiled in cygwin without getting any special libs?
|
||||
(22:01:09) bryce: no, you must download the libs to compile
|
||||
(22:01:25) osmaker|hereish: k
|
||||
(22:01:34) bryce: http://bochs.sourceforge.net/tmp/wxwindows/binaries/cygwin/wxMSW-2.3.3-cygwinlib-release.tar.gz
|
||||
(22:01:48) bryce: that's a 3.6meg download, containing the wxwindows 2.3.3 library built for cygwin
|
||||
(22:02:03) bryce: including header files
|
||||
(22:02:30) cbothamy: I have to go, see you around
|
||||
(22:02:49) bryce: bye cbothamy
|
||||
(22:03:08) astaroth: anyone have a moment or 2 for a couple of troubleshooting questions?
|
||||
(22:03:42) bryce: osmaker: if you want to build wx in cygwin yourself, be sure to read [ 615617 ] wxWindows port won't compile in cygwin at http://sourceforge.net/tracker/index.php?func=detail&aid=615617&group_id=12580&atid=112580
|
||||
(22:03:53) bryce: astaroth: ok
|
||||
(22:06:05) astaroth: I seem to be missing something: using the freedos image from the homepage, bochs (orignally tried the rpm, then the source distro, now am using the cvs) seems to hang when trying to get to the floppy image a.img (or others for that matter) any thoughts?
|
||||
(22:06:59) bryce: are you booting the floppy, or using it after boot?
|
||||
(22:09:27) astaroth: i have tried both, and am currently booting with the c image so that i could run debug and try a raw int 13 read from the floppy, but it hangs (i continue to get the "useconds: expected ticks: ..." so it is not crashed, just held up somewhere
|
||||
(22:09:49) bryce: are you using a recent ROMBIOS with current CVS?
|
||||
(22:10:06) bryce: if bios doesn't match binary it can do strange things like that
|
||||
(22:10:23) astaroth: hmmm....
|
||||
(22:10:46) bryce: copy bios/BIOS-bochs-latest out of CVS and use it
|
||||
(22:12:34) ***astaroth hangs his head in shame
|
||||
(22:12:50) astaroth: thanks...that fixed it
|
||||
(22:13:07) bryce: great!
|
||||
(22:13:51) bryce: simple but non-obvious
|
||||
(22:14:31) astaroth: now, onward and upward. (trying to get NeXTStep/OpenStep to install)
|
||||
</pre>
|
||||
|
||||
<!--content ends here -->
|
||||
|
||||
|
||||
<!--#include virtual="includes/footer.txt" -->
|
||||
|
||||
|
||||
Last Modified on <!--#flastmod file="mailinglists.html" -->.<BR>
|
||||
|
||||
<!--#include virtual="includes/cright.txt" -->
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -1,200 +0,0 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>bochs: The Open Source IA-32 Emulation Project (IRC Chat Transcript)</TITLE>
|
||||
|
||||
<!--#include virtual="includes/header.txt" -->
|
||||
|
||||
<!--content starts here-->
|
||||
<img src="images/logo.png" alt="A Window, Tux, and the BSD Daemon" width="160" height="175" align="right">
|
||||
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Transcript of Bochs Chat from February 1, 2004</b></font><BR><BR>
|
||||
|
||||
<p>
|
||||
|
||||
<FONT SIZE="2">19:58:25</FONT> <B>Jan_B_A:</B></FONT> Hello Daniel<BR>
|
||||
<FONT SIZE="2">19:58:38</FONT> <B>danielg4:</B></FONT> hello<BR>
|
||||
<FONT SIZE="2">20:01:05</FONT> <B>cbothamy:</B></FONT> hi<BR>
|
||||
<FONT SIZE="2">20:02:22</FONT> <B>Jan_B_A:</B></FONT> Hi Christopher.<BR>
|
||||
<FONT SIZE="2">20:06:08</FONT> <B>cbothamy:</B></FONT> it's 19:10 UTC, maybe we can start<BR>
|
||||
<FONT SIZE="2">20:06:25</FONT> <B>Jan_B_A:</B></FONT> So, am I tonights newbie in this forum? Has you all taken part in similar "meetings" before?<BR>
|
||||
<FONT SIZE="2">20:07:21</FONT> <B>cbothamy:</B></FONT> ok, Jan is here, Daniel also, who else ?<BR>
|
||||
<FONT SIZE="2">20:07:42</FONT> <B>cbothamy:</B></FONT> Jan_B_A: last meeting was logged, see http://bochs.sourceforge.net/irc-20021013.html<BR>
|
||||
<FONT SIZE="2">20:10:10</FONT> <B>Jan_B_A:</B></FONT> Thanks - I am looking at it now.<BR>
|
||||
<FONT SIZE="2">20:11:05</FONT> <B>Jan_B_A:</B></FONT> FYI, I am a newcomer to Bochs. My main interest in Bochs is as a platform for running old MS-DOS and Win9x games. Some of my games run fine in DOSBox (an DOS emulator) but some don't. I hope that Bochs will eventually allow me to run anything.<BR>
|
||||
<FONT SIZE="2">20:12:44</FONT> <B>Jan_B_A:</B></FONT> I have absolutely no knowledge of x86 programming. Assemblywise I am fluent in 6502, and a bit rusty in PDP-11 and 68000.<BR>
|
||||
<FONT SIZE="2">20:13:09</FONT> <B>Jan_B_A:</B></FONT> My webmastering skills are mainly restricted to handcrafting HTML code using Vim (a vi-clone). But what I do not know, I learn!<BR>
|
||||
<FONT SIZE="2">20:13:41</FONT> <B>danielg4:</B></FONT> I'm fluent in 68000 and rusty in x86 and 6502.<BR>
|
||||
<FONT SIZE="2">20:14:07</FONT> <B>danielg4:</B></FONT> never did pdp-11<BR>
|
||||
<FONT SIZE="2">20:15:14</FONT> <B>Jan_B_A:</B></FONT> Daniel, if you are fluent in 68000, you will feel right at home with PDP-11. Addressing modes, op-codes, etc - they are so close that they could be cousins!<BR>
|
||||
<FONT SIZE="2">20:16:02</FONT> <B>danielg4:</B></FONT> that's a bit OT because bochs will be ported to neither<BR>
|
||||
<FONT SIZE="2">20:16:40</FONT> <B>Jan_B_A:</B></FONT> Okay, back on topic then - which is?<BR>
|
||||
<FONT SIZE="2">20:16:43</FONT> <B>cbothamy:</B></FONT> Jan_B_A: Jean-Michel Poure offered to help on the website. I'll tell him to contact you, ok ?<BR>
|
||||
<FONT SIZE="2">20:18:10</FONT> <B>Jan_B_A:</B></FONT> Sure. Any idea what you would like to see happening? Any urgent changes needed? Or do me and Jean-Michel just look it over, and make a internal version for approval by ???<BR>
|
||||
<FONT SIZE="2">20:19:42</FONT> <B>cbothamy:</B></FONT> There is no urgent changes needed. I guess a lot of links are wrong now, and new links could be added.<BR>
|
||||
<FONT SIZE="2">20:21:50</FONT> <B>Jan_B_A:</B></FONT> Okay. I/we will look it over and see what needs to be updated.<BR>
|
||||
<FONT SIZE="2">20:21:52</FONT> <B>cbothamy:</B></FONT> Also the source code used to be viewable on the website. The latest version available is 1.4pre1. Maybe we can remove the feature and link straight to sourceforge<BR>
|
||||
<FONT SIZE="2">20:22:51</FONT> <B>danielg4:</B></FONT> The only source I saw was ViewCVS.<BR>
|
||||
<FONT SIZE="2">20:23:01</FONT> <B>cbothamy:</B></FONT> or add the newer versions.<BR>
|
||||
<FONT SIZE="2">20:23:52</FONT> <B>cbothamy:</B></FONT> url is http://bochs.sourceforge.net/cgi-bin/lxr/source<BR>
|
||||
<FONT SIZE="2">20:24:17</FONT> <B>cbothamy:</B></FONT> Jan_B_A: do you know how to update the website ?<BR>
|
||||
<FONT SIZE="2">20:24:38</FONT> <B>Jan_B_A:</B></FONT> I have just opened up the "Web Site Request" tracker at SourceForge - Whew! I think the first line of action is to review those requests, get them closed or prioritised, and assigned to someone.<BR>
|
||||
<FONT SIZE="2">20:25:48</FONT> <B>danielg4:</B></FONT> I just checked http://bochs.sourceforge.net/cgi-bin/lxr/source. Wow, is it old!<BR>
|
||||
<FONT SIZE="2">20:25:50</FONT> <B>Jan_B_A:</B></FONT> cbothamy: I do not have a clue (yet!). But I am confident that I will figure it out.<BR>
|
||||
<FONT SIZE="2">20:27:25</FONT> <B>cbothamy:</B></FONT> Jan_B_A: absolutely, I'll check if you have admin rights on the tracker items<BR>
|
||||
<FONT SIZE="2">20:28:35</FONT> <B>cbothamy:</B></FONT> Jan_B_A: I'll write a document and send it to you. I'll also update the developer's guide at the same time<BR>
|
||||
<FONT SIZE="2">20:29:30</FONT> <B>cbothamy:</B></FONT> Jan_B_A: I think you have Admin rights <BR>
|
||||
<FONT SIZE="2">20:29:40</FONT> <B>cbothamy:</B></FONT> on the tracker items<BR>
|
||||
<FONT SIZE="2">20:30:06</FONT> <B>danielg4:</B></FONT> I know I do.<BR>
|
||||
<FONT SIZE="2">20:30:56</FONT> <B>Jan_B_A:</B></FONT> Fine.<BR>
|
||||
<FONT SIZE="2">20:31:14</FONT> <B>danielg4:</B></FONT> hello, Frank<BR>
|
||||
<FONT SIZE="2">20:31:30</FONT> <B>fcorneli:</B></FONT> hi<BR>
|
||||
<FONT SIZE="2">20:33:13</FONT> <B>cbothamy:</B></FONT> ok, Bochs 2.1.1 is still not out. I'm waiting for anybody to confirm the floppy dialog works or not on win2k.<BR>
|
||||
<FONT SIZE="2">20:33:22</FONT> <B>Jan_B_A:</B></FONT> One of the items discussed recently was a new/better format for the .bochsrc file. How do you feel about going XML with it? To start with perhaps just a frontent that uses XSL to convert it into the old form?<BR>
|
||||
<FONT SIZE="2">20:34:44</FONT> <B>danielg4:</B></FONT> I don't think that's necessary for the forseeable future.<BR>
|
||||
<FONT SIZE="2">20:35:15</FONT> <B>cbothamy:</B></FONT> Jan_B_A: I'm not sure about XML. It has been discussed once before. I don't see any benefits in using xml for a properties file.<BR>
|
||||
<FONT SIZE="2">20:35:38</FONT> <B>danielg4:</B></FONT> cbothamy: I think Volker made a second patch regarding the floppy browse.<BR>
|
||||
<FONT SIZE="2">20:35:56</FONT> <B>Jan_B_A:</B></FONT> No Win2K license here. I might be able to borrow a CD from a friend, just for testing, but it would be easier if someone with W2K already installed could test it.<BR>
|
||||
<FONT SIZE="2">20:36:19</FONT> <B>fcorneli:</B></FONT> problem is that you'll need a portable xml parser that is available on all supported platforms... is there a good portable xml parser?<BR>
|
||||
<FONT SIZE="2">20:37:25</FONT> <B>danielg4:</B></FONT> Such a parser is likely to be GPL, rather than LGPL.<BR>
|
||||
<FONT SIZE="2">20:37:41</FONT> <B>Jan_B_A:</B></FONT> The Apache project has something. The developers at my work use a lot of that stuff. Xerxes is the name I think.<BR>
|
||||
<FONT SIZE="2">20:38:08</FONT> <B>fcorneli:</B></FONT> yes, there is also the gpl vs lgpl problem...<BR>
|
||||
<FONT SIZE="2">20:38:26</FONT> <B>cbothamy:</B></FONT> gnome has libxml2, that is released under the MIT license<BR>
|
||||
<FONT SIZE="2">20:38:45</FONT> <B>fcorneli:</B></FONT> compatible with lgpl?<BR>
|
||||
<FONT SIZE="2">20:42:15</FONT> <B>cbothamy:</B></FONT> I think so. But I think we a java-properties-like configuration file would be good enough.<BR>
|
||||
<FONT SIZE="2">20:42:47</FONT> <B>danielg4:</B></FONT> I just took a quick look at the Apache license. Doesn't look compatible.<BR>
|
||||
<FONT SIZE="2">20:45:03</FONT> <B>cbothamy:</B></FONT> ok, so you all have read the roadmap document http://marc.theaimsgroup.com/?l=bochs-dev&m=107550424808607&w=2<BR>
|
||||
<FONT SIZE="2">20:45:10</FONT> <B>fcorneli:</B></FONT> XML-izing the config file can wait... but anyway, the config system needs some work... e.g. the main menu is static while it could be generated at run-time...<BR>
|
||||
<FONT SIZE="2">20:47:31</FONT> <B>danielg4:</B></FONT> I'd have to reread the LGPL.<BR>
|
||||
<FONT SIZE="2">20:47:44</FONT> <B>fcorneli:</B></FONT> Chris, how about letting the file ROADMAP live in the Bochs CVS tree? Would be a good guide for developers...<BR>
|
||||
<FONT SIZE="2">20:48:38</FONT> <B>cbothamy:</B></FONT> that's a good idea. What we could also do is use the tasks system of source forge.<BR>
|
||||
<FONT SIZE="2">20:49:04</FONT> <B>danielg4:</B></FONT> They're not mutually exclusive.<BR>
|
||||
<FONT SIZE="2">20:50:49</FONT> <B>cbothamy:</B></FONT> fcorneli: "main menu is static" that's the menu when you press the "config" button ?<BR>
|
||||
<FONT SIZE="2">20:50:57</FONT> <B>fcorneli:</B></FONT> yes...<BR>
|
||||
<FONT SIZE="2">20:51:25</FONT> <B>fcorneli:</B></FONT> the main menu text lives somewhere in a file... while it should be generated at run-time by iterating the main menu objects<BR>
|
||||
<FONT SIZE="2">20:51:45</FONT> <B>fcorneli:</B></FONT> AFAIK currently this is not the case...<BR>
|
||||
<FONT SIZE="2">20:52:32</FONT> <B>danielg4:</B></FONT> That would certainly solve the problems with hot-swapping virtual drives.<BR>
|
||||
<FONT SIZE="2">20:52:47</FONT> <B>fcorneli:</B></FONT> This stopped me from adding an extra menu for my pcidev...<BR>
|
||||
<FONT SIZE="2">20:52:58</FONT> <B>cbothamy:</B></FONT> ok, I'll add a paragraph in the roadmap about config files and dynamic config menu<BR>
|
||||
<FONT SIZE="2">20:54:23</FONT> <B>fcorneli:</B></FONT> yes, the menu menu definitely be generated a run-time so it can be changed at run-time as needed...<BR>
|
||||
<FONT SIZE="2">20:56:09</FONT> <B>Jan_B_A:</B></FONT> As I wrote earlier, I am no big coder, so my efforts wrt. the roadmap will be in the "housekeeping" category. E.g. going through the User Guide, check for a new release of FreeDOS, make a new image, etc, and get the web site/download area updated.<BR>
|
||||
<FONT SIZE="2">20:57:39</FONT> <B>Jan_B_A:</B></FONT> If Cygwin is suitable for compiling Bochs, I might take a stab at extended the 'boot:' option to take a prioritised list of devices to boot from.<BR>
|
||||
<FONT SIZE="2">20:58:03</FONT> <B>fcorneli:</B></FONT> How many people are actually actively developing on Bochs?<BR>
|
||||
<FONT SIZE="2">20:58:24</FONT> <B>cbothamy:</B></FONT> Jan_B_A: this is fine. We definitely need to keep our website and disk images up to date. <BR>
|
||||
<FONT SIZE="2">20:58:36</FONT> <B>danielg4:</B></FONT> Another thing that should be in the ROADMAP is bringing the BIOS into conformance with Ralf Brown's INT list.<BR>
|
||||
<FONT SIZE="2">21:00:07</FONT> <B>cbothamy:</B></FONT> fcorneli: between 5 and 10.<BR>
|
||||
<FONT SIZE="2">21:01:56</FONT> <B>Jan_B_A:</B></FONT> The roadmap also talks about speed.... The DOSBox people seems to plan to add some kind of Just-In-Time compiler to their emulator. Anyone been following that?<BR>
|
||||
<FONT SIZE="2">21:02:27</FONT> <B>cbothamy:</B></FONT> danielg4: this is a huge task. what we usually do is to wait for bug reports stating that a specific functions is missing.<BR>
|
||||
<FONT SIZE="2">21:03:36</FONT> <B>danielg4:</B></FONT> If we continue to do that, the BIOS will grow larger than the max size.<BR>
|
||||
<FONT SIZE="2">21:04:05</FONT> <B>fcorneli:</B></FONT> About that JiT, GNU Lightning could be an option... It's not that good (no peephole optimizations) but at least it's portable.<BR>
|
||||
<FONT SIZE="2">21:04:23</FONT> <B>cbothamy:</B></FONT> danielg4: right, Volker and I think we should rewrite parts in asm to shrink its size.<BR>
|
||||
<FONT SIZE="2">21:06:08</FONT> <B>danielg4:</B></FONT> And at the same time, introduce jump tables with all the Ralf Brown functions as placeholders.<BR>
|
||||
<FONT SIZE="2">21:08:06</FONT> <B>cbothamy:</B></FONT> for jit-compiling there is also qemu. The dynamic compiler module is lgpl. it seems to be working quite well, the can boot win98 with the latest version.<BR>
|
||||
<FONT SIZE="2">21:08:44</FONT> <B>danielg4:</B></FONT> I thought qemu only ran Linux binaries...<BR>
|
||||
<FONT SIZE="2">21:09:35</FONT> <B>cbothamy:</B></FONT> it's got two modes, one without mmu for user mode, and one with a mmu for entire systems<BR>
|
||||
<FONT SIZE="2">21:09:48</FONT> <B>danielg4:</B></FONT> If the JiT compiler module in it is LGPL, I think we should adopt it.<BR>
|
||||
<FONT SIZE="2">21:11:24</FONT> <B>cbothamy:</B></FONT> danielg4: at least we have to give it a look, to check the feasability. Now the problem is who want to do it ? <BR>
|
||||
<FONT SIZE="2">21:13:02</FONT> <B>cbothamy:</B></FONT> I add "jump tables place holders" in the bios section of the roadmap.<BR>
|
||||
<FONT SIZE="2">21:14:33</FONT> <B>fcorneli:</B></FONT> The advantage of having two modes (user mode and full system) for the CPU is that you can binary search for bugs in the instructions in user mode.<BR>
|
||||
<FONT SIZE="2">21:15:33</FONT> <B>fcorneli:</B></FONT> I once developed a 'virtual cpu' that could be detached at run-time, allowing for binary searching of bugs... it would be nice to have the same functionality for the Bochs CPU.<BR>
|
||||
<FONT SIZE="2">21:15:34</FONT> <B>danielg4:</B></FONT> That's how the 68000 works :)<BR>
|
||||
<FONT SIZE="2">21:16:57</FONT> <B>cbothamy:</B></FONT> fcorneli: I'm afraid I don't get it.. How does is work ?<BR>
|
||||
<FONT SIZE="2">21:17:22</FONT> <B>Jan_B_A:</B></FONT> *also confused about the term 'binary search for bugs'*<BR>
|
||||
<FONT SIZE="2">21:17:34</FONT> <B>fcorneli:</B></FONT> Check out: http://www.elis.ugent.be/~fcorneli/downloads/vcpu-README<BR>
|
||||
<FONT SIZE="2">21:20:16</FONT> <B>Night:</B></FONT> hi, all<BR>
|
||||
<FONT SIZE="2">21:20:31</FONT> <B>cbothamy:</B></FONT> hi Stanislav<BR>
|
||||
<FONT SIZE="2">21:20:38</FONT> <B>Night:</B></FONT> I see I too late<BR>
|
||||
<FONT SIZE="2">21:21:17</FONT> <B>Night:</B></FONT> Somebody could post be the log of dicussion ?<BR>
|
||||
<FONT SIZE="2">21:21:46</FONT> <B>fcorneli:</B></FONT> `echo /dev/random` :)<BR>
|
||||
<FONT SIZE="2">21:21:58</FONT> <B>fcorneli:</B></FONT> I mean cat...<BR>
|
||||
<FONT SIZE="2">21:23:15</FONT> <B>Night:</B></FONT> I see I didn't missed anything ? ;)<BR>
|
||||
<FONT SIZE="2">21:23:34</FONT> <B>danielg4:</B></FONT> You did, alittle.<BR>
|
||||
<FONT SIZE="2">21:24:21</FONT> <B>cbothamy:</B></FONT> log is here http://cbothamy.free.fr/projects/bochs/freenode-%23bochs.log<BR>
|
||||
<FONT SIZE="2">21:24:39</FONT> <B>danielg4:</B></FONT> Is that live?<BR>
|
||||
<FONT SIZE="2">21:24:53</FONT> <B>cbothamy:</B></FONT> hi Volker<BR>
|
||||
<FONT SIZE="2">21:25:00</FONT> <B>fcorneli:</B></FONT> Binary searching for bugs in instruction implementations is only possible when you can detach the emulation and let the user space take over.<BR>
|
||||
<FONT SIZE="2">21:26:01</FONT> <B>fcorneli:</B></FONT> Source code available at: http://www.elis.ugent.be/~fcorneli/downloads/vcpu-0.1.1.tar.gz<BR>
|
||||
<FONT SIZE="2">21:27:28</FONT> <B>vruppert:</B></FONT> Hi Christophe. After adding a new feature in the win32 runtime dialog I started testing gaim.<BR>
|
||||
<FONT SIZE="2">21:27:43</FONT> <B>Night:</B></FONT> ok, i am reading the log now<BR>
|
||||
<FONT SIZE="2">21:29:35</FONT> <B>rO|:</B></FONT> made an OS disk image, 2cts only, but maybe you like to offer it though..<BR>
|
||||
<FONT SIZE="2">21:30:28</FONT> <B>cbothamy:</B></FONT> vruppert: do we know if the win2k dialog bug is fixed ?<BR>
|
||||
<FONT SIZE="2">21:32:09</FONT> <B>vruppert:</B></FONT> I don't know. Is someone here using Bochs on Win2k ?<BR>
|
||||
<FONT SIZE="2">21:32:24</FONT> <B>Night:</B></FONT> i am<BR>
|
||||
<FONT SIZE="2">21:32:46</FONT> <B>Night:</B></FONT> I could check, just say that ;)<BR>
|
||||
<FONT SIZE="2">21:34:27</FONT> <B>Night:</B></FONT> cristophe, your log is broken between 19:09 and 19:42 or nobody really did say a word ?<BR>
|
||||
<FONT SIZE="2">21:34:43</FONT> <B>Jan_B_A:</B></FONT> Night: Physical diskettes in Win2K - can you test that too?<BR>
|
||||
<FONT SIZE="2">21:35:25</FONT> <B>Night:</B></FONT> What should be with diskettes ?<BR>
|
||||
<FONT SIZE="2">21:35:54</FONT> <B>cbothamy:</B></FONT> Night: this is local time. 19h00 utc is 20h00 local<BR>
|
||||
<FONT SIZE="2">21:36:10</FONT> <B>danielg4:</B></FONT> Night: It's the timecode that's broken, not the log.<BR>
|
||||
<FONT SIZE="2">21:38:01</FONT> <B>danielg4:</B></FONT> It is now 20:45 UTC<BR>
|
||||
<FONT SIZE="2">21:38:44</FONT> <B>Night:</B></FONT> ok<BR>
|
||||
<FONT SIZE="2">21:40:38</FONT> <B>cbothamy:</B></FONT> ok for Stanislav and Volker, we have been talking about Bochs improvements : website, config files, JIT, updating the bios, and Frank presented his virtual cpu<BR>
|
||||
<FONT SIZE="2">21:40:54</FONT> <B>Jan_B_A:</B></FONT> Sorry - I could be mixing things up - The issue with Win2K is just the dialog for handling diskettes? Not actually reading them. I think I got this mixed up due a message in the Help forum where someone had problems with diskettes in XP.<BR>
|
||||
<FONT SIZE="2">21:41:28</FONT> <B>danielg4:</B></FONT> Jan_B_A: yes<BR>
|
||||
<FONT SIZE="2">21:42:47</FONT> <B>Jan_B_A:</B></FONT> *blush*<BR>
|
||||
<FONT SIZE="2">21:42:50</FONT> <B>Night:</B></FONT> I got CVS version from yesterday. When I clicking Browse button I get "ComDialogExtendedError return 0x3002" error message<BR>
|
||||
<FONT SIZE="2">21:43:54</FONT> <B>danielg4:</B></FONT> vruppert: Does that help?<BR>
|
||||
<FONT SIZE="2">21:43:55</FONT> <B>Night:</B></FONT> with physical diskettes it working fine<BR>
|
||||
<FONT SIZE="2">21:44:10</FONT> <B>vruppert:</B></FONT> Night: That means "illegal filename"<BR>
|
||||
<FONT SIZE="2">21:45:05</FONT> <B>Night:</B></FONT> very informative ;)<BR>
|
||||
<FONT SIZE="2">21:45:40</FONT> <B>rO|:</B></FONT> is there any reason why a normal w95 bootcd shouldn't work in bochs?<BR>
|
||||
<FONT SIZE="2">21:47:03</FONT> <B>Night:</B></FONT> when I starting from empty "path" field it looks working. I have no disket images so I could not check at all<BR>
|
||||
<FONT SIZE="2">21:47:53</FONT> <B>vruppert:</B></FONT> The floppy dialog sends the path stored in the parameter to the file open dialog. It works here if the parameter contains an image filename.<BR>
|
||||
<FONT SIZE="2">21:48:12</FONT> <B>Night:</B></FONT> can you change the "ComDialogExtendedError" message to normal "Illegal filename" ?<BR>
|
||||
<FONT SIZE="2">21:48:37</FONT> <B>Jan_B_A:</B></FONT> rol: No reason. I installed Win95 fine on Bochs 2.1 running on WinXP.<BR>
|
||||
<FONT SIZE="2">21:49:08</FONT> <B>vruppert:</B></FONT> If the path is a raw device it seems to fail. We have to find a workaround for this case.<BR>
|
||||
<FONT SIZE="2">21:50:49</FONT> <B>rO|:</B></FONT> someone trying yesterday on OS X had probs installing a w95 bootcd<BR>
|
||||
<FONT SIZE="2">21:51:23</FONT> <B>Night:</B></FONT> that about APIC and SMP support in 2.1.x ? We already have 3 patches for APIC in "patches" folder.<BR>
|
||||
<FONT SIZE="2">21:51:46</FONT> <B>Night:</B></FONT> Is any of them gets Bochs closer to WinNT SMP boot ?<BR>
|
||||
<FONT SIZE="2">21:53:11</FONT> <B>vruppert:</B></FONT> I have to leave the channel now. Tomorrow I will read the log and try to find a workaround for the win32 floppy dialog problem.<BR>
|
||||
<FONT SIZE="2">21:53:29</FONT> <B>cbothamy:</B></FONT> ok, bye volker, see you around<BR>
|
||||
<FONT SIZE="2">21:54:36</FONT> <B>cbothamy:</B></FONT> Night: Sorry I have not tried any of those patches. I add an item in the roadmap about apic and winnt smp<BR>
|
||||
<FONT SIZE="2">21:56:08</FONT> <B>danielg4:</B></FONT> Linux-smp might be easier to get to run.<BR>
|
||||
<FONT SIZE="2">21:58:05</FONT> <B>Night:</B></FONT> now I am working on FPU code replacement with softfloat lib.<BR>
|
||||
<FONT SIZE="2">21:58:23</FONT> <B>Night:</B></FONT> It looks faster and free of bugs<BR>
|
||||
<FONT SIZE="2">21:59:13</FONT> <B>cbothamy:</B></FONT> right, I've seen your post in the mailing list<BR>
|
||||
<FONT SIZE="2">21:59:24</FONT> <B>Night:</B></FONT> the last problem is transcendential instructions (log, sin/cos/tag, exp and etc). Any ideas how to implement them ?<BR>
|
||||
<FONT SIZE="2">21:59:36</FONT> <B>wli:</B></FONT> power series<BR>
|
||||
<FONT SIZE="2">21:59:43</FONT> <B>danielg4:</B></FONT> cbothamy: That was Scott Duplichan.<BR>
|
||||
<FONT SIZE="2">22:00:55</FONT> <B>Night:</B></FONT> do you think standard C/C++ math.h functions could help ?<BR>
|
||||
<FONT SIZE="2">22:01:50</FONT> <B>danielg4:</B></FONT> Not for transcendental funcs.<BR>
|
||||
<FONT SIZE="2">22:02:00</FONT> <B>Night:</B></FONT> I see no functions with 'long double' parameter ;(<BR>
|
||||
<FONT SIZE="2">22:03:12</FONT> <B>danielg4:</B></FONT> Not all platforms have a long double.<BR>
|
||||
<FONT SIZE="2">22:04:22</FONT> <B>danielg4:</B></FONT> On PowerPC, for example, it's the same as double, but there is also a 'double double.'<BR>
|
||||
<FONT SIZE="2">22:08:33</FONT> <B>danielg4:</B></FONT> The disadvantage to softfloat is that it doesn't use the host's FPU.<BR>
|
||||
<FONT SIZE="2">22:09:47</FONT> <B>Night:</B></FONT> on x86 you could execute an instruction itself and on other platforms you will have a problems with handling of numeric exceptions and etc<BR>
|
||||
<FONT SIZE="2">22:10:52</FONT> <B>Night:</B></FONT> host fpu could not produce you for example "precision" exception and you will miss it. for me accuracy of emulation is the first task.<BR>
|
||||
<FONT SIZE="2">22:14:10</FONT> <B>danielg4:</B></FONT> Perhaps softfloat could be used for transcendental funcs and math.h for arithmetic?<BR>
|
||||
<FONT SIZE="2">22:14:49</FONT> <B>Night:</B></FONT> btw, how about multithreading/multiprocessing in bochs ? I mean if Bochs will be able to run any device and cpu in separate thread ...<BR>
|
||||
<FONT SIZE="2">22:16:07</FONT> <B>danielg4:</B></FONT> I agree. Giving the CPU its own thread sould be the first step. Perhaps an FPU thread next?<BR>
|
||||
<FONT SIZE="2">22:16:14</FONT> <B>cbothamy:</B></FONT> Night: the problem with multithreading is to be portable.<BR>
|
||||
<FONT SIZE="2">22:17:00</FONT> <B>danielg4:</B></FONT> There are standard C funcs for it, AFAIK.<BR>
|
||||
<FONT SIZE="2">22:17:34</FONT> <B>Night:</B></FONT> not more problematic than GUI or devices. I sure there are portable libraries which provide threads/semaphores services<BR>
|
||||
<FONT SIZE="2">22:24:51</FONT> <B>Jan_B_A:</B></FONT> Hello??<BR>
|
||||
<FONT SIZE="2">22:25:34</FONT> <B>danielg4:</B></FONT> I'm going to need to leave pretty soon, but I'll leave the irc client running & read it later.<BR>
|
||||
<FONT SIZE="2">22:27:04</FONT> <B>danielg4:</B></FONT> bye bye<BR>
|
||||
<FONT SIZE="2">22:27:16</FONT> <B>cbothamy:</B></FONT> bye daniel<BR>
|
||||
<FONT SIZE="2">22:27:20</FONT> <B>fcorneli:</B></FONT> bye<BR>
|
||||
<FONT SIZE="2">22:27:38</FONT> <B>Jan_B_A:</B></FONT> If there is nothing else to discuss (the math problems was over my head) I was going to leave too. Will start working on the site asap.<BR>
|
||||
<FONT SIZE="2">22:28:14</FONT> <B>cbothamy:</B></FONT> ok I'll have to go soon as well. What I'm going to do is upload the roadmap in the cvs, and open tasks ans subtasks on sourceforge.<BR>
|
||||
<FONT SIZE="2">22:29:02</FONT> <B>Night:</B></FONT> cristophe, add to the roadmap that we should find some ideas to check correctness of instructions emulation, especially system instructions<BR>
|
||||
<FONT SIZE="2">22:29:56</FONT> <B>cbothamy:</B></FONT> ok<BR>
|
||||
<FONT SIZE="2">22:29:58</FONT> <B>Night:</B></FONT> arithmetic instructions could be validated with simply random testing<BR>
|
||||
<FONT SIZE="2">22:31:15</FONT> <B>Night:</B></FONT> ok, I also leave now ...<BR>
|
||||
<FONT SIZE="2">22:31:22</FONT> <B>Night:</B></FONT> bye<BR>
|
||||
<FONT SIZE="2">22:32:03</FONT> <B>fcorneli:</B></FONT> I'm leaving too, see you all later around, and happy hacking... bye bye<BR>
|
||||
<FONT SIZE="2">22:32:28</FONT> <B>Jan_B_A:</B></FONT> bye bye<BR>
|
||||
<FONT SIZE="2">22:32:41</FONT> <B>cbothamy:</B></FONT> bye Frank. Thanks for being here<BR>
|
||||
<FONT SIZE="2">22:33:06</FONT> <B>fcorneli:</B></FONT> no prob. cul<BR>
|
||||
|
||||
<!--content ends here -->
|
||||
|
||||
|
||||
<!--#include virtual="includes/footer.txt" -->
|
||||
|
||||
|
||||
Last Modified on <!--#flastmod file="mailinglists.html" -->.<BR>
|
||||
|
||||
<!--#include virtual="includes/cright.txt" -->
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -1,78 +0,0 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>bochs: The Open Source IA-32 Emulation Project (IRC Discussion)</TITLE>
|
||||
|
||||
<!--#include virtual="includes/header.txt" -->
|
||||
|
||||
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Bochs Chat on Tuesday June 19, 2001</b></font><BR><BR>
|
||||
|
||||
Please join the Bochs community for an open discussion this coming Tuesday
|
||||
(6/19/2001). The discussion will take place between 6:00PM and 8:00PM, US
|
||||
Pacific time (GMT-0700). Last time it continued for more than two hours beyond
|
||||
the expected ending time! Anyone who is interested may join the #Bochs channel
|
||||
during this period. Topics will include:
|
||||
<ul>
|
||||
<li>What major bugs remain in 1.2.1?
|
||||
<li>Implementing Networking in Bochs
|
||||
<li>Bochs GUI: status report from EKS and Bryce, planning
|
||||
<li>Suggestions for the SourceForge website, documentation
|
||||
<li>What are your favorite features or least favorite bugs
|
||||
<li>How can you get Windows running on Bochs quickly?
|
||||
<li>Whatever else comes up
|
||||
</ul>
|
||||
|
||||
<font face="arial, helvetica" color="#1e029a" size="4"><b>Time Zone Conversion</b></font><BR><BR>
|
||||
Bochs enthusiasts come from all different time zones. The start and end times
|
||||
are given in Pacific Daylight Time, or GMT-0700. If it's still not clear,
|
||||
you can figure it out from the offset between your wall clock and the current
|
||||
time given here.
|
||||
<BR><BR>
|
||||
<table>
|
||||
<tr>
|
||||
<td>Current time </td><td> <!--#echo var="DATE_LOCAL"--></td>
|
||||
<tr><td>Discussion start time </td><td> Tuesday, 19-Jun-2001 18:00:00 PDT</td>
|
||||
<tr><td>Discussion end time </td><td> Tuesday, 19-Jun-2001 20:00:00 PDT</td>
|
||||
</table>
|
||||
|
||||
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>What is IRC and
|
||||
how do I get it?</b></font><BR><BR>
|
||||
There are many programs that allow you to access IRC. Many windows users use a
|
||||
client program called MIRC. Just do a search for "irc" on <a
|
||||
href="http://www.yahoo.com">www.yahoo.com</a> or your favorite search engine,
|
||||
and you will find many references to it. One site devoted to learning how to
|
||||
use IRC is called <a
|
||||
href="http://www.newircusers.com/">www.newircusers.com</a>.
|
||||
<BR>
|
||||
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Which IRC server should I use?</b></font><BR><BR>
|
||||
<pre>
|
||||
Server: irc.newnet.net [ <a href="http://www.newnet.net/nnservers.html">More NewNet Servers</a> ]
|
||||
Port: 6667
|
||||
Channel: #Bochs
|
||||
</pre>
|
||||
If we have trouble with newnet, we will move to a different
|
||||
one and update this web page. This page was updated <!--#echo
|
||||
var="LAST_MODIFIED"-->. PDT is GMT-0700.
|
||||
<BR>
|
||||
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>I can't be there!
|
||||
What can I do?</b></font><BR><BR>
|
||||
|
||||
We will put a transcript of this session onto the website afterward, in
|
||||
case you can't be there. If you have something specific to say or ask,
|
||||
contact
|
||||
<a
|
||||
href="http://bochs.sourceforge.net/cgi-bin/topper.pl?name=Email+Bryce+Denney&url=http://sourceforge.net/sendmessage.phpqmrktousereq185114">Bryce
|
||||
Denney</a> and he can paste it in on your behalf.
|
||||
|
||||
<!--#include virtual="includes/footer.txt" -->
|
||||
|
||||
|
||||
Last Modified on <!--#echo var="LAST_MODIFIED"-->.<BR>
|
||||
|
||||
<!--#include virtual="includes/cright.txt" -->
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -1,56 +0,0 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>bochs: The Open Source IA-32 Emulation Project (IRC Survey)</TITLE>
|
||||
<!--#include virtual="includes/header.txt" -->
|
||||
|
||||
<h1>IRC Survey 5/30/2001</h1>
|
||||
|
||||
<h2>
|
||||
What do you use Bochs for?
|
||||
</h2>
|
||||
<pre>
|
||||
OS Developer: to test software that you are writing
|
||||
Educator/Student: to see how the computer works
|
||||
Win Apps: To run Windows applications under some other OS
|
||||
Run other x86 OSes
|
||||
</pre>
|
||||
|
||||
<h2>
|
||||
What are the most important areas for future bug fixes?
|
||||
</h2>
|
||||
<pre>
|
||||
bug1: mouse support (takes too much CPU, some modes not implemented)
|
||||
bug2: keyboard (missing keys, international support)
|
||||
bug3: cdrom model (support on win95,98 and other OSes)
|
||||
bug4: miscellaneous CPU model problems (unimplemented instructions)
|
||||
bug5: documentation is lacking
|
||||
bug6: my favorite OS or application _____ doesn't boot yet!
|
||||
</pre>
|
||||
|
||||
<h2>
|
||||
What are the most important feature requests?
|
||||
</h2>
|
||||
<pre>
|
||||
feature1: disk image tools
|
||||
feature2: timing problems (bochs takes up 100% of CPU, keyboard autorepeats too much)
|
||||
feature3: cdrom (read from cdrom disk image, boot from CD)
|
||||
feature4: hard disk (allow more than 2, read from raw partitions, etc.)
|
||||
feature5: floppy disk (detect different sizes)
|
||||
feature6: video (display speed ?, missing video modes)
|
||||
feature7: networking (get bochs talking to the world)
|
||||
feature8: emulation speed (guest-to-host communication, profiling to find slow code)
|
||||
feature8: building for win32 sucks because of missing makefile problem
|
||||
feature10: GUI for configuration and runtime control
|
||||
</pre>
|
||||
|
||||
|
||||
|
||||
<!--#include virtual="includes/footer.txt" -->
|
||||
|
||||
|
||||
Last Modified on <!--#flastmod file="techdata.html" -->.<BR>
|
||||
|
||||
<!--#include virtual="includes/cright.txt" -->
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -1,38 +0,0 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>bochs: The Open Source IA-32 Emulation Project (Bochs Links)</TITLE>
|
||||
|
||||
<!--#include virtual="includes/header.txt" -->
|
||||
|
||||
<img src="images/logo.png" alt="A Window, Tux, and the BSD Daemon" width="160" height="175" align="right">
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Bochs-related Links</b></font><BR>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<a href="http://www.fysnet.net/mtools.htm">Ben Lunt's MTOOLS for win32</a>. Mtools allows you to read and write files inside a DOS/Windows
|
||||
disk image file. For other platforms, visit the <a href="http://gnu.org/s/mtools/">Mtools main site</a> for source code.
|
||||
<li>
|
||||
Don Becker's <a href="http://www.psyon.org/bochs-win32">Bochs-Win32 page</a>
|
||||
contains binaries for Windows platforms.
|
||||
<li>
|
||||
<a href="http://www.psyon.org/bochs-rfb">Bochs-RFB</a>, also by Don Becker,
|
||||
allows you to access the emulated system via the VNC Viewer from AT&T.
|
||||
Don's Bochs-RFB code is now integrated into Bochs as of version 1.2.pre1.
|
||||
<li>
|
||||
Christophe Bothamy has written an <a href="http://www.nongnu.org/vgabios/">Open Source VGA BIOS</a>, distributed under the LGPL.
|
||||
<li>
|
||||
<a href="http://bfe.sourceforge.net">BFE</a> is a graphical debugger interface for
|
||||
Bochs by <a href="mailto:brand@qzx.com">Brand Huntsman</a>.
|
||||
<li> Georg Potthast has written a <a href="http://peter-bochs.googlecode.com/files/Bochs%20-%20a%20Guide%20and%20Tutorial%20for%20Windows%20II.pdf">guide and tutorial</a> for running Bochs on Windows.
|
||||
</ul>
|
||||
|
||||
|
||||
<!--#include virtual="includes/footer.txt" -->
|
||||
|
||||
|
||||
Last Modified on <!--#flastmod file="links.html" -->.<BR>
|
||||
|
||||
<!--#include virtual="includes/cright.txt" -->
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -1,139 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>Linux Cross-Reference</TITLE>
|
||||
</HEAD>
|
||||
<BODY BGCOLOR=WHITE>
|
||||
<H1 ALIGN=CENTER>
|
||||
Help doing searches<BR>
|
||||
<A HREF="http:/source/">
|
||||
<I>Browse the code</I></A></H1>
|
||||
|
||||
|
||||
<I> This text is directly stolen from the Glimpse manual page. I have
|
||||
tried to remove things that do not apply to the lxr searcher, but
|
||||
beware, some things might have slipped through. I'll try to put
|
||||
together something better when I get the time. For more information on
|
||||
glimpse go to the <A HREF="http://glimpse.cs.arizona.edu">Glimpse
|
||||
homepage</A>.</I>
|
||||
|
||||
<A NAME="Patterns"></A><H2>Patterns</H2>
|
||||
<P>
|
||||
glimpse supports a large variety of patterns, including simple
|
||||
strings, strings with classes of characters, sets of strings,
|
||||
wild cards, and regular expressions (see <A HREF="#Limitations">Limitations</A>).
|
||||
|
||||
<P> <H3>Strings</H3>
|
||||
|
||||
Strings are any sequence of characters, including the special symbols
|
||||
`^' for beginning of line and `$' for end of line. The following
|
||||
special characters (`$', `^', `*', `[', `^', `|', `(', `)', `!', and
|
||||
`\' ) as well as the following meta characters special to glimpse (and
|
||||
agrep): `;', `,', `#', `>', `<', `-', and `.', should be preceded by
|
||||
`\\' if they are to be matched as regular characters. For example,
|
||||
\\^abc\\\\ corresponds to the string ^abc\\, whereas ^abc corresponds
|
||||
to the string abc at the beginning of a line.
|
||||
|
||||
<P> <H3>Classes of characters</H3>
|
||||
a list of characters inside [] (in order) corresponds to any character
|
||||
from the list. For example, [a-ho-z] is any character between a and h
|
||||
or between o and z. The symbol `^' inside [] complements the list.
|
||||
For example, [^i-n] denote any character in the character set except
|
||||
character 'i' to 'n'.
|
||||
The symbol `^' thus has two meanings, but this is consistent with
|
||||
egrep.
|
||||
The symbol `.' (don't care) stands for any symbol (except for the
|
||||
newline symbol).
|
||||
|
||||
<P> <H3>Boolean operations</H3>
|
||||
Glimpse
|
||||
supports an `AND' operation denoted by the symbol `;'
|
||||
an `OR' operation denoted by the symbol `,',
|
||||
a limited version of a 'NOT' operation (starting at version 4.0B1)
|
||||
denoted by the symbol `~',
|
||||
or any combination.
|
||||
For example, pizza;cheeseburger' will output all lines containing
|
||||
both patterns.
|
||||
'{political,computer};science' will match 'political science'
|
||||
or 'science of computers'.
|
||||
|
||||
|
||||
<P><H3>Wild cards</H3>
|
||||
The symbol '#' is used to denote a sequence
|
||||
of any number (including 0)
|
||||
of arbitrary characters (see <A HREF="#Limitations">Limitations</A>).
|
||||
The symbol # is equivalent to .* in egrep.
|
||||
In fact, .* will work too, because it is a valid regular expression
|
||||
(see below), but unless this is part of an actual regular expression,
|
||||
# will work faster.
|
||||
(Currently glimpse is experiencing some problems with #.)
|
||||
|
||||
|
||||
<P><H3>Combination of exact and approximate matching</H3>
|
||||
Any pattern inside angle brackets <> must match the text exactly even
|
||||
if the match is with errors. For example, <mathemat>ics matches
|
||||
mathematical with one error (replacing the last s with an a), but
|
||||
mathe<matics> does not match mathematical no matter how many errors are
|
||||
allowed. (This option is buggy at the moment.)
|
||||
|
||||
|
||||
<H3>Regular expressions</H3>
|
||||
Since the index is word based, a regular expression must match words
|
||||
that appear in the index for glimpse to find it. Glimpse first strips
|
||||
the regular expression from all non-alphabetic characters, and
|
||||
searches the index for all remaining words. It then applies the
|
||||
regular expression matching algorithm to the files found in the index.
|
||||
For example, glimpse 'abc.*xyz' will search the index for all files
|
||||
that contain both 'abc' and 'xyz', and then search directly for
|
||||
'abc.*xyz' in those files. (If you use glimpse -w 'abc.*xyz', then
|
||||
'abcxyz' will not be found, because glimpse will think that abc and
|
||||
xyz need to be matches to whole words.) The syntax of regular
|
||||
expressions in glimpse is in general the same as that for agrep. The
|
||||
union operation `|', Kleene closure `*', and parentheses () are all
|
||||
supported. Currently '+' is not supported. Regular expressions are
|
||||
currently limited to approximately 30 characters (generally excluding
|
||||
meta characters). The maximal number of errors
|
||||
for regular expressions that use '*' or '|' is 4.
|
||||
|
||||
<P>
|
||||
<A NAME="Limitations"></A><H2>Limitations</H2>
|
||||
The index of glimpse is word based. A pattern that contains more than
|
||||
one word cannot be found in the index. The way glimpse overcomes this
|
||||
weakness is by splitting any multi-word pattern into its set of words
|
||||
and looking for all of them in the index.
|
||||
For example, <I>'linear programming'</I> will first consult the index
|
||||
to find all files containing both <I>linear</I> and <I>programming</I>,
|
||||
and then apply agrep to find the combined pattern.
|
||||
This is usually an effective solution, but it can be slow for
|
||||
cases where both words are very common, but their combination is not.
|
||||
|
||||
<P>
|
||||
As was mentioned in the section on <A HREF="#Patterns">Patterns</A> above, some characters
|
||||
serve as meta characters for glimpse and need to be
|
||||
preceded by '\\' to search for them. The most common
|
||||
examples are the characters '.' (which stands for a wild card),
|
||||
and '*' (the Kleene closure).
|
||||
So, "glimpse ab.de" will match abcde, but "glimpse ab\\.de"
|
||||
will not, and "glimpse ab*de" will not match ab*de, but
|
||||
"glimpse ab\\*de" will.
|
||||
The meta character - is translated automatically to a hypen
|
||||
unless it appears between [] (in which case it denotes a range of
|
||||
characters).
|
||||
|
||||
<P>
|
||||
There is no size limit for simple patterns and simple patterns
|
||||
within Boolean expressions.
|
||||
More complicated patterns, such as regular expressions,
|
||||
are currently limited to approximately 30 characters.
|
||||
Lines are limited to 1024 characters.
|
||||
|
||||
<P>
|
||||
<HR>
|
||||
|
||||
<ADDRESS>
|
||||
<A HREF="mailto:lxr@linux.no">
|
||||
Arne Georg Gleditsch and Per Kristian Gjermshus</A>
|
||||
</ADDRESS>
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -1,42 +0,0 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>bochs: The Open Source IA-32 Emulation Project (Mailing Lists)</TITLE>
|
||||
|
||||
<!--#include virtual="includes/header.txt" -->
|
||||
|
||||
<!--content starts here-->
|
||||
<img src="images/logo.png" alt="A Window, Tux, and the BSD Daemon" width="160" height="175" align="right">
|
||||
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Bochs Mailing Lists</b></font><BR><BR>
|
||||
There are now two Bochs mailing lists, bochs-announce and bochs-developers. Bochs-announce is a
|
||||
moderated, low-traffic list which carries only periodic announcements of bochs releases and important updates.
|
||||
Bochs-developers is the forum for all Bochs discussions and questions. There is no need to subscribe to both lists,
|
||||
because all bochs-announce messages are forwarded to the developers list. If you subscribe to both, you will get 2
|
||||
copies of every announcement. Anyone who is interested may join either list, unless you abuse it of course.<BR><BR>
|
||||
<BR><BR>
|
||||
Note that bochs-announce is new as of 5/10/2001, so there are no archives before that date.<BR><BR>
|
||||
<b>Click on the links below to signup for the following lists:</b>
|
||||
<ul>
|
||||
<li><a href="https://lists.sourceforge.net/lists/listinfo/bochs-announce">Bochs-Announce</a>
|
||||
<li><a href="https://lists.sourceforge.net/lists/listinfo/bochs-developers">Bochs-Developers</a>
|
||||
<li><a href="https://lists.sourceforge.net/lists/listinfo/bochs-cvs">Bochs-CVS</a>
|
||||
</ul>
|
||||
<BR>
|
||||
<b>Click on the links below to view the archives for the following lists:</b>
|
||||
<ul>
|
||||
<li><a href="http://sourceforge.net/mailarchive/forum.php?forum_name=bochs-announce">Bochs-Announce</a>
|
||||
<li><a href="http://sourceforge.net/mailarchive/forum.php?forum_name=bochs-developers">Bochs-Developers</a>
|
||||
<li><a href="http://sourceforge.net/mailarchive/forum.php?forum_name=bochs-cvs">Bochs-CVS</a>
|
||||
</ul>
|
||||
<!--content ends here -->
|
||||
|
||||
|
||||
<!--#include virtual="includes/footer.txt" -->
|
||||
|
||||
|
||||
Last Modified on <!--#flastmod file="mailinglists.html" -->.<BR>
|
||||
|
||||
<!--#include virtual="includes/cright.txt" -->
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -1,15 +0,0 @@
|
|||
README was last updated Thu Jun 14 08:03:50 PDT 2001
|
||||
|
||||
This directory contains information about Bochs networking, and our plans
|
||||
to improve it.
|
||||
|
||||
A summary of the different networking plans under consideration:
|
||||
bochs-network-planning.txt
|
||||
|
||||
Conversation between Peter and Bryce from 6/14/2001 with more details:
|
||||
peter_bryce_20010614.html
|
||||
|
||||
Diagrams that Peter sketched to describe some possibile plans.
|
||||
host_only.gif describes plan #1
|
||||
pkt_filter.gif describes plan #2
|
||||
bridge.gif describes plan #5
|
||||
|
|
@ -1,70 +0,0 @@
|
|||
While talking to Peter Grehan about network support for Bochs, we came up with
|
||||
the following possible plans. All plans use the emulated NE2K in the guest OS
|
||||
except for #6, which uses the serial port instead. Peter says that #6 is
|
||||
close to working already, but that #1 is the most interesting. In the next
|
||||
few days, he will describe #1 in more detail and mail it to bochs-developers
|
||||
and plex86 lists.
|
||||
|
||||
Here the plans, in no particular order. Please correct mistakes, add pros and
|
||||
cons, and if you must, add even more plans at the end. (Warning: We
|
||||
may ask you to implement it...)
|
||||
|
||||
1. Emulated NE2K + virtual ethernet driver
|
||||
Pros: you can talk to host
|
||||
if you set up IP forwarding in the host, you can talk to the world
|
||||
Cons: must have root access to load a kernel module,
|
||||
must be written separately for each host OS,
|
||||
not all OSes support IP forwarding
|
||||
|
||||
2. Emulated NE2K + packet filters (BPF, LSF)
|
||||
Pros: infrastructure is already there in iodev/eth_*.cc
|
||||
each packet mover can support several OSes if
|
||||
they have the right library/kernel feature such as bpf.
|
||||
user can run it, if packet filter permits
|
||||
Cons: can't talk to host!
|
||||
|
||||
3. Emulated NE2K + emulate network protocols with portable code. Bochs
|
||||
interprets ethernet frames from the NE2K and turns them into host OS
|
||||
networking function calls. For outgoing TCP for example, bochs would open a
|
||||
TCP port using BSD sockets and send and receive data on bochs' behalf. To get
|
||||
data back into Bochs, we would build ethernet frames and place them in the
|
||||
emulated NE2K RX queue to make the guest OS think that another host on the
|
||||
ethernet had responded. For incoming TCP, user tells bochs to redirect host
|
||||
port X to guest OS port Y, and bochs binds to host port X using socket code.
|
||||
When connections and data arrive, it turns them into ethernet frames and puts
|
||||
them into the emulated NE2K RX queue.
|
||||
|
||||
Pros: can be portable socket code!
|
||||
can run as a normal user!
|
||||
Cons: each protocol must be handled separately
|
||||
hard to extract TCP information from ethernet frames (maybe
|
||||
we can borrow linux or other networking code)
|
||||
Peter Grehan, author of current NE2K code, says it's not practical!
|
||||
|
||||
4. Emulated NE2K + PPP on host. Bochs guest OS runs an NE2K, bochs emulator
|
||||
translates ethernet-ppp and moves packets to/from PPPD running on the host.
|
||||
This might be called EoPPP!
|
||||
|
||||
Pros: PPP already exists for many platforms
|
||||
all IP protocols supported
|
||||
if you set up IP forwarding in the host, you can talk to the world
|
||||
Cons: requires root access on host to start PPP
|
||||
may require virtual terminal (excludes win?)
|
||||
have to emulate some ethernet functions
|
||||
|
||||
5. Emulated NE2K + Kernel module using bridging code (this is what vmware does)
|
||||
Pros: bochs appears to be on the same LAN as the host, with different MAC
|
||||
requires no extra config on the host or guest OS
|
||||
Cons: Must have root access to load a kernel module,
|
||||
must be written separately for each host OS,
|
||||
bridging code not present in all kernels
|
||||
|
||||
6. PPP link using bochs serial code
|
||||
Pros: use normal networking on guest and host
|
||||
only minor coding required: we just need to make serial open
|
||||
a TTY in the correct mode
|
||||
works on any platform that has PPP
|
||||
if you set up IP forwarding in the host, you can talk to the world
|
||||
Cons: requires root access on host to start PPP
|
||||
may require virtual terminal (excludes win?)
|
||||
probably slower because of overhead of running PPP in emulation
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 6.5 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.1 KiB |
|
|
@ -1,27 +0,0 @@
|
|||
<HTML>
|
||||
<pre>
|
||||
This file was last modified Thu Jun 14 08:11:43 PDT 2001
|
||||
|
||||
This directory contains information about Bochs networking, and our plans
|
||||
to improve it.
|
||||
|
||||
A summary of the different networking plans under consideration:
|
||||
<a href="bochs-network-planning.txt">bochs-network-planning.txt</a>
|
||||
|
||||
Conversation between Peter and Bryce from 6/14/2001 with more details:
|
||||
<a href="peter_bryce_20010614.html">peter_bryce_20010614.html</a>
|
||||
|
||||
Diagrams that Peter sketched to describe some possibile plans.
|
||||
- <a href="host_only.gif">host_only.gif</a> describes plan #1
|
||||
- <a href="pkt_filter.gif">pkt_filter.gif</a> describes plan #2
|
||||
- <a href="bridge.gif">bridge.gif</a> describes plan #5
|
||||
|
||||
Other links to check out:
|
||||
<a href="http://user-mode-linux.sf.net/networking.html">User mode linux, networking page</a>
|
||||
|
||||
<a href="http://blitzen.canberra.edu.au/slirp">Slirp</a> which allows users with only a shell account to have PPP/(C)SLIP
|
||||
access. This might be used as one way to get bochs talking to the rest
|
||||
of the world.
|
||||
|
||||
</pre>
|
||||
</HTML>
|
||||
|
|
@ -1,469 +0,0 @@
|
|||
<FONT COLOR="#ff0000"><FONT SIZE="2">(07:59:11) </FONT><B>peter_grehan:</B></FONT> finally logged on...
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(07:59:36) </FONT><B>brycedenney:</B></FONT> hey
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(07:59:41) </FONT><B>brycedenney:</B></FONT> how's it going?
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:00:28) </FONT><B>brycedenney:</B></FONT> if lag is too bad, we can try irc or AOL IM
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:01:40) </FONT><B>peter_grehan:</B></FONT> sorry
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:01:46) </FONT><B>peter_grehan:</B></FONT> fire away with the net questions.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:02:07) </FONT><B>brycedenney:</B></FONT> did you see Dave's post this morning?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:02:25) </FONT><B>peter_grehan:</B></FONT> no
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:02:27) </FONT><B>brycedenney:</B></FONT> (EKS) he and I got to talking about kernel drivers
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:03:05) </FONT><B>brycedenney:</B></FONT> you'll get it soon, I guess we should start with the big picture
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:03:30) </FONT><B>brycedenney:</B></FONT> we need bochs to be able to talk to the host machine and other machines in the world.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:03:43) </FONT><B>peter_grehan:</B></FONT> just reading the email now...
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:03:46) </FONT><B>brycedenney:</B></FONT> ok
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:04:14) </FONT><B>brycedenney:</B></FONT> we have user-code solutions for a few OSes that talk to the world but not the host machine
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:04:57) </FONT><B>peter_grehan:</B></FONT> ok
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:05:32) </FONT><B>brycedenney:</B></FONT> so we need to dream up a plan to talk to both host and world, eventually supporting all systems
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:05:36) </FONT><B>brycedenney:</B></FONT> :)
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:06:36) </FONT><B>peter_grehan:</B></FONT> this involves writing a virtual ethernet driver
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:06:56) </FONT><B>brycedenney:</B></FONT> isn't that what EKS describes?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:07:09) </FONT><B>peter_grehan:</B></FONT> engineer the interface from the source they provide. However
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:07:24) </FONT><B>peter_grehan:</B></FONT> yep
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:08:31) </FONT><B>peter_grehan:</B></FONT> the host o/s driver *can't* be generic
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:08:34) </FONT><B>peter_grehan:</B></FONT> ps-specific code
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:08:40) </FONT><B>brycedenney:</B></FONT> os
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:08:43) </FONT><B>brycedenney:</B></FONT> right
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:09:38) </FONT><B>brycedenney:</B></FONT> ok so one plan is to write a virtual ethernet driver for each supported OS
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:10:13) </FONT><B>peter_grehan:</B></FONT> that's the only real way to do this.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:10:15) </FONT><B>brycedenney:</B></FONT> I need to test this: can you get multiline sends (this is 3 lines long)<BR>
|
||||
line 2<BR>
|
||||
line 3
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:10:51) </FONT><B>peter_grehan:</B></FONT> yep.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:10:53) </FONT><B>brycedenney:</B></FONT> good
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:11:02) </FONT><B>brycedenney:</B></FONT> one plan:
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:11:06) </FONT><B>brycedenney:</B></FONT> A virtual ethernet driver allows you to talk to the host and the world.<BR>
|
||||
Pros: talk to both host and world<BR>
|
||||
Cons: Must have root access.<BR>
|
||||
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:11:23) </FONT><B>brycedenney:</B></FONT> does that seem correct to you?
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:11:41) </FONT><B>brycedenney:</B></FONT> cons: must be written separately for each OS
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:12:32) </FONT><B>peter_grehan:</B></FONT> not necessarily - it really only allows you to talk to the host
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:12:42) </FONT><B>brycedenney:</B></FONT> but then IP routing lets you talk to the rest
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:12:49) </FONT><B>brycedenney:</B></FONT> without any wierd hacks
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:12:55) </FONT><B>brycedenney:</B></FONT> ?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:13:20) </FONT><B>peter_grehan:</B></FONT> only if forwarding is enabled
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:13:38) </FONT><B>brycedenney:</B></FONT> with root access, you can make it work
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:13:45) </FONT><B>peter_grehan:</B></FONT> yep.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:13:48) </FONT><B>brycedenney:</B></FONT> you might need to redo your kernel or something
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:14:11) </FONT><B>peter_grehan:</B></FONT> you need to load a module
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:15:08) </FONT><B>brycedenney:</B></FONT> how about this then:
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:15:11) </FONT><B>brycedenney:</B></FONT> 1. A virtual ethernet driver <BR>
|
||||
Pros: you can talk to both host and world<BR>
|
||||
Cons: Must have root access to load a kernel module, <BR>
|
||||
must be written separately for each host OS,<BR>
|
||||
must set up IP forwarding to talk to the world.<BR>
|
||||
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:15:56) </FONT><B>peter_grehan:</B></FONT> that's correct.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:16:05) </FONT><B>brycedenney:</B></FONT> ok here's another plan
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:16:21) </FONT><B>brycedenney:</B></FONT> 2. packet filters (BPF, LSF)<BR>
|
||||
Pros: infrastructure is already there in iodev/eth_*.cc<BR>
|
||||
each packet mover can support several OSes if <BR>
|
||||
they have the right library/kernel feature.<BR>
|
||||
user can run it, <BR>
|
||||
Cons: can't talk to host<BR>
|
||||
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:17:44) </FONT><B>peter_grehan:</B></FONT> that's right. there are still some issues with this - at one stage
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:18:33) </FONT><B>peter_grehan:</B></FONT> I just remembered: there is a port of BPF to windows which I've used. It's quite good
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:18:46) </FONT><B>brycedenney:</B></FONT> cool!
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:19:39) </FONT><B>peter_grehan:</B></FONT> one other option is a kernel module that hooks into bridging code. this is what VmWare uses - it makes the guest o/s look like it's on the same LAN as the host o/s. Very similar to the packet filter option.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:20:35) </FONT><B>brycedenney:</B></FONT> does bridging code make other machines on the net see a different MAC address from the host?
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:20:50) </FONT><B>brycedenney:</B></FONT> or is it IP based?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:21:08) </FONT><B>peter_grehan:</B></FONT> yep
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:21:12) </FONT><B>brycedenney:</B></FONT> ip
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:21:15) </FONT><B>brycedenney:</B></FONT> ?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:22:16) </FONT><B>peter_grehan:</B></FONT> I should have mentioned: other hosts would see a different MAC addr
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:22:24) </FONT><B>brycedenney:</B></FONT> cool!
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:22:49) </FONT><B>brycedenney:</B></FONT> any hope of doing that in windows? does it have bridging code?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:23:31) </FONT><B>peter_grehan:</B></FONT> no
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:23:49) </FONT><B>brycedenney:</B></FONT> but it's a good solution for systems that support it
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:24:28) </FONT><B>peter_grehan:</B></FONT> it's the best in that it requires no extra config on the host o/s
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:25:32) </FONT><B>brycedenney:</B></FONT> 5. Kernel module using bridging code<BR>
|
||||
Pros: bochs appears to be a different MAC than the host,<BR>
|
||||
requires no extra config on the host o/s<BR>
|
||||
Cons: Must have root access to load a kernel module,<BR>
|
||||
must be written separately for each host OS,<BR>
|
||||
bridging code not present in all kernels,<BR>
|
||||
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:26:47) </FONT><B>peter_grehan:</B></FONT> yep
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:27:01) </FONT><B>brycedenney:</B></FONT> you may wonder where are 3 & 4 :)
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:27:08) </FONT><B>brycedenney:</B></FONT> 3. TCP only networking<BR>
|
||||
Pros: can be portable socket code,<BR>
|
||||
can run as a normal user<BR>
|
||||
Cons: each protocol must be handled separately<BR>
|
||||
hard to extract TCP information from ethernet frames (maybe<BR>
|
||||
we could borrow linux or other networking code)<BR>
|
||||
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:27:58) </FONT><B>peter_grehan:</B></FONT> that one ain't gonna work. there are whole companies built on the basis of less code than what that will take !
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:28:10) </FONT><B>brycedenney:</B></FONT> :)
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:28:47) </FONT><B>brycedenney:</B></FONT> I don't want to spent too much time on it
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:29:17) </FONT><B>brycedenney:</B></FONT> but why couldn't you rip off code from an open source kernel
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:29:30) </FONT><B>brycedenney:</B></FONT> that translates ethernet frames into a usable form
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:30:11) </FONT><B>peter_grehan:</B></FONT> it's not just translating - you have to implement a complete stack
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:30:21) </FONT><B>peter_grehan:</B></FONT> possible work for outgoing TCP connections
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:30:34) </FONT><B>peter_grehan:</B></FONT> I should say
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:32:02) </FONT><B>brycedenney:</B></FONT> You mentioned in an email that you have to get the kernel code running as a user, and FYI ther's a whole project that has already done that (<A HREF="http://user-mode-linux.sourceforge.net/">http://user-mode-linux.sourceforge.net/</A>)
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:33:24) </FONT><B>brycedenney:</B></FONT> for incoming TCP connections you would need some tricks. What if you tell bochs "Map local TCP port 3023 to bochs port 23"
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:34:02) </FONT><B>brycedenney:</B></FONT> then bochs would have to bind to TCP port 3023, and when it gets connections it would build up the appropriate ethernet frame and put it into bochs's NE2K packet mover.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:35:01) </FONT><B>peter_grehan:</B></FONT> yep
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:35:01) </FONT><B>peter_grehan:</B></FONT> psuedo driver !
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:35:01) </FONT><B>peter_grehan:</B></FONT> plus
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:35:30) </FONT><B>brycedenney:</B></FONT> The only reason I'm so interested in this plan is the pros are very important: portable code, running as a user
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:35:44) </FONT><B>peter_grehan:</B></FONT> that's a lot of configuration. you may not know in advance all the ports you would need.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:35:51) </FONT><B>brycedenney:</B></FONT> almost all the other plans, a student with a user account could never even try it.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:36:15) </FONT><B>brycedenney:</B></FONT> bochs configuration at runtime we can do, we're planning a control panel of sorts
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:37:03) </FONT><B>brycedenney:</B></FONT> we linux users have to remember, not everybody is root! :)
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:37:58) </FONT><B>peter_grehan:</B></FONT> the student account thing isn't quite true
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:38:13) </FONT><B>brycedenney:</B></FONT> what plan would allow non-root networking?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:39:41) </FONT><B>peter_grehan:</B></FONT> I can't think of one that is going to cover all cases. For windows
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:41:58) </FONT><B>peter_grehan:</B></FONT> I'll try and draw some pictures and send them to you
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:42:01) </FONT><B>brycedenney:</B></FONT> ok
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:42:26) </FONT><B>brycedenney:</B></FONT> so under cons I will add "Peter thinks it's not worth the trouble" :)
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:42:44) </FONT><B>brycedenney:</B></FONT> BTW, how much time do you have left?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:42:55) </FONT><B>peter_grehan:</B></FONT> yeh
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:43:22) </FONT><B>peter_grehan:</B></FONT> maybe another 1/2 hour or so... did you want to go over any other net stuff ???
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:43:34) </FONT><B>brycedenney:</B></FONT> I have one more plan.....
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:43:37) </FONT><B>brycedenney:</B></FONT> :_
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:43:39) </FONT><B>brycedenney:</B></FONT> :)
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:43:52) </FONT><B>peter_grehan:</B></FONT> have at it..
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:44:00) </FONT><B>brycedenney:</B></FONT> 4. IP only networking through hack of PPP on host. Bochs guest OS runs an <BR>
|
||||
NE2K, bochs emulator includes some parts of user-level PPP code and moves<BR>
|
||||
packets to/from the PPP kernel module.<BR>
|
||||
<BR>
|
||||
Pros: PPP kernel code already written for many platforms<BR>
|
||||
PPP user code already written<BR>
|
||||
maybe can be run as a normal user<BR>
|
||||
all IP protocols supported<BR>
|
||||
Cons: maybe hard to extract IP information from ethernet frames<BR>
|
||||
(is it really that hard?)<BR>
|
||||
have to emulate some ethernet functions<BR>
|
||||
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:45:22) </FONT><B>brycedenney:</B></FONT> It's a bit crazy, but motivated by the fact that tons of people get all their network access through PPP, so it's not that much of a limitation for Bochs to get its network access through PPP.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:45:32) </FONT><B>peter_grehan:</B></FONT> I thought that would be better off done through the serial driver itself
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:45:41) </FONT><B>peter_grehan:</B></FONT> doing a type of eth-ppp bridge.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:45:59) </FONT><B>brycedenney:</B></FONT> it seems like better performance to get many bytes at a time in the ne2k than sending bits at a time via serial
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:46:11) </FONT><B>peter_grehan:</B></FONT> The serial driver is currently optimised for interactive input
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:47:20) </FONT><B>brycedenney:</B></FONT> Do you have a concept of how many emulated instructions are required to build an ethernet frame VS sending the equivalent amount of data through serial driver?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:47:42) </FONT><B>peter_grehan:</B></FONT> Maybe I'm being a bit too harsh. Many early PPP implementations were made to look like ethernet drivers to the host. I just noticed today that the standard 'pppd' has a config option to direct output to a pseudo-terminal
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:47:44) </FONT><B>brycedenney:</B></FONT> it's the number of emulated instructions that's the limiting factor.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:48:51) </FONT><B>peter_grehan:</B></FONT> The ne2k has to manually write every byte out in any case
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:49:08) </FONT><B>brycedenney:</B></FONT> no DMA? :)
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:49:27) </FONT><B>peter_grehan:</B></FONT> nope
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:49:41) </FONT><B>brycedenney:</B></FONT> we could emulate a DMA capable card one day, but whatever.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:50:05) </FONT><B>brycedenney:</B></FONT> do you think serial and ne2k methods would take approximately the same # of bochs instructions to send out?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:51:00) </FONT><B>peter_grehan:</B></FONT> The serial is going to take more
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:51:12) </FONT><B>brycedenney:</B></FONT> I expected it would, but why
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:51:29) </FONT><B>brycedenney:</B></FONT> (I haven't programmed either one :) )
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:51:58) </FONT><B>peter_grehan:</B></FONT> I only wanted to get a FreeBSD serial console working
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:53:12) </FONT><B>brycedenney:</B></FONT> any reason why the current bochs serial emulation couldn't handle a PPP connection?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:53:54) </FONT><B>peter_grehan:</B></FONT> some work would be needed to abstract out the sending/receiving of bytes
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:54:07) </FONT><B>brycedenney:</B></FONT> ?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:55:33) </FONT><B>peter_grehan:</B></FONT> the serial code currently writes bytes to file descriptor 0
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:55:50) </FONT><B>brycedenney:</B></FONT> right, you'd want to open a TTY or something instead
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:56:03) </FONT><B>peter_grehan:</B></FONT> yep.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:56:26) </FONT><B>brycedenney:</B></FONT> other than that, anything not supported that PPP might need?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:57:10) </FONT><B>peter_grehan:</B></FONT> You'd have to set up the TTY for raw mode
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:57:45) </FONT><B>brycedenney:</B></FONT> ok, but as far as the serial port emulation in bochs, it has all the registers and bits
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:58:31) </FONT><B>brycedenney:</B></FONT> Did you say why serial would take more instructions? I'm interested in some guess like 50% more, 100% more, since I don't know what the constraints are.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:58:34) </FONT><B>peter_grehan:</B></FONT> yep
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:58:47) </FONT><B>brycedenney:</B></FONT> great! I'll play with serial a bit.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:59:11) </FONT><B>brycedenney:</B></FONT> (bad pun was not intended :) )
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:00:20) </FONT><B>peter_grehan:</B></FONT> async PPP has overhead
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:01:27) </FONT><B>brycedenney:</B></FONT> ok
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:02:27) </FONT><B>brycedenney:</B></FONT> we didn't actually talk about <BR>
|
||||
4. IP only networking through hack of PPP on host. Bochs guest OS runs an<BR>
|
||||
NE2K, bochs emulator includes some parts of user-level PPP code and moves<BR>
|
||||
packets to/from the PPP kernel module.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:02:52) </FONT><B>brycedenney:</B></FONT> except to say that it might be done with PPP on the guest os
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:02:58) </FONT><B>brycedenney:</B></FONT> does it have any merits at all?
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:03:19) </FONT><B>brycedenney:</B></FONT> is my description clear enough to know what I'm talking about?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:03:58) </FONT><B>peter_grehan:</B></FONT> Yeh
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:04:01) </FONT><B>peter_grehan:</B></FONT> it could be made to work.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:04:23) </FONT><B>brycedenney:</B></FONT> it's only useful if the overhead of running PPP on the guest rather than ethernet driver is large enough
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:05:06) </FONT><B>brycedenney:</B></FONT> if overhead is similar, we should just use serial since it doesn't require any PPP hacking.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:05:12) </FONT><B>peter_grehan:</B></FONT> it would also allow non-root networking
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:05:55) </FONT><B>brycedenney:</B></FONT> same as running PPP direct, you may need root to set you up as a legal PPP user
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:05:55) </FONT><B>peter_grehan:</B></FONT> it doesn't need hacking
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:06:15) </FONT><B>brycedenney:</B></FONT> you mean plan 4 doesn't need hacking?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:06:57) </FONT><B>peter_grehan:</B></FONT> no kernel hacking
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:07:35) </FONT><B>brycedenney:</B></FONT> right, but some changes to PPPD I expect
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:08:34) </FONT><B>peter_grehan:</B></FONT> I don't think so - from what I saw
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:09:00) </FONT><B>brycedenney:</B></FONT> are you saying bochs could read and write to a PPPD-controlled terminal
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:09:27) </FONT><B>brycedenney:</B></FONT> and just translate ethernet<->PPP when bochs or the ppp had a packet?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:10:08) </FONT><B>peter_grehan:</B></FONT> That's right
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:10:17) </FONT><B>brycedenney:</B></FONT> hey
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:10:31) </FONT><B>brycedenney:</B></FONT> I didn't think of it that way, but it's good
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:10:35) </FONT><B>peter_grehan:</B></FONT> Bochs serial driver - when a character is sent out
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:10:57) </FONT><B>peter_grehan:</B></FONT> The translation from ethernet-ppp
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:11:58) </FONT><B>brycedenney:</B></FONT> I missed something
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:12:20) </FONT><B>peter_grehan:</B></FONT> about eth-ppp ?
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:12:22) </FONT><B>brycedenney:</B></FONT> are you doing multiline sends ?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:12:33) </FONT><B>peter_grehan:</B></FONT> I think I hit return accidentally there :-(
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:12:46) </FONT><B>brycedenney:</B></FONT> I only got: "Bochs serial driver - when a character is sent out" and then "The translation from ethernet-ppp" that's all
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:13:13) </FONT><B>peter_grehan:</B></FONT> I'll type that bit again:
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:13:21) </FONT><B>brycedenney:</B></FONT> sorry
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:13:47) </FONT><B>peter_grehan:</B></FONT> when a character is sent out
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:13:58) </FONT><B>peter_grehan:</B></FONT> did that come thru OK ?
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:14:11) </FONT><B>brycedenney:</B></FONT> one line only "when a character is sent out"
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:14:58) </FONT><B>peter_grehan:</B></FONT> next line: when a char arrives on the pseudo-term
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:15:57) </FONT><B>brycedenney:</B></FONT> ok
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:16:56) </FONT><B>brycedenney:</B></FONT> it seems that yahoo IM is failing here :(
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:17:17) </FONT><B>peter_grehan:</B></FONT> the east coast is coming on-line :-)
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:18:31) </FONT><B>brycedenney:</B></FONT> ping1
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:18:57) </FONT><B>peter_grehan:</B></FONT> still here
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:19:08) </FONT><B>brycedenney:</B></FONT> good
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:19:16) </FONT><B>brycedenney:</B></FONT> I can't tell if I'm losing messages or just dense.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:19:38) </FONT><B>peter_grehan:</B></FONT> maybe msgs are being lost...
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:20:04) </FONT><B>brycedenney:</B></FONT> we're close to being out of time anyway
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:20:18) </FONT><B>brycedenney:</B></FONT> we have 6 plans now!!
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:20:23) </FONT><B>brycedenney:</B></FONT> 1. A virtual ethernet driver<BR>
|
||||
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:20:27) </FONT><B>brycedenney:</B></FONT> 2. packet filters (BPF, LSF)
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:20:31) </FONT><B>brycedenney:</B></FONT> 3. TCP only networking
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:20:36) </FONT><B>brycedenney:</B></FONT> 4. IP only networking through hack of PPP on host.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:20:41) </FONT><B>brycedenney:</B></FONT> 5. Kernel module using bridging code
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:20:45) </FONT><B>brycedenney:</B></FONT> 6. PPP link using bochs serial code
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:21:00) </FONT><B>brycedenney:</B></FONT> all have pros and cons of course
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:21:26) </FONT><B>brycedenney:</B></FONT> Is there any of them that you would like to work on, time permitting?
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:22:12) </FONT><B>brycedenney:</B></FONT> or do you want to advise others who do have the time and seem to know what they're talking about?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:22:12) </FONT><B>peter_grehan:</B></FONT> I can help out
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:22:19) </FONT><B>peter_grehan:</B></FONT> sure
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:22:35) </FONT><B>brycedenney:</B></FONT> which seems most promising?
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:22:42) </FONT><B>brycedenney:</B></FONT> what OS do you use anyway? freebsd?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:23:11) </FONT><B>peter_grehan:</B></FONT> I run Linux on my desktop
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:23:18) </FONT><B>brycedenney:</B></FONT> cool, me too
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:23:23) </FONT><B>peter_grehan:</B></FONT> I used a heavily modified FreeBSD when I was at Nokia :-)
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:23:59) </FONT><B>brycedenney:</B></FONT> which plan interests you the most?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:24:37) </FONT><B>peter_grehan:</B></FONT> probably 1
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:24:48) </FONT><B>peter_grehan:</B></FONT> 6 would be the easiest to get up and running.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:25:26) </FONT><B>brycedenney:</B></FONT> maybe it's worth making 6 work first since it seems pretty easy
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:25:35) </FONT><B>peter_grehan:</B></FONT> sure
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:25:53) </FONT><B>brycedenney:</B></FONT> and then let's start talking about #1 on bochs-developers and plex86 since they will both be interested
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:25:58) </FONT><B>brycedenney:</B></FONT> esp on linux
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:26:30) </FONT><B>peter_grehan:</B></FONT> OK. Is there much io-dev work coming out of plex86 ?
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:26:47) </FONT><B>brycedenney:</B></FONT> we can probably get some volunteers to help
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:27:17) </FONT><B>brycedenney:</B></FONT> iodev on plex86: not yet, but I think a lot of people are not sure how to help until Kevin's done more of the core stuff
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:27:26) </FONT><B>brycedenney:</B></FONT> I think there will be interest.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:27:49) </FONT><B>peter_grehan:</B></FONT> they have some catching up to do
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:28:08) </FONT><B>brycedenney:</B></FONT> plex86 doesn't consider kernel modules a Con :)
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:29:04) </FONT><B>peter_grehan:</B></FONT> OK
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:29:49) </FONT><B>brycedenney:</B></FONT> would you like to describe #1 in more detail and send it to plex86 and bochs-dev list? I'll finish up my summary of the various plans and send it to bochs-dev at least.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:30:10) </FONT><B>peter_grehan:</B></FONT> OK. See you later.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:30:12) </FONT><B>brycedenney:</B></FONT> and if you don't mind, I would like to post a log of this conversation since I think it will give some important details.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:30:22) </FONT><B>peter_grehan:</B></FONT> Sure.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:30:22) </FONT><B>brycedenney:</B></FONT> or put it on the web or something
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:30:33) </FONT><B>brycedenney:</B></FONT> Thanks Peter! This was very helpful.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:30:43) </FONT><B>peter_grehan:</B></FONT> Bye.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:30:54) </FONT><B>brycedenney:</B></FONT> bye
|
||||
<BR>
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 4.9 KiB |
149
sfsite/news.html
149
sfsite/news.html
|
|
@ -1,149 +0,0 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>bochs: The Open Source IA-32 Emulation Project (Bochs News/History)</TITLE>
|
||||
|
||||
<!--#include virtual="includes/header.txt" -->
|
||||
|
||||
<img src="images/logo.png" alt="A Window, Tux, and the BSD Daemon" width="160" height="175" align="right">
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Bochs News</b></font><BR>
|
||||
|
||||
<UL>
|
||||
<li><b>January 5, 2020:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6.11/">Bochs 2.6.11</a> is now available.
|
||||
<li><b>December 1, 2019:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6.10/">Bochs 2.6.10</a> is now available.
|
||||
<li><b>April 9, 2017:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6.9/">Bochs 2.6.9</a> is now available.
|
||||
<li><b>May 3, 2015:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6.7/">Bochs 2.6.8</a> is now available.
|
||||
<li><b>November 2, 2014:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6.7/">Bochs 2.6.7</a> is now available.
|
||||
<li><b>June 15, 2014:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6.6/">Bochs 2.6.6</a> is now available.
|
||||
<li><b>June 1, 2014:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6.5/">Bochs 2.6.5</a> is now available.
|
||||
<li><b>May 26, 2013:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6.2/">Bochs 2.6.2</a> is now available.
|
||||
<li><b>April 7, 2013:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6.1/">Bochs 2.6.1</a> is now available.
|
||||
<li><b>September 2, 2012:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.6/">Bochs 2.6</a> is now available.
|
||||
<li><b>January 6, 2012:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.5.1/">Bochs 2.5.1</a> is now available.
|
||||
<li><b>November 27, 2011:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.5/">Bochs 2.5</a> is now available (first release from SVN).
|
||||
<li><b>February 23, 2011:</b> Bochs project moved to Subversion (SVN) source control.
|
||||
<li><b>February 22, 2011:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.4.6/">Bochs 2.4.6</a> is now available.
|
||||
<li><b>April, 2010:</b> After long time Bochs is back to top 25 of SourceForce projects !
|
||||
<li><b>April 25, 2010:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.4.5/">Bochs 2.4.5</a> is now available.
|
||||
<li><b>November 12, 2009:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.4.2/">Bochs 2.4.2</a> is now available.
|
||||
<li><b>June 7, 2009:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.4.1/">Bochs 2.4.1</a> is now available.
|
||||
<li><b>May 3, 2009:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.4/">Bochs 2.4</a> is now available.
|
||||
<li><b>June 3, 2008:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.3.7">Bochs 2.3.7</a> is now available.
|
||||
<li><b>December 24, 2007:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.3.6">Bochs 2.3.6</a> is now available.
|
||||
<li><b>September 16, 2007:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.3.5">Bochs 2.3.5</a> is now available.
|
||||
<li><b>August 27, 2006:</b> <a href="https://sourceforge.net/projects/bochs/files/bochs/2.3">Bochs 2.3</a> is now available.
|
||||
<li><b>January 29, 2006:</b> <a href="http://sourceforge.net/project/showfiles.php?group_id=12580&package_id=17475&release_id=389181">Bochs 2.2.6</a> is now available.
|
||||
<li><b>December 30, 2005:</b> <a href="http://sourceforge.net/project/showfiles.php?group_id=12580&package_id=17475&release_id=381709">Bochs 2.2.5</a> is now available.
|
||||
<li><b>July 8, 2005:</b> <a href="http://sourceforge.net/project/showfiles.php?group_id=12580&package_id=17475&release_id=340639">Bochs 2.2.1</a> is now available.
|
||||
<li><b>May 28, 2005:</b> <a href="http://sourceforge.net/project/showfiles.php?group_id=12580&package_id=17475&release_id=330621">Bochs 2.2</a> is now available.
|
||||
<li><b>August 1, 2004:</b> Bochs is SF project of the month for August 2004 !
|
||||
<li><b>February 8, 2004:</b> <a href="http://sourceforge.net/project/showfiles.php?group_id=12580&package_id=17475&release_id=215733">Bochs 2.1.1</a> is now available.
|
||||
<li><b>January 13, 2004:</b> <a href="http://sourceforge.net/project/showfiles.php?group_id=12580&package_id=17475&release_id=209220">Bochs 2.1</a> is now available.
|
||||
<li><b>January 19, 2003:</b> <a href="http://sourceforge.net/project/showfiles.php?group_id=12580&package_id=17475&release_id=135273">Bochs 2.0.2</a> is now available.
|
||||
<li><b>January 4, 2003:</b> <a href="http://sourceforge.net/project/showfiles.php?group_id=12580&package_id=17475&release_id=131547">Bochs 2.0.1</a> is now available.
|
||||
<li><b>December 21, 2002:</b> <a href="http://sourceforge.net/project/showfiles.php?group_id=12580&package_id=17475&release_id=129437">Bochs 2.0</a> is now available.
|
||||
<li><b>June 23, 2002:</b> <a href="http://sourceforge.net/project/showfiles.php?group_id=12580&package_id=17475&release_id=96344">Bochs 1.4.1</a> is now available.
|
||||
<li><b>March 27, 2002:</b> <a href="http://sourceforge.net/project/showfiles.php?group_id=12580&package_id=17475&release_id=79121">Bochs 1.4</a> is now available.
|
||||
<li><b>March 11, 2002:</b> <a href="http://sourceforge.net/project/showfiles.php?group_id=12580&package_id=17475&release_id=79122"> Bochs 1.4.pre2</a> is now available.
|
||||
<li><b>March 3, 2002:</b> <a href="http://sourceforge.net/project/showfiles.php?group_id=12580&package_id=17475&release_id=78152"> Bochs 1.4.pre1</a> is now available.
|
||||
<li><b>December 10, 2001:</b> <a href="http://sourceforge.net/project/showfiles.php?group_id=12580&package_id=17475&release_id=65067">Bochs 1.3</a> is now available
|
||||
<li><b>November 17, 2001:</b> <a href="http://sourceforge.net/project/showfiles.php?group_id=12580&package_id=17475&release_id=61806">Bochs 1.3.pre1</a> is now available.
|
||||
<li><b>June 24, 2001:</b> Thanks to Psyon, Bochs in the CVS now has CD-ROM support under Win9x.
|
||||
<li><b>June 16, 2001:</b> <a href="http://sourceforge.net/project/showfiles.php?group_id=12580&package_id=17475&release_id=39123">Bochs 1.2.1</a> is now available.
|
||||
<li><b>June 3, 2001:</b> <a href="http://sourceforge.net/project/showfiles.php?group_id=12580&package_id=17475&release_id=37919">Bochs 1.2</a> is now available in both source and binary form. Read all about this major new release over <a href="http://bochs.sourceforge.net/cgi-bin/topper.pl?name=Press+Release+for+Bochs+1.2&url=http://bochs.sourceforge.net/bochs-pr-20010604.txt">here</a>.
|
||||
<li><b>May 23, 2001:</b> Activity Update - Less than a month after the transfer to Sourceforge, Bochs has reached the top of the <a
|
||||
href="http://sourceforge.net/top/mostactive.php?type=week">SourceForge</a> project activity chart! Thanks to Todd T. Fries for the update.
|
||||
<li><b>May 22, 2001:</b> Bochs is number two on the <a
|
||||
href="http://sourceforge.net/top/mostactive.php?type=week">SourceForge</a> project activity chart today!
|
||||
<li><b>May 17, 2001:</b> <a href="http://sourceforge.net/project/showfiles.php?group_id=12580&package_id=17475&release_id=35465">Bochs 1.1.2</a> is released, fixing several bugs found in the previous Bugfix2 release.
|
||||
<li><b>May 12, 2001:</b> After hovering around 10th place on the SourceForge <a href="http://sourceforge.net/top/mostactive.php?type=week">activity rankings</a> for
|
||||
the better part of a week, Bochs moves up even further! Bochs is listed as the 6th most active project on SF today.
|
||||
<li><b>May 11, 2001:</b> Our new site is released with more information, a new screen shots section, CVS nightly tarballs, and much more!
|
||||
<li><b>May 3, 2001:</b> We are trying to gather a screenshot gallery of Bochs in action.
|
||||
If you have a screenshot you would like to share, please e-mail it
|
||||
to <a href="mailto:tbutler@uninetsolutions.com">Tim Butler</a>.<BR>
|
||||
<li><b>May 3, 2001:</b> Actual transition to
|
||||
<a href="http://bochs.sourceforge.net/">bochs.sourceforge.net</a> takes place.
|
||||
<li><b>May 2, 2001:</b> The bochs-developers@redhat.com mailing list has moved to
|
||||
bochs-developers@lists.sourceforge.net. Please use the sourceforge list,
|
||||
since the redhat one will soon be shut down. If you want to subscribe to
|
||||
the new list, <a href="http://lists.sourceforge.net/lists/listinfo/bochs-developers">go here</a>.
|
||||
|
||||
<li><b>Apr 30, 2001:</b> With support from Kevin Lawton, Bochs development has moved
|
||||
to <a href="http://bochs.sourceforge.net">bochs.sourceforge.net</a>. Look for new
|
||||
releases, CVS access, bug tracking, and more on the SourceForge pages. The
|
||||
mailing list is still hosted at redhat.com, but will soon be switched to SF as
|
||||
well.
|
||||
<li><b>Apr 9, 2001:</b> Bryce Denney collected patches from bochs-developers mailing
|
||||
list and sourceforge to create the Bugfix2 release.
|
||||
<li><b>Nov 14, 2000:</b> Bochs.com moves to new ISP,
|
||||
<a href="http://www.fastxs.net/">FastXS.net</a>.
|
||||
<li><b>Mar 22, 2000:</b>
|
||||
<a href="http://www.linux-mandrake.com/en/announce-bochs-20000323.php3">
|
||||
MandrakeSoft buys Bochs for Linux and commits it to Open Source.
|
||||
</a>
|
||||
Bochs now has the LGPL license.
|
||||
<li><b>Jan 4, 2000:</b>
|
||||
New release:
|
||||
Integrated FPU emulator into main bochs source; FPU
|
||||
emulation now works on big-endian machines (tested on SPARC).
|
||||
<li><b>Nov 14, 1999:</b>
|
||||
New release:
|
||||
CDROM emulation works on Win32. Some Win32 cleanup.
|
||||
CALL instruction fix.
|
||||
<li><b>Nov 11, 1999:</b>
|
||||
New release:
|
||||
Sound Blaster 16 emulation integrated.
|
||||
<li><b>Nov 2, 1999:</b>
|
||||
New release:
|
||||
WinNT4.0 installs in bochs from CDROM. More Win32 mods integrated.
|
||||
<li><b>Oct 23, 1999:</b>
|
||||
New release:
|
||||
More fixes to CPU emulation. CDROM also works on OpenBSD. Mac update.
|
||||
<li><b>Oct 14, 1999:</b>
|
||||
New release:
|
||||
CDROM emulation now works (only Linux so far).
|
||||
<li><b>Oct 12, 1999:</b>
|
||||
New release:
|
||||
Moved default to Pentium emulation,
|
||||
added x86 hardware debug features, more Pentium mods, ...
|
||||
<li><b>Oct 4, 1999:</b>
|
||||
New release:
|
||||
Partial Pentium emulation. Windows'95/Linux boot and
|
||||
recognize Pentium emulation.
|
||||
<li><b>Sep 25, 1999:</b>
|
||||
New release:
|
||||
Minix boots again. Fixes to BIOS, floppy, and Makefiles.
|
||||
<li><b>Sep 23, 1999:</b>
|
||||
New release:
|
||||
Fixes/enhancements for VGA, debugger, floppy.
|
||||
<li><b>Sep 20, 1999:</b>
|
||||
New release: Bochs now compiles with
|
||||
<a href="http://www.linuxsupportline.com/~billm/">wm-FPU-emu</a>
|
||||
, for users who need direct floating point support.
|
||||
<li><b>Sep 7, 1999:</b> New release includes minor bug fixes.
|
||||
<li><b>Sep 7, 1999:</b> FreeMWare is off to good start, with
|
||||
code releases already. CVS services are now available
|
||||
to the development team.
|
||||
<li><b>Jul 8, 1999:</b> New release includes a bunch of changes
|
||||
<li><b>May 17, 1999:</b> I (Kevin Lawton) will be at
|
||||
<A HREF="http://www.linuxexpo.org">Linux Expo '99</A>.
|
||||
<li><b>Apr 30, 1999:</b> Developer submits Sound Blaster 16 emulation.
|
||||
<li><b>Mar 12, 1999:</b> First test release with dynamic translation!
|
||||
<li><b>Mar 11, 1999:</b> Developer submits NE2000 network card emulation.
|
||||
<li><b>Feb 19, 1999:</b> New release includes a number of submitted diffs.
|
||||
<li><b>Jan 27, 1999:</b> Rehashed CPU to separate fetch-decode/address-resolve/execute
|
||||
phases.
|
||||
<li><b>Jan 10, 1999:</b> Bochs now compiles under BeOS R4 x86 with gcc.
|
||||
<li><b>Dec xx, 1998:</b> Bochs is ported to the Mac by David Batterham.
|
||||
</UL>
|
||||
|
||||
<!--#include virtual="includes/footer.txt" -->
|
||||
|
||||
|
||||
Last Modified on <!--#flastmod file="news.html" -->.<BR>
|
||||
|
||||
<!--#include virtual="includes/cright.txt" -->
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -1,469 +0,0 @@
|
|||
<FONT COLOR="#ff0000"><FONT SIZE="2">(07:59:11) </FONT><B>peter_grehan:</B></FONT> finally logged on...
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(07:59:36) </FONT><B>brycedenney:</B></FONT> hey
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(07:59:41) </FONT><B>brycedenney:</B></FONT> how's it going?
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:00:28) </FONT><B>brycedenney:</B></FONT> if lag is too bad, we can try irc or AOL IM
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:01:40) </FONT><B>peter_grehan:</B></FONT> sorry
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:01:46) </FONT><B>peter_grehan:</B></FONT> fire away with the net questions.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:02:07) </FONT><B>brycedenney:</B></FONT> did you see Dave's post this morning?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:02:25) </FONT><B>peter_grehan:</B></FONT> no
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:02:27) </FONT><B>brycedenney:</B></FONT> (EKS) he and I got to talking about kernel drivers
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:03:05) </FONT><B>brycedenney:</B></FONT> you'll get it soon, I guess we should start with the big picture
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:03:30) </FONT><B>brycedenney:</B></FONT> we need bochs to be able to talk to the host machine and other machines in the world.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:03:43) </FONT><B>peter_grehan:</B></FONT> just reading the email now...
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:03:46) </FONT><B>brycedenney:</B></FONT> ok
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:04:14) </FONT><B>brycedenney:</B></FONT> we have user-code solutions for a few OSes that talk to the world but not the host machine
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:04:57) </FONT><B>peter_grehan:</B></FONT> ok
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:05:32) </FONT><B>brycedenney:</B></FONT> so we need to dream up a plan to talk to both host and world, eventually supporting all systems
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:05:36) </FONT><B>brycedenney:</B></FONT> :)
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:06:36) </FONT><B>peter_grehan:</B></FONT> this involves writing a virtual ethernet driver
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:06:56) </FONT><B>brycedenney:</B></FONT> isn't that what EKS describes?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:07:09) </FONT><B>peter_grehan:</B></FONT> engineer the interface from the source they provide. However
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:07:24) </FONT><B>peter_grehan:</B></FONT> yep
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:08:31) </FONT><B>peter_grehan:</B></FONT> the host o/s driver *can't* be generic
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:08:34) </FONT><B>peter_grehan:</B></FONT> ps-specific code
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:08:40) </FONT><B>brycedenney:</B></FONT> os
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:08:43) </FONT><B>brycedenney:</B></FONT> right
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:09:38) </FONT><B>brycedenney:</B></FONT> ok so one plan is to write a virtual ethernet driver for each supported OS
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:10:13) </FONT><B>peter_grehan:</B></FONT> that's the only real way to do this.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:10:15) </FONT><B>brycedenney:</B></FONT> I need to test this: can you get multiline sends (this is 3 lines long)<BR>
|
||||
line 2<BR>
|
||||
line 3
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:10:51) </FONT><B>peter_grehan:</B></FONT> yep.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:10:53) </FONT><B>brycedenney:</B></FONT> good
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:11:02) </FONT><B>brycedenney:</B></FONT> one plan:
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:11:06) </FONT><B>brycedenney:</B></FONT> A virtual ethernet driver allows you to talk to the host and the world.<BR>
|
||||
Pros: talk to both host and world<BR>
|
||||
Cons: Must have root access.<BR>
|
||||
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:11:23) </FONT><B>brycedenney:</B></FONT> does that seem correct to you?
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:11:41) </FONT><B>brycedenney:</B></FONT> cons: must be written separately for each OS
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:12:32) </FONT><B>peter_grehan:</B></FONT> not necessarily - it really only allows you to talk to the host
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:12:42) </FONT><B>brycedenney:</B></FONT> but then IP routing lets you talk to the rest
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:12:49) </FONT><B>brycedenney:</B></FONT> without any wierd hacks
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:12:55) </FONT><B>brycedenney:</B></FONT> ?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:13:20) </FONT><B>peter_grehan:</B></FONT> only if forwarding is enabled
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:13:38) </FONT><B>brycedenney:</B></FONT> with root access, you can make it work
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:13:45) </FONT><B>peter_grehan:</B></FONT> yep.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:13:48) </FONT><B>brycedenney:</B></FONT> you might need to redo your kernel or something
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:14:11) </FONT><B>peter_grehan:</B></FONT> you need to load a module
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:15:08) </FONT><B>brycedenney:</B></FONT> how about this then:
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:15:11) </FONT><B>brycedenney:</B></FONT> 1. A virtual ethernet driver <BR>
|
||||
Pros: you can talk to both host and world<BR>
|
||||
Cons: Must have root access to load a kernel module, <BR>
|
||||
must be written separately for each host OS,<BR>
|
||||
must set up IP forwarding to talk to the world.<BR>
|
||||
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:15:56) </FONT><B>peter_grehan:</B></FONT> that's correct.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:16:05) </FONT><B>brycedenney:</B></FONT> ok here's another plan
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:16:21) </FONT><B>brycedenney:</B></FONT> 2. packet filters (BPF, LSF)<BR>
|
||||
Pros: infrastructure is already there in iodev/eth_*.cc<BR>
|
||||
each packet mover can support several OSes if <BR>
|
||||
they have the right library/kernel feature.<BR>
|
||||
user can run it, <BR>
|
||||
Cons: can't talk to host<BR>
|
||||
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:17:44) </FONT><B>peter_grehan:</B></FONT> that's right. there are still some issues with this - at one stage
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:18:33) </FONT><B>peter_grehan:</B></FONT> I just remembered: there is a port of BPF to windows which I've used. It's quite good
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:18:46) </FONT><B>brycedenney:</B></FONT> cool!
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:19:39) </FONT><B>peter_grehan:</B></FONT> one other option is a kernel module that hooks into bridging code. this is what VmWare uses - it makes the guest o/s look like it's on the same LAN as the host o/s. Very similar to the packet filter option.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:20:35) </FONT><B>brycedenney:</B></FONT> does bridging code make other machines on the net see a different MAC address from the host?
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:20:50) </FONT><B>brycedenney:</B></FONT> or is it IP based?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:21:08) </FONT><B>peter_grehan:</B></FONT> yep
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:21:12) </FONT><B>brycedenney:</B></FONT> ip
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:21:15) </FONT><B>brycedenney:</B></FONT> ?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:22:16) </FONT><B>peter_grehan:</B></FONT> I should have mentioned: other hosts would see a different MAC addr
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:22:24) </FONT><B>brycedenney:</B></FONT> cool!
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:22:49) </FONT><B>brycedenney:</B></FONT> any hope of doing that in windows? does it have bridging code?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:23:31) </FONT><B>peter_grehan:</B></FONT> no
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:23:49) </FONT><B>brycedenney:</B></FONT> but it's a good solution for systems that support it
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:24:28) </FONT><B>peter_grehan:</B></FONT> it's the best in that it requires no extra config on the host o/s
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:25:32) </FONT><B>brycedenney:</B></FONT> 5. Kernel module using bridging code<BR>
|
||||
Pros: bochs appears to be a different MAC than the host,<BR>
|
||||
requires no extra config on the host o/s<BR>
|
||||
Cons: Must have root access to load a kernel module,<BR>
|
||||
must be written separately for each host OS,<BR>
|
||||
bridging code not present in all kernels,<BR>
|
||||
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:26:47) </FONT><B>peter_grehan:</B></FONT> yep
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:27:01) </FONT><B>brycedenney:</B></FONT> you may wonder where are 3 & 4 :)
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:27:08) </FONT><B>brycedenney:</B></FONT> 3. TCP only networking<BR>
|
||||
Pros: can be portable socket code,<BR>
|
||||
can run as a normal user<BR>
|
||||
Cons: each protocol must be handled separately<BR>
|
||||
hard to extract TCP information from ethernet frames (maybe<BR>
|
||||
we could borrow linux or other networking code)<BR>
|
||||
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:27:58) </FONT><B>peter_grehan:</B></FONT> that one ain't gonna work. there are whole companies built on the basis of less code than what that will take !
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:28:10) </FONT><B>brycedenney:</B></FONT> :)
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:28:47) </FONT><B>brycedenney:</B></FONT> I don't want to spent too much time on it
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:29:17) </FONT><B>brycedenney:</B></FONT> but why couldn't you rip off code from an open source kernel
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:29:30) </FONT><B>brycedenney:</B></FONT> that translates ethernet frames into a usable form
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:30:11) </FONT><B>peter_grehan:</B></FONT> it's not just translating - you have to implement a complete stack
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:30:21) </FONT><B>peter_grehan:</B></FONT> possible work for outgoing TCP connections
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:30:34) </FONT><B>peter_grehan:</B></FONT> I should say
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:32:02) </FONT><B>brycedenney:</B></FONT> You mentioned in an email that you have to get the kernel code running as a user, and FYI ther's a whole project that has already done that (<A HREF="http://user-mode-linux.sourceforge.net/">http://user-mode-linux.sourceforge.net/</A>)
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:33:24) </FONT><B>brycedenney:</B></FONT> for incoming TCP connections you would need some tricks. What if you tell bochs "Map local TCP port 3023 to bochs port 23"
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:34:02) </FONT><B>brycedenney:</B></FONT> then bochs would have to bind to TCP port 3023, and when it gets connections it would build up the appropriate ethernet frame and put it into bochs's NE2K packet mover.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:35:01) </FONT><B>peter_grehan:</B></FONT> yep
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:35:01) </FONT><B>peter_grehan:</B></FONT> psuedo driver !
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:35:01) </FONT><B>peter_grehan:</B></FONT> plus
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:35:30) </FONT><B>brycedenney:</B></FONT> The only reason I'm so interested in this plan is the pros are very important: portable code, running as a user
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:35:44) </FONT><B>peter_grehan:</B></FONT> that's a lot of configuration. you may not know in advance all the ports you would need.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:35:51) </FONT><B>brycedenney:</B></FONT> almost all the other plans, a student with a user account could never even try it.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:36:15) </FONT><B>brycedenney:</B></FONT> bochs configuration at runtime we can do, we're planning a control panel of sorts
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:37:03) </FONT><B>brycedenney:</B></FONT> we linux users have to remember, not everybody is root! :)
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:37:58) </FONT><B>peter_grehan:</B></FONT> the student account thing isn't quite true
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:38:13) </FONT><B>brycedenney:</B></FONT> what plan would allow non-root networking?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:39:41) </FONT><B>peter_grehan:</B></FONT> I can't think of one that is going to cover all cases. For windows
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:41:58) </FONT><B>peter_grehan:</B></FONT> I'll try and draw some pictures and send them to you
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:42:01) </FONT><B>brycedenney:</B></FONT> ok
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:42:26) </FONT><B>brycedenney:</B></FONT> so under cons I will add "Peter thinks it's not worth the trouble" :)
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:42:44) </FONT><B>brycedenney:</B></FONT> BTW, how much time do you have left?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:42:55) </FONT><B>peter_grehan:</B></FONT> yeh
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:43:22) </FONT><B>peter_grehan:</B></FONT> maybe another 1/2 hour or so... did you want to go over any other net stuff ???
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:43:34) </FONT><B>brycedenney:</B></FONT> I have one more plan.....
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:43:37) </FONT><B>brycedenney:</B></FONT> :_
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:43:39) </FONT><B>brycedenney:</B></FONT> :)
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:43:52) </FONT><B>peter_grehan:</B></FONT> have at it..
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:44:00) </FONT><B>brycedenney:</B></FONT> 4. IP only networking through hack of PPP on host. Bochs guest OS runs an <BR>
|
||||
NE2K, bochs emulator includes some parts of user-level PPP code and moves<BR>
|
||||
packets to/from the PPP kernel module.<BR>
|
||||
<BR>
|
||||
Pros: PPP kernel code already written for many platforms<BR>
|
||||
PPP user code already written<BR>
|
||||
maybe can be run as a normal user<BR>
|
||||
all IP protocols supported<BR>
|
||||
Cons: maybe hard to extract IP information from ethernet frames<BR>
|
||||
(is it really that hard?)<BR>
|
||||
have to emulate some ethernet functions<BR>
|
||||
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:45:22) </FONT><B>brycedenney:</B></FONT> It's a bit crazy, but motivated by the fact that tons of people get all their network access through PPP, so it's not that much of a limitation for Bochs to get its network access through PPP.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:45:32) </FONT><B>peter_grehan:</B></FONT> I thought that would be better off done through the serial driver itself
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:45:41) </FONT><B>peter_grehan:</B></FONT> doing a type of eth-ppp bridge.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:45:59) </FONT><B>brycedenney:</B></FONT> it seems like better performance to get many bytes at a time in the ne2k than sending bits at a time via serial
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:46:11) </FONT><B>peter_grehan:</B></FONT> The serial driver is currently optimised for interactive input
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:47:20) </FONT><B>brycedenney:</B></FONT> Do you have a concept of how many emulated instructions are required to build an ethernet frame VS sending the equivalent amount of data through serial driver?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:47:42) </FONT><B>peter_grehan:</B></FONT> Maybe I'm being a bit too harsh. Many early PPP implementations were made to look like ethernet drivers to the host. I just noticed today that the standard 'pppd' has a config option to direct output to a pseudo-terminal
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:47:44) </FONT><B>brycedenney:</B></FONT> it's the number of emulated instructions that's the limiting factor.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:48:51) </FONT><B>peter_grehan:</B></FONT> The ne2k has to manually write every byte out in any case
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:49:08) </FONT><B>brycedenney:</B></FONT> no DMA? :)
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:49:27) </FONT><B>peter_grehan:</B></FONT> nope
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:49:41) </FONT><B>brycedenney:</B></FONT> we could emulate a DMA capable card one day, but whatever.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:50:05) </FONT><B>brycedenney:</B></FONT> do you think serial and ne2k methods would take approximately the same # of bochs instructions to send out?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:51:00) </FONT><B>peter_grehan:</B></FONT> The serial is going to take more
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:51:12) </FONT><B>brycedenney:</B></FONT> I expected it would, but why
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:51:29) </FONT><B>brycedenney:</B></FONT> (I haven't programmed either one :) )
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:51:58) </FONT><B>peter_grehan:</B></FONT> I only wanted to get a FreeBSD serial console working
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:53:12) </FONT><B>brycedenney:</B></FONT> any reason why the current bochs serial emulation couldn't handle a PPP connection?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:53:54) </FONT><B>peter_grehan:</B></FONT> some work would be needed to abstract out the sending/receiving of bytes
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:54:07) </FONT><B>brycedenney:</B></FONT> ?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:55:33) </FONT><B>peter_grehan:</B></FONT> the serial code currently writes bytes to file descriptor 0
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:55:50) </FONT><B>brycedenney:</B></FONT> right, you'd want to open a TTY or something instead
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:56:03) </FONT><B>peter_grehan:</B></FONT> yep.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:56:26) </FONT><B>brycedenney:</B></FONT> other than that, anything not supported that PPP might need?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:57:10) </FONT><B>peter_grehan:</B></FONT> You'd have to set up the TTY for raw mode
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:57:45) </FONT><B>brycedenney:</B></FONT> ok, but as far as the serial port emulation in bochs, it has all the registers and bits
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:58:31) </FONT><B>brycedenney:</B></FONT> Did you say why serial would take more instructions? I'm interested in some guess like 50% more, 100% more, since I don't know what the constraints are.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(08:58:34) </FONT><B>peter_grehan:</B></FONT> yep
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:58:47) </FONT><B>brycedenney:</B></FONT> great! I'll play with serial a bit.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(08:59:11) </FONT><B>brycedenney:</B></FONT> (bad pun was not intended :) )
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:00:20) </FONT><B>peter_grehan:</B></FONT> async PPP has overhead
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:01:27) </FONT><B>brycedenney:</B></FONT> ok
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:02:27) </FONT><B>brycedenney:</B></FONT> we didn't actually talk about <BR>
|
||||
4. IP only networking through hack of PPP on host. Bochs guest OS runs an<BR>
|
||||
NE2K, bochs emulator includes some parts of user-level PPP code and moves<BR>
|
||||
packets to/from the PPP kernel module.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:02:52) </FONT><B>brycedenney:</B></FONT> except to say that it might be done with PPP on the guest os
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:02:58) </FONT><B>brycedenney:</B></FONT> does it have any merits at all?
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:03:19) </FONT><B>brycedenney:</B></FONT> is my description clear enough to know what I'm talking about?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:03:58) </FONT><B>peter_grehan:</B></FONT> Yeh
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:04:01) </FONT><B>peter_grehan:</B></FONT> it could be made to work.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:04:23) </FONT><B>brycedenney:</B></FONT> it's only useful if the overhead of running PPP on the guest rather than ethernet driver is large enough
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:05:06) </FONT><B>brycedenney:</B></FONT> if overhead is similar, we should just use serial since it doesn't require any PPP hacking.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:05:12) </FONT><B>peter_grehan:</B></FONT> it would also allow non-root networking
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:05:55) </FONT><B>brycedenney:</B></FONT> same as running PPP direct, you may need root to set you up as a legal PPP user
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:05:55) </FONT><B>peter_grehan:</B></FONT> it doesn't need hacking
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:06:15) </FONT><B>brycedenney:</B></FONT> you mean plan 4 doesn't need hacking?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:06:57) </FONT><B>peter_grehan:</B></FONT> no kernel hacking
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:07:35) </FONT><B>brycedenney:</B></FONT> right, but some changes to PPPD I expect
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:08:34) </FONT><B>peter_grehan:</B></FONT> I don't think so - from what I saw
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:09:00) </FONT><B>brycedenney:</B></FONT> are you saying bochs could read and write to a PPPD-controlled terminal
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:09:27) </FONT><B>brycedenney:</B></FONT> and just translate ethernet<->PPP when bochs or the ppp had a packet?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:10:08) </FONT><B>peter_grehan:</B></FONT> That's right
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:10:17) </FONT><B>brycedenney:</B></FONT> hey
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:10:31) </FONT><B>brycedenney:</B></FONT> I didn't think of it that way, but it's good
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:10:35) </FONT><B>peter_grehan:</B></FONT> Bochs serial driver - when a character is sent out
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:10:57) </FONT><B>peter_grehan:</B></FONT> The translation from ethernet-ppp
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:11:58) </FONT><B>brycedenney:</B></FONT> I missed something
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:12:20) </FONT><B>peter_grehan:</B></FONT> about eth-ppp ?
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:12:22) </FONT><B>brycedenney:</B></FONT> are you doing multiline sends ?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:12:33) </FONT><B>peter_grehan:</B></FONT> I think I hit return accidentally there :-(
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:12:46) </FONT><B>brycedenney:</B></FONT> I only got: "Bochs serial driver - when a character is sent out" and then "The translation from ethernet-ppp" that's all
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:13:13) </FONT><B>peter_grehan:</B></FONT> I'll type that bit again:
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:13:21) </FONT><B>brycedenney:</B></FONT> sorry
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:13:47) </FONT><B>peter_grehan:</B></FONT> when a character is sent out
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:13:58) </FONT><B>peter_grehan:</B></FONT> did that come thru OK ?
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:14:11) </FONT><B>brycedenney:</B></FONT> one line only "when a character is sent out"
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:14:58) </FONT><B>peter_grehan:</B></FONT> next line: when a char arrives on the pseudo-term
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:15:57) </FONT><B>brycedenney:</B></FONT> ok
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:16:56) </FONT><B>brycedenney:</B></FONT> it seems that yahoo IM is failing here :(
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:17:17) </FONT><B>peter_grehan:</B></FONT> the east coast is coming on-line :-)
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:18:31) </FONT><B>brycedenney:</B></FONT> ping1
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:18:57) </FONT><B>peter_grehan:</B></FONT> still here
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:19:08) </FONT><B>brycedenney:</B></FONT> good
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:19:16) </FONT><B>brycedenney:</B></FONT> I can't tell if I'm losing messages or just dense.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:19:38) </FONT><B>peter_grehan:</B></FONT> maybe msgs are being lost...
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:20:04) </FONT><B>brycedenney:</B></FONT> we're close to being out of time anyway
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:20:18) </FONT><B>brycedenney:</B></FONT> we have 6 plans now!!
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:20:23) </FONT><B>brycedenney:</B></FONT> 1. A virtual ethernet driver<BR>
|
||||
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:20:27) </FONT><B>brycedenney:</B></FONT> 2. packet filters (BPF, LSF)
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:20:31) </FONT><B>brycedenney:</B></FONT> 3. TCP only networking
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:20:36) </FONT><B>brycedenney:</B></FONT> 4. IP only networking through hack of PPP on host.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:20:41) </FONT><B>brycedenney:</B></FONT> 5. Kernel module using bridging code
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:20:45) </FONT><B>brycedenney:</B></FONT> 6. PPP link using bochs serial code
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:21:00) </FONT><B>brycedenney:</B></FONT> all have pros and cons of course
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:21:26) </FONT><B>brycedenney:</B></FONT> Is there any of them that you would like to work on, time permitting?
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:22:12) </FONT><B>brycedenney:</B></FONT> or do you want to advise others who do have the time and seem to know what they're talking about?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:22:12) </FONT><B>peter_grehan:</B></FONT> I can help out
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:22:19) </FONT><B>peter_grehan:</B></FONT> sure
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:22:35) </FONT><B>brycedenney:</B></FONT> which seems most promising?
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:22:42) </FONT><B>brycedenney:</B></FONT> what OS do you use anyway? freebsd?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:23:11) </FONT><B>peter_grehan:</B></FONT> I run Linux on my desktop
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:23:18) </FONT><B>brycedenney:</B></FONT> cool, me too
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:23:23) </FONT><B>peter_grehan:</B></FONT> I used a heavily modified FreeBSD when I was at Nokia :-)
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:23:59) </FONT><B>brycedenney:</B></FONT> which plan interests you the most?
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:24:37) </FONT><B>peter_grehan:</B></FONT> probably 1
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:24:48) </FONT><B>peter_grehan:</B></FONT> 6 would be the easiest to get up and running.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:25:26) </FONT><B>brycedenney:</B></FONT> maybe it's worth making 6 work first since it seems pretty easy
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:25:35) </FONT><B>peter_grehan:</B></FONT> sure
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:25:53) </FONT><B>brycedenney:</B></FONT> and then let's start talking about #1 on bochs-developers and plex86 since they will both be interested
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:25:58) </FONT><B>brycedenney:</B></FONT> esp on linux
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:26:30) </FONT><B>peter_grehan:</B></FONT> OK. Is there much io-dev work coming out of plex86 ?
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:26:47) </FONT><B>brycedenney:</B></FONT> we can probably get some volunteers to help
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:27:17) </FONT><B>brycedenney:</B></FONT> iodev on plex86: not yet, but I think a lot of people are not sure how to help until Kevin's done more of the core stuff
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:27:26) </FONT><B>brycedenney:</B></FONT> I think there will be interest.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:27:49) </FONT><B>peter_grehan:</B></FONT> they have some catching up to do
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:28:08) </FONT><B>brycedenney:</B></FONT> plex86 doesn't consider kernel modules a Con :)
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:29:04) </FONT><B>peter_grehan:</B></FONT> OK
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:29:49) </FONT><B>brycedenney:</B></FONT> would you like to describe #1 in more detail and send it to plex86 and bochs-dev list? I'll finish up my summary of the various plans and send it to bochs-dev at least.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:30:10) </FONT><B>peter_grehan:</B></FONT> OK. See you later.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:30:12) </FONT><B>brycedenney:</B></FONT> and if you don't mind, I would like to post a log of this conversation since I think it will give some important details.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:30:22) </FONT><B>peter_grehan:</B></FONT> Sure.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:30:22) </FONT><B>brycedenney:</B></FONT> or put it on the web or something
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:30:33) </FONT><B>brycedenney:</B></FONT> Thanks Peter! This was very helpful.
|
||||
<BR>
|
||||
<FONT COLOR="#ff0000"><FONT SIZE="2">(09:30:43) </FONT><B>peter_grehan:</B></FONT> Bye.
|
||||
<BR>
|
||||
<FONT COLOR="#0000ff"><FONT SIZE="2">(09:30:54) </FONT><B>brycedenney:</B></FONT> bye
|
||||
<BR>
|
||||
|
|
@ -1,68 +0,0 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>bochs: The Open Source IA-32 Emulation Project (Related Projects)</TITLE>
|
||||
|
||||
<!--#include virtual="includes/header.txt" -->
|
||||
|
||||
<img src="images/logo.png" alt="A Window, Tux, and the BSD Daemon" width="160" height="175" align="right">
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Related Projects</b></font><BR>
|
||||
|
||||
<ul>
|
||||
<li><a href="http://plex86.sourceforge.net">Plex86</a>
|
||||
has been rehashed/revitalized to offer a very lightweight Virtual Machine (VM)
|
||||
for running Linux/x86. Rather than implement a full and heavyweight VM which
|
||||
can run all guest Operating Systems, the new approach is designed to run
|
||||
only Linux VMs, making the new plex86 architecture on the order of 10x or 100x
|
||||
more simplistic.
|
||||
|
||||
<li><a href="http://wiki.qemu.org">QEMU</a>
|
||||
is a generic and open source processor emulator which achieves a good emulation
|
||||
speed by using dynamic translation.
|
||||
|
||||
<li><a href="http://www.vmware.com">Vmware</a> is a commercial virtual PC type
|
||||
system for Linux and Windows-based PC's. According to their FAQ, "
|
||||
VMware Workstation runs multiple operating systems, including Microsoft
|
||||
Windows, Linux, and Novell NetWare, simultaneously on a single PC in fully
|
||||
networked, portable virtual machines."
|
||||
|
||||
<li><a href="http://www.winehq.com">WINE (Wine Is Not an Emulator)</a> is
|
||||
creating an implementation of the Win32 API's for POSIX-based operating
|
||||
systems. The project says it currently has 90% of the API's implemented. WINE
|
||||
is open source software licensed under a GNU LGPL license.
|
||||
|
||||
<li><a href="http://www.microsoft.com/windowsxp/virtualpc/previous/default.asp">Connectix Virtual PC</a> is still
|
||||
another commercial virtual PC implementation. Connectix Corporation was
|
||||
bought by Microsoft in February 2003. Their FAQ says, "Connectix Virtual PC
|
||||
for Windows is a client based software virtualization application that allows
|
||||
you to simultaneously run multiple operating systems on a single PC."
|
||||
|
||||
<li><a href="http://www.windriver.com/simics">Virtutech
|
||||
Simics</a> is a commercial simulator that can target IA32, IA64, Sparc, Alpha,
|
||||
ARM, PowerPC, and MIPS architectures. From their website: "Virtutech Simics is
|
||||
a full system simulation platform that provides a controlled, deterministic,
|
||||
and fully virtualized environment. It simulates both uniprocessor and
|
||||
multiprocessor systems, provides a common infrastructure for a broad variety of
|
||||
tasks, including: microprocessor design; memory hierarchy design; component
|
||||
development and testing; automated software quality testing; SoC virtual
|
||||
prototypes; hardware-software co-simulation; and the development of firmware,
|
||||
drivers, and operating systems."
|
||||
<li>
|
||||
Bernhard Bablok has created a <a
|
||||
href="http://www.bablokb.de/bochs-tools/">Bochs Tools</a> page.
|
||||
"You want to run your favorite Linux-installation with the Bochs-Emulator but
|
||||
you think it is too tedious to install it from within Bochs? Bochs-Tools are
|
||||
the solution for your problem. With Bochs-Tools, cloning an existing
|
||||
OS-installation to a Bochs-image is only a matter of a few commands. "
|
||||
</a>
|
||||
|
||||
</ul>
|
||||
|
||||
<!--#include virtual="includes/footer.txt" -->
|
||||
|
||||
|
||||
Last Modified on <!--#flastmod file="related.html" -->.<BR>
|
||||
|
||||
<!--#include virtual="includes/cright.txt" -->
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -1,351 +0,0 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>bochs: The Open Source IA-32 Emulation Project (About Bochs 2.0)</TITLE>
|
||||
|
||||
<!--#include virtual="includes/header.txt" -->
|
||||
|
||||
<img src="images/logo.png" alt="A Window, Tux, and the BSD Daemon" width="160" height="175" align="right">
|
||||
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Bochs 2.0 is
|
||||
Coming!</b></font><BR>
|
||||
|
||||
This page describes the latest progress as we move toward releasing Bochs 2.0.
|
||||
Please check it periodically, because it will change regularly.
|
||||
<p>
|
||||
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>What's new?
|
||||
</b></font><BR>
|
||||
Our last release was Bochs 1.4.1 on June 23 of this year. Since then there
|
||||
has been a LOT of development activity, especially since mid-August. Here's
|
||||
a summary.
|
||||
<ul>
|
||||
<li> CPU optimizations boost simulation speed by around 2x. (Kevin Lawton)
|
||||
<li> Bochs now supports up to 8 hard drives, or 8 CDROMs, or any combination
|
||||
(Christophe Bothamy)
|
||||
<li> The wxWindows interface has grown so that you can edit all bochsrc
|
||||
parameters using menus and dialog boxes (Bryce Denney)
|
||||
<li> Added support for the AMD x86-64 instruction set used in their Hammer processor (Peter Tattam)
|
||||
<li> Added support for MMX instructions (Stanislav Shwartzman)
|
||||
<li> Added support for SSE and SSE2 instructions (Stanislav Shwartzman)
|
||||
<li> Remote GDB stub support (Johan Rydberg, Stu Grossman)
|
||||
<li> Added plugin support for Linux, Solaris, MacOS X, and Cygwin. Plugins
|
||||
allow you to compile Bochs with support for many options and load the
|
||||
pieces that you want at runtime.
|
||||
</ul>
|
||||
|
||||
Here is the current <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/bochs/bochs/CHANGES?rev=HEAD&content-type=text/vnd.viewcvs-markup">Change Log</a>. It is now complete, after lots of work by Bryce, Christophe, and Volker.
|
||||
<p>
|
||||
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>The Release
|
||||
Process </b></font><BR>
|
||||
|
||||
Before the 2.0 release is finalized, a few things need to happen. First, the
|
||||
developers declare a feature freeze, during which only bug fixes will be
|
||||
added to the CVS. The feature freeze began around the first of November,
|
||||
and will continue until the release is ready. During the feature freeze, we
|
||||
focus on testing Bochs in all sorts of configurations, fixing bugs, updating
|
||||
documentation, and generally cleaning things up. The freeze will last until we
|
||||
have some confidence that the most critical bugs have been fixed or worked
|
||||
around, and that Bochs will compile and work on all supported platforms. <p>
|
||||
|
||||
During this time, the Source Forge bug/feature/patch trackers are very
|
||||
important and very useful. Any bug that we intend to fix before the 2.0
|
||||
release should be marked with Group="to be fixed in v2.0". At the time of
|
||||
release, there will be no more open bugs, features, or patches marked for v2.0.
|
||||
All items that are marked for v2.0 will be either fixed (and closed), or
|
||||
postponed by changing their Group marking to something else like "long range
|
||||
goal". Using the bug database helps to ensure that nothing important gets
|
||||
forgotten. When you're looking at the Source Forge database, you can click on
|
||||
the Group box and select just the items that are selected for v2.0. <p>
|
||||
|
||||
|
||||
As the release approaches, we make some pre-release versions with binaries so
|
||||
that it's easy for people to try out the new features and check if we've broken
|
||||
anything. These will be called 2.0.pre1, 2.0.pre2, etc. Meanwhile, we
|
||||
continue fixing things, cleaning up, and trying very hard not to add more bugs
|
||||
in the process. Eventually the developers will agree that we've done enough
|
||||
testing and we should go ahead and call it 2.0.
|
||||
<p>
|
||||
|
||||
Click to see <a href="http://bochs.sourceforge.net/cgi-bin/topper.pl?name=Report+a+Bug&url=http://sourceforge.net/tracker/qmrkgroup_ideq12580ampatideq112580">Bug Reports</a>. <br>
|
||||
Click to see <a href="http://bochs.sourceforge.net/cgi-bin/topper.pl?name=Request+a+Feature&url=http://sourceforge.net/tracker/qmrkatideq362580ampgroup_ideq12580ampfunceqbrowse">Feature Requests</a>. <br>
|
||||
Click to see <a href="http://bochs.sourceforge.net/cgi-bin/topper.pl?name=Patches&url=http://sourceforge.net/tracker/qmrkatideq312580ampgroup_ideq12580ampfunceqbrowse">Patches</a>. <br>
|
||||
|
||||
<hr>
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Try out
|
||||
a Pre-Release </b></font><BR>
|
||||
|
||||
<table border=1>
|
||||
<th>Date</th>
|
||||
<th>Version</th>
|
||||
<th>Description</th>
|
||||
<th>Download</th>
|
||||
|
||||
<tr>
|
||||
<td rowspan=6>2002-12-15</td>
|
||||
<td rowspan=6>Bochs 2.0.pre4</td>
|
||||
<td>Bochs source code</td>
|
||||
<td><a href="http://osdn.dl.sourceforge.net/sourceforge/bochs/bochs-2.0.pre4.tar.gz">2.8meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Source RPM for Linux (all architectures)</td>
|
||||
<td><a href="http://osdn.dl.sourceforge.net/sourceforge/bochs/bochs-2.0.pre4.src.rpm">2.8meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Binary RPM for x86 Linux. This RPM was built on a Redhat 7.3 system. It
|
||||
was compiled with plugins, CDROM, SB emulation, NE2000, VBE,
|
||||
all speed optimizations, PCI, MMX, SSE, and SSE2. The default display
|
||||
library is X11, but you can also select between SDL, term, RFB, wxWindows,
|
||||
svgalib, or no gui using the display_library option in bochsrc.
|
||||
</td>
|
||||
<td><a href="http://osdn.dl.sourceforge.net/sourceforge/bochs/bochs-2.0.pre4.i386.rpm">3.2meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>ZIP file with Win32 binaries. The binaries were compiled with support for
|
||||
CDROM, SB emulation, NE2000, VBE, and all speed optimizations. There are
|
||||
two Bochs executables: bochs.exe without the debugger, and bochsdbg.exe
|
||||
which is compiled with the Bochs debugger.
|
||||
</td>
|
||||
<td><a href="http://osdn.dl.sourceforge.net/sourceforge/bochs/bochs-2.0.pre4.win32-bin.zip">2.6meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>.EXE installer package for Win32 with all the same same binaries as the ZIP.
|
||||
The NSIS installer is very new, so please test out every little feature to see
|
||||
if anything needs to be improved. The installer work was completed by Michael
|
||||
Rich.
|
||||
</td>
|
||||
<td><a href="http://osdn.dl.sourceforge.net/sourceforge/bochs/Bochs-2.0.pre4.exe">2.6meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>ZIP file with Bochs source code configured for MS VC++ 6.0 (win32).
|
||||
Download this file if you want to rebuild Bochs in VC++ yourself, perhaps
|
||||
with different options. You can unzip this file, load up the MS VC++ workspace
|
||||
"bochs.dsw" and just click on Build.
|
||||
</td>
|
||||
<td><a href="http://osdn.dl.sourceforge.net/sourceforge/bochs/bochs-2.0.pre4.win32-src.zip">2.3meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td rowspan=6>2002-12-05</td>
|
||||
<td rowspan=6>Bochs 2.0.pre3</td>
|
||||
<td>Bochs source code</td>
|
||||
<td><a href="http://osdn.dl.sourceforge.net/sourceforge/bochs/bochs-2.0.pre3.tar.gz">2.0meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Source RPM for Linux (all architectures)</td>
|
||||
<td><a href="http://osdn.dl.sourceforge.net/sourceforge/bochs/bochs-2.0.pre3.src.rpm">1.9meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Binary RPM for x86 Linux. This RPM was built on a Redhat 7.3 system. It
|
||||
was compiled with plugins, CDROM, SB emulation, NE2000, VBE,
|
||||
all speed optimizations, PCI, MMX, SSE, and SSE2. The default display
|
||||
library is X11, but you can also select between SDL, term, RFB, wxWindows,
|
||||
svgalib, or no gui using the display_library option in bochsrc.
|
||||
</td>
|
||||
<td><a href="http://osdn.dl.sourceforge.net/sourceforge/bochs/bochs-2.0.pre3.i386.rpm">3.1meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>ZIP file with Win32 binaries. The binaries were compiled with support for
|
||||
CDROM, SB emulation, NE2000, VBE, and all speed optimizations. There are
|
||||
two Bochs executables: bochs.exe without the debugger, and bochsdbg.exe
|
||||
which is compiled with the Bochs debugger.
|
||||
</td>
|
||||
<td><a href="http://osdn.dl.sourceforge.net/sourceforge/bochs/bochs-2.0.pre3.win32-bin.zip">2.3meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>.EXE installer package for Win32 with all the same same binaries as the ZIP.
|
||||
The NSIS installer is very new, so please test out every little feature to see
|
||||
if anything needs to be improved. The installer work was completed by Michael
|
||||
Rich.
|
||||
</td>
|
||||
<td><a href="http://osdn.dl.sourceforge.net/sourceforge/bochs/Bochs-2.0.pre3.exe">2.4meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>ZIP file with Bochs source code configured for MS VC++ 6.0 (win32).
|
||||
Download this file if you want to rebuild Bochs in VC++ yourself, perhaps
|
||||
with different options. You can unzip this file, load up the MS VC++ workspace
|
||||
"bochs.dsw" and just click on Build.
|
||||
</td>
|
||||
<td><a href="http://osdn.dl.sourceforge.net/sourceforge/bochs/bochs-2.0.pre3.win32-src.zip">2.3meg</a></td>
|
||||
</tr>
|
||||
|
||||
|
||||
<tr>
|
||||
<td rowspan=7>2002-11-19</td>
|
||||
<td rowspan=7>Bochs 2.0.pre2</td>
|
||||
<td>Bochs source code</td>
|
||||
<td><a href="http://osdn.dl.sourceforge.net/sourceforge/bochs/bochs-2.0.pre2.tar.gz">1.9meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Source RPM for Linux (all architectures)</td>
|
||||
<td><a
|
||||
href="http://osdn.dl.sourceforge.net/sourceforge/bochs/bochs-2.0.pre2.src.rpm">1.9meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Binary RPM for x86 Linux. This RPM was built on a Redhat 8.0 system. It
|
||||
was compiled with plugins, CDROM, SB emulation, NE2000, VBE,
|
||||
all speed optimizations, PCI, MMX, SSE, and SSE2. The default display
|
||||
library is X11, but you can also select between SDL, term, RFB, wxWindows, or no
|
||||
gui using the display_library option in bochsrc.
|
||||
</td>
|
||||
<td><a href="http://osdn.dl.sourceforge.net/sourceforge/bochs/bochs-2.0.pre2.i386.rpm">2.1meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Binary RPM for x86 Linux, compiled for Redhat 7.3.
|
||||
</td>
|
||||
<td><a href="http://bochs.sf.net/tmp/bochs-2.0.pre2.redhat73.i386.rpm">2.1meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>ZIP file with Win32 binaries. The binaries were compiled with support for
|
||||
CDROM, SB emulation, NE2000, VBE, and all speed optimizations.
|
||||
</td>
|
||||
<td><a href="http://osdn.dl.sourceforge.net/sourceforge/bochs/bochs-2.0.pre2.win32-bin.zip">2.3meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>.EXE installer package for Win32 with all the same same binaries as the ZIP.
|
||||
The NSIS installer is very new, so please test out every little feature to see
|
||||
if anything needs to be improved. The installer work was completed by Michael
|
||||
Rich.
|
||||
</td>
|
||||
<td><a href="http://osdn.dl.sourceforge.net/sourceforge/bochs/Bochs-2.0.pre2.exe">2.4meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>ZIP file with Bochs source code configured for MS VC++ 6.0 (win32). You can
|
||||
unzip this file, load up the MS VC++ workspace "bochs.dsw" and just click on
|
||||
Build.
|
||||
</td>
|
||||
<td><a href="http://osdn.dl.sourceforge.net/sourceforge/bochs/bochs-2.0.pre2.win32-src.zip">2.3meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td rowspan=3>2002-11-14</td>
|
||||
<td rowspan=3>Bochs 2.0.pre1</td>
|
||||
<td>Bochs source code</td>
|
||||
<td><a href="http://twtelecom.dl.sourceforge.net/sourceforge/bochs/bochs-2.0.pre1.tar.gz">1.9meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Source RPM for Linux (all architectures)</td>
|
||||
<td><a href="http://twtelecom.dl.sourceforge.net/sourceforge/bochs/bochs-2.0.pre1.src.rpm">1.8meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Binary RPM for x86 Linux. This RPM was built on a Redhat 6.2 system. It
|
||||
was compiled with support for X windows, CDROM, SB emulation, NE2000, VBE, and
|
||||
all speed optimizations.</td>
|
||||
<td><a href="http://twtelecom.dl.sourceforge.net/sourceforge/bochs/bochs-2.0.pre1.i386.rpm">1.8meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td rowspan=7>2002-09-07</td>
|
||||
<td rowspan=7>wxWindows 2.3.3</td>
|
||||
<td>
|
||||
The main wxWindows site is at <a href="http://wxwindows.org">http://wxwindows.org/</a>. Bochs works best with version 2.3.3. A few binary packages
|
||||
that have been tested with Bochs are listed below. If you find a binary that
|
||||
matches your system, try it. Otherwise, look on the wxWindows web site and see
|
||||
what you can find.
|
||||
</td>
|
||||
<td> </td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>
|
||||
Source RPM for Linux (all architectures)
|
||||
</td>
|
||||
<td><a href="http://twtelecom.dl.sourceforge.net/sourceforge/wxwindows/wxGTK-2.3.3-1.src.rpm">4.8meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>
|
||||
Binary RPM for x86 Linux, containing wxWindows dynamic libraries.
|
||||
This RPM was compiled on an x86 machine running Redhat Linux 8.0.
|
||||
</td>
|
||||
<td><a href="http://bochs.sourceforge.net/tmp/wxwindows/binaries/linux/redhat80/wxGTK-2.3.3-1.i386.rpm">2.3meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>
|
||||
Binary RPM for x86 Linux, containing wxWindows static libraries.
|
||||
This RPM was compiled on an x86 machine running Redhat Linux 8.0.
|
||||
</td>
|
||||
<td><a href="http://bochs.sourceforge.net/tmp/wxwindows/binaries/linux/redhat80/wxGTK-static-2.3.3-1.i386.rpm">2.2meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>
|
||||
Binary RPM for x86 Linux, containing header files that you need to
|
||||
compile any wxWindows application. This RPM was compiled on an x86 machine
|
||||
running Redhat Linux 8.0. 551k.
|
||||
</td>
|
||||
<td><a href="http://bochs.sourceforge.net/tmp/wxwindows/binaries/linux/redhat80/wxGTK-devel-2.3.3-1.i386.rpm">551k</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>
|
||||
ZIP file with Cygwin libraries, release version. These were compiled
|
||||
without debug support.
|
||||
</td>
|
||||
<td><a href="http://bochs.sourceforge.net/tmp/wxwindows/binaries/cygwin/wxMSW-2.3.3-cygwinlib-release.tar.gz">3.6meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>
|
||||
ZIP file with Cygwin libraries, debug version. These were compiled
|
||||
with debug support so they are useful if you are doing any kind of
|
||||
wxWindows development.
|
||||
</td>
|
||||
<td><a href="http://bochs.sourceforge.net/tmp/wxwindows/binaries/cygwin/wxMSW-2.3.3-cygwinlib-release.tar.gz">8.8meg</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>2002-10-06</td>
|
||||
<td>SDL 1.4.5</td>
|
||||
<td>
|
||||
The SDL library can be downloaded from <a
|
||||
href="http://libsdl.org">http://libsdl.org</a>. Bochs has been tested most
|
||||
with 1.2.4, but get the most recent version you can find.
|
||||
</td>
|
||||
<td> </td>
|
||||
</tr>
|
||||
|
||||
|
||||
<!-- begin template
|
||||
<tr>
|
||||
<td>2002-11-14</td>
|
||||
<td>Bochs 2.0.pre1</td>
|
||||
<td>
|
||||
Description of what the heck it is
|
||||
</td>
|
||||
<td><a href="URL">Download</a></td>
|
||||
</tr>
|
||||
end template -->
|
||||
|
||||
|
||||
</table>
|
||||
|
||||
|
||||
<!--#include virtual="includes/footer.txt" -->
|
||||
|
||||
|
||||
Last Modified on <!--#flastmod file="index.html" --> by Bryce<BR>
|
||||
|
||||
<!--#include virtual="includes/cright.txt" -->
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -1,50 +0,0 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>bochs: The Open Source IA-32 Emulation Project (Bochs in Action Screenshots)</TITLE>
|
||||
|
||||
<!--#include virtual="includes/header.txt" -->
|
||||
|
||||
<img src="images/logo.png" alt="A Window, Tux, and the BSD Daemon" width="160" height="175" align="right">
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Bochs Screenshots</b></font><BR>
|
||||
Anxious to see how Bochs looks? These screenshots let you see Bochs running a variety of typical and exotic
|
||||
operating systems.
|
||||
If you are currently using Bochs, and you have a screenshot you would like to share with us, please e-mail it to
|
||||
<a href="mailto:tbutler@uninetsolutions.com">Tim Butler</a>. Thanks!
|
||||
|
||||
<ul>
|
||||
<li><IMG SRC="screenshot/winxp-smp2-t.png" ALT="[IMG]" width="50" height="41"> <A HREF="screenshot/winxp-smp2.png">Bochs (with 2 CPUs and HT) running Windows XP</a> (700k) - From Stanislav Shwartsman (2006/02/11)
|
||||
<li><IMG SRC="screenshot/w2k-canja-t.gif" ALT="[IMG]" width="57" height="39"> <A HREF="screenshot/w2k-canja.jpg">Bochs running Windows 2000!</a> (70k) - From Viorel Canja
|
||||
<li><IMG SRC="screenshot/win104-t.gif" ALT="[IMG]" width="50" height="38" width="50" height="38"> <A HREF="screenshot/win104.gif">Windows 1.04 running inside Bochs</A>, from Scott Duplichan
|
||||
<li><IMG SRC="screenshot/SiteInWinInBochs-t.png" ALT="[IMG]" width="57" height="39"> <A HREF="screenshot/SiteInWinInBochs.png">Bochs running Internet Explorer/win95 running on a Linux Mandrake PC with TUN ethernet device</a> (233k) - From Christophe Bothamy
|
||||
<li><IMG SRC="screenshot/redhat-vnc-t.gif" ALT="[IMG]" width="50" height="38"> <A HREF="screenshot/redhat-vnc.gif">Bochs running X windows applications under Redhat 6.0. The display was exported to another machine using VNC.</a> (53k) - From Bryce Denney
|
||||
<li><img src="screenshot/ipaq-dlxlinux-t.gif" ALT="[IMG]" width="50" height="38"><a href="screenshot/ipaq-dlxlinux.png">Bochs running on an IPAQ</a>, a StrongARM based handheld computer from Compaq. This screen shot was donated by Dwayne Fontenot. More of his screenshots are <a href="http://intimate.handhelds.org/screens.shtml">here</a>.
|
||||
<li><IMG SRC="screenshot/bochs-in-bochs-t.gif" ALT="[IMG]" width="50" height="38"> <A HREF="screenshot/bochs-in-bochs.gif">Bochs running inside Bochs for Windows</a> (16k) - From ???
|
||||
<li><IMG SRC="screenshot/bochs-qnx-t.gif" ALT="[IMG]" width="50" height="38"> <A HREF="screenshot/bochs-qnx.jpg">Bochs running the QNX Demo Disk</a> (84k) - From Don Becker
|
||||
<li><IMG SRC="screenshot/WinMe-t.gif" ALT="[IMG]" width="50" height="38"> <A HREF="screenshot/WinMe.gif">Bochs running Windows ME</a> (12k) - From Roberto Sanchez
|
||||
<li><IMG SRC="screenshot/nt40-t.gif" ALT="[IMG]" width="50" height="38"> <A HREF="screenshot/nt40.gif">Bochs on Linux</A> running Windows NT 4.0. (11k) - From Kevin Lawton
|
||||
<li><IMG SRC="screenshot/qnx4-1-t.gif" ALT="[IMG]" width="50" height="38"> <A HREF="screenshot/qnx4-1.png">Bochs starting the QNX Demo Disk</a> (20k) - From Danigo Ludovic
|
||||
<li><IMG SRC="screenshot/qnx4-2-t.gif" ALT="[IMG]" width="50" height="38"> <A HREF="screenshot/qnx4-2.png">Bochs running the QNX Demo Disk</a> (12k) - From Danigo Ludovic
|
||||
<li><IMG SRC="screenshot/whistler-t.gif" ALT="[IMG]" width="50" height="38" width="50" height="38"> <A HREF="screenshot/whistler.jpg">Bochs for Windows</A> running DOS on Itanium (IA-64). (182k) - From Chris Wertman
|
||||
<li><IMG SRC="screenshot/bochs_for_windows2-t.gif" ALT="[IMG]" width="50" height="38"> <A HREF="screenshot/bochs_for_windows2.bmp">Bochs on Windows</A> running Windows 95. (1021k) - From Micha Moffie
|
||||
<li><IMG SRC="screenshot/bochs_win95_capture-t.gif" ALT="[IMG]" width="50" height="38"> <A HREF="screenshot/bochs_win95_capture.jpg">Bochs on LinuxPPC</A> running Windows 95. (122k) - From Brad Davis
|
||||
<li><IMG SRC="screenshot/bochsncs-t.gif" ALT="[IMG]" width="50" height="38" width="50" height="38"> <A HREF="screenshot/bochsncs.jpg">Bochs for Linux</A> running Norton Commander on DOS. (90k) - From Hartwig Bolle
|
||||
<li><IMG SRC="screenshot/doom-t.gif" ALT="[IMG]" width="50" height="38"> <A HREF="screenshot/doom.gif">Bochs on Linux</A> running "Doom" on DOS. (67k) - From Kevin Lawton
|
||||
<li><IMG SRC="screenshot/freedos-t.gif" ALT="[IMG]" width="50" height="38"> <A HREF="screenshot/freedos.png">Bochs on Linux</A> running FreeDOS. (18k) - From CY
|
||||
<li><IMG SRC="screenshot/kidos-t.gif" ALT="[IMG]" width="50" height="38"> <A HREF="screenshot/kidos.jpg">Bochs on Linux</A> running KidOS. (15k) - From David Decotigny
|
||||
<li><IMG SRC="screenshot/rfb1-t.gif" ALT="[IMG]" width="50" height="38"> <A HREF="screenshot/rfb1.jpg">Bochs-RFB (VNC) for Windows</A> displaying an MS-DOS session. (58k) - From Donald Becker
|
||||
<li><IMG SRC="screenshot/smp-t.gif" ALT="[IMG]" width="50" height="38" width="50" height="38"> <A HREF="screenshot/smp.gif">SMP-Bochs for Linux</A> display Linux SMP. (14k) - From Bryce Denney
|
||||
<li><IMG SRC="screenshot/os2runs-t.gif" ALT="[IMG]" width="50" height="38" width="50" height="38"> <A HREF="screenshot/os2runs.gif">OS/2 running inside Bochs</A>, from Diego Henriquez.
|
||||
</ul>
|
||||
|
||||
<a href="http://sourceforge.net/project/screenshots.php?group_id=12580">More screenshots...</a>
|
||||
<BR><BR>
|
||||
|
||||
<!--#include virtual="includes/footer.txt" -->
|
||||
|
||||
|
||||
Last Modified on <!--#flastmod file="screenshots.html" -->.<BR>
|
||||
|
||||
<!--#include virtual="includes/cright.txt" -->
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -1,16 +0,0 @@
|
|||
<HTML>
|
||||
<BODY BGCOLOR="#FFFFFF">
|
||||
<table border="0" cellspacing="0" cellpadding="0"><tr>
|
||||
<td bgcolor="#aacbff"><font face="arial, helvetica" bgcolor="#000000">Bochs Site and Bug Search</font></td>
|
||||
<td bgcolor="#FFFFFF" width="1"><font face="arial, helvetica" bgcolor="#000000"> </font></td>
|
||||
<td bgcolor="#AAAAAA"><font face="arial, helvetica" bgcolor="#000000">Bochs Developers Mailing List Search</font></td>
|
||||
<td bgcolor="#FFFFFF" width="1"><font face="arial, helvetica" bgcolor="#000000"> </font></td>
|
||||
<td bgcolor="#AAAAAA"><font face="arial, helvetica" bgcolor="#000000">Bochs LXR Search</font></td>
|
||||
</tr>
|
||||
<tr><td colspan="5" bgcolor="#aacbff">
|
||||
|
||||
RESULTS GO HERE.
|
||||
|
||||
</td></tr></table>
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -1,69 +0,0 @@
|
|||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>bochs: The Open Source IA-32 Emulation Project (Tech Specs)</TITLE>
|
||||
|
||||
<!--#include virtual="includes/header.txt" -->
|
||||
|
||||
<img src="images/logo.png" alt="A Window, Tux, and the BSD Daemon" width="160" height="175" align="right">
|
||||
<BR><font face="arial, helvetica" color="#1e029a" size="4"><b>Technical Documents Related to Bochs</b></font><BR>
|
||||
|
||||
Because Bochs emulates much of the standard PC hardware, developers must have access to good
|
||||
documentation for the hardware that they wish to emulate. To fill this need, here is a collection
|
||||
of technical specs that are relevant to PC emulation. All documents are collected from public web
|
||||
sites, so links to the original source are provided when possible. In some cases, a copy has been
|
||||
placed on the Bochs web site in addition to the link to the original source. This was done to
|
||||
avoid the common problem of documents moving or disappearing from the web. If you know of any
|
||||
copyright problems with our mirroring of this information, please let us know and we will
|
||||
replace the document with a link or remove it. If you have technical specs that might be useful
|
||||
to Bochs developers, please email <a href="mailto:tbutler@uninetsolutions.com">Tim Butler</a>.
|
||||
|
||||
|
||||
<ul>
|
||||
<B>Local Resources</B><BR><BR>
|
||||
<li><IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="techspec/8042.TXT">8042.TXT</A>
|
||||
<li><IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="techspec/CMOS-reference.txt">CMOS-reference.txt</A>
|
||||
<li><IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="techspec/DMA_RTI.TXT">DMA_RTI.TXT</A>
|
||||
<li><IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="techspec/IDE-reference.txt">IDE-reference.txt</A>
|
||||
<li><IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="techspec/PORTS.LST">XT, AT, and
|
||||
PS/2 I/O port addresses</A>
|
||||
<li><IMG SRC="/icons/compressed.gif" ALT="[TAR.GZ]"> <A HREF="techspec/intel-82093-apic.pdf.gz">Intel 82093AA I/O APIC Datasheet</A>
|
||||
<li><IMG SRC="/icons/compressed.gif" ALT="[TAR.GZ]"> <A HREF="techspec/intel-8259a-pic.pdf.gz">Intel 8259A PIC Datasheet</A>
|
||||
<li><IMG SRC="/icons/compressed.gif" ALT="[TAR.GZ]"> <A HREF="techspec/intel-82c54-timer.pdf.gz">Intel 82C54 Programmable Interval Timer Datasheet</A>
|
||||
<li><IMG SRC="/icons/compressed.gif" ALT="[TAR.GZ]"> <A
|
||||
HREF="techspec/intel-ia32-sdg1.pdf.gz">IA-32 Intel Architecture Software Developer's Manual 1: Basic Architecture</A>
|
||||
<li><IMG SRC="/icons/compressed.gif" ALT="[TAR.GZ]"> <A
|
||||
HREF="techspec/intel-ia32-sdg2.pdf.gz">IA-32 Intel Architecture Software
|
||||
Developer's Manual 2: Instruction Set Reference</A>
|
||||
<li><IMG SRC="/icons/compressed.gif" ALT="[TAR.GZ]"> <A
|
||||
HREF="techspec/intel-ia32-sdg3.pdf.gz">IA-32 Intel Architecture Software
|
||||
Developer's Manual 3: System Programming Guide</A>
|
||||
<li><IMG SRC="/icons/compressed.gif" ALT="[TAR.GZ]"> <A HREF="techspec/intel-mp-spec.pdf.gz">Intel Multiprocessor Specification</A>
|
||||
<li><IMG SRC="/icons/compressed.gif" ALT="[TAR.GZ]"> <A HREF="techspec/el-torito.pdf.gz">Spec for El Torito, which describes how to boot the PC from a CDROM.</A>
|
||||
<li><IMG SRC="/icons/compressed.gif" ALT="[TAR.GZ]"> <A HREF="techspec/DP8390D.pdf.gz">Datasheet for DP8390/NS32490D Network Interface Controller, used in the NE2000</A>
|
||||
<li><IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="techspec/adlib_sb.txt">Programming the AdLib/Sound Blaster FM Music Chips (Ver 2.0) by Jeffrey S. Lee</A>
|
||||
|
||||
|
||||
|
||||
<BR><BR><B>Remote Resources</b><BR><BR>
|
||||
<li><IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="http://ata-atapi.com/">ATA-Atapi Information by Hale Landis</A>
|
||||
<li><IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="http://www.t13.org/">Technical Committee T13</a> of the National Committee on Information Technology Standards (NCITS) is responsible for the interface standards for ATA/ATAPI. Several version of the ATA/ATAPI specs are on their site under Documents.
|
||||
<li><IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="http://www.cs.cmu.edu/~ralf/files.html">Ralf Brown's famous interrupt list</A>
|
||||
<li><IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="http://www.cs.cmu.edu/~ralf/undoc.html">Ralf Brown's undocumented stuff</A>
|
||||
<li><IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="http://kos.enix.org/docs.php">ENIX hardware documentation (descriptions are in French, but docs are in English)</A>
|
||||
<li><IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="http://x86.ddj.com/">Dr. Dobb's Microprocessor Resources</A>
|
||||
<li><IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="http://rpm.org">RPM reference and new versions</A>
|
||||
<li><IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="http://www.ecma.ch/">ECMA is an standards organization for info and communication systems</A>
|
||||
<li><IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="http://www.parashift.com/c++-faq-lite/index.html">C++ FAQ Lite by Marshall Cline</a>, a very good C++ Frequently Asked Questions list
|
||||
<li><IMG SRC="/icons/text.gif" ALT="[TXT]"> <a href="http://www.scs.stanford.edu/nyu/04fa/lab/specsbbs101.pdf">BIOS Boot Specification
|
||||
<li><IMG SRC="/icons/text.gif" ALT="[TXT]"> <a href="http://www.osdever.net/documents/PNPBIOSSpecification-v1.0a.pdf">PNPBIOS Specification v1.0a
|
||||
</ul>
|
||||
|
||||
<!--#include virtual="includes/footer.txt" -->
|
||||
|
||||
|
||||
Last Modified on <!--#flastmod file="techdata.html" -->.<BR>
|
||||
|
||||
<!--#include virtual="includes/cright.txt" -->
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
|
@ -1,36 +0,0 @@
|
|||
plat-table.html:971118a:Solaris sparc gcc:Win95:green:
|
||||
form-00003.txt:1.1.1:Linux x86:FreeDOS:yellow:
|
||||
form-00006.txt:1.1.1:Win32 VC++:Win98:green:
|
||||
form-00007.txt:1.1.1:Linux x86:Linux console:green:
|
||||
form-00008.txt:1.1.1:Linux x86:NetBSD:red:
|
||||
form-00009.txt:1.1.1:Linux x86:OpenBSD:red:
|
||||
form-00010.txt:1.1.1:Linux x86:PicoBSD:green:
|
||||
form-00011.txt:1.1.1:Linux x86:PragmaLinux:green:
|
||||
form-00007-sol.txt:1.1.1:Solaris sparc gcc:Linux console:green:
|
||||
form-00008-sol.txt:1.1.1:Solaris sparc gcc:NetBSD:red:
|
||||
form-00009-sol.txt:1.1.1:Solaris sparc gcc:OpenBSD:red:
|
||||
form-00010-sol.txt:1.1.1:Solaris sparc gcc:PicoBSD:green:
|
||||
form-00011-sol.txt:1.1.1:Solaris sparc gcc:PragmaLinux:green:
|
||||
plat-table.html:990108:BeOS x86:Win95:green
|
||||
plat-table.html:971118:BeOS PPC:Win95:green
|
||||
plat-table.html:971118:Linux x86:Win95:green
|
||||
plat-table.html:971118:FreeBSD:DOS:green
|
||||
plat-table.html:980629:Win32 VC++:DOS:green
|
||||
plat-table.html:981222:Mac:Win95:green
|
||||
plat-table.html:990110:Alpha Tru64 Unix:Win95:green
|
||||
plat-table.html:991114:AIX:FreeDOS:green
|
||||
form-00012.txt:1.1.1:Win32 VC++:Win95:green
|
||||
form-00013.txt:1.1.1:Linux PPC:DOS:green
|
||||
form-00014.txt:1.1.1:Linux PPC:Win95:green
|
||||
form-00015.txt:1.1.1:Linux x86:Win95:yellow
|
||||
form-00016.txt:cvs 27-Apr-01:Alpha Tru64 Unix:Linux console:green
|
||||
form-00017.txt:cvs 09-May-01:Linux x86:OpenBSD:yellow
|
||||
form-00018.txt:cvs 16-May-01:Linux x86:Win3.1:yellow
|
||||
form-00019.txt:cvs 26-May-01:Linux x86:Win95:green
|
||||
form-00020.txt:1.2.pre1:MacOS X:Linux console:green
|
||||
form-00021.txt:1.2.pre1:Win32 VC++:Linux console:green
|
||||
form-00022.txt:1.2.pre1:Solaris sparc gcc:DOS:green
|
||||
form-00023.txt:1.2:IRIX:Linux console:green
|
||||
form-00024.txt:1.2:Win32 VC++:Linux console:green
|
||||
form-00025.txt:cvs 02-Jun-01:Linux x86:Linux console:green
|
||||
form-00026.txt:1.2.1:Win32 VC++:QNX:green
|
||||
|
|
@ -1,129 +0,0 @@
|
|||
-------------------------------------------------------------
|
||||
BOCHS TESTING FORM Version 0.4
|
||||
-------------------------------------------------------------
|
||||
|
||||
Because of the variety of platforms and configurations that Bochs
|
||||
supports, it is difficult for any one person to test it thoroughly.
|
||||
This form is intended to help the Bochs developers keep track of test
|
||||
results from different sources. To avoid confusion, this form should
|
||||
be submitted once for each combination of host OS and guest OS you
|
||||
try. For example: your host OS is Debian Linux and you get both Win95
|
||||
and FreeDOS to start up. You would send one form for
|
||||
Win95-under-Debian and a second form for FreeDOS-under-Debian. In
|
||||
this case it would save time to fill in the host OS part, copy it a
|
||||
few times and fill out the guest OS part for each copy.
|
||||
|
||||
To fill in a blank such as [__], replace the underlines and leave
|
||||
the brackets. Example: [Sun Ultrasparc 10]. To fill in a
|
||||
multiple-choice, just put an X in the brackets. Example: [X]
|
||||
Mail completed forms to bochs-developers@lists.sourceforge.net
|
||||
|
||||
|
||||
What is the date?
|
||||
[__]
|
||||
|
||||
What is your name?
|
||||
[__]
|
||||
|
||||
What is your email address?
|
||||
[__]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[ ] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 2400 MHz Intel Pentium 4.
|
||||
[__]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[__]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] compiled from version 2.3.7
|
||||
[ ] compiled from version [_____]
|
||||
[ ] I compiled it from the CVS sources from date: [__]
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[ ] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[__]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[__]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[ ] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[__]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[ ] floppy image
|
||||
[ ] raw floppy drive
|
||||
[ ] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[ ] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[__]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
x86-64 [X] [ ] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
SMP [X] [ ] [ ] [__]
|
||||
keyboard [X] [ ] [ ] [__]
|
||||
floppy disk [X] [ ] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [X] [ ] [ ] [__]
|
||||
mouse [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
save/restore [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
Cirrus Logic SVGA [X] [ ] [ ] [__]
|
||||
USB [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-developers@lists.sourceforge.net
|
||||
|
|
@ -1,26 +0,0 @@
|
|||
What is your name?
|
||||
[Danilo Paliani]
|
||||
|
||||
What is your email address?
|
||||
[lab.village1@saritel.it]
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[x86]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Solaris 7]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[ ] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[X] other source distribution from URL: [990708a]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[win95]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
|
@ -1,106 +0,0 @@
|
|||
What is your name?
|
||||
[Bryce Denney]
|
||||
|
||||
What is your email address?
|
||||
[bryce dot denney at bigfoot dot com]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[400MHz AMD K6]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Redhat Linux 6.2 with 2.2.14]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[X] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[.conf.x86]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[egcs-2.91.66]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[freedos beta 4]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[ ] floppy image
|
||||
[ ] raw floppy drive
|
||||
[X] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[installation, fdisk, format, dir]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[
|
||||
1. edit hangs forever- the clock in lower right updates, but no keystrokes are
|
||||
recognized
|
||||
2. after running a few commands, sometimes dir appears empty from then on
|
||||
3. emacs starts up once, then tells you to exit and start again. The second
|
||||
time it appears to hang forever on "Saving F's in C:\EMACS\emacs ..."
|
||||
4. compinfo crashes bochs with panic,
|
||||
pit: outp(43h): comm Bh, mode 04, bcd 00 unhandled
|
||||
]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [X] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [X] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,98 +0,0 @@
|
|||
What is your name?
|
||||
[Bryce Denney]
|
||||
|
||||
What is your email address?
|
||||
[bryce dot denney at bigfoot dot com]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[AMD 400MHz]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Redhat Linux 6.2, kernel 2.2.14]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[X] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[.conf.x86]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[egcs-2.91.66]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[Redhat Linux 6.2]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[X] floppy image
|
||||
[ ] raw floppy drive
|
||||
[ ] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[UNIX command line utils]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [X] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [X] [ ] [__]
|
||||
floating point [ ] [X] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [ ] [X] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,30 +0,0 @@
|
|||
What is your name?
|
||||
[Kevin Lawton]
|
||||
|
||||
What is your email address?
|
||||
[kevin@bochs.com]
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[BeBox PPC]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[BeOS PR2]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[ ] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[X] other source distribution from URL: [971118a]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[CodeWarrior]
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[win95]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
|
|
@ -1,100 +0,0 @@
|
|||
Submitted 4/27/2001.
|
||||
|
||||
What is your name?
|
||||
[Chris Holland]
|
||||
|
||||
What is your email address?
|
||||
[cholland@wickwack.com]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[550MHx Intel Pentium 3]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Windows 98 second edition (4.10.2222 A)]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[X] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[ ] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[X] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[__]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8804 for 80x86]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[Windows 98 (Version 4.10.2222) boot disk]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[X] floppy image
|
||||
[ ] raw floppy drive
|
||||
[ ] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[__]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [X] [ ] [X] I used a floppy disk image created by a utility.
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [X] [ ] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,98 +0,0 @@
|
|||
What is your name?
|
||||
[Bryce Denney]
|
||||
|
||||
What is your email address?
|
||||
[bryce dot denney at bigfoot dot com]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[400MHz AMD K6]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Redhat Linux 6.2 with 2.2.14]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[X] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[.conf.x86]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[egcs-2.91.66]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[linux test image from bochs.sourceforge.net]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[ ] floppy image
|
||||
[ ] raw floppy drive
|
||||
[X] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[unix command line utils]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [X] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [X] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,98 +0,0 @@
|
|||
What is your name?
|
||||
[Bryce Denney]
|
||||
|
||||
What is your email address?
|
||||
[bryce dot denney at bigfoot dot com]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[400MHz AMD K6]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Redhat Linux 6.2 with 2.2.14]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[X] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[.conf.x86]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[egcs-2.91.66]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[linux test image from bochs.sourceforge.net]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[ ] floppy image
|
||||
[ ] raw floppy drive
|
||||
[X] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[unix command line utils]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [X] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [X] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
What is your name?
|
||||
[Bryce Denney]
|
||||
|
||||
What is your email address?
|
||||
[bryce dot denney at bigfoot dot com]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[400MHz AMD K6]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Redhat Linux 6.2 with 2.2.14]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[X] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[.conf.x86]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[egcs-2.91.66]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[netbsd test image from bochs.sourceforge.net]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[X] floppy image
|
||||
[ ] raw floppy drive
|
||||
[ ] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[ ] Yes
|
||||
[X] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[hard disk panic during boot.
|
||||
|
||||
200470320 pic:slave: OCW3 not implemented (68)
|
||||
200772055 KBD: LED status set to 00
|
||||
203100071 DMA(ignored): write: 00d6h = 00c0h
|
||||
203100090 DMA(ignored): write: 00d4h = 0000h
|
||||
277515049 hard drive: RESET
|
||||
277533056 disk: Reset complete {DISK}
|
||||
bochs: panic, disk: IO read(0x1f2): current command not
|
||||
read/write ]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[__]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [X] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [ ] [X] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
What is your name?
|
||||
[Bryce Denney]
|
||||
|
||||
What is your email address?
|
||||
[bryce dot denney at bigfoot dot com]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[400MHz AMD K6]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Redhat Linux 6.2 with 2.2.14]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[X] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[.conf.x86]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[egcs-2.91.66]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[netbsd test image from bochs.sourceforge.net]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[X] floppy image
|
||||
[ ] raw floppy drive
|
||||
[ ] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[ ] Yes
|
||||
[X] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[hard disk panic during boot.
|
||||
|
||||
200470320 pic:slave: OCW3 not implemented (68)
|
||||
200772055 KBD: LED status set to 00
|
||||
203100071 DMA(ignored): write: 00d6h = 00c0h
|
||||
203100090 DMA(ignored): write: 00d4h = 0000h
|
||||
277515049 hard drive: RESET
|
||||
277533056 disk: Reset complete {DISK}
|
||||
bochs: panic, disk: IO read(0x1f2): current command not
|
||||
read/write ]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[__]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [X] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [ ] [X] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,102 +0,0 @@
|
|||
What is your name?
|
||||
[Bryce Denney]
|
||||
|
||||
What is your email address?
|
||||
[bryce dot denney at bigfoot dot com]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[400MHz AMD K6]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Redhat Linux 6.2 with 2.2.14]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[X] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[.conf.x86]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[egcs-2.91.66]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[OpenBSD test image from bochs.sourceforge.net]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[X] floppy image
|
||||
[ ] raw floppy drive
|
||||
[ ] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[ ] Yes
|
||||
[X] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[
|
||||
337125081 hard drive: RESET
|
||||
337126557 disk: Reset complete {DISK}
|
||||
bochs: panic, disk: IO read(0x1f2): current command not read/write
|
||||
]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[__]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [X] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [ ] [X] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,102 +0,0 @@
|
|||
What is your name?
|
||||
[Bryce Denney]
|
||||
|
||||
What is your email address?
|
||||
[bryce dot denney at bigfoot dot com]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[400MHz AMD K6]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Redhat Linux 6.2 with 2.2.14]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[X] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[.conf.x86]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[egcs-2.91.66]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[OpenBSD test image from bochs.sourceforge.net]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[X] floppy image
|
||||
[ ] raw floppy drive
|
||||
[ ] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[ ] Yes
|
||||
[X] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[
|
||||
337125081 hard drive: RESET
|
||||
337126557 disk: Reset complete {DISK}
|
||||
bochs: panic, disk: IO read(0x1f2): current command not read/write
|
||||
]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[__]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [X] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [ ] [X] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,98 +0,0 @@
|
|||
What is your name?
|
||||
[Bryce Denney]
|
||||
|
||||
What is your email address?
|
||||
[bryce dot denney at bigfoot dot com]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[400MHz AMD K6]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Redhat Linux 6.2 with 2.2.14]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[X] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[.conf.x86]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[egcs-2.91.66]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[PicoBSD test image from bochs.sourceforge.net]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[X] floppy image
|
||||
[ ] raw floppy drive
|
||||
[ ] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[unix command line utils]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [X] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [X] [ ] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,98 +0,0 @@
|
|||
What is your name?
|
||||
[Bryce Denney]
|
||||
|
||||
What is your email address?
|
||||
[bryce dot denney at bigfoot dot com]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[400MHz AMD K6]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Redhat Linux 6.2 with 2.2.14]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[X] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[.conf.x86]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[egcs-2.91.66]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[PicoBSD test image from bochs.sourceforge.net]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[X] floppy image
|
||||
[ ] raw floppy drive
|
||||
[ ] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[unix command line utils]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [X] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [X] [ ] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,98 +0,0 @@
|
|||
What is your name?
|
||||
[Bryce Denney]
|
||||
|
||||
What is your email address?
|
||||
[bryce dot denney at bigfoot dot com]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[400MHz AMD K6]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Redhat Linux 6.2 with 2.2.14]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[X] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[.conf.x86]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[egcs-2.91.66]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[pragmalinux test image from bochs.sourceforge.net]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[X] floppy image
|
||||
[ ] raw floppy drive
|
||||
[ ] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[unix command line utils]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [X] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [X] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,98 +0,0 @@
|
|||
What is your name?
|
||||
[Bryce Denney]
|
||||
|
||||
What is your email address?
|
||||
[bryce dot denney at bigfoot dot com]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[400MHz AMD K6]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Redhat Linux 6.2 with 2.2.14]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[X] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[.conf.x86]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[egcs-2.91.66]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[pragmalinux test image from bochs.sourceforge.net]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[X] floppy image
|
||||
[ ] raw floppy drive
|
||||
[ ] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[unix command line utils]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [X] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [X] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,93 +0,0 @@
|
|||
What is the date?
|
||||
[4/29/2001]
|
||||
|
||||
What is your name?
|
||||
[Don Becker]
|
||||
|
||||
What is your email address?
|
||||
[x-odus@iname.com]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Windows 2000]
|
||||
|
||||
What version of bochs are you using?
|
||||
[X] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[ ] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[X] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[__]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[Microsoft VC++]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[Win95]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[ ] floppy image
|
||||
[ ] raw floppy drive
|
||||
[X] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[__]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [X] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [X] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
cdrom [ ] [ ] [X] [not detected]
|
||||
sb16 [ ] [ ] [X] [didn't work]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [ ] [X] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,101 +0,0 @@
|
|||
What is the date?
|
||||
[Apr 30, 2001]
|
||||
|
||||
What is your name?
|
||||
[Brad Davis]
|
||||
|
||||
What is your email address?
|
||||
[davis@enel.ucalgary.ca]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[G4 PPC]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Yellow Dog LinuxPPC Champion Server 1.2 with 2.2.17pre20-ben3 kernel]
|
||||
|
||||
What version of bochs are you using?
|
||||
[X] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[none]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[gcc 2.95.2]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[MS-DOS 6.20]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[X] floppy image
|
||||
[ ] raw floppy drive
|
||||
[X] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[edit, qbasic, msd]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[scandisk: locked up when asking if to perform surface scan]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [X] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [X] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,101 +0,0 @@
|
|||
What is the date?
|
||||
[May 01, 2001]
|
||||
|
||||
What is your name?
|
||||
[Brad Davis]
|
||||
|
||||
What is your email address?
|
||||
[davis@enel.ucalgary.ca]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[G4 PPC]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Yellowdog LinuxPPC Champion Server 1.2 with 2.2.17pre20-ben3 kernel]
|
||||
|
||||
What version of bochs are you using?
|
||||
[X] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[__]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[gcc 2.95.2]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[Win 95]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[X] floppy image
|
||||
[ ] raw floppy drive
|
||||
[X] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[Included Win Programs]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [X] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [X] [ ] [__]
|
||||
floating point [ ] [X] [ ] [__]
|
||||
cdrom [ ] [ ] [X] [But computer has DVD drive]
|
||||
sb16 [ ] [X] [ ] [__]
|
||||
ne2000 [ ] [ ] [X] [Windows cant load driver]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,103 +0,0 @@
|
|||
What is your name?
|
||||
[Bryce Denney]
|
||||
|
||||
What is your email address?
|
||||
[bryce dot denney at bigfoot dot com]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[400MHz AMD K6]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Redhat Linux 6.2 with 2.2.14]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[X] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[.conf.x86]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[egcs-2.91.66]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[Win95 bootable hard disk image]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[ ] floppy image
|
||||
[ ] raw floppy drive
|
||||
[X] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[Booted in safe mode only, in 800x600 VGA with decent colors.
|
||||
Start menu and desktop properties seem to work ok.
|
||||
]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[
|
||||
Mouse motion too slow to be usable. See bug #420671 on sourceforge,
|
||||
http://sourceforge.net/tracker/index.php?func=detail&aid=420671&group_id=12580&atid=112580
|
||||
]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [X] [ ] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [X] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,104 +0,0 @@
|
|||
What is your name?
|
||||
[Kenneth Block]
|
||||
|
||||
What is your email address?
|
||||
[Kenneth.block@compaq.com]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[x] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[Compaq/Digital Alpha Station 600]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Compaq Tru64 UNIX V5.1 (Rev. 732); Mon Dec 4 17:27:20 EST 2000]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[ ] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[x] other source distribution from URL: [cvs checkout on 4/27/01]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[x] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[--enable-fpu]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
|
||||
[Compaq C V6.3-025 on Compaq Tru64 UNIX V5.1 (Rev. 732)]
|
||||
[Compiler Driver V6.3-026 (sys) cc Driver]
|
||||
|
||||
[Compaq C++ V6.3-002 for Compaq Tru64 UNIX V5.1 (Rev. 732)]
|
||||
[Compiler Driver V6.3-002 (cxx) cxx Driver]
|
||||
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[x] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[Tiny Linux image provided]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[ ] floppy image
|
||||
[ ] raw floppy drive
|
||||
[x] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[x] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[ls, cat, etc.]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [X] [ ] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [X] [ ] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,100 +0,0 @@
|
|||
What is your name?
|
||||
[Bryce Denney]
|
||||
|
||||
What is your email address?
|
||||
[bryce dot denney at bigfoot dot com]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[400MHz AMD K6]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Redhat Linux 6.2 with 2.2.14]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[ ] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[X] other source distribution from URL: [CVS checkout 5/9/2001]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[.conf.x86]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[egcs-2.91.66]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[126Meg OpenBSD disk image from Todd Fries]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[ ] floppy image
|
||||
[ ] raw floppy drive
|
||||
[X] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[command line utils]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[Keyboard repeat rate is a real problem. If you are not very careful
|
||||
to peck the key and release it instantly, you will get 2 or more of each
|
||||
letter. ]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [X] [ ] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [X] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,36 +0,0 @@
|
|||
Date: 5/16/2001
|
||||
Tester: Chris Schmidt
|
||||
|
||||
Version of Bochs: bochs-20010515 CVS snapshot
|
||||
Computer/Hardware/OS Used:
|
||||
AMD K-7 Athlon 650mhz, 384mb RAM. Slackware Linux 2.2.19
|
||||
OS Installed on Bochs: DOS 6.22 w/ Windows 3.1
|
||||
|
||||
Settings in .bochsrc:
|
||||
megs: 128
|
||||
boot: c
|
||||
diskc: file=win31.img, cyl=900, heads=15, spt=17 (112MB Image)
|
||||
keyboard_serial_delay: 200
|
||||
floppy_command_delay: 500
|
||||
ips: 1500000
|
||||
vga_update_interval: 300000
|
||||
|
||||
Bochs compiling information: No problems
|
||||
|
||||
Installation Information:
|
||||
Giving bochs 128megs of RAM at it's disposal DOS 6.22 started up from boot
|
||||
disk and installed just fine, like any normal installation. When I went to
|
||||
install Windows 3.1 it copied all the files from the first and second disk,
|
||||
then said it was going into windows mode, and bochs died. The second time I
|
||||
tried it, it worked fine and Windows installed as normal.
|
||||
|
||||
Type of mouse: PS/2
|
||||
|
||||
Problems:
|
||||
The mouse is VERY jerky and tends to go to the top or bottom of the screen
|
||||
as you try to move it around. It's almost impossible to use the mouse.
|
||||
|
||||
Usage details:
|
||||
Did not get much use out of it due to the mouse trouble and slowness of the
|
||||
OS itself.
|
||||
|
||||
|
|
@ -1,105 +0,0 @@
|
|||
What is the date?
|
||||
[26.05.2001]
|
||||
|
||||
What is your name?
|
||||
[Volker Ruppert]
|
||||
|
||||
What is your email address?
|
||||
[PRIVATE]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[ ] Ok, put it on a web page
|
||||
[X] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[AMD K6-2 500MHz]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[SuSE Linux 7.1 with 2.2.18 kernel]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] compiled from version 1.0 (3/25/2000 snapshot)
|
||||
[ ] compiled from version 1.1 (bugfix1)
|
||||
[ ] compiled from version 1.1.1 (bugfix2)
|
||||
[ ] compiled from version 1.1.2 (bugfix3)
|
||||
[ ] compiled from version 1.2-pre1
|
||||
[X] I compiled it from the CVS sources from date: [26.05.2001]
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[./configure --enable-cdrom]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[gcc 2.95.2]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[If the BX_SHOW_IPS feature is enabled, there is an error in main.cc]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[Windows 95]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[X] floppy image
|
||||
[ ] raw floppy drive
|
||||
[X] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[IE40, TweakUI]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [X] [ ] [compatibility mode only]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [X] [ ] [compatibility mode only]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
mouse [X] [ ] [ ] [__]
|
||||
cdrom [ ] [ ] [X] [not detected]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [compilation with PCI support fails]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [ ] [X] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,122 +0,0 @@
|
|||
What is the date?
|
||||
[5/29/2001]
|
||||
|
||||
What is your name?
|
||||
[Bryce Denney]
|
||||
|
||||
What is your email address?
|
||||
[bryce dot denney at bigfoot dot com]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[PowerPC G4 with 384meg RAM]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[MacOS X, build 3K78]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] compiled from version 1.0 (3/25/2000 snapshot)
|
||||
[ ] compiled from version 1.1 (bugfix1)
|
||||
[ ] compiled from version 1.1.1 (bugfix2)
|
||||
[ ] compiled from version 1.1.2 (bugfix3)
|
||||
[X] compiled from version 1.2-pre1
|
||||
[ ] I compiled it from the CVS sources from date: [__]
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[ ] Yes
|
||||
[ ] No, configure crashed.
|
||||
[X] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[
|
||||
NOTE: This was done on a system that has no X windows libraries!
|
||||
./configure (no args): it said it could not find X windows libraries,
|
||||
then it set itself up for X windows anyway. This failed of course.
|
||||
If I install X windows I'll try it again.
|
||||
./configure --with-term: could not find mvaddch in any of the
|
||||
three libraries it searched (curses, ncurses, termlib). So I changed
|
||||
configure.in to search for waddch instead of mvwaddch, ran autoconf
|
||||
again, and it said that waddch is found in curses. However it still
|
||||
will not build because of a few missing functions: keypad(), set_curs(),
|
||||
and nodelay(). It's only complaining about "implicit declaration" of
|
||||
these; they may actually be in the library but not the header?
|
||||
./configure --with-rfb: worked great! Not tested much though.
|
||||
]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[Reading specs from /usr/libexec/gcc/darwin/ppc/2.95.2/specs
|
||||
Apple Computer, Inc. version gcc-926, based on gcc version 2.95.2 19991024
|
||||
(release) ]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes, once I started using RFB mode.
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[./configure --with-rfb works fine
|
||||
X will probably be ok if I ever install it.
|
||||
]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[4meg linux image from web site]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[ ] floppy image
|
||||
[ ] raw floppy drive
|
||||
[X] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[not time to run many, this machine is very slow]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[none yet]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [X] [ ] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [X] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
mouse [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,64 +0,0 @@
|
|||
What is your name?
|
||||
[Hiroshi OKAMOTO]
|
||||
|
||||
What is your email address?
|
||||
[okamoto@cilab.tutkie.tut.ac.jp]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[1GHz Intel PentiumIII]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Microsoft Windows 2000 Service Pack 1 (Japanese)]
|
||||
|
||||
What version of bochs are you using?
|
||||
[X] binary of 1.2.pre1 for win32
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[DLX Linux hard disk image from bochs.sourceforge.net]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[ ] floppy image
|
||||
[ ] raw floppy drive
|
||||
[X] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[Y] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[Not tested]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[Not tested]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [X] [ ] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [X] [ ] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
|
@ -1,106 +0,0 @@
|
|||
What is the date?
|
||||
[June, 4th 2001]
|
||||
|
||||
What is your name?
|
||||
[Ulli Woelfel]
|
||||
|
||||
What is your email address?
|
||||
[uwoelfel@t-online.de]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing
|
||||
results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[x] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[Sun Ultra 60, 2x300MHz]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Solaris 8 01/01]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] I compiled it from 04/09/2001 bugfix snapshot
|
||||
[ ] I compiled it from 04/06/2001 bugfix snapshot
|
||||
[ ] I compiled it from 03/25/2000 snapshot
|
||||
[x] other source distribution from
|
||||
URL:[http://prdownloads.sourceforge.net/bochs/bochs-1.2.pre1.tar.gz]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[x] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[none]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[gcc 2.95.3]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[x] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[MSDOS 6.22]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[ ] floppy image
|
||||
[ ] raw floppy drive
|
||||
[x] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[x] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[edit]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[I have problems with typing the '/' character, also with edit the <alt>
|
||||
key doesn't work. I'm using
|
||||
a german Sun type 5 keyboard]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [x] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [x] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
mouse [ ] [ ] [x] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [ ] [ ] [x] [works only in b&w]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,106 +0,0 @@
|
|||
What is the date?
|
||||
[Wednesday 6th June 2001]
|
||||
|
||||
What is your name?
|
||||
[Nick Blievers]
|
||||
|
||||
What is your email address?
|
||||
[nickb@bigpond.net.au]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[64bit SGI Box (IP27)]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[IRIX 6.5.10f]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] compiled from version 1.0 (3/25/2000 snapshot)
|
||||
[ ] compiled from version 1.1 (bugfix1)
|
||||
[ ] compiled from version 1.1.1 (bugfix2)
|
||||
[ ] compiled from version 1.1.2 (bugfix3)
|
||||
[ ] compiled from version 1.2-pre1
|
||||
[X] compiled from version 1.2
|
||||
[ ] I compiled it from the CVS sources from date: [__]
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[--with-x --with-x11 --enable-apic]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[gcc 2.95.1]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[Linux]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[ ] floppy image
|
||||
[ ] raw floppy drive
|
||||
[X] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[Didn't try apart from basic Linux utils, all I had downloaded was the 10 MB DLX image]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [X] [ ] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [ ] [X] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
mouse [ ] [X] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [ ] [X] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,100 +0,0 @@
|
|||
What is the date?
|
||||
[6/6/2001]
|
||||
|
||||
What is your name?
|
||||
[James Preston]
|
||||
|
||||
What is your email address?
|
||||
[PRIVATE]
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[4 x 500MHz Intel Family 6 Model 7 Stepping 3]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Windows Terminal Server Editioni; NT 4.00.1381 SP 6]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] compiled from version 1.0 (3/25/2000 snapshot)
|
||||
[ ] compiled from version 1.1 (bugfix1)
|
||||
[ ] compiled from version 1.1.1 (bugfix2)
|
||||
[ ] compiled from version 1.1.2 (bugfix3)
|
||||
[ ] compiled from version 1.2-pre1
|
||||
[ ] I compiled it from the CVS sources from date: [__]
|
||||
[ ] other source distribution from URL: [__]
|
||||
[X] binary distribution from URL: [http://prdownloads.sourceforge.net/bochs/bochs-1.2.win32.zip]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[ ] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[__]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[__]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[ ] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[DLX Linux]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[ ] floppy image
|
||||
[ ] raw floppy drive
|
||||
[X] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[Only sampled the DLX programs.]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [X] [ ] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [X] [ ] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
mouse [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [X] [ ] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,120 +0,0 @@
|
|||
What is the date?
|
||||
[02.06.2001]
|
||||
|
||||
What is your name?
|
||||
[Volker Ruppert]
|
||||
|
||||
What is your email address?
|
||||
[PRIVATE]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[ ] Ok, put it on a web page
|
||||
[X] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[AMD K6-II 500MHz]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[SuSE Linux 7.1 with 2.2.18 kernel]
|
||||
|
||||
What version of bochs are you using?
|
||||
[ ] compiled from version 1.0 (3/25/2000 snapshot)
|
||||
[ ] compiled from version 1.1 (bugfix1)
|
||||
[ ] compiled from version 1.1.1 (bugfix2)
|
||||
[ ] compiled from version 1.1.2 (bugfix3)
|
||||
[ ] compiled from version 1.2-pre1
|
||||
[X] I compiled it from the CVS sources from date: [June 2, 2001]
|
||||
[ ] other source distribution from URL: [__]
|
||||
[ ] binary distribution from URL: [__]
|
||||
|
||||
Please fill in the next few questions only if you compiled Bochs
|
||||
yourself, as opposed to downloading a binary.
|
||||
|
||||
Did the configure script run ok, and detect your hardware and
|
||||
operating system?
|
||||
[X] Yes
|
||||
[ ] No, configure crashed.
|
||||
[ ] No, configure ran ok but produced a bad configuration.
|
||||
[ ] No, I cannot run configure on my platform (win32 and mac).
|
||||
|
||||
If you used configure, what arguments did you give it? If you used a
|
||||
.conf.* script, give the name of the .conf script instead.
|
||||
[./configure --enable-cdrom --enable-split-hd --enable-pci]
|
||||
|
||||
What compiler did you use? (Please include version.)
|
||||
[gcc 2.95.2]
|
||||
|
||||
Did Bochs compile clean without any hacking?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If you had to make changes to compile, please summarize the problems you
|
||||
had or include diffs.
|
||||
[__]
|
||||
|
||||
End of compile-specific questions!
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[DLX Linux 1.0 from http://bochs.sourceforge.net/guestos/dlxlinux2.tar.gz]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[ ] floppy image
|
||||
[ ] raw floppy drive
|
||||
[X] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[There are lots of warnings like this:
|
||||
|
||||
00197891463 [CPU ] BxError: instruction with op1=0xfe
|
||||
00197891463 [CPU ] nnn was 4
|
||||
00197891463 [CPU ] WARNING: Encountered an unknown instruction (signalling
|
||||
illegal instruction):
|
||||
|
||||
]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[bash (not easy to use, because I cannot find some keys)]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
floppy disk [ ] [X] [ ] [__]
|
||||
raw floppy disk [ ] [X] [ ] [__]
|
||||
hard disk [ ] [X] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
mouse [X] [ ] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [cdrom and fstype not supported
|
||||
by DLX kernel]
|
||||
sb16 [X] [ ] [ ] [compilation fails if sb16
|
||||
support is enabled]
|
||||
ne2000 [X] [ ] [ ] [__]
|
||||
i440FX pci [X] [ ] [ ] [bochs cannot load BIOS if
|
||||
enabled in .bochsrc]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [ ] [X] [ ] [__]
|
||||
|
||||
------------------------
|
||||
Note from Bryce: compilation of sb16 should be fixed in CVS as of
|
||||
June 9, 2001.
|
||||
------------------------
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,72 +0,0 @@
|
|||
What is the date?
|
||||
[19 jun 2001]
|
||||
|
||||
What is your name?
|
||||
[Dmitry Kondakov]
|
||||
|
||||
What is your email address?
|
||||
[Kondakov@power.bmstu.ru]
|
||||
|
||||
Do you mind if your name and email address are placed on a testing results
|
||||
web page so that people with a similar setup can write to you?
|
||||
[X] Ok, put it on a web page
|
||||
[ ] No, keep my address private.
|
||||
|
||||
What type of hardware are you using, e.g. 500MHz Intel Celeron.
|
||||
[600 MHz Intel Pentium III]
|
||||
|
||||
What operating system are you using? Please be specific, e.g.
|
||||
Redhat Linux 6.2 with 2.2.16 kernel.
|
||||
[Windows 2000 Professional]
|
||||
|
||||
What version of bochs are you using?
|
||||
[X] binary distribution from URL: [prdownloads.sourceforge.net/bochs/bochs-1.2.1.win32.zip]
|
||||
|
||||
What guest operating system are you using inside bochs?
|
||||
[QNX demo (network v405)]
|
||||
|
||||
Are you booting from a floppy or hard disk?
|
||||
[X] floppy image
|
||||
[ ] raw floppy drive
|
||||
[ ] hard drive image
|
||||
[ ] raw hard drive (is this even possible?)
|
||||
[ ] other [__]
|
||||
|
||||
Did the guest operating system boot successfully?
|
||||
[X] Yes
|
||||
[ ] No
|
||||
|
||||
If no, what error messages do you see on the console or in the log file?
|
||||
[__]
|
||||
|
||||
What applications worked under this guest operating system?
|
||||
[All]
|
||||
|
||||
What applications failed under this guest operating system? Did the
|
||||
application function incorrectly, crash Bochs, or what? If you got a
|
||||
panic, paste in the panic message that you received with some
|
||||
description of what was happening at the time.
|
||||
[__]
|
||||
|
||||
The remaining questions are about Bochs features that you may not have
|
||||
used. If you tried out the feature, move the X to the "works" or
|
||||
"fails" column.
|
||||
|
||||
Not Works
|
||||
tested ok Fails Comments?
|
||||
keyboard [ ] [X] [ ] [__]
|
||||
floppy disk [X] [ ] [ ] [__]
|
||||
raw floppy disk [X] [ ] [ ] [__]
|
||||
hard disk [X] [ ] [ ] [__]
|
||||
floating point [X] [ ] [ ] [__]
|
||||
mouse [ ] [X] [ ] [__]
|
||||
cdrom [X] [ ] [ ] [__]
|
||||
sb16 [X] [ ] [ ] [__]
|
||||
ne2000 [ ] [ ] [X] [not found]
|
||||
i440FX pci [X] [ ] [ ] [__]
|
||||
debugger [X] [ ] [ ] [__]
|
||||
external loader [X] [ ] [ ] [__]
|
||||
VGA [ ] [X] [ ] [__]
|
||||
|
||||
Thank you for your contribution in the Bochs testing effort! Please
|
||||
mail completed forms to bochs-testing@tlw.com.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
The table entry you clicked comes from the
|
||||
<a href="/docs-html/whatisbochs.html#Platforms">supported platforms table</a>
|
||||
in the Bochs documentation. A more detailed report is not available.
|
||||
|
|
@ -1,51 +0,0 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE></TITLE>
|
||||
</HEAD>
|
||||
<BODY>
|
||||
Test using name,url syntax only.
|
||||
|
||||
These links are pasted right out of test/index.html and test/include/header.html
|
||||
to test if topper-sf.pl still works with name/url syntax.
|
||||
<p>
|
||||
|
||||
<a href="http://bochs.sourceforge.net/cgi-bin/topper-sf.pl?name=CVS+Access+Information&url=http://sourceforge.net/cvs/qmrkgroup_ideq12580" class="sidebar">Anonymous CVS</a>
|
||||
|
||||
|
||||
<br>
|
||||
<a href="http://bochs.sourceforge.net/cgi-bin/topper-sf.pl?name=Fre+quently+Asked+Questions&url=http://bochs.sourceforge.net/docs-html/faq.html" class="sidebar">Bochs FAQ</a>
|
||||
<p>
|
||||
Test using new sftype,id syntax.
|
||||
<p>
|
||||
|
||||
<a href="/cgi-bin/topper-sf.pl?sftype=bug">Bug index</a>
|
||||
<br>
|
||||
<a href="/cgi-bin/topper-sf.pl?sftype=bug&id=419387">Bug number 419387</a>
|
||||
<br>
|
||||
<a href="/cgi-bin/topper-sf.pl?sftype=bug&id=421116">Bug number 421116</a>
|
||||
<br>
|
||||
<a href="/cgi-bin/topper-sf.pl?sftype=bug&id=add">Submit bug report</a>
|
||||
<br>
|
||||
|
||||
<a href="/cgi-bin/topper-sf.pl?sftype=patch">Patch index</a>
|
||||
<br>
|
||||
<a href="/cgi-bin/topper-sf.pl?sftype=patch&id=421888">Patch number 421888</a>
|
||||
<br>
|
||||
<a href="/cgi-bin/topper-sf.pl?sftype=patch&id=420442">Patch number 420442</a>
|
||||
<br>
|
||||
<a href="/cgi-bin/topper-sf.pl?sftype=patch&id=add">Submit patch</a>
|
||||
<br>
|
||||
|
||||
<a href="/cgi-bin/topper-sf.pl?sftype=feature">Feature index</a>
|
||||
<br>
|
||||
<a href="/cgi-bin/topper-sf.pl?sftype=feature&id=418731">Feature number 418731</a>
|
||||
<br>
|
||||
<a href="/cgi-bin/topper-sf.pl?sftype=feature&id=421107">Feature number 421107</a>
|
||||
<br>
|
||||
<a href="/cgi-bin/topper-sf.pl?sftype=feature&id=add">Submit feature request</a>
|
||||
<br>
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
|
||||
|
|
@ -1,39 +0,0 @@
|
|||
This is a catalog of sites where we have submitted bochs.
|
||||
All in this list have Bryce's standard bochs password, which
|
||||
is written as <PASSWORD>
|
||||
|
||||
--------------------------------------------------------------------------
|
||||
winsite.com
|
||||
updated to bochs 1.2.1, jun 15 2001
|
||||
|
||||
- Go to uploads.winsite.com
|
||||
- click on "if you already have a winsite software submission account"
|
||||
- email is "bryce.denney@bigfoot.com" password is <PASSWORD>
|
||||
- click on "replace existing program with new version"
|
||||
- update information and submit
|
||||
--------------------------------------------------------------------------
|
||||
nonags.com
|
||||
I submitted 1.2 but I they haven't updated yet
|
||||
can't remember the password, but I have a few guesses :)
|
||||
--------------------------------------------------------------------------
|
||||
www.icewalkers.com
|
||||
updated to 1.2.1, june 15 2001
|
||||
|
||||
- At the top of the home page, find the Name and Password fields.
|
||||
- Type name "Bryce Denney" and password <PASSWORD>, then Login.
|
||||
- in the upper left corner, find the search text box and type bochs return.
|
||||
- click on update
|
||||
- update the download and redhat package URL
|
||||
- press submit
|
||||
--------------------------------------------------------------------------
|
||||
tucows.com
|
||||
|
||||
For 1.2.1 they updated for us!
|
||||
Go to tucows.com
|
||||
in the "Search Software library" blank type bochs return.
|
||||
This brings up bochs and also macbochs
|
||||
Click bochs 1.*
|
||||
Choose on a mirror site from list.
|
||||
You should see bochs on there.
|
||||
Down in the choices at bottom, choose "Submit Software"
|
||||
|
||||
Loading…
Reference in New Issue