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.19 by cebix, 2001-03-29T14:20:52Z vs.
Revision 1.39 by gbeauche, 2005-05-13T09:33:51Z

# Line 2 | Line 2
2    Basilisk II
3    A 68k Macintosh emulator
4  
5 <  Copyright (C) 1997-2001 Christian Bauer et al.
5 >  Copyright (C) 1997-2004 Christian Bauer et al.
6  
7  
8   License
# Line 22 | Line 22 | 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, NetBSD 1.4.2 and
25 >  - Unix (tested under Linux, Solaris 2.x, FreeBSD 3.x, NetBSD 1.4.x and
26      IRIX 6.5)
27    - AmigaOS 3.x
28    - Windows NT 4.0 (mostly works under Windows 95/98, too)
29 +  - Mac OS X 10.1, 10.2
30  
31   Some features of Basilisk II:
32    - Emulates either a Mac Classic (which runs MacOS 0.x thru 7.5)
# Line 68 | Line 69 | The settings are stored in a text file:
69   BeOS:
70    /boot/home/config/settings/BasiliskII_prefs
71  
72 < Unix:
72 > Unix, Mac OS X:
73    ~/.basilisk_ii_prefs
74  
75   AmigaOS:
# Line 94 | Line 95 | disk <volume description>
95    This item describes one MacOS volume to be mounted by Basilisk II.
96    There can be multiple "disk" lines in the preferences file. Basilisk II
97    can handle hardfiles (byte-per-byte images of HFS volumes in a file on
98 <  the host system) as well as HFS partitions on hard disks etc. (but Basilisk
99 <  II doesn't know about MacOS partition tables; it relies on the host OS to
100 <  handle this). The "volume description" is either the pathname of a hardfile
101 <  or a platform-dependant description of an HFS partition or drive. If the
102 <  volume description starts with an asterisk ("*"), the volume is write
103 <  protected for MacOS (and the "*" is discarded).
98 >  the host system), HFS partitions on hard disks etc., and MacOS-partitioned
99 >  disks (it can only access the first partition, though). The "volume
100 >  description" is either the pathname of a hardfile or a platform-dependant
101 >  description of an HFS partition or drive. If the volume description is
102 >  prefixed by an asterisk ("*"), the volume is write protected for MacOS.
103 >
104 >  Basilisk II can also handle some types of Mac "disk image" files directly,
105 >  as long as they are uncompressed and unencoded.
106  
107    BeOS:
108      To specify an HFS partition, simply specify its path (e.g.
109 <    "/dev/disk/scsi/0/1/0/0_3"). If you don't specify any volume, Basilisk II
109 >    "/dev/disk/scsi/0/1/0/0_3"). If you don't specify any volumes, Basilisk II
110      will search for and use all available HFS partitions.
111  
112    Unix:
113 <    To specify an HFS partition, simply specify its path (e.g.
114 <    "/dev/sda5").
113 >    To specify an HFS partition, simply specify its path (e.g. "/dev/sda5").
114 >    If you want to access a MacOS-partitioned hard disk or removable volume
115 >    (Jaz, Zip etc.) and your operating system doesn't understand MacOS
116 >    partition tables, you can specify the block device name (e.g. "/dev/sda")
117 >    to access the first HFS partition on the device. Under Linux, if you
118 >    don't specify any volumes, Basilisk II will search /etc/fstab for
119 >    unmounted HFS partitions and use these.
120  
121    AmigaOS:
122      Partitions/drives are specified in the following format:
# Line 146 | Line 154 | extfs <direcory path>
154    This item specifies the root directory for the "Host Directory Tree"
155    file system (the "Unix/BeOS/Amiga/..." icon on the Finder desktop).
156    All objects contained in that directory are accessible by Mac applications.
157 +
158    This feature is only available when File System Manager V1.2 or later
159    is installed on the Mac side. FSM 1.2 is built-in beginning with MacOS 7.6
160    and can be installed as a system extension (downloadable from Apple, look
# Line 185 | Line 194 | scsi0 <SCSI target> ... scsi6 <SCSI targ
194  
195   screen <video mode>
196  
197 <  This item describes the type of video display to be used by Basilisk II.
198 <  If you are using a Mac Classic ROM, the display is always 1-bit 512x342
199 <  and this item is ignored. The format of the "video mode" is platform
200 <  specific.
197 >  This item describes the type of video display to be used by default for
198 >  Basilisk II. If you are using a Mac Classic ROM, the display is always
199 >  1-bit 512x342 and this item is ignored. The format of the "video mode" is
200 >  platform specific.
201  
202    BeOS:
203      The "video mode" is one of the following:
# Line 208 | Line 217 | screen <video mode>
217    Unix:
218      The "video mode" is one of the following:
219        win/<width>/<height>
220 <        Color display in an X11 window of the given size. The color depth
221 <        (8/15/24 bit) depends on the depth of the underlying X11 screen.
222 <        This is the default.
220 >        Color display in an X11 window of the given size. There are several
221 >        resolutions and color depths available. The set of color depths
222 >        depends on the capabilities of the X11 server, the operating system,
223 >        and Basilisk II compile-time options, but 1 bit and the default depth
224 >        of the X11 screen should always be available.
225        dga/<width>/<height>
226          [if Basilisk II was configured with --enable-xf86-dga]
227          Full-screen display using the XFree86 DGA extension. The color depth
# Line 274 | Line 285 | screen <video mode>
285      application via Alt-Tab, Basilisk II is put in "snooze" mode (i.e. MacOS
286      is frozen).
287  
288 +  Mac OS X:
289 +    The "video mode" is one of the following:
290 +      win/<width>/<height>
291 +      win/<width>/<height>/<bits per pixel>
292 +        A refreshed (and buffered) Quartz window.
293 +      full/<width>/<height>
294 +      full/<width>/<height>/<bits per pixel>
295 +        A CGDirectDisplay full screen mode. <bits> can currently be 8, 16 or 32.
296 +        If not specified, the default is 32. There is currently no way to switch
297 +        between the Mac OS X and Basilisk II display, but Apple-Option-Escape
298 +        instantly and safely terminates the Basilisk II program.
299 +
300   seriala <serial port description>
301  
302    This item describes the serial port to be used as Port A (Modem Port)
# Line 324 | Line 347 | ether <ethernet card description>
347    is not available and this setting is ignored. The "ethernet card description"
348    is a platform-dependant description of an ethernet card.
349  
350 +  General note: To use TCP/IP from MacOS, you should assign a different IP
351 +  address to the MacOS (entered into the MacOS TCP/IP (or MacTCP) control
352 +  panel). Otherwise there will be confusion about which operating system will
353 +  handle incoming packets.
354 +
355    BeOS:
356      It doesn't matter what you give as "ethernet card description", Basilisk II
357      will always use the first Ethernet card it finds as long an an "ether"
# Line 334 | Line 362 | ether <ethernet card description>
362  
363    Linux:
364      The "ethernet card description" is the name of an Ethernet interface.
365 <    There are two approaches to networking with Basilisk II:
365 >    There are four approaches to networking with Basilisk II:
366  
367 <      1. Direct access to an Ethernet card via the "sheep_net" driver.
368 <         In this case, the "ethernet card description" must be the name
369 <         of a real Ethernet card, e.g. "eth0". It also requires the "sheep_net"
370 <         driver to be installed and accessible. This approach will allow you
371 <         to run all networking protocols under MacOS (TCP/IP, AppleTalk, IPX
372 <         etc.) but there is no connection between Linux networking and MacOS
373 <         networking. MacOS will only be able to talk to other machines on
374 <         the Ethernet, but not to other networks that your Linux box routes
375 <         (e.g. a second Ethernet or a PPP connection to the Internet).
367 >      1. Direct access to an Ethernet card via the "sheep_net" kernel module.
368 >         The "ethernet card description" must be the name of a real Ethernet
369 >         card, e.g. "eth0".
370 >
371 >         The sheep_net module is included in the Basilisk II source
372 >         distribution in the directory "src/Unix/Linux/NetDriver". You have
373 >         to compile and install the module yourself:
374 >
375 >           $ su
376 >           [enter root password]
377 >           # make
378 >           # make dev
379 >           [this will create a /dev/sheep_net device node; you should give
380 >            appropriate access rights to the user(s) running Basilisk II]
381 >           # insmod sheep_net.o
382 >
383 >         If you copy the sheep_net.o module to a place where it can be found
384 >         by the kernel module loader ("/lib/modules/<version>/kernel/drivers/net"
385 >         for 2.4 kernels) and add the line
386 >
387 >           alias char-major-10-198 sheep_net
388 >
389 >         to "/etc/modules.conf", the kernel should be able to load the module
390 >         automatically when Basilisk II is started.
391 >
392 >         The sheep_net module will allow you to run all networking protocols
393 >         under MacOS (TCP/IP, AppleTalk, IPX etc.) but there is no connection
394 >         between Linux networking and MacOS networking. MacOS will only be
395 >         able to talk to other machines on the Ethernet, but not to other
396 >         networks that your Linux box routes (e.g. a second Ethernet or a PPP
397 >         connection to the Internet).
398  
399        2. Putting Basilisk II on a virtual Ethernet via the "ethertap" device.
400           In this case, the "ethernet card description" must be the name
401           of an ethertap interface, e.g. "tap0". It also requires that you
402 <         configure your kernel to enable routing and the ethertap device:
402 >         configure your kernel to enable routing and ethertap support:
403           under "Networking options", enable "Kernel/User netlink socket" and
404           "Netlink device emulation", under "Network device support", activate
405           "Ethertap network tap". You also have to modify drivers/net/ethertap.c
# Line 382 | Line 432 | ether <ethernet card description>
432           your network administrator about the nets and zones you can use
433           (instead of the ones given in the example above).
434  
435 +      3. Access the network through a "tuntap" interface.
436 +         The "ethernet card description" must be set to "tun".
437 +
438 +         TUN/TAP provides packet reception and transmission for user
439 +         space programs.  It can be viewed as a simple Point-to-Point
440 +         or Ethernet device, which instead of receiving packets from a
441 +         physical media, receives them from user space program and
442 +         instead of sending packets via physical media writes them to
443 +         the user space program.
444 +
445 +         A virtual network configuration script is required and the
446 +         default is /usr/local/BasiliskII/tunconfig unless you specify
447 +         a different file with the "etherconfig" item.
448 +
449 +         This script requires you that "sudo" is properly configured
450 +         so that "/sbin/ifconfig" and "/sbin/iptables" can be executed
451 +         as root. Otherwise, you can still write a helper script which
452 +         invokes your favorite program to enhance a user priviledges.
453 +         e.g. in a KDE environment, kdesu can be used as follows:
454 +
455 +           #!/bin/sh
456 +           exec /usr/bin/kdesu -c /path/to/tunconfig $1 $2
457 +
458 +      4. Access the network through the user mode network stack.
459 +         (the code and this documentation come from QEMU)
460 +
461 +         By setting the "ethernet card description" to "slirp",
462 +         Basilisk II uses a completely user mode network stack (you
463 +         don't need root priviledges to use the virtual network). The
464 +         virtual network configuration is the following:
465 +
466 +           Basilisk II <------> Firewall/DHCP server <-----> Internet
467 +           (10.0.2.x)      |         (10.0.2.2)
468 +                           |
469 +                           ----> DNS server (10.0.2.3)
470 +                           |
471 +                           ----> SMB server (10.0.2.4)
472 +
473 +         Basilisk II behaves as if it was behind a firewall which
474 +         blocks all incoming connections. You can use a DHCP client to
475 +         automatically configure the network in Basilisk II.
476 +
477 +         In order to check that the user mode network is working, you
478 +         can ping the address 10.0.2.2 and verify that you got an
479 +         address in the range 10.0.2.x from the Basilisk II virtual
480 +         DHCP server.
481 +
482 +         Note that ping is not supported reliably to the internet as
483 +         it would require root priviledges. It means you can only ping
484 +         the local router (10.0.2.2).
485 +
486 +         When using the built-in TFTP server, the router is also the
487 +         TFTP server.
488 +
489    FreeBSD:
490      The "ethertap" method described above also works under FreeBSD, but since
491      no-one has found the time to write a section for this manual, you're on
# Line 394 | Line 498 | ether <ethernet card description>
498      not an Ethernet device, Basilisk II will display a warning message and
499      disable Ethernet networking.
500  
501 +  See the next item for an alternative way to do networking with Basilisk II.
502 +
503 + udptunnel <"true" or "false">
504 +
505 +  Setting this to "true" enables a special network mode in which all network
506 +  packets sent by MacOS are tunnelled over UDP using the host operating
507 +  system's native TCP/IP stack. This can only be used to connect computers
508 +  running Basilisk II (and not, for example, for connecting to the Internet
509 +  or an AppleShare server running on a real Mac), but it is probably the
510 +  easiest way to set up a network between two instances of Basilisk II
511 +  because the UDP tunnelling doesn't require any special kernel modules or
512 +  network add-ons. It relies on IP broadcasting, however, so its range is
513 +  limited. It should be fine though for doing a little file sharing or
514 +  playing Spectre.
515 +
516 + udpport <IP port number>
517 +
518 +  This item specifies the IP port number to use for the "UDP Tunnel" mode.
519 +  The default is 6066.
520 +
521   rom <ROM file path>
522  
523    This item specifies the file name of the Mac ROM file to be used by
# Line 428 | Line 552 | frameskip <frames to skip>
552  
553   modelid <MacOS model ID>
554  
555 <  Specifies the Model ID that Basilisk II should report to MacOS.
556 <  The default is "5" which corresponds to a Mac IIci. If you want to
557 <  run MacOS 8, you have to set this to "14" (Quadra 900). Other values
558 <  are not officially supported and may result in crashes. MacOS versions
559 <  earlier than 7.5 may only run with the Model ID set to "5". If you are
560 <  using a Mac Classic ROM, the model is always "Mac Classic" and this
561 <  setting is ignored.
555 >  Specifies the Macintosh model ID that Basilisk II should report to MacOS.
556 >  The default is "5" which corresponds to a Mac IIci. If you want to run
557 >  MacOS 8, you have to set this to "14" (Quadra 900). Other values are not
558 >  officially supported and may result in crashes. MacOS versions earlier
559 >  than 7.5 may only run with the Model ID set to "5". If you are using a Mac
560 >  Classic ROM, the model is always "Mac Classic" and this setting is
561 >  ignored.
562  
563   nosound <"true" or "false">
564  
# Line 454 | Line 578 | nogui <"true" or "false">
578    error alerts. All errors will then be reported to stdout. The default
579    is "false".
580  
581 + keyboardtype <keyboard-id>
582 +
583 +  Specifies the keyboard type that BasiliskII should report to the MacOS.
584 +  The default is "5" which is a "Apple Extended Keyboard II (ISO)",
585 +  but many other numbers are understood by most versions of the MacOS
586 +  (e.g. 11 is a "Macintosh Plus Keyboard with keypad",
587 +        13 is a "Apple PowerBook Keyboard (ISO)" )
588 +
589   For additional information, consult the source.
590  
591  
# Line 498 | Line 630 | Unix:
630      the number of key events sent to MacOS for each wheel movement (the
631      number of lines to scroll).
632  
633 +  ignoresegv <"true" or "false">
634 +
635 +    Set this to "true" to ignore illegal memory accesses. The default
636 +    is "false". This feature is only implemented on the following
637 +    platforms: Linux/x86, Linux/ppc, Darwin/ppc.
638 +
639 +  dsp <device name>
640 +  mixer <device name>
641 +
642 +    Under Linux and FreeBSD, this specifies the devices to be used for sound
643 +    output and volume control, respectively. The defaults are "/dev/dsp" and
644 +    "/dev/mixer".
645 +
646   AmigaOS:
647  
648    sound <sound output description>
# Line 508 | Line 653 | AmigaOS:
653  
654        ahi/<hexadecimal mode ID>
655  
656 +  scsimemtype <type>
657 +
658 +    This item controls the type of memory to use for SCSI buffers. Possible
659 +    values are:
660 +      0 Chip memory
661 +      1 24-bit DMA capable memory
662 +      2 Any memory
663 +
664 +    Be warned that many SCSI host adapters will not work with the "Any memory"
665 +    setting. Basilisk II has no way of knowing which memory type is supported
666 +    by the host adapter and setting an unsupported type will result in data
667 +    corruption.
668 +
669   Windows:
670  
671    noscsi <"true" or "false">
# Line 518 | Line 676 | Windows:
676      means is that the control is not returned to the application until the
677      command is completely finished. Normally this is not an issue, but when a
678      CDR/CDRW is closed or erased the burner program typically wants to wait in
679 <    some progress dialog The result may be that the application reports a
679 >    some progress dialog the result may be that the application reports a
680      time-out error, but the operation completes all right anyway.
681  
682    nofloppyboot <"true" or "false">
# Line 532 | Line 690 | Windows:
690      This is very useful since many devices have almost identical ATAPI and SCSI
691      versions of their hardware, and MacOS applications usually support the SCSI
692      version only. The example below is typical:
693 <  
693 >
694        replacescsi "HP" "CD-Writer+ 7100" "PHILIPS" "CDD3600"
695 <  
695 >
696      Note the use of quotes.
697  
698    rightmouse <0/1>
# Line 559 | Line 717 | Windows:
717      and some other need it to be turned off. Consult the documentation
718      of your CD software to learn which one is optimal for you.
719  
720 <  framesleepticks <milliseconds>    
720 >  framesleepticks <milliseconds>
721  
722      The amount of time between video frames.
723  
# Line 569 | Line 727 | Windows:
727  
728    stickymenu <true/false>
729  
730 <    If true, the main menu bar is kept open even after the mouse button is released,
731 <    under all OS versions (OS 8 has this feature already). There are extensions to do
732 <    the same thing, but it's faster to handle this in native code.
733 <    Default is "true".
730 >    If true, the main menu bar is kept open even after the mouse button is
731 >    released, under all OS versions (OS 8 has this feature already). There
732 >    are extensions to do the same thing, but it's faster to handle this in
733 >    native code. Default is "true".
734  
735    ntdx5hack <"true" or "false">
736  
737 <    You may need this on NT if your display adapter driver has a bug in DirectX
738 <    palette support. Black and white are reversed. It fixes the palette issue
739 <    by using GDI palette instead of D3D palette. Default is false.
737 >    You may need this on NT if your display adapter driver has a bug in
738 >    DirectX palette support. Black and white are reversed. It fixes the
739 >    palette issue by using GDI palette instead of D3D palette. Default is
740 >    false.
741 >
742 >
743 > JIT-specific configuration
744 > --------------------------
745 >
746 > A Just-In-Time (JIT) translation engine is available for x86. This is
747 > aimed at translating 68040 instructions to native equivalent code
748 > sequences, thus providing faster emulation speeds.
749 >
750 >  jit <"true" or "false">
751 >
752 >    Set this to "true" to enable the JIT compiler. Default value is
753 >    "true" if the JIT compiler was compiled in. Besides, this is
754 >    effective only if Basilisk II is configured to emulate a 68040.
755 >
756 >  jitfpu <"true" or "false">
757 >
758 >    Set this to "true" to enable translation of floating-point (FPU)
759 >    instructions. Default is "true".
760 >
761 >  jitcachesize <size>
762 >
763 >    Allocate "size" kilobytes of RAM for the translation cache. The
764 >    value given will be rounded down to the nearest multiple of a page
765 >    size. Minimal value is "2048" (2MB). Default value is "8192" (8MB).
766 >
767 >  jitlazyflush <"true" or "false">
768 >
769 >    Set this to "true" to enable lazy invalidation of the translation
770 >    cache. This is always recommended as it usually makes the system
771 >    more responsive and faster, especially while running MacOS
772 >    8.X. Default value is "true".
773 >
774 >  jitdebug <"true" or "false">
775 >
776 >    Set this to "true" to enable the JIT debugger. This requires a
777 >    build of Basilisk II with the cxmon debugger. Default is "false".
778  
779  
780   Usage
# Line 603 | Line 799 | Keyboard:
799    On PC-style keyboards, "Alt" is the Mac "Command" key, while the "Windows"
800    key is the Mac "Option" key.
801  
802 + Mouse:
803 +  Under Unix, pressing Ctrl-F5 while the Basilisk II window is active will
804 +  grab the mouse. This is needed for compatibility with some MacOS programs,
805 +  especially games such as flight simulators. Press Ctrl-F5 again to return
806 +  to normal mouse operation.
807 +
808   Floppy:
809    Basilisk II can only handle 1.44MB MFM floppies. Depending on your platform,
810 <  flopyy disk changes might not be detected automatically. Under Linux, press
810 >  floppy disk changes might not be detected automatically. Under Unix, press
811    Ctrl-F1 to mount a floppy. Under BeOS, select the appropriate "Mount" menu
812    item or press Ctrl-F1 to mount a floppy. Under Windows, press Ctrl-Shift-F11.
813  
814   HFS partitions:
815    Having HFS partitions mounted for read-write access under Basilisk II while
816    they are also mounted on the host OS will most likely result in volume
817 <  corruption and data losses. Unmount your HFS volumes before starting
817 >  corruption and data loss. Unmount your HFS volumes before starting
818    Basilisk II.
819  
820   ZIP drives:
# Line 631 | Line 833 | Mac Classic emulation:
833    ROM. Also, the video display is fixed to 512x342 in monochrome. The AmigaOS
834    and BeOS/PPC versions of Basilisk II cannot do Mac Classic emulation.
835  
836 + Video resolution switching:
837 +  Run-time switching of video resolutions requires the Display Manager. This
838 +  is included in MacOS versions 7.6 and above, and available as a system
839 +  extension for earlier MacOS versions as a free download from ftp.apple.com
840 +  (look for "Display Software 2.x"). Click on "Options..." in the "Monitors"
841 +  control panel to select the resolution.
842 +
843   Sound output:
844    Sound output under Basilisk II requires Sound Manager 3.0 or later. This
845 <  is included starting with MacOS 7.5 and available as a system extension
846 <  for earlier MacOS versions. Sample rate, bit resolution and mono/stereo
847 <  can be selected in the Sound control panel (section "Sound Out").
845 >  is included in MacOS versions 7.5 and above, and available as a system
846 >  extension for earlier MacOS versions as a free download from ftp.apple.com.
847 >  Sample rate, bit resolution and mono/stereo can be selected in the Sound
848 >  control panel (section "Sound Out").
849  
850   Ethernet:
851    Basilisk II supports all Ethernet protocols. Running a protocol under
852    Basilisk II that already runs within the host operating system on the same
853    network card (e.g. running MacTCP under Basilisk II on a BeOS machine) may
854    or may not work (generally, it should work, but some specific things like
855 <  "ping" may not). If you have problems with FTP, try setting your FTP client
855 >  "ping" may not). If you have problems with FTP, try setting the FTP client
856    to passive mode.
857  
858   LocalTalk:
# Line 652 | Line 862 | LocalTalk:
862  
863   Serial:
864    You can use the serial ports in Basilisk II to connect to the Internet
865 <  with a modem and "MacPPP".
865 >  with a modem and the "MacPPP" or "Open Transport/PPP" software.
866  
867  
868   Technical Documentation
# Line 666 | Line 876 | Acknowledgements
876  
877   Contributions by (in alphabetical order):
878   - Orlando Bassotto <future@powercube.mediabit.net>: FreeBSD support
879 < - Gwenole Beauchesne <gb@dial.oleane.com>: SPARC assembly optimizations and
880 <   fbdev video code
879 > - Gwenolé Beauchesne <gb@dial.oleane.com>: SPARC assembly optimizations,
880 >   lots of work on the Unix video code, fixes and improvements to the
881 >   JIT compiler
882   - Marc Chabanas <Marc.Chabanas@france.sun.com>: Solaris sound support
883   - Marc Hellwig <Marc.Hellwig@uni-mainz.de>: audio output, BeOS video code
884     and networking
# Line 677 | Line 888 | Contributions by (in alphabetical order)
888   - Jürgen Lachmann <juergen_lachmann@t-online.de>: AmigaOS CyberGraphX support
889   - Samuel Lander <blair_sp@hotmail.com>: tile-based window refresh code
890   - David Lawrence <davidl@jlab.org>: incremental window refresh code
891 + - Bernie Meyer <bmeyer@csse.monash.edu.au>: original UAE-JIT code
892 + - Nigel Pearson <nigel@ind.tansu.com.au>: Mac OS X port
893   - Lauri Pesonen <lpesonen@nic.fi>: Windows NT port
894   - Bernd Schmidt <crux@pool.informatik.rwth-aachen.de>: UAE 68k emulation
895 + - Michael Z. Sliczniak <msliczniak@comcast.net>: Mach memory fault recovery
896   - and others...
897  
898   Special thanks to:
# Line 696 | Line 910 | You found a bug? Well, use the source, f
910    <Christian.Bauer@uni-mainz.de>
911   for inclusion in the next release of Basilisk II.
912  
913 + If you don't have a fix, you should post a bug report using the Source Forge
914 + bug tracker, supplying as much information as possible (operating system and
915 + versions of Basilisk II and MacOS being used, relevant hardware information,
916 + the exact steps to reproduce the bug, etc.):
917 +  http://sourceforge.net/tracker/?group_id=2123&atid=102123
918 +
919 + I also strongly suggest reading this before posting a bug report:
920 +  http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
921 +
922  
923   Author
924   ------
925  
926 < You can contact me at <Christian.Bauer@uni-mainz.de>. Don't send bug
927 < reports, send fixes. Ports to other platforms are also very welcome.
928 < Please contact me before you intend to make major changes to the source.
929 < You might be working on something that I have already done or I may have
930 < different ideas about the Right Way to do it.
931 <
932 < Questions about ROM files will not be answered. There is also no point in
933 < sending me questions etc. that are specific to the Windows port of
934 < Basilisk II. I don't have Windows and can't say anything about that.
935 < Ask Lauri Pesonen instead.
926 > You can contact me at <Christian.Bauer@uni-mainz.de>, but please don't do
927 > so unless absolutely necessary. I'm maintaining Basilisk II in my spare
928 > time and am not able to provide technical support for everyone. If you have
929 > questions, consider posting them to one of the support forums mentioned
930 > below.
931 >
932 > You are encouraged to contact me personally when
933 > - you have bug fixes or small enhancements for the code
934 > - you want to port Basilisk II to another platform
935 > - you want to discuss technical issues
936 > - you intend to make major changes to the source; you might be working on
937 >   something that I have already done, or I may have different ideas about
938 >   the Right Way to do it
939 >
940 > There is no point in sending me questions about
941 > - ROM files and how/where to get them
942 > - versions of Basilisk II that run on operating systems other than Unix,
943 >   BeOS and AmigaOS. If you are using any other operating system, there's
944 >   no point in asking me how to to X or why Y doesn't work because I won't
945 >   know either. Instead, you should look in the "Acknowledgements" section
946 >   of this manual to find the person responsible. For example, if your
947 >   question is specific to the Windows operating system, ask Lauri Pesonen.
948 >   I don't have Windows and can't answer your questions and I'm too lazy to
949 >   forward mail to Lauri myself. In any case, it would probably be better
950 >   to post your questions to a public forum as it will get a much wider
951 >   audience there.
952  
953  
954   Support
# Line 718 | Line 957 | Support
957   The official Basilisk II home page is at
958    http://www.uni-mainz.de/~bauec002/B2Main.html
959  
960 < There is no user-level support for Basilisk II at the moment.
960 > The Basilisk II project page on SourceForge is at
961 >  http://sourceforge.net/projects/basilisk/
962 >
963 > If you have problems, you may want to visit the Basilisk II forums:
964 >  http://sourceforge.net/forum/?group_id=2123
965 >
966 > There is also a mailing list for Basilisk II users:
967 >  http://lists.sourceforge.net/lists/listinfo/basilisk-user
968 >
969 > And another mailing list for Basilisk II developers:
970 >  http://lists.sourceforge.net/lists/listinfo/basilisk-devel
971 >
972 > Some general advice about asking technical support questions can be found at
973 >  http://www.tuxedo.org/~esr/faqs/smart-questions.html
974 >
975 > Keeping this in mind will greatly increase your chances of getting a useful
976 > answer.
977  
978  
979   History

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines