- document new .bochsrc options (basically just copy .bochsrc description

into the docbook)

bochs/doc/docbook/user/user.dbk

@@ -1,7 +1,7 @@
 <!--
 ================================================================
 doc/docbook/user/user.dbk
-$Id: user.dbk,v 1.38 2002-03-28 06:45:06 bdenney Exp $
+$Id: user.dbk,v 1.39 2002-03-28 07:50:34 bdenney Exp $
 
 This is the top level file for the Bochs Users Manual.
 ================================================================
@@ -2459,6 +2459,40 @@ just a configuration problem like "could not find hard drive image."
 </tip>
 </section>
 
+<section><title>com1</title>
+<para>
+Specifies the device to use as com1.  This can be a real serial line, or
+a pty.  To use a pty (under X/Unix), create two windows (xterms,
+usually).  One of them will run bochs, and the other will act as com1.
+Find out the tty the com1 window using the `tty' command, and use that
+as the `dev' parameter.  Then do `sleep 1000000' in the com1 window to
+keep the shell from messing with things, and run bochs in the other
+window.  Serial I/O to com1 (port 0x3f8) will all go to the other
+window.
+</para>
+<para>
+Examples:
+<screen>
+com1: dev=/dev/ttyp9
+com1: dev=/dev/cua0
+</screen>
+</para>
+</section>
+
+<section><title>parport1</title>
+<para>
+This defines a parallel (printer) port.  When turned on, the emulated
+printer port sends characters printed by the guest OS into an output file.
+</para>
+<para>
+Examples:
+<screen>
+parport1: enable=1, file="parport.out"
+parport1: enable=0
+</screen>
+</para>
+</section>
+
 <section><title>sb16</title>
 <para>
 Examples:
@@ -2557,6 +2591,23 @@ transfered from the keyboard to controller over the serial path.
 </para>
 </section>
 
+<section><title>keyboard_paste_delay</title>
+<para>
+Approximate time in microseconds between attempts to paste
+characters to the keyboard controller. This leaves time for the
+guest os to deal with the flow of characters.  The ideal setting
+depends on how your operating system processes characters.  The
+default of 100000 usec (.1 seconds) was chosen because it works
+consistently in Windows.
+</para>
+<para>
+Example:
+  keyboard_paste_delay: 100000
+<screen>
+</screen>
+</para>
+</section>
+
 <section><title>floppy_command_delay</title>
 <para>
 Examples:
@@ -2632,12 +2683,72 @@ Examples:
 <screen>
   private_colormap: enabled=1
 </screen>
-Requests that the GUI create and use it's  own non-shared colormap.  This
+Requests that the GUI create and use its  own non-shared colormap.  This
 colormap  will  be used when in the bochs window. If not enabled, a shared
 colormap  scheme  may be used.  Once again, enabled=1  turns on this feature
 and 0 turns it off.
 </section>
 
+<section><title>ne2k</title>
+<para>
+The ne2k line configures an emulated NE2000-compatible ethernet adapter,
+which allows the guest machine to communicate on the network.  To disable
+the NE2000 just comment out the ne2k line.
+</para>
+<para>
+Examples:
+<screen>
+ne2k: ioaddr=0x280, irq=9, mac=b0:c4:20:00:00:00, ethmod=fbsd, ethdev=xl0
+ne2k: ioaddr=0x280, irq=9, mac=b0:c4:20:00:00:00, ethmod=linux, ethdev=eth0
+ne2k: ioaddr=0x280, irq=9, mac=b0:c4:20:00:00:01, ethmod=win32, ethdev=<replaceable>MYCARD</replaceable>
+ne2k: ioaddr=0x280, irq=9, mac=fe:fd:00:00:00:01, ethmod=tap, ethdev=tap0
+
+ioaddr, irc: You probably won't need to change ioaddr and irq, unless there
+are IRQ conflicts.
+
+mac: The MAC address MUST NOT match the address of any machine on the net.
+Also, the first byte must be an even number (bit 0 set means a multicast
+address), and you cannot use ff:ff:ff:ff:ff:ff because that's the broadcast
+address.  For the ethertap module, you must use fe:fd:00:00:00:01.  There may
+be other restrictions too.  To be safe, just use the b0:c4... address.
+
+ethdev: The ethdev value is the name of the network interface on your host
+platform.  On UNIX machines, you can get the name by running ifconfig.  On
+Windows machines, you must run niclist to get the name of the ethdev.
+Niclist source code is in misc/niclist.c and it is included in Windows 
+binary releases.
+</screen>
+</para>
+</section>
+
+<section><title>keyboard_mapping</title>
+<para>
+Examples:
+<screen>
+  keyboard_mapping: enabled=0, map=
+  keyboard_mapping: enabled=1, map=gui/keymaps/x11-pc-de.map
+</screen>
+This enables a remap of a physical localized keyboard to a
+virtualized U.S. keyboard, as the PC architecture expects.
+If enabled, the keymap file must be specified.
+</para>
+</section>
+
+<section><title>keyboard_type</title>
+<para>
+Examples:
+<screen>
+  keyboard_type: xt
+  keyboard_type: at
+  keyboard_type: mf
+</screen>
+Type of keyboard returned by a "identify keyboard" command to the
+keyboard controler. It must be one of "xt", "at" or "mf".
+Defaults to "mf". It should be ok for almost everybody. A known
+exception is french macs, that do have a "at"-like keyboard.
+</para>
+</section>
+
 </section> <!--end of bochsrc section-->
 
 <section id="keymap"><title>How to write your own keymap table</title>