ViewVC Help
View File | Revision Log | Show Annotations | Revision Graph | Root Listing
root/cebix/BasiliskII/README
(Generate patch)

Comparing BasiliskII/README (file contents):
Revision 1.5 by cebix, 1999-10-04T22:37:53Z vs.
Revision 1.18 by cebix, 2001-02-10T20:58:03Z

# Line 1 | Line 1
1  
2 <        Basilisk II, Version 0.7
3 <        A free, portable Mac II emulator
2 >  Basilisk II
3 >  A 68k Macintosh emulator
4  
5 <        Copyright (C) 1997-1999 Christian Bauer et al.
6 <        Freely distributable
5 >  Copyright (C) 1997-2001 Christian Bauer et al.
6  
7  
8   License
# Line 16 | Line 15 | See the file "COPYING" that is included
15   Overview
16   --------
17  
18 < Basilisk II is a free, portable, Open Source 68k Mac emulator. It requires
19 < a copy of a Mac ROM and a copy of MacOS to run. Basilisk II is freeware and
20 < distributed under the GNU General Public License.
18 > Basilisk II is an Open Source 68k Macintosh emulator. That is, it enables
19 > you to run 68k MacOS software on you computer, even if you are using a
20 > different operating system. However, you still need a copy of MacOS and
21 > a Macintosh ROM image to use Basilisk II.
22  
23   Basilisk II has currently been ported to the following systems:
24    - BeOS R4 (PowerPC and x86)
25 <  - Unix (tested under Linux, Solaris 2.5, FreeBSD 3.x and IRIX 6.5)
25 >  - Unix (tested under Linux, Solaris 2.5, FreeBSD 3.x, NetBSD 1.4.2 and
26 >    IRIX 6.5)
27    - AmigaOS 3.x
28    - Windows NT 4.0 (mostly works under Windows 95/98, too)
29  
# Line 35 | Line 36 | Some features of Basilisk II:
36    - Floppy disk driver (only 1.44MB disks supported)
37    - Driver for HFS partitions and hardfiles
38    - CD-ROM driver with basic audio functions
39 +  - Easy file exchange with the host OS via a "Host Directory Tree" icon
40 +    on the Mac desktop
41    - Ethernet driver
42    - Serial drivers
43    - SCSI Manager (old-style) emulation
44    - Emulates extended ADB keyboard and 3-button mouse
45 <  - Uses UAE 68k emulation or (under AmigaOS) real 68k processor
45 >  - Uses UAE 68k emulation or (under AmigaOS and NetBSD/m68k) real 68k
46 >    processor
47  
48   The emulator is not yet complete. See the file "TODO" for a list of
49   unimplemented stuff.
# Line 137 | Line 141 | cdrom <CD-ROM drive description>
141    installed CD-ROM drives. The format of the "CD-ROM drive description"
142    is the same as that of "disk" lines.
143  
144 + extfs <direcory path>
145 +
146 +  This item specifies the root directory for the "Host Directory Tree"
147 +  file system (the "Unix/BeOS/Amiga/..." icon on the Finder desktop).
148 +  All objects contained in that directory are accessible by Mac applications.
149 +  This feature is only available when File System Manager V1.2 or later
150 +  is installed on the Mac side. FSM 1.2 is built-in beginning with MacOS 7.6
151 +  and can be installed as a system extension (downloadable from Apple, look
152 +  for the FSM SDK in the developer section) for earlier MacOS versions.
153 +
154   scsi0 <SCSI target> ... scsi6 <SCSI target>
155  
156    These items describe the SCSI target to be used for a given Mac SCSI
# Line 198 | Line 212 | screen <video mode>
212          (8/15/24 bit) depends on the depth of the underlying X11 screen.
213          This is the default.
214        dga/<width>/<height>
215 <        Full-screen display using the X11 DGA extensions. The color depth
215 >        [if Basilisk II was configured with --enable-xf86-dga]
216 >        Full-screen display using the XFree86 DGA extension. The color depth
217          (8/15/24 bit) depends on the depth of the underlying X11 screen.
218          "width" and "height" specify the maximum width/height to use.
219 <        Saying "dga/0/0" means "complete screen". For DGA to work, Basilisk II
220 <        must be compiled with DGA support enabled (selectable in the configure
221 <        script).
219 >        Saying "dga/0/0" means "complete screen".
220 >      dga/<frame buffer name>
221 >        [if Basilisk II was configured with --enable-fbdev-dga]
222 >        Full-screen display using the frame buffer device /dev/fb. The color
223 >        depth (8/15/24 bit) depends on the depth of the underlying X11 screen.
224 >        The "frame buffer name" is looked up in the "fbdevices" file (whose
225 >        path can be specified with the "fbdevicefile" prefs item) to determine
226 >        certain characteristics of the device (doing a "ls -l /dev/fb" should
227 >        tell you what your frame buffer name is).
228  
229    AmigaOS:
230      The "video mode" is one of the following:
# Line 215 | Line 236 | screen <video mode>
236          15-bit truecolor display in a Picasso96 PIP. This requires
237          Picasso96 as well as a PIP-capable graphics card (e.g. Picasso IV).
238        scr/<hexadecimal mode ID>
239 <        8/15/24-bit fullscreen display on a Picasso96 screen with the given
240 <        mode ID. This requires Picasso96. For 15 and 24 bit, the frame buffer
241 <        format must be QuickDraw-compatible (big-endian, xRGB 1:5:5:5 or
242 <        xRGB 8:8:8:8). The screen size will be the default size for that
243 <        mode ID.
239 >        8/15/24-bit fullscreen display on a Picasso96/CyberGraphX screen with
240 >        the given mode ID. This requires Picasso96 or CyberGraphX. For 15 and
241 >        24 bit, the frame buffer format must be QuickDraw-compatible
242 >        (big-endian, xRGB 1:5:5:5 or xRGB 8:8:8:8). The screen size will be
243 >        the default size for that mode ID.
244  
245    Windows:
246      The "video mode" is one of the following:
# Line 306 | Line 327 | ether <ethernet card description>
327    BeOS:
328      It doesn't matter what you give as "ethernet card description", Basilisk II
329      will always use the first Ethernet card it finds as long an an "ether"
330 <    line exists (e.g. say "ether yes"). As Basilisk II requires the sheep_net
331 <    net server add-on from SheepShaver, you can only use Ethernet on PowerPC
332 <    machines.
330 >    line exists (e.g. say "ether yes"). Using Ethernet requires the "sheep_net"
331 >    Net Server add-on to be installed. The first time you start Basilisk II
332 >    with Ethernet enabled you will be asked whether it's OK to make the
333 >    necessary changes to your BeOS network configuration to enable sheep_net.
334  
335    Linux:
336      The "ethernet card description" is the name of an Ethernet interface.
337      There are two approaches to networking with Basilisk II:
338 +
339        1. Direct access to an Ethernet card via the "sheep_net" driver.
340           In this case, the "ethernet card description" must be the name
341           of a real Ethernet card, e.g. "eth0". It also requires the "sheep_net"
# Line 322 | Line 345 | ether <ethernet card description>
345           networking. MacOS will only be able to talk to other machines on
346           the Ethernet, but not to other networks that your Linux box routes
347           (e.g. a second Ethernet or a PPP connection to the Internet).
348 +
349        2. Putting Basilisk II on a virtual Ethernet via the "ethertap" device.
350           In this case, the "ethernet card description" must be the name
351           of an ethertap interface, e.g. "tap0". It also requires that you
352           configure your kernel to enable routing and the ethertap device:
353           under "Networking options", enable "Kernel/User netlink socket" and
354           "Netlink device emulation", under "Network device support", activate
355 <         "Ethertap network tap". Next, see /usr/src/linux/Documentation/
356 <         networking/ethertap.txt for information on how to set up /dev/tap*
357 <         device nodes and activate the ethertap interface. Under MacOS,
358 <         select an IP address that is on the virtual network and set the
359 <         default gateway to the IP address of the ethertap interface. This
360 <         approach will let you access all networks that your Linux box has
361 <         access to (especially, if your Linux box has a dial-up Internet
362 <         connection and is configured for IP masquerading, you can access
363 <         the Internet from MacOS). The drawback is that you can only use
364 <         network protocols that Linux can route, so you have to install and
365 <         configure netatalk if you want to use AppleTalk.
355 >         "Ethertap network tap". You also have to modify drivers/net/ethertap.c
356 >         a bit before compiling the new kernel:
357 >
358 >          - insert "#define CONFIG_ETHERTAP_MC 1" near the top (after the
359 >            #include lines)
360 >          - comment out the line "dev->flags|=IFF_NOARP;" in ethertap_probe()
361 >
362 >         Next, see /usr/src/linux/Documentation/networking/ethertap.txt for
363 >         information on how to set up /dev/tap* device nodes and activate the
364 >         ethertap interface. Under MacOS, select an IP address that is on the
365 >         virtual network and set the default gateway to the IP address of the
366 >         ethertap interface. This approach will let you access all networks
367 >         that your Linux box has access to (especially, if your Linux box has
368 >         a dial-up Internet connection and is configured for IP masquerading,
369 >         you can access the Internet from MacOS). The drawback is that you
370 >         can only use network protocols that Linux can route, so you have to
371 >         install and configure netatalk if you want to use AppleTalk. Here is
372 >         an example /etc/atalk/atalkd.conf for a LAN:
373 >
374 >           eth0 -seed -phase 2 -net 1 -addr 1.47 -zone "Ethernet"
375 >           tap0 -seed -phase 2 -net 2 -addr 2.47 -zone "Basilisknet"
376 >
377 >         (the "47" is an arbitrary node number). This will set up a zone
378 >         "Ethernet" (net 1) for the Ethernet and a zone "Basilisknet" (net 2)
379 >         for the internal network connection of the ethertap interface.
380 >         MacOS should automatically recognize the nets and zones upon startup.
381 >         If you are in an existing AppleTalk network, you should contact
382 >         your network administrator about the nets and zones you can use
383 >         (instead of the ones given in the example above).
384  
385    AmigaOS:
386      You have to specify the name of the SANA-II Ethernet device and the device
# Line 375 | Line 417 | frameskip <frames to skip>
417    For refreshed graphics modes (usually window modes), this specifies
418    how many frames to skip after drawing one frame. Higher values make
419    the video display more responsive but require more processing power.
420 <  The default is "8".
420 >  The default is "8". Under Unix/X11, a value of "0" selects a "dynamic"
421 >  update mode that cuts the display into rectangles and updates each
422 >  rectangle individually, depending on display changes.
423  
424   modelid <MacOS model ID>
425  
# Line 414 | Line 458 | System-specific configuration
458   Unix:
459  
460    keycodes <"true" or "false">
461 <  keycodefile <Keycode file path>
461 >  keycodefile <keycodes file path>
462  
463      By default, the X11 event handler in Basilisk II uses KeySyms to
464      translate keyboard event to Mac keycodes. While this method is very
# Line 425 | Line 469 | Unix:
469      not on the selected keymap. Unfortunately it depends on the X server
470      being used and possibly also on the type of keyboard attached. So
471      Basilisk II needs a table to translate X keycodes to Mac keycodes.
472 <    This table is read by default from /usr/local/lib/basilisk_ii_keycodes
472 >    This table is read by default from /usr/local/share/BasiliskII/keycodes
473      unless you specify a different file with the "keycodefile" item.
474 <    A sample keycode file ("basilisk_ii_keycodes") is included with
475 <    Basilisk II.
474 >    A sample keycode file is included with Basilisk II.
475 >
476 >  fbdevicefile <fbdevices file path>
477 >
478 >    This option specifies the file that contains frame buffer device
479 >    specifications for the fbdev-DGA video mode (when Basilisk II was
480 >    configured with --enable-fbdev-dga). The default location of the file
481 >    is /usr/local/share/BasiliskII/fbdevices. A sample file is included
482 >    with Basilisk II.
483 >
484 >  mousewheelmode <mode>
485 >
486 >    If you have a mouse with a wheel, this option specifies whether moving
487 >    the wheel will be reported to the MacOS as "Page up/down" (mode 0) or
488 >    "Cursor up/down" (mode 1) keys.
489 >
490 >  mousewheellines <number of lines>
491 >
492 >    If "mousewheelmode" is set to mode 1 (Cursor up/down), this option sets
493 >    the number of key events sent to MacOS for each wheel movement (the
494 >    number of lines to scroll).
495  
496   AmigaOS:
497  
# Line 596 | Line 659 | Please see the included file "TECH" for
659   Acknowledgements
660   ----------------
661  
662 < Contributions by:
600 < - Bernd Schmidt <crux@pool.informatik.rwth-aachen.de>: UAE 68k emulation
601 < - Marc Hellwig <Marc.Hellwig@uni-mainz.de>: audio output, BeOS video code
602 <   and networking
603 < - Lauri Pesonen <lpesonen@nic.fi>: Windows NT port
662 > Contributions by (in alphabetical order):
663   - Orlando Bassotto <future@powercube.mediabit.net>: FreeBSD support
664 < - Brian J. Johnson <bjohnson@sgi.com>: IRIX support
664 > - Gwenole Beauchesne <gb@dial.oleane.com>: SPARC assembly optimizations and
665 >   fbdev video code
666   - Marc Chabanas <Marc.Chabanas@france.sun.com>: Solaris sound support
667 + - Marc Hellwig <Marc.Hellwig@uni-mainz.de>: audio output, BeOS video code
668 +   and networking
669   - Bill Huey <billh@mag.ucsd.edu>: 15/16 bit DGA and 15/16/32 bit X11
670     window support
671 + - Brian J. Johnson <bjohnson@sgi.com>: IRIX support
672 + - Jürgen Lachmann <juergen_lachmann@t-online.de>: AmigaOS CyberGraphX support
673 + - Samuel Lander <blair_sp@hotmail.com>: tile-based window refresh code
674   - David Lawrence <davidl@jlab.org>: incremental window refresh code
675 + - Lauri Pesonen <lpesonen@nic.fi>: Windows NT port
676 + - Bernd Schmidt <crux@pool.informatik.rwth-aachen.de>: UAE 68k emulation
677 + - and others...
678  
679   Special thanks to:
680   - Bernd Schmidt for letting me use his UAE 68k emulation

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines