--- BasiliskII/README	1999/10/03 16:21:28	1.2
+++ BasiliskII/README	2001/01/25 22:24:36	1.16
@@ -1,28 +1,29 @@
 
-	Basilisk II, Version 0.7
-	A free, portable Mac II emulator
+  Basilisk II, Version 0.8
+  A 68k Macintosh emulator
 
-	Copyright (C) 1997-1999 Christian Bauer et al.
-	Freely distributable
+  Copyright (C) 1997-2001 Christian Bauer et al.
 
 
 License
 -------
 
 Basilisk II is available under the terms of the GNU General Public License.
-See the file "COPYING" that is included in this archive for details.
+See the file "COPYING" that is included in the distribution for details.
 
 
 Overview
 --------
 
-Basilisk II is a free, portable, Open Source 68k Mac emulator. It requires
-a copy of a Mac ROM and a copy of MacOS to run. Basilisk II is freeware and
-distributed under the GNU General Public License.
+Basilisk II is an Open Source 68k Macintosh emulator. That is, it enables
+you to run 68k MacOS software on you computer, even if you are using a
+different operating system. However, you still need a copy of MacOS and
+a Macintosh ROM image to use Basilisk II.
 
 Basilisk II has currently been ported to the following systems:
   - BeOS R4 (PowerPC and x86)
-  - Unix (tested under Linux, Solaris 2.5, FreeBSD 3.x and IRIX 6.5)
+  - Unix (tested under Linux, Solaris 2.5, FreeBSD 3.x, NetBSD 1.4.2 and
+    IRIX 6.5)
   - AmigaOS 3.x
   - Windows NT 4.0 (mostly works under Windows 95/98, too)
 
@@ -35,105 +36,24 @@ Some features of Basilisk II:
   - Floppy disk driver (only 1.44MB disks supported)
   - Driver for HFS partitions and hardfiles
   - CD-ROM driver with basic audio functions
+  - Easy file exchange with the host OS via a "Host Directory Tree" icon
+    on the Mac desktop
   - Ethernet driver
   - Serial drivers
   - SCSI Manager (old-style) emulation
   - Emulates extended ADB keyboard and 3-button mouse
-  - Uses UAE 68k emulation or (under AmigaOS) real 68k processor
+  - Uses UAE 68k emulation or (under AmigaOS and NetBSD/m68k) real 68k
+    processor
 
 The emulator is not yet complete. See the file "TODO" for a list of
 unimplemented stuff.
 
 
-Requirements
-------------
-
-To use Basilisk II, you need either a 512K Mac Classic ROM image or a
-512K or 1MB 32-bit clean Macintosh ROM image. You also need a copy of MacOS
-(0.x thru 7.5 for Classic emulation, 7.x or 8.0/8.1 for Mac II emulation).
-For copyright reasons, none of these items are included with Basilisk II.
-MacOS 7.5.3 and earlier versions can be downloaded from Apple and various
-other Internet sites. Mac ROM files are not freely available. You have to
-own a real Mac and read out its ROM. No, I don't know where you can download
-ROM files. No, I won't send you one.
-
-Depending on the platform you use, Basilisk II has additional requirements:
-
-BeOS:
-  You need BeOS R4 or better. On a PowerPC system you also need the
-  "sheep" driver that comes with SheepShaver. To use Ethernet, you need
-  the "sheep_net" add-on that also comes with SheepShaver (both items
-  are included in the SheepShaver Trial Versions). The PowerPC version of
-  Basilisk II cannot do Mac Classic emulation.
-
-Unix:
-  You need X11R4, pthreads support and GNU make. To use the GUI preferences
-  editor, you also need GTK+ version 1.2 or better. On Linux, you need
-  glibc 2.0 or better.
-
-AmigaOS:
-  You need at least a 68020 and AmigaOS 3.0 or better. To get the GUI
-  preferences editor, you need gtlayout.library V39 or later. To get sound
-  output, you need AHI V2 or later. Both items can be found on Aminet. You
-  also need the "PrepareEmul" utility that somes with ShapeShifter (or any
-  equivalent PrepareEmul substitute). The AmigaOS version of Basilisk II
-  cannot do Mac Classic emulation.
-
-Windows:
-  You need at least Windows NT 4.0. Windows 95 and 98 can be used too, with a
-  somewhat reduced set of features. Basilisk II supports DirectX version 5 or
-  later, but version 3 may also work, depending on your graphics card.
-
-
-Installation
-------------
-
-BeOS:
-  If you have a binary distribution of Basilisk II for BeOS, there are
-  executables for BeOS/PPC and BeOS/x86 included. If you have the source
-  distribution, cd to "src/BeOS", and type "make". Basilisk II cannot run
-  concurrently with SheepShaver. Trying to do so will crash Basilisk II,
-  or SheepShaver, or both. On a PowerPC system you must have installed the
-  "sheep" driver that comes with SheepShaver. To use Ethernet, you must have
-  installed the "sheep_net" add-on that also comes with SheepShaver 
-
-Unix:
-  To compile Basilisk II, cd to "src/Unix", and type "./configure" followed
-  by "make" and (optionally) "make install". To use Ethernet networking under
-  Linux, you either have to configure your kernel for ethertap support or make
-  and install the "sheep_net" driver: cd to "src/Unix/Linux/NetDriver" and
-  type "make". This should produce a kernel module "sheep_net.o". Now su root
-  and type "./MAKEDEV" which will install the device node "/dev/sheep_net".
-  Then say "/sbin/insmod sheep_net.o" and the driver should be ready for use.
-  You should give appropriate access rights to /dev/sheep_net if you don't
-  want to run Basilisk II as root.
-
-  This is what Brian J. Johnson says about compiling for IRIX:
-   "I recommend compiling with "-Ofast".  This requires changing "-g"
-    to "-Ofast" in the Makefile, and adding "-ipa" to LDFLAGS.  This
-    turns on massive interprocedural optimization, and makes for much
-    better performance."
+Requirements and Installation
+-----------------------------
 
-AmigaOS:
-  If you have a binary distribution of Basilisk II for AmigaOS, there is an
-  executable included. You must also have the "PrepareEmul" utility installed
-  that comes with ShapeShifter (or any equivalent PrepareEmul substitute,
-  see the ShapeShifter docs). If you have the source distribution, cd to
-  "src/AmigaOS" and type "smake". To recompile Basilisk II, you need SAS/C
-  6.58. Earlier versions may not work.
-
-Windows NT:
-  If you have a binary distribution of Basilisk II for Windows, there is a
-  Windows NT binary included. To access CD-ROMs under Windows NT, the driver
-  "cdenable.sys" must be copied to your "\WinNT\System32\drivers" directory.
-  To access CD-ROMs under Windows 9x, the driver "cdenable.vxd" must be copied
-  to the "\Windows\System" directory. To recompile Basilisk II, you need
-  MS Visual V++ 5.0 or later. Symantec C++ should work, too, with some
-  modifications. See the "sysdeps.h" file in the "Windows" directory.
-
-The ROM file has to be named "ROM" and put in the same directory as the
-Basilisk II executable but you can specify a different location for the ROM
-file with the "rom" option in the preferences file.
+Please consult the file "INSTALL" for a list of system requirements and
+installation instructions.
 
 
 Configuration
@@ -221,6 +141,16 @@ cdrom <CD-ROM drive description>
   installed CD-ROM drives. The format of the "CD-ROM drive description"
   is the same as that of "disk" lines.
 
+extfs <direcory path>
+
+  This item specifies the root directory for the "Host Directory Tree"
+  file system (the "Unix/BeOS/Amiga/..." icon on the Finder desktop).
+  All objects contained in that directory are accessible by Mac applications.
+  This feature is only available when File System Manager V1.2 or later
+  is installed on the Mac side. FSM 1.2 is built-in beginning with MacOS 7.6
+  and can be installed as a system extension (downloadable from Apple, look
+  for the FSM SDK in the developer section) for earlier MacOS versions.
+
 scsi0 <SCSI target> ... scsi6 <SCSI target>
 
   These items describe the SCSI target to be used for a given Mac SCSI
@@ -250,9 +180,8 @@ scsi0 <SCSI target> ... scsi6 <SCSI targ
     "scsi.device/2").
 
   Windows:
-    Ignored. Basilisk II scans for all SCSI devices and the first 6 found
-    devices are made visible to the MacOS. You cannot explicitly enable a
-    device, but you can disable a device (see the "disablescsi" command).
+    The "SCSI target" has the format <"Vendor"> <"Model"> (e.g.
+    scsi0 "HP" "CD-Writer+ 7100"). Note the use of quotes.
 
 screen <video mode>
 
@@ -282,11 +211,20 @@ screen <video mode>
         Color display in an X11 window of the given size. The color depth
         (8/15/24 bit) depends on the depth of the underlying X11 screen.
         This is the default.
-      dga
-        Full-screen display using the X11 DGA extensions. The color depth
+      dga/<width>/<height>
+        [if Basilisk II was configured with --enable-xf86-dga]
+        Full-screen display using the XFree86 DGA extension. The color depth
         (8/15/24 bit) depends on the depth of the underlying X11 screen.
-        For DGA to work, Basilisk II must be compiled with DGA support
-        enabled (selectable in the configure script).
+        "width" and "height" specify the maximum width/height to use.
+        Saying "dga/0/0" means "complete screen".
+      dga/<frame buffer name>
+        [if Basilisk II was configured with --enable-fbdev-dga]
+        Full-screen display using the frame buffer device /dev/fb. The color
+        depth (8/15/24 bit) depends on the depth of the underlying X11 screen.
+        The "frame buffer name" is looked up in the "fbdevices" file (whose
+        path can be specified with the "fbdevicefile" prefs item) to determine
+        certain characteristics of the device (doing a "ls -l /dev/fb" should
+        tell you what your frame buffer name is).
 
   AmigaOS:
     The "video mode" is one of the following:
@@ -298,11 +236,11 @@ screen <video mode>
         15-bit truecolor display in a Picasso96 PIP. This requires
         Picasso96 as well as a PIP-capable graphics card (e.g. Picasso IV).
       scr/<hexadecimal mode ID>
-        8/15/24-bit fullscreen display on a Picasso96 screen with the given
-        mode ID. This requires Picasso96. For 15 and 24 bit, the frame buffer
-        format must be QuickDraw-compatible (big-endian, xRGB 1:5:5:5 or
-        xRGB 8:8:8:8). The screen size will be the default size for that
-        mode ID.
+        8/15/24-bit fullscreen display on a Picasso96/CyberGraphX screen with
+        the given mode ID. This requires Picasso96 or CyberGraphX. For 15 and
+        24 bit, the frame buffer format must be QuickDraw-compatible
+        (big-endian, xRGB 1:5:5:5 or xRGB 8:8:8:8). The screen size will be
+        the default size for that mode ID.
 
   Windows:
     The "video mode" is one of the following:
@@ -396,6 +334,7 @@ ether <ethernet card description>
   Linux:
     The "ethernet card description" is the name of an Ethernet interface.
     There are two approaches to networking with Basilisk II:
+
       1. Direct access to an Ethernet card via the "sheep_net" driver.
          In this case, the "ethernet card description" must be the name
          of a real Ethernet card, e.g. "eth0". It also requires the "sheep_net"
@@ -405,23 +344,42 @@ ether <ethernet card description>
          networking. MacOS will only be able to talk to other machines on
          the Ethernet, but not to other networks that your Linux box routes
          (e.g. a second Ethernet or a PPP connection to the Internet).
+
       2. Putting Basilisk II on a virtual Ethernet via the "ethertap" device.
          In this case, the "ethernet card description" must be the name
          of an ethertap interface, e.g. "tap0". It also requires that you
          configure your kernel to enable routing and the ethertap device:
          under "Networking options", enable "Kernel/User netlink socket" and
          "Netlink device emulation", under "Network device support", activate
-         "Ethertap network tap". Next, see /usr/src/linux/Documentation/
-         networking/ethertap.txt for information on how to set up /dev/tap*
-         device nodes and activate the ethertap interface. Under MacOS,
-         select an IP address that is on the virtual network and set the
-         default gateway to the IP address of the ethertap interface. This
-         approach will let you access all networks that your Linux box has
-         access to (especially, if your Linux box has a dial-up Internet
-         connection and is configured for IP masquerading, you can access
-         the Internet from MacOS). The drawback is that you can only use
-         network protocols that Linux can route, so you have to install and
-         configure netatalk if you want to use AppleTalk.
+         "Ethertap network tap". You also have to modify drivers/net/ethertap.c
+         a bit before compiling the new kernel:
+
+          - insert "#define CONFIG_ETHERTAP_MC 1" near the top (after the
+            #include lines)
+          - comment out the line "dev->flags|=IFF_NOARP;" in ethertap_probe()
+
+         Next, see /usr/src/linux/Documentation/networking/ethertap.txt for
+         information on how to set up /dev/tap* device nodes and activate the
+         ethertap interface. Under MacOS, select an IP address that is on the
+         virtual network and set the default gateway to the IP address of the
+         ethertap interface. This approach will let you access all networks
+         that your Linux box has access to (especially, if your Linux box has
+         a dial-up Internet connection and is configured for IP masquerading,
+         you can access the Internet from MacOS). The drawback is that you
+         can only use network protocols that Linux can route, so you have to
+         install and configure netatalk if you want to use AppleTalk. Here is
+         an example /etc/atalk/atalkd.conf for a LAN:
+
+           eth0 -seed -phase 2 -net 1 -addr 1.47 -zone "Ethernet"
+           tap0 -seed -phase 2 -net 2 -addr 2.47 -zone "Basilisknet"
+
+         (the "47" is an arbitrary node number). This will set up a zone
+         "Ethernet" (net 1) for the Ethernet and a zone "Basilisknet" (net 2)
+         for the internal network connection of the ethertap interface.
+         MacOS should automatically recognize the nets and zones upon startup.
+         If you are in an existing AppleTalk network, you should contact
+         your network administrator about the nets and zones you can use
+         (instead of the ones given in the example above).
 
   AmigaOS:
     You have to specify the name of the SANA-II Ethernet device and the device
@@ -458,7 +416,9 @@ frameskip <frames to skip>
   For refreshed graphics modes (usually window modes), this specifies
   how many frames to skip after drawing one frame. Higher values make
   the video display more responsive but require more processing power.
-  The default is "8".
+  The default is "8". Under Unix/X11, a value of "0" selects a "dynamic"
+  update mode that cuts the display into rectangles and updates each
+  rectangle individually, depending on display changes.
 
 modelid <MacOS model ID>
 
@@ -497,7 +457,7 @@ System-specific configuration
 Unix:
 
   keycodes <"true" or "false">
-  keycodefile <Keycode file path>
+  keycodefile <keycodes file path>
 
     By default, the X11 event handler in Basilisk II uses KeySyms to
     translate keyboard event to Mac keycodes. While this method is very
@@ -508,10 +468,29 @@ Unix:
     not on the selected keymap. Unfortunately it depends on the X server
     being used and possibly also on the type of keyboard attached. So
     Basilisk II needs a table to translate X keycodes to Mac keycodes.
-    This table is read by default from /usr/local/lib/basilisk_ii_keycodes
+    This table is read by default from /usr/local/share/BasiliskII/keycodes
     unless you specify a different file with the "keycodefile" item.
-    A sample keycode file ("basilisk_ii_keycodes") is included with
-    Basilisk II.
+    A sample keycode file is included with Basilisk II.
+
+  fbdevicefile <fbdevices file path>
+
+    This option specifies the file that contains frame buffer device
+    specifications for the fbdev-DGA video mode (when Basilisk II was
+    configured with --enable-fbdev-dga). The default location of the file
+    is /usr/local/share/BasiliskII/fbdevices. A sample file is included
+    with Basilisk II.
+
+  mousewheelmode <mode>
+
+    If you have a mouse with a wheel, this option specifies whether moving
+    the wheel will be reported to the MacOS as "Page up/down" (mode 0) or
+    "Cursor up/down" (mode 1) keys.
+
+  mousewheellines <number of lines>
+
+    If "mousewheelmode" is set to mode 1 (Cursor up/down), this option sets
+    the number of key events sent to MacOS for each wheel movement (the
+    number of lines to scroll).
 
 AmigaOS:
 
@@ -552,15 +531,42 @@ Windows:
   
     Note the use of quotes.
 
-  disablescsi <"Vendor"> <"Model">
+  rightmouse <0/1>
 
-    Disables this vendor/model combination. You may need this simply because
-    you have more than 6 SCSI devices, or the particular device has problems
-    under BasiliskII. E.g.
+    Defines what the right mouse button is used for. The default values of 0
+    means that it is used to move windowed mode BasiliskII screen.
+    Value 1 sends a combination Control and mouse click to the MacOS.
+    This may be useful under OS versions 8 and above.
 
-      disablescsi "HP" "CD-Writer+ 7100"
-  
-    Again, note the use of quotes.
+  keyboardfile <path>
+
+    Defines the path of the customized keyboard code file.
+
+  pollmedia <"true" or "false">
+
+    If true (default), tries to automatically detect new media.
+    Applies to all "floppy", "cd" or "disk" removable media except
+    1.44 MB floppies. May cause modest slow down. If unchecked, 
+    use Ctrl-Shift-F11 to manually mount new media.
+    If you have auto-insert notification (AIN) enabled, you may turn this
+    option off. Note that some CD related software require AIN,
+    and some other need it to be turned off. Consult the documentation
+    of your CD software to learn which one is optimal for you.
+
+  framesleepticks <milliseconds>    
+
+    The amount of time between video frames.
+
+  showfps <true/false>
+
+    If true, the real frame rate is displayed.
+
+  stickymenu <true/false>
+
+    If true, the main menu bar is kept open even after the mouse button is released,
+    under all OS versions (OS 8 has this feature already). There are extensions to do 
+    the same thing, but it's faster to handle this in native code.
+    Default is "true".
 
   ntdx5hack <"true" or "false">
 
@@ -652,17 +658,22 @@ Please see the included file "TECH" for
 Acknowledgements
 ----------------
 
-Contributions by:
- - Bernd Schmidt <crux@pool.informatik.rwth-aachen.de>: UAE 68k emulation
- - Marc Hellwig <Marc.Hellwig@uni-mainz.de>: audio output, BeOS video code
-   and networking
- - Lauri Pesonen <lpesonen@nic.fi>: Windows NT port
+Contributions by (in alphabetical order):
  - Orlando Bassotto <future@powercube.mediabit.net>: FreeBSD support
- - Brian J. Johnson <bjohnson@sgi.com>: IRIX support
+ - Gwenole Beauchesne <gb@dial.oleane.com>: SPARC assembly optimizations and
+   fbdev video code
  - Marc Chabanas <Marc.Chabanas@france.sun.com>: Solaris sound support
+ - Marc Hellwig <Marc.Hellwig@uni-mainz.de>: audio output, BeOS video code
+   and networking
  - Bill Huey <billh@mag.ucsd.edu>: 15/16 bit DGA and 15/16/32 bit X11
    window support
+ - Brian J. Johnson <bjohnson@sgi.com>: IRIX support
+ - Jürgen Lachmann <juergen_lachmann@t-online.de>: AmigaOS CyberGraphX support
+ - Samuel Lander <blair_sp@hotmail.com>: tile-based window refresh code
  - David Lawrence <davidl@jlab.org>: incremental window refresh code
+ - Lauri Pesonen <lpesonen@nic.fi>: Windows NT port
+ - Bernd Schmidt <crux@pool.informatik.rwth-aachen.de>: UAE 68k emulation
+ - and others...
 
 Special thanks to:
  - Bernd Schmidt for letting me use his UAE 68k emulation