diff --git a/bochs/doc/docbook/misc.txt b/bochs/doc/docbook/misc.txt index 8a172b4ed..ea8a08491 100644 --- a/bochs/doc/docbook/misc.txt +++ b/bochs/doc/docbook/misc.txt @@ -4,58 +4,6 @@ This is a temporary place to paste in stuff that should go into the docs one day. When it is transferred into docbook, let's remove it from misc.txt. -------------------------------------------------------------------------- --------------------------------------------------------------------------- --------------------------------------------------------------------------- --------------------------------------------------------------------------- -Date: Thu, 15 Nov 2001 13:31:34 -0800 -From: David Christy -To: bryce@tlw.com -Subject: usefull info for mounting - - -I didn't see this in the doc's so I thought you might like a -short description of how to mount a disk image file into -loopback filesystem for maintenance purposes. - --------------------------------------------- - -1) First run - -fdisk -l - -... and it should print out a partition table (with a few -complaints requesting the drive geometry, and I don't know -if older versions require a block device) In fact fdisk will -even work to modify partitions in an image, but you must -specify the drive geometry that's in the bocsrc first. - -2) Whatever it says the starting partition is, subtract 1 -and multiply by 512 - -3) Type - -mount -o loop,offset= -/mount/dir - -or if it's just a floppy image, just - -mount -o loop floppy.img /mount/dir - ---------------------------------------------------- - -I would recommend putting -o ro for read only access if -bochs is in use. For unusual filesystems you may need to -add a -t flag to the mount command to specify the -filesystem type. - -see man mount, losetup, and fdisk for more info - - - -BOCHS Rocks!!! - - - -------------macintosh.txt----------------- BBD Mon Nov 25 08:23:28 EST 2002 This file has been in our main directory for years and years, and has not @@ -228,134 +176,7 @@ 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 or - ---------------------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. - -
Quick Start for Linux users - - - -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! - - -
How can I try out Bochs in 10 minutes or less? - -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 $HOME/.bochsdlx. 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. - - -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! - - -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. - - - -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. - - - -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. - - -
- ------------------------------------------- -Windows 3.1 install hints - -Date: Fri, 13 Dec 2002 09:56:48 -0700 -From: Ben Lunt -To: bochs-devel - -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 @@ -422,5 +243,4 @@ 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 - - +-------------------------------------------------------------------------- diff --git a/bochs/doc/docbook/user/user.dbk b/bochs/doc/docbook/user/user.dbk index 331f9a0c8..c6a326a1c 100644 --- a/bochs/doc/docbook/user/user.dbk +++ b/bochs/doc/docbook/user/user.dbk @@ -104,13 +104,14 @@ operating system has not been written. -Bochs was written by Kevin Lawton starting in 1994. It began as a -commercial product, which you could buy with source code for ... +Bochs was written by Kevin Lawton starting in 1994. It started as a program with a +commercial license, at the price of 25 USD, for use as-is. If a user needed to link +it to other software, that user would have to negotiate a special license. &NEEDHELP; We need a Bochs historian to help out here. For background, it would be -interesting to know how much Bochs used to cost and what it was used for. I -thought I saw an interview out there somewhere where Kevin says why he started +interesting to know how much Bochs sources used to cost and what it was used for. +I thought I saw an interview out there somewhere where Kevin says why he started it and some more background information. Finally, in March 2000, MandrakeSoft (now called @@ -383,7 +384,7 @@ currently work with. Yes Implements ElTorito, EDD v3.0, basic APM feature, PCIBIOS features and the PCI interrupt routing table. The latest version of the Bochs BIOS - has a 32-bit init for ACPI, SMM and SMP. Bochs also known no work with recent + has a 32-bit init for ACPI, SMM and SMP. Bochs also known to work with recent SeaBIOS images. @@ -1014,8 +1015,8 @@ for instructions. -The SVN checkout process (above) gives you a directory called bochs that -contains the very latest source code. I will refer to this directory +The SVN checkout process (above) gives you a directory called bochs +that contains the very latest source code. I will refer to this directory as &bochsdir;. In each subdirectory directory there's also a directory called ".svn" which tells the SVN software where the code was checked out, what version you have, and where to go for future updates. @@ -1110,7 +1111,7 @@ any release since March 2000. The command is user$ svn co https://bochs.svn.sourceforge.net/svnroot/bochs/tags/tagname bochs -The tag tells which release you want, and it can be one of the following: +The tagname tells which release you want, and it can be one of the following: Bochs Release Tags