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.6 by cebix, 1999-10-21T13:19:11Z vs.
Revision 1.10 by cebix, 2000-04-10T18:52:15Z

# Line 1 | Line 1
1  
2 <        Basilisk II, Version 0.7
2 >        Basilisk II, Version 0.8
3          A free, portable Mac II emulator
4  
5 <        Copyright (C) 1997-1999 Christian Bauer et al.
5 >        Copyright (C) 1997-2000 Christian Bauer et al.
6          Freely distributable
7  
8  
# Line 35 | Line 35 | Some features of Basilisk II:
35    - Floppy disk driver (only 1.44MB disks supported)
36    - Driver for HFS partitions and hardfiles
37    - CD-ROM driver with basic audio functions
38 +  - Easy file exchange with the host OS via a "Host Directory Tree" icon
39 +    on the Mac desktop
40    - Ethernet driver
41    - Serial drivers
42    - SCSI Manager (old-style) emulation
# Line 137 | Line 139 | cdrom <CD-ROM drive description>
139    installed CD-ROM drives. The format of the "CD-ROM drive description"
140    is the same as that of "disk" lines.
141  
142 + extfs <direcory path>
143 +
144 +  This item specifies the root directory for the "Host Directory Tree"
145 +  file system (the "Unix/BeOS/Amiga/..." icon on the Finder desktop).
146 +  All objects contained in that directory are accessible by Mac applications.
147 +  This feature is only available when File System Manager V1.2 or later
148 +  is installed on the Mac side. FSM 1.2 is built-in beginning with MacOS 7.6
149 +  and can be installed as a system extension (downloadable from Apple, look
150 +  for the FSM SDK in the developer section) for earlier MacOS versions.
151 +
152   scsi0 <SCSI target> ... scsi6 <SCSI target>
153  
154    These items describe the SCSI target to be used for a given Mac SCSI
# Line 198 | Line 210 | screen <video mode>
210          (8/15/24 bit) depends on the depth of the underlying X11 screen.
211          This is the default.
212        dga/<width>/<height>
213 <        Full-screen display using the X11 DGA extensions. The color depth
213 >        [if Basilisk II was configured with --enable-xf86-dga]
214 >        Full-screen display using the XFree86 DGA extension. The color depth
215          (8/15/24 bit) depends on the depth of the underlying X11 screen.
216          "width" and "height" specify the maximum width/height to use.
217 <        Saying "dga/0/0" means "complete screen". For DGA to work, Basilisk II
218 <        must be compiled with DGA support enabled (selectable in the configure
219 <        script).
217 >        Saying "dga/0/0" means "complete screen".
218 >      dga/<frame buffer name>
219 >        [if Basilisk II was configured with --enable-fbdev-dga]
220 >        Full-screen display using the frame buffer device /dev/fb. The color
221 >        depth (8/15/24 bit) depends on the depth of the underlying X11 screen.
222 >        The "frame buffer name" is looked up in the "fbdevices" file (whose
223 >        path can be specified with the "fbdevicefile" prefs item) to determine
224 >        certain characteristics of the device (doing a "ls -l /dev/fb" should
225 >        tell you what your frame buffer name is).
226  
227    AmigaOS:
228      The "video mode" is one of the following:
# Line 313 | Line 332 | ether <ethernet card description>
332    Linux:
333      The "ethernet card description" is the name of an Ethernet interface.
334      There are two approaches to networking with Basilisk II:
335 +
336        1. Direct access to an Ethernet card via the "sheep_net" driver.
337           In this case, the "ethernet card description" must be the name
338           of a real Ethernet card, e.g. "eth0". It also requires the "sheep_net"
# Line 322 | Line 342 | ether <ethernet card description>
342           networking. MacOS will only be able to talk to other machines on
343           the Ethernet, but not to other networks that your Linux box routes
344           (e.g. a second Ethernet or a PPP connection to the Internet).
345 +
346        2. Putting Basilisk II on a virtual Ethernet via the "ethertap" device.
347           In this case, the "ethernet card description" must be the name
348           of an ethertap interface, e.g. "tap0". It also requires that you
349           configure your kernel to enable routing and the ethertap device:
350           under "Networking options", enable "Kernel/User netlink socket" and
351           "Netlink device emulation", under "Network device support", activate
352 <         "Ethertap network tap". Next, see /usr/src/linux/Documentation/
353 <         networking/ethertap.txt for information on how to set up /dev/tap*
354 <         device nodes and activate the ethertap interface. Under MacOS,
355 <         select an IP address that is on the virtual network and set the
356 <         default gateway to the IP address of the ethertap interface. This
357 <         approach will let you access all networks that your Linux box has
358 <         access to (especially, if your Linux box has a dial-up Internet
359 <         connection and is configured for IP masquerading, you can access
360 <         the Internet from MacOS). The drawback is that you can only use
361 <         network protocols that Linux can route, so you have to install and
362 <         configure netatalk if you want to use AppleTalk.
352 >         "Ethertap network tap". You also have to modify devices/net/ethertap.c
353 >         a bit before compiling the new kernel:
354 >
355 >          - insert "#define CONFIG_ETHERTAP_MC 1" near the top (after the
356 >            #include lines)
357 >          - comment out the line "dev->flags|=IFF_NOARP;" in ethertap_probe()
358 >
359 >         Next, see /usr/src/linux/Documentation/networking/ethertap.txt for
360 >         information on how to set up /dev/tap* device nodes and activate the
361 >         ethertap interface. Under MacOS, select an IP address that is on the
362 >         virtual network and set the default gateway to the IP address of the
363 >         ethertap interface. This approach will let you access all networks
364 >         that your Linux box has access to (especially, if your Linux box has
365 >         a dial-up Internet connection and is configured for IP masquerading,
366 >         you can access the Internet from MacOS). The drawback is that you
367 >         can only use network protocols that Linux can route, so you have to
368 >         install and configure netatalk if you want to use AppleTalk. Here is
369 >         an example /etc/atalk/atalkd.conf for a LAN:
370 >
371 >           eth0 -seed -phase 2 -net 1 -addr 1.47 -zone "Ethernet"
372 >           tap0 -seed -phase 2 -net 2 -addr 2.47 -zone "Basilisknet"
373 >
374 >         (the "47" is an arbitrary node number). This will set up a zone
375 >         "Ethernet" (net 1) for the Ethernet and a zone "Basilisknet" (net 2)
376 >         for the internal network connection of the ethertap interface.
377 >         MacOS should automatically recognize the nets and zones upon startup.
378 >         If you are in an existing AppleTalk network, you should contact
379 >         your network administrator about the nets and zones you can use
380 >         (instead of the ones given in the example above).
381  
382    AmigaOS:
383      You have to specify the name of the SANA-II Ethernet device and the device
# Line 414 | Line 453 | System-specific configuration
453   Unix:
454  
455    keycodes <"true" or "false">
456 <  keycodefile <Keycode file path>
456 >  keycodefile <keycodes file path>
457  
458      By default, the X11 event handler in Basilisk II uses KeySyms to
459      translate keyboard event to Mac keycodes. While this method is very
# Line 425 | Line 464 | Unix:
464      not on the selected keymap. Unfortunately it depends on the X server
465      being used and possibly also on the type of keyboard attached. So
466      Basilisk II needs a table to translate X keycodes to Mac keycodes.
467 <    This table is read by default from /usr/local/lib/basilisk_ii_keycodes
467 >    This table is read by default from /usr/local/share/BasiliskII/keycodes
468      unless you specify a different file with the "keycodefile" item.
469 <    A sample keycode file ("basilisk_ii_keycodes") is included with
470 <    Basilisk II.
469 >    A sample keycode file is included with Basilisk II.
470 >
471 >  fbdevicefile <fbdevices file path>
472 >
473 >    This option specifies the file that contains frame buffer device
474 >    specifications for the fbdev-DGA video mode (when Basilisk II was
475 >    configured with --enable-fbdev-dga). The default location of the file
476 >    is /usr/local/share/BasiliskII/fbdevices. A sample file is included
477 >    with Basilisk II.
478  
479   AmigaOS:
480  
# Line 607 | Line 653 | Contributions by:
653   - Bill Huey <billh@mag.ucsd.edu>: 15/16 bit DGA and 15/16/32 bit X11
654     window support
655   - David Lawrence <davidl@jlab.org>: incremental window refresh code
656 + - Samuel Lander <blair_sp@hotmail.com>: tile-based window refresh code
657   - Gwenole Beauchesne <gb@dial.oleane.com>: SPARC assembly optimizations and
658     fbdev video code
659   - and others...

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines