misc.txt

来自「bochs : one pc simulator.」· 文本 代码 · 共 427 行 · 第 1/2 页

The following files from the main bochs distribution have been modified to
compile properly on the Mac:

bochs.h
main.cc
memory/memory.cc
memory/misc_mem.cc
iodev/floppy.cc
iodev/harddrv.cc

The changes are just conditional compilations which won't affect other
platforms (search for "#ifdef macintosh" and "#ifndef macintosh" if you want
to see what the changes are). These changes will need to be integrated into
the main distribution if the MacOS port is going to go ahead seriously.

-- David Batterham <[e-mail]> or <[e-mail]>

--------------------win32.txt----------------------
BBD Mon Nov 25 08:27:24 EST 2002
The win32 build instructions are out of date too.  The --with-win32-vcpp
has been deprecated since at least March 2002.  More current instructions
are already in the docs, so this info may not be of much use.

Building Bochs for Win32
------------------------

This has only been tested with MS Visual C++ 6.0.

The normal build process on a unix system is to run configure to build all the
makefiles and config.h, and then run make to compile Bochs.  Configure takes a
large number of command line arguments, for example to disable floating point
or to enable sound blaster emulation.  Configure works beautifully on unix
systems to help make the code portable, however it cannot run on Windows.
(Maybe, if you have cygwin.)  Therefore, you need to either 1) run configure
on a unix box and copy the makefiles and config.h, or 2) download the
makefiles which are distributed in a separate ZIP file.

If you want to run configure yourself, consider using the shell script
".conf.win32-vcpp" since it has been tested.  Look at it to make sure
the options make sense for you.  You can always run configure by hand too,
just be sure to include the option --with-win32-vcpp so that it creates
makefiles for win32.  Copy config.h, Makefile, and the Makefiles in all
subdirectories over to your windows box into the same directory as the Bochs
source.

If you download the makefiles in a ZIP, just extract them into the
same directory as the Bochs source.  The config.h and top level Makefile
should end up in the same directory as Bochs.h.

Once the makefiles are installed, building Bochs is easy.  Start up an MSDOS
window, run the .BAT file that sets up the environment variables
(C:\vc98\bin\vcvars32.bat on my system), and then run NMAKE in the Bochs
source directory.  You will get lots of compile warnings, but hopefully no
fatal errors!  At the end, you should see Bochs.exe in the source directory.




<!-- *************************************************************** -->

Wed Dec 11 13:56:20 EST 2002
this text came from build/linux/DOC-linux.html.
Originally it was an intro to Bochs for Linux users.  I converted it all to
docbook.  I moved most of the info from DOC-linux.html into different
sections of the user guide, and the rest I put here in misc.txt.  Maybe these
paragraphs will be useful in some kind of introduction to something, or maybe
not.

<section><title>Quick Start for Linux users</title>
<!--much text removed, put into user guide -->

<para>
This file is an introduction to Bochs for Linux users.  It assumes that you
have just installed a Bochs binary distribution, and now you want to see what
Bochs can do!
</para>

<section><title>How can I try out Bochs in 10 minutes or less?</title>
<para>
This RPM package includes a sample disk image containing DLX Linux, which you
can boot within Bochs.  To start up DLX linux, just type "bochs-dlx" in an
xterm.  The first time it runs, it creates a disk image in a directory
called <filename>$HOME/.bochsdlx</filename>.  Then it creates a Bochs Display
window and prints some log messages into the xterm.  The display window is the
most interesting, but if something goes wrong the log messages should give an
idea of what has happened.
</para>
<para>
Meanwhile, the Bochs display screen should look like a PC booting...and in
fact it is!  Bochs begins simulating a PC from the time the power turns on.
You will see the VGA BIOS message, and it begins loading Linux from the disk
image.  The disk image is just a big file that Bochs uses as if it were a
real hard drive.  After a while, you see Linux boot messages and eventually a
login prompt.  You are now running DLX Linux in a window!
</para>
<para>
Bochs simulates every instruction of an x86 CPU, so it is very memory- and
compute-intensive.  The speed of your real CPU will make a big difference in
how fast the DLX Linux image boots.  On a 1GHz Pentium, the sample Linux 
image takes about 10 seconds to boot.
</para>

<para>
In this brief introduction you saw how Bochs can boot and run an x86 operating
system in a window.  It doesn't have to be Linux, of course!  Various people
have been able to install and run DOS, Windows 3.1, Windows 95/98/ME/NT/XP,
Linux, FreeBSD, NetBSD, OpenBSD, and probably others that we've never even
heard of.  In fact Bochs is used by many operating system developers to test
out their software in a controlled environment without having to reboot their
development machine.
</para>

<para>
If you are learning about Bochs for the first time, you might want to
download a few other prebuilt disk images of other operating systems from the
Bochs website.  They range from very small (1.44 meg floppy disk images) to
hundreds of megabytes.  Most disk images on the web site come with a
working configuration file (often called bochsrc.txt) so they should work
without much effort.  This will give you an idea of what Bochs can do,
and how it might be useful to you.
</para>

</section>

------------------------------------------
Windows 3.1 install hints

Date: Fri, 13 Dec 2002 09:56:48 -0700
From: Ben Lunt <[e-mail]>
To: bochs-devel <[e-mail]>

I was playing with bochs a bit last night and successfully
got windows 3.1 installed on a c.img file and run with
almost no errors.

I first started with three original DOS 5.0 720k images,
FDISKed, FORMATed, and then install.

Then changed to seven 1_44m disks and installed Win16.
Each time either OS asked for a new disk, I simply
copied the expected image to a.img and continued.


------------------------------------------
WinNT4 guest network problems

From: Jeremy Wilkins <jeb at jeremywilkins.freeserve.co.uk>
To: [e-mail]
Subject: [Bochs-developers] Odd network errors with NT4 Guest OS

I'm having trouble transferring files over the network to the guest OS 
(NT4 SP1). If I'm using SMB then the it errors out early on with a 
session cancelled. The file is 36Mb (SP6). I've tried with various file 
sizes, 3Meg files work, 5 meg files do not.

I've also tried shuffling the files over http with similar problems, 
small files are fine (can browse websites) but large files just error out.

The system is a 1Ghz Windows XP SP1 box with bochs 2.02, guest OS is 
allocated 64Mb of RAM and running Windows NT4 SP1.

Any clues, anyone experiencing similar problems?

--

From: didier <dgautheron at magic.fr>
To: Jeremy Wilkins <jeb at jeremywilkins.freeserve.co.uk>
Cc: [e-mail]
Subject: Re: [Bochs-developers] Odd network errors with NT4 Guest OS

Did you try with a big IPS? start the guest clock applet and try to get 
a more or less accurate time, with 1 Ghz should be in the 50 000 000 range.
IIRC NT timeout and abort before it send the whole packet.

--

From: Jeremy Wilkins <jeb at jeremywilkins.freeserve.co.uk>
To: didier <dgautheron at magic.fr>, [e-mail]
Subject: Re: [Bochs-developers] Odd network errors with NT4 Guest OS

Thanks, 60 000 000 seems to have done the trick (I can copy sp6 across 
anyway). My original guess of 4000000 IPS was probably a bit low :)

thanks again

------------------------------------------
TAP under FreeBSD 

Date: Fri, 14 Feb 2003 02:12:38 +0100
From: Ronald Klop <ronald at echteman.nl>
To: bochs-developers at lists.sourceforge.net

I've made eth_tap.cc working under FreeBSD 4.7, because the fbsd network driver
didn't work for me.
It's not a very clean patch, but the changes are minimal.

Some notes:
- I found that some of the includes aren't used at all (on FreeBSD).
- The socket which is created before /dev/tap0 is opened doesn't work, because
tap0 is created after opening the device.
- Maybe the eth_tap device can use a configure script like the eth_tuntap
device, because the device must be configured after opening.
- The padding of the ethernet frame with 2 bytes isn't needed in FreeBSD.
- I didn't do any work to check for this in configure, because I don't know how
configure works and don't have the time work it out now.
- the guest os must set (maybe this can be documented somewhere):
kldload if_tap (if tap is not compiled in the kernel)
ifconfig tap0 inet 10.0.1.1 netmask 255.255.255.0
sysctl net.inet.ip.forwarding=1
sysctl net.link.ether.inet.proxyall=1