--- hatari/doc/manual.html 2019/04/01 07:13:55 1.1.1.7 +++ hatari/doc/manual.html 2019/04/01 07:15:04 1.1.1.8 @@ -4,7 +4,7 @@ Hatari User's Manual - + @@ -16,25 +16,23 @@ color:#000000; margin-left:10px; margin-right:10px; - font-family:Verdana,Arial,Helvetica,sans-serif; font-size:12pt; + font-family:Verdana,Arial,Helvetica,sans-serif; } - h1 { font-size:28pt; } - h2 { font-size:22pt; border-bottom:solid thin black;} - h3 { font-size:16pt; } - h4 { font-size:13pt; } + h2 { border-bottom:solid thin black;} + h4.gui { clear:right } - td { font-family:Verdana,Arial,Helvetica,sans-serif; font-size:12pt; } + td { font-family:Verdana,Arial,Helvetica,sans-serif; } a:link { color:#000099; background-color:#ffffff; text-decoration:none; } a:visited { color:#cc0000; background-color:#ffffff; text-decoration:none;} a:hover { color:#0000ff; background-color:#ffffff; text-decoration:none; } a:active { color:#993399; background-color:#ffffff; text-decoration:none; } - *.commandline { font-family:Fixed,Courier,monospace; font-size:11pt; } + *.commandline { font-family:Fixed,Courier,monospace; font-size:90% } *.file { color: #000088;} *.button { color: #468E64;} - *.key { color:#550000; font-family:Fixed,Courier,monospace; font-size:11pt; } + *.key { color:#550000; font-family:Fixed,Courier,monospace; font-size:90% } *.backdropped { background-color:#ffffee; } *.image {margin-left: 5px; margin-right: 5px; border-width:2px; border-style:solid; border-color:#eeeeff; padding:1cm; text-align:center; } *.floatimage { clear:right; float:right; margin-left:0.5cm; border-width:2px; border-style:solid; border-color:#eeeeff; padding:0.5cm; } @@ -48,12 +46,11 @@

Hatari User's Manual

-Version 1.0 +Version 1.1

-Project initiator and main developer of Hatari: Thomas Huth -
-Manual written by: Matthias Arndt +Manual written by: Thomas Huth, Matthias Arndt + & Eero Tamminen

Hatari on the WWW:

Features

@@ -185,11 +181,11 @@ there is support for most of the enhance @@ -199,7 +195,7 @@ There is support for following additiona
  • TT low/med/high resolution support
  • ST/TT palette switching and video shifter
  • RAM upto 14MiB (ST-RAM only, there is no support for TT-RAM yet)
    • -
  • Only TOS version 3.06 can be used in TT mode.
    • +
  • Only TOS version 3.06 (and EmuTOS) can be used in TT mode.
    • @@ -211,11 +207,12 @@ There is support for following additiona
  • Mono/RGB/VGA/TV monitor types
  • Some few parts of the Falcon sound system are emulated (e.g. the additional sample rates of the DMA sound)
    • -
  • TOS versions 4.00, 4.02, 4.04 and 4.92 can be used in Falcon mode.
    • +
  • TOS versions 4.00, 4.02, 4.04 and 4.92 (and EmuTOS) can be used in Falcon mode.
    • -

    DSP is not emulated, but there's a dummy mode with which some -additional demos work. +

    +DSP emulation is still very experimental and unstable, but there's a dummy mode, +too, which helps to get some demos and games running.

    @@ -236,20 +233,17 @@ Certain versions of Hatari have successf the following systems:

    Compiling and running

    @@ -269,12 +263,18 @@ most cases. Make sure to have the header for it installed as well.

    +For optional features like PNG format screenshots and Hatari window +embedding, you need to have the header files for libpng and libX11. +

    +

    Of course, you need the GNU C compiler and (GNU) Make, too!

    -

    Change to the hatari/ directory and adapt the configuration file -Makefile.cnf to suite your system. -Alternatively, you can use the supplied configure script to auto-detect -all parameters (type " ./configure --help" +

    Change to the hatari/ directory, copy +Makefile-default.cnf to +Makefile.cnf and adapt the configuration file +to suite your system. Alternatively, you can use the supplied configure +script to auto-detect all parameters (type +"./configure --help" to see the options of the script). Don't forget to use some good CFLAGS for the compiler optimizations, e.g. run configure in the following way: @@ -314,7 +314,8 @@ release versions of Hatari. EmuTOS is an it at: http://emutos.sourceforge.net/. It is not the best solution for playing games or running other old software -due to compatibility issues, but it's free and compatible with Hatari.

    +due to compatibility issues (see emutos.txt for +more details), but it's free and compatible with Hatari.

    If you do not specify a TOS image on the commandline nor can Hatari find a suitable TOS image in the default dir, you'll get the chance to select a TOS image file from the GUI.

    @@ -349,220 +350,814 @@ to toggle windowed and fullscreen mode. hatari [options] [disk image name] -

    The command line options are following -(the long version is in parenthesis):

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +

    Hatari command line options are split into several categories:

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + +

    General options

    +
    General optionsDescription
    -h (--help)Prints command line options and terminates
    -v (--version)Prints version information and terminates
    --confirm-quit <x>Confirm Hatari quitting (x = y/n)
    -c <file>
    (--configfile <file>)    		Use the given file as configuration file - instead of ~/.hatari/hatari.cfg
    Display optionsDescription
    -m (--mono)Starts the emulated Atari ST in monochrome - resolution (deprecated)
    --monitor <x>Select monitor type (x = mono/rgb/vga/tv)
    -f (--fullscreen)Start in fullscreen mode
    --windowForces Hatari to use a windowed mode
    -z <x>
    (--zoom <x>)    		Doubles ST low resolution (1=no, 2=yes)
    --frameskips <x>Shows only every <x> frame (speeds up emulation!)
    --borders <bool>Show screen borders (for overscan demos etc.)
    --spec512 <x>Use threshold x to decide when to render a screen with the slower - but more
    accurate Spectrum512 screen conversion functions - (0 <= x <= 512, 0=disable)
    --bpp <x>Force color bitdepth (x=8/16/32, 0=autodetection)
    VDI optionsDescription
    --vdi-planesSpecify extended VDI resolution bit-depth, x = 1/2/4
    --vdi-width <w>Specify extended VDI resolution width - (320 < w <= 1024, multiple of 128)
    --vdi-height <h>Specify extended VDI resolution height - (200 < h <= 768, multiple of text height)
    Device optionsDescription
    -j <port>
    (--joystick <port>)    		Activates joystick emulation via cursor keys - for given joystick "port"
    (0-5, see joystick dialog)
    --printer <file>Enable printer support and write data to the specified file
    --midi <file>Enable MIDI output and write midi data to the specified file
    --rs232 <file>Enable RS232 communication via the specified file
    Disk optionsDescription
    -d <dir>
    (--harddrive <dir>)    		Emulates a hard disk at the GEMDOS level - (<dir> = root directory)
    --acsi <imagefile>Emulate an ACSI hard disk with an image file
    --slowfdc <bool>Slow down FDC emulation (deprecated)
    Memory optionsDescription
    -s <x>
    (--memsize <x>)    		set amount of emulated RAM upto 14MB
    - x=0 for 512K, x=1,x=2 or x=4 for 1, 2 or 4 MB
    --tos <imagefile>Specify TOS ROM image to use
    --cartridge <file>Use file as the cartridge on the ROM port.
    - This currently does not work together with GEMDOS hard disk emulation!
    --memstate <file>Load memory snap-shot file
    CPU optionsDescription
    --cpulevel <x>Set the CPU type (x => 680x0) — - works with EmuTOS / TOS 2.06 only!
    --cpuclock <x>Set the CPU frequency in MHz (8, 16 or 32)
    --compatible <bool>Use a more compatible but slower 68000 CPU mode
    Misc system optionsDescription
    --machine <x>Select machine type (x = st/ste/tt/falcon)
    --blitter <bool>Use blitter emulation (for ST only)
    --dsp <x>Select DSP type (Falcon only, x = none/dummy(/emu))
    --sound <x>Sound quality (x = off/low/med/hi)
    -k <file>
    (--keymap <file>)    		Read (additional) keyboard mapping from file
    Debug optionsDescription
    -D (--debug)Activates the simple builtin debugger
    --log <file>Direct log output to the specified file
    --trace <type1,...>Activate debug traces, use --trace help to see the options
    + + + +
    +−h, −−help
    + + + + +
    +Print command line options and terminate +
    + + + + +
    +−v, −−version
    + + + + +
    +Print version information and terminate +
    + + + + +
    +−−confirm-quit <bool>
    + + + + +
    +Whether Hatari confirms quitting +
    + + + + +
    +−c, −−configfile +<filename>
    + + + + +
    +use the given file as configuration file instead of +~/.hatari/hatari.cfg +
    + + + + +
    +−−fast-forward <bool>
    + + + + +
    +On fast machine helps skipping (fast forwarding) Hatari +output +
    + +

    Display options

    + + + + +
    +−m, −−mono
    + + + + +
    +Start in monochrome mode instead of color +
    + + + + +
    +−−monitor <x>
    + + + + +
    +Select monitor type (x = mono/rgb/vga/tv) +
    + + + +
    +−f, −−fullscreen
    + + + + +
    +Start the emulator in fullscreen mode +
    + + + + +
    +−w, −−window
    + + + + +
    +Start the emulator in window mode +
    + + + + +
    +−z, −−zoom <x>
    + + + + +
    +Zoom low resolution (1=no, 2=yes) +
    + + + + +
    +−−frameskips <x>
    + + + + +
    +Skip <x> frames after each displayed frame to +accelerate emulation (0=disabled, >4 uses automatic +frameskip with given value as maximum) +
    + + + + +
    +−−borders <bool>
    + + + + +
    +Show screen borders (for overscan demos, ST(e) color mode +specific etc) +
    + + + + +
    +−−statusbar <bool>
    + + + + +
    +Show statusbar (with floppy leds etc etc) +
    + + + + +
    +−−drive-led <bool>
    + + + + +
    +Show overlay drive led when statusbar isn’t +shown +
    + + + + +
    +−−spec512 <x>
    + + + + +
    +Hatari uses this threshold to decide when to render a +screen with the slower but more accurate Spectrum512 screen +conversion functions (0 <= x <= 512, 0=disable) +
    + + + + +
    +−−bpp <bool>
    + + + + +
    +Force internal bitdepth (x = 8/15/16/32, 0=disable) +
    + +

    VDI options

    + + + + +
    +−−vdi <bool>
    + + + + +
    +Whether to use VDI screen mode +
    + + + + +
    +−−vdi−planes <x>
    + + + + +
    +Use extended VDI resolution with bit depth <x> (x = +1, 2 or 4) +
    + + + + +
    +−−vdi−width <w>
    + + + + +
    +Use extended VDI resolution with width <w> (384 +<= w <= 1024) +
    + + + + +
    +−−vdi−height <h>
    + + + + +
    +Use extended VDI resolution with height <h> (200 +< h <= 768) +
    + +

    Devices options

    + + + + +
    +−j, −−joystick +<port>
    + + + + +
    +Emulate joystick with cursor keys in given port (0-5) +
    + + + + +
    +−−joy<port> +<type>
    + + + + +
    +Set joystick type (none/keys/real) for given port +
    + + + + +
    +−−printer <file>
    + + + + +
    +Enable printer support and write data to <file> +
    + + + + +
    +−−midi <filename>
    + + + + +
    +Enable midi support and write midi data to +<file> +
    + + + + +
    +−−rs232 <filename>
    + + + + +
    +Enable serial port support and use <file> as the +device +
    + +

    Disk options

    + + + + +
    +−−disk-a <file>
    + + + + +
    +Set disk image for floppy drive A +
    + + + + +
    +−−disk-b <file>
    + + + + +
    +Set disk image for floppy drive B +
    + + + + +
    +−d, −−harddrive +<dir>
    + + + + +
    +Emulate an ST harddrive (<dir> = root +directory) +
    + + + + +
    +−−acsi <file>
    + + + + +
    +Emulate an ACSI hard disk with an image <file> +
    + + + + +
    +−−ide <file>
    + + + + +
    +Emulate an IDE hard disk with an image <file> (not +working yet) +
    + + + + +
    +−−slowfdc <bool>
    + + + + +
    +slow down FDC emulation (deprecated) +
    + +

    Memory options

    + + + + +
    +−s, −−memsize <x>
    + + + + +
    +Set amount of emulated RAM, x = 1 to 14 MiB, or 0 for 512 +KiB +
    + + + + +
    +−t, −−tos +<imagefile>
    + + + + +
    +Specify TOS ROM image to use +
    + + + + +
    +−−cartridge <imagefile>
    + + + + +
    +Use ROM cartridge image <file> (only works if +GEMDOS HD emulation and extended VDI resolution are +disabled) +
    + + + + +
    +−−memstate <file>
    + + + + +
    +Load memory snap-shot <file> +
    + +

    CPU options

    + + + + +
    +−−cpulevel <x>
    + + + + +
    +Specify CPU (680x0) to use (use x >= 1 with EmuTOS or +TOS >= 2.06 only!) +
    + + + + +
    +−−cpuclock <x>
    + + + + +
    +Set the CPU clock (8, 16 or 32 Mhz) +
    + + + + +
    +−−compatible <bool>
    + + + + +
    +Use a more compatible but slower 68000 CPU mode +
    + +

    Misc system options

    + + + + +
    +−−machine <x>
    + + + + +
    +select machine type (x = st, ste, tt or falcon) +
    + + + + +
    +−−blitter <bool>
    + + + + +
    +Enable blitter emulation (ST only) +
    + + + + +
    +−−dsp <x>
    + + + + +
    +Falcon DSP emulation (x = none, dummy or emu, Falcon +only) +
    + + + + +
    +−−sound <x>
    + + + + +
    +Sound quality (off/low/med/hi, off=faster) +
    + + + + +
    +−k, −−keymap +<file>
    + + + + +
    +load keyboard mapping from <file> +
    + +

    Debug options

    + + + + +
    +−D, −−debug +<bool>
    + + + + +
    +Enable Hatari debugger console interface +
    + + + + +
    +−−bios-intercept
    + + + + +
    +Enable Bios/XBios interception +
    + + + + +
    +−−trace <trace1,...>
    + + + + +
    +Activate debug traces, see --trace help for available tracing options +
    + + + + +
    +−−control-socket <file>
    + + + + +
    +Hatari reads options from given socket at run-time +
    + + + + +
    +−−log-file <file>
    + + + + +
    +Save log output to <file> (default=stderr) +
    + + + + +
    +−−log-level <x>
    + + + + +
    +Log output level (x=debug/todo/info/warn/error/fatal) +
    + + + + +
    +−−alert-level <x>
    + + + + +
    +Show dialog for log messages above given level +
    +

    Type hatari --help to list all the command line options supported by a given version of Hatari.

    @@ -578,7 +1173,7 @@ an allmost complete Atari ST computer sy with the mouse. The GUI is rather self explanatory.

    -

    The Main Menu

    +

    The Main Menu

    Hatari's GUI - the main menu @@ -603,7 +1198,7 @@ return to the host OS.

    Click Cancel to abandon any changes that you have made.

    -

    The System Dialog

    +

    The System Dialog

    Hatari's GUI - the system dialog @@ -642,8 +1237,8 @@ that you have made.

    work with an STE, it's normally safe to always work in STE mode.
    TT and Falcon are more advanced, but they are not as compatible to the ST as - the STE was. So many old games and demos do not work with these machine types - anymore. There were only very few programs that were made for the TT + the STE was. Therefore many old games and demos do not work with these machine + types anymore. There were only very few programs that were made for the TT exclusively, while there were some interesting games and demos specially made for the Falcon. Note: TT and Falcon emulation are very incomplete. They may not work @@ -675,34 +1270,34 @@ that you have made.

    value slows down the emulation. The patch gives you a better performance. It is normally safe to enable the patch, but if you encounter a program that does not work, you can try to disable the patch to see if it works then.

    -

    Select if you want to use slow FDC emulation. Slow is more compatible esp. - with games and demos that use custom loaders.

    +

    + Select if you want to use slow FDC emulation. "Slow down FDC" is + normally not required, except for some few slideshows / intros which run too + fast without this option. +

    NOTE: These parameters are very sensitive to the emulated ST and it is strongly recommended to reset the emulated ST after changing these options.

    -

    The Disks Dialog

    +

    The Disks Dialog

    -Hatari's GUI - the disks dialog +Hatari's GUI - the disks dialog

    Use the upper dialog to choose which floppy disks should be emulated in the disk drives.

    -

    You can use most standard Atari ST disk image files. See the chapter -"Floppy disk images" +

    You can use most standard Atari ST disk image files. You may select +and browse also zipped disk images. See the chapter "Floppy disk images" for details.

    -

    Click on the button Browse next to the -A: and B: option to go to the fileselector. -You may select and browse zipped disk images as well.

    -

    -The fileselector looks like this: +

    Click on the button Browse next to the +A: and B: option to go to the fileselector:

    -Hatari's GUI - the fileselector +Hatari's GUI - the fileselector

    Click on Eject to eject a disk image @@ -749,10 +1344,10 @@ on the harddrive. This option is checked by default if you specify a harddrive image or a directory via the command line.

    -

    The Memory Dialog

    +

    The Memory Dialog

    -
    -Hatari's GUI - the memory dialog +
    +Hatari's GUI - the memory dialog

    You can select the amount of RAM for the emulated ST here. Only @@ -770,10 +1365,11 @@ restored.

    different versions of Hatari. E.q. if you compile a newer Hatari, you cannot load your old memory snapshots back.

    -

    The ROM Dialog

    -
    -Hatari's GUI - the ROM dialog +

    The ROM Dialog

    + +
    +Hatari's GUI - the ROM dialog

    Here you can select the TOS image to use. Click on -

    The Joystick Dialog

    + +

    The Joystick Dialog

    Hatari's GUI - the joystick dialog @@ -835,10 +1432,11 @@ on the fire button in shoot'em-up games. certain games. In some other games, it gets worse if you enable this option.

    See also the chapter "Emulated Joystick" for details.

    -

    The Screen Dialog

    + +

    The Screen Dialog

    -Hatari's GUI - the screen dialog +Hatari's GUI - the screen dialog

    @@ -863,14 +1461,20 @@ certain games. In some other games, it g enabled on slow computers.

    - "Force 8Bpp" will force Hatari to use an 8bit video mode. - You don't need this for modern video cards. + "Statusbar" toggles the statusbar at the bottom of the screen. + The statusbar shows the floppy drive LEDs, the current frameskip value, + the machine type including TOS version and memory size, and whether + recording is currently active.

    The "Frame Skip" option can be set to speed up the emulator - if it is running too slow on your system. 1 to 8 frames will be dropped - after each frame that has been drawn. Disable frame-skip if you have a - fast computer. + if it is running too slow on your system. Disable frame-skip if you have + a fast computer. When selecting 1, 2 or 4, drawing of corresponding number + of frames will be skipped after each frame actually shown by Hatari. + Select "Auto" to let the emulator to decide whether, and + how many frames will be skipped.
    + Note: The frameskip option also affects the frame rate of the + screen animation recording!

    You can select which sort of monitor to use. This option depends on the @@ -898,16 +1502,17 @@ conformant applications. 99% of all game activate any extended resolution here.

    Click Capture Screen to create a -screenshot in .BMP format to the current working directory or click Record Animation to record a sequence of single +screenshot in PNG (or BMP) format to the current working directory or click +Record Animation to record a sequence of single screenshots. You can opt to only record new movie frames when the screen content really changed.

    -

    The Keyboard Dialog

    + +

    The Keyboard Dialog

    -Hatari's GUI - the keyboard dialog +Hatari's GUI - the keyboard dialog

    Here you can select the keyboard mapping to use. Two different mappings @@ -928,11 +1533,18 @@ screen content really changed. mapping for all keys that are not defined by your map file. Have a look at the supplied example mapfile (keymap-sample.txt) to see how to create your own keyboard mapping.

    +

    + When the emulator runs in fast forward mode, and you want to type text, + it can be annoying that the emulated system detects multiple key events + due to the key repetition of the emulated system. To avoid this you can + disable the key repetition in fast forward mode here. +

    -

    The Sound Dialog

    -
    -Hatari's GUI - the sound dialog +

    The Sound Dialog

    + +
    +Hatari's GUI - the sound dialog

    Here you can control the sound subsystem.

    @@ -941,28 +1553,25 @@ sound emulation is turned off.

    3 frequencies from low to high quality are available. Experiment a little bit to find out which fits best for your setup. Medium quality will work ok in most cases.

    -

    You can select to record a piece of sound here. Check which format -to use and click the button. It is a toggle button so -you will need to return to the GUI to switch sound recording off again.

    +

    You can select to record a piece of sound here. The file name +extension you use (.WAV or .YM), determines in which format the sound +is recorded in. The record button is a toggle so you will need to +return to the GUI to switch sound recording off again +(or to use the keyboard shortcut for that).

    -

    The Devices Dialog

    -

    Check here if you want to enable experimental printer support. See -the chapter "Emulated printer" for details.

    +

    The Devices Dialog

    -
    -Hatari's GUI - the device dialog +
    +Hatari's GUI - the device dialog
    +

    Check here if you want to enable experimental printer support. See +the chapter "Emulated printer" for details.

    +

    As Hatari currently only supports printing to file, click on Select to select the file to print to. You can enter a new filename as well.

    -

    NOTE: As the printer emulation is not perfect yet, -activated printer support may interfere with the emulated sound. -This is due to the fact that the Atari ST uses some general I/O ports -of the soundchip for the printer port. The Hatari team suggests to -disable printing while using games and demos. -

    Check the second checkmark if you want to enable experimental RS232 support. The RS232 device is configured according to the settings of the emulated RS232 of the Atari ST. This means Hatari will @@ -981,7 +1590,8 @@ MIDI device file for output.

    Don't enable them unless you really need them!

    -

    Keyboard shortcuts

    + +

    Keyboard shortcuts

    While the emulator is running, you can activate or toggle various features via Hatari keyboard shortcuts. Below are listed the default @@ -998,21 +1608,21 @@ shortcut key bindings:

    ALTGR+g - grabs a screenshot + grab a screenshot ALTGR+i - boss key: leave full screen mode and iconify -window + boss key: leave full screen mode, pause Hatari +and iconify its window ALTGR+j - toggles joystick emulation via cursor keys -between port 0, port 1 and being off from those ports + toggle joystick emulation via cursor keys +on/off between ports 0 and 1 ALTGR+m - (un-)locks the mouse into the window + (un-)lock the mouse into the window ALTGR+r @@ -1024,6 +1634,10 @@ between port 0, port 1 and being off fro switch) + ALTGR+d + open dialog to select/change disk A + + ALTGR+s enable/disable sound @@ -1049,23 +1663,23 @@ switch) ALTGR+f or F11 - toggles fullscreen and windowed mode + toggle between fullscreen and windowed mode ALTGR+o or F12 - activate the GUI + activate the options GUI PAUSE - will go to the debugger if Hatari was started with - the -D option + pause emulation or go to the debugger + if Hatari was started with the -D option

    You can change the key bindings from the Hatari configuration file. The required key values you can see from the SDL_keysym.h include file -(usually in /usr/include/SDL/). +(usually in /usr/include/SDL/).

    Emulated Atari ST keyboard

    @@ -1106,13 +1720,11 @@ key on the ST. The following keys have s -

    The right CTRL key is used by default as the -fire button of the emulated joystick when you turn on joystick emulation -via keyboard.

    -

    The cursor keys will be used by default as the emulated ST joystick, -unless you are using joystick emulation via a real joystick or have disabled -joystick emulation completely. Then the cursor keys will act as the cursor -keys of the emulated Atari ST, of course.

    +

    If joystick emulation via keyboard is enabled, by default cursor keys +are used for the directions and right CTRL key +as the fire button. Otherwise they act as corresponding keys of the emulated +Atari ST.

    +

    Emulated mouse

    @@ -1141,7 +1753,7 @@ firebutton will act as the normal firebu second firebutton will emulate a keypress of the SPACE key on the ST as many ST -games utilitze the SPACE bar for secondary game functions. (Xenon for +games utilize the SPACE bar for secondary game functions. (Xenon for example)

    If you do not have a PC joystick or joypad, then you do not need to desperate. You can emulate one of the two Atari ST joysticks via the @@ -1149,19 +1761,19 @@ cursor keys. Just activate it in the GUI as the joystick directions, the right CTRL key will act as the firebutton. You can still use the cursor keys as the ST's cursorkeys in this mode as long as you press SHIFT -along with the cursorkeys.

    +along with the cursorkeys. You can also configure these keys from the +joystick options.

    Emulated video

    -

    Hatari by default only handles ST modes, ST-LOW, ST-MED and ST-HIGH.

    -

    Overscan effects and so called "Border Removal" are possible too.

    -

    Due to the fact that these effects are achieved by using quirks and -glitches in the original chips to do things beyond their specification -emulation is a bit tricky for these and not all ST applications -utilizing these techniques will work properly in Hatari. -Especially so called "Sync Scrolling", a special technique to emulate -the low byte of the video address, currently does not work properly in -Hatari. +

    Hatari emulates all screen modes of the original machine.

    +

    +ST/STE shifter overscan effects are emulated, but due to the fact +that these effects are achieved by using quirks and glitches in the +original chips to do things beyond their specification, emulation is +a bit tricky for these effects. As a result, some demos using these +techniques might not be displayed correctly in Hatari, known ones are +listed in the compatibility.html file.

    Beside that you can setup extended VDI modes. These only work with GEM-compliant applications and they are equal to fitting a videocard @@ -1271,17 +1883,21 @@ a zipped disk image.

    Hard disk support

    -

    Hatari supports two ways of emulating a ST hard drive: The low-level -ACSI hard disk emulation and a GEMDOS based drive emulation.

    +

    +Hatari supports two ways of emulating a ST hard drive: The low-level +ACSI hard disk emulation and a GEMDOS based drive emulation. Please +note that changing the HD-image or the GEMDOS HD-folder will reset +the emulated Atari since it is not possible to switch the hard disk +while the emulator is running. +

    ACSI hard disk emulation

    To use the ACSI hard disk emulation, you need a hard disk image file with a pre-installed HD driver in it. So either try to image your old ST hard disk or grab one from the internet (e.g. from the Hatari website). -Please note that AHDI 5.0 is the only hard disk driver that -is currently working and supported. Other hard disk drivers likely will not -work. +Please note that AHDI 5.0 is currently the only hard disk driver +that is officially supported. Other hard disk drivers might not work.

    To create a new ACSI hard disk image, you can start with an empty image that @@ -1308,24 +1924,21 @@ don't want to rename all files to get ca possible to store that folder on a FAT filesystem since those filesystems are case-insensitive.

    GEMDOS drive emulation is an easy way to share files between the -host system and the emulated Atari, but it is known to be incomplete -and +host system and the emulated Atari, but it is known to be incomplete and a little bit unstable, especially if you use it together with the ACSI hard disk emulation. So if your programs complain that they could not find/read/write files on the GEMDOS HD drive, you should try to copy them to a floppy disk image or a real hard disk image!

    -

    Due to the way the GEMDOS drive emulation is implemented at the -moment, it is not possible to use a cartridge image together with -GEMDOS drive emulation.

    -

    Note that changing the HD-image or the GEMDOS HD-folder will reset -the emulated Atari since it is not possible to switch the hard disk -while the emulator is running.

    -

    -That's all for the moment. -May the fun without the price to be with you ;-) ! +There are also some known limitations which are due to the way the GEMDOS +drive emulation is implemented: First, it is not possible to use a cartridge +image together with GEMDOS drive emulation at the same time. +Second, the GEMDOS HD emulation does not work very well with TOS +1.00 and 1.02. So you should use at least TOS 1.04 if you want +to use the GEMDOS HD emulation.

    +

    Appendix

    Copying

    @@ -1396,7 +2009,7 @@ parts of the emulated system is much tri src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" border="0" height="31" width="88"> - February 29th 2008 + November 23rd 2008