General 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 - | -
| - | --k, --keymap -<file> | -
| - | -load keyboard mapping from <file> - | -
-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>
+Read additional configuration values from +<file>, these override values read from the global and +user configuration files +
+-k, --keymap +<file>
+load keyboard mapping from +<file>
+--fast-forward +<bool>
+On fast machine helps skipping (fast +forwarding) Hatari output
-Common 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 - | -
| - | ---grab | -
| - | -Grab mouse (also) in window mode - | -
| - | ---fast-forward <bool> | -
| - | -On fast machine helps skipping (fast forwarding) Hatari -output - | -
| - | ---frameskips <x> | -
| - | -Skip <x> frames after each displayed frame to -accelerate emulation (0=disabled, >4 uses automatic -frameskip with given value as maximum) - | -
| - | ---statusbar <bool> | -
| - | -Show statusbar (with floppy leds etc etc) - | -
| - | ---drive-led <bool> | -
| - | -Show overlay drive led when statusbar isn’t shown - | -
| - | ---bpp <bool> | -
| - | -Force internal bitdepth (x = 8/15/16/32, 0=disable) - | -
-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 windowed mode
+--grab
+Grab mouse (also) in windowed mode
+--borders <bool>
+Show ST/STE/Falcon screen borders +(for low/med resolution overscan demos)
+--frameskips +<x>
+Skip <x> frames after each +displayed frame to accelerate emulation (0=disabled, >4 uses +automatic frameskip with given value as maximum)
+--slowdown <x>
+Slow down emulation by factor of x +(used as multiplier for VBL wait time)
+--statusbar +<bool>
+Show statusbar (with floppy leds etc +etc)
+--drive-led +<bool>
+Show overlay drive led when statusbar +isn’t shown
+--max-width +<x>
+Preferred / maximum window width +for borders / zooming
+--max-height +<x>
+Preferred / maximum window height +for borders / zooming
+--bpp +<bool>
+Force internal bitdepth (x = +8/15/16/32, 0=disable)
-ST/STE specific display options
-| - | ---borders <bool> | -
| - | -Show screen borders (for low/med resolution overscan demos) - | -
| - | ---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) - | -
| - | --z, --zoom <x> | -
| - | -Zoom low resolution (1=no, 2=yes) - | -
--desktop-st +<bool>
+Whether fullscreen mode uses desktop +resolution to avoid: messing multi-screen setups, several seconds +delay needed by LCD monitors resolution switching and the resulting +sound break. As Hatari ST/E display code doesn’t support +zooming (except low-rez doubling), it doesn’t get scaled (by +Hatari or monitor) when this is enabled. Therefore this is mainly +useful only if you suffer from the described effects, but still +want to grab mouse and remove other distractions from the screen +just by toggling fullscreen mode. (disabled by default)
+--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)
+-z, --zoom +<x>
+Zoom (double) low resolution (1=no, +2=yes)
+ +TT/Falcon specific display options
++Zooming to sizes specified below is internally done using integer scaling +factors. This means that different Atari resolutions may show up with +different sizes, but they are never blurry. +
--desktop <bool>
+Whether to use desktop resolution on +fullscreen to avoid issues related to resolution switching. +Otherwise fullscreen will use a resolution that is closest to the +Hatari window size. (enabled by default)
+--force-max +<bool>
+Hatari window size is forced to +specified maximum size and black borders used when Atari resolution +doesn’t scale evenly to it. This is most useful when +recording videos of Falcon demos that change their resolution. +(disabled by default)
+--aspect +<bool>
+Whether to do monitor aspect ratio +correction (enabled by default)
- -Falcon/TT specific display options
--Zooming to sizes specified below is internally done using integer -scaling factors. This means that different Atari resolutions may show -up with different sizes, but they are never blurry. -
-| - | ---desktop <bool> | -
| - | -Whether to use desktop resolution on fullscreen to avoid issues -related to resolution switching. Otherwise fullscreen will use -a resolution that is closest to the Hatari window size - | -
| - | ---max-width <x> | -
| - | -Maximum window width for zooming - | -
| - | ---max-height <x> | -
| - | -Maximum window height for zooming - | -
| - | ---aspect <bool> | -
| - | -Whether to do monitor aspect ratio correction - | -
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> (320 < w <= 1280) - | -
| - | ---vdi-height <h> | -
| - | -Use extended VDI resolution with height <h> (200 < h <= 960) - | -
--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> (320 < w <= 1280)
+--vdi-height +<h>
+Use extended VDI resolution with height +<h> (200 < h <= 960)
-Screen capture options
-| - | ---crop <bool> | -
| - | -Remove statusbar from the screen captures - | -
| - | ---avirecord | -
| - | -Start AVI recording - | -
| - | ---avi-vcodec <x> | -
| - | -Select avi video codec (x = bmp/png) - | -
| - | ---avi-fps <x> | -
| - | -Force avi frame rate (x = 50/60/71/...) - | -
| - | ---avi-file <file> | -
| - | -Use <file> to record avi - | -
--crop +<bool>
+Remove statusbar from the screen +captures
+--avirecord
+Start AVI recording
+--avi-vcodec +<x>
+Select avi video codec (x = +bmp/png)
+--avi-fps +<x>
+Force avi frame rate (x = +50/60/71/...)
+--avi-file +<file>
+Use <file> to record avi
-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-in <filename> | -
| - | -Enable MIDI support and write MIDI data to <file> - | -
| - | ---midi-out <filename> | -
| - | -Enable MIDI support and read MIDI data from <file> - | -
| - | ---rs232-in <filename> | -
| - | -Enable serial port support and use <file> as the input device - | -
| - | ---rs232-out <filename> | -
| - | -Enable serial port support and use <file> as the output device - | -
-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-in +<filename>
+Enable MIDI support and write MIDI data +to <file>
+--midi-out +<filename>
+Enable MIDI support and read MIDI data +from <file>
+--rs232-in +<filename>
+Enable serial port support and use +<file> as the input device
+--rs232-out +<filename>
+Enable serial port support and use +<file> as the output device
-Disk options
-| - | ---disk-a <file> | -
| - | -Set disk image for floppy drive A - | -
| - | ---disk-b <file> | -
| - | -Set disk image for floppy drive B - | -
| - | ---protect-floppy <x> | -
| - | -Write protect floppy image contents (on/off/auto). With "auto" option -write protection is according to the disk image file attributes. - | -
| - | ---protect-hd <x> | -
| - | -Write protect harddrive <dir> contents (on/off/auto). With "auto" -option the protection can be controlled by setting individual files -attributes as it disables the file attribute modifications for -the GEMDOS hard disk emulation. - | -
| - | --d, --harddrive <dir> | -
| - | -Emulate harddrive partition(s) with <dir> contents - | -
| - | ---acsi <file> | -
| - | -Emulate an ACSI hard disk with an image <file> - | -
| - | ---ide-master <file> | -
| - | -Emulate an IDE master hard disk with an image <file> - | -
| - | ---ide-slave <file> | -
| - | -Emulate an IDE slave hard disk with an image <file> - | -
| - | ---slowfdc <bool> | -
| - | -slow down FDC emulation (deprecated) - | -
--drive-a +<bool>
+Enable/disable drive A (default is on)
+--drive-b +<bool>
+Enable/disable drive B (default is on)
+--drive-a-heads +<x>
+Set number of heads for drive A (1=single sided, 2=double sided)
+--drive-b-heads +<x>
+Set number of heads for drive B (1=single sided, 2=double sided)
+--disk-a +<file>
+Set disk image for floppy drive A
+--disk-b +<file>
+Set disk image for floppy drive B
+--protect-floppy +<x>
+Write protect floppy image contents +(on/off/auto). With "auto" option write protection is according to +the disk image file attributes
+--protect-hd +<x>
+Write protect hard drive <dir> +contents (on/off/auto). With "auto" option the protection can be +controlled by setting individual files attributes as it disables +the file attribute modifications for the GEMDOS HD +emulation
+--gemdos-case <x>
+Specify whether new dir/filenames are forced to be +in upper or lower case with the GEMDOS HD emulation. Off/upper/lower, off by default +
+-d, --harddrive +<dir>
+Emulate hard disk partition(s) with +<dir> contents. If directory contains only single letter +(C-Z) subdirectories, each of these subdirectories will be treated +as a separate partition, otherwise the given directory itself will +be assigned to drive "C:". In the multiple partition case, the +letters used as the subdirectory names will determine to which +drives/partitions they’re assigned. If <dir> is +an empty string, then harddrive's emulation is disabled
+--acsi +<file>
+Emulate an ACSI hard drive with an image +<file>
+--ide-master +<file>
+Emulate an IDE master hard drive with an +image <file>
+--ide-slave +<file>
+Emulate an IDE slave hard drive with an +image <file>
+--fastfdc +<bool>
+Speed up FDC emulation (can cause +incompatibilities)
-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> - | -
+--memstate <file>
+Load memory snap-shot <file>
+-s, --memsize +<x>
+Set amount of emulated RAM, x = 1 to 14 +MiB, or 0 for 512 KiB
+ +ROM options
+-t, +--tos <imagefile>
+Specify TOS ROM image to use
+--patch-tos +<bool>
+Use this option to enable/disable TOS +ROM patching. Experts only! Leave this enabled unless you know what +you are doing!
+--cartridge +<imagefile>
+Use ROM cartridge image <file> +(only works if GEMDOS HD emulation and extended VDI resolution are +disabled)
-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 - | -
+--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 with better prefetch accuracy and cycle counting
-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) - | -
| - | ---mic <bool> | -
| - | -Enable/disable (Falcon only) microphone - | -
| - | ---sound <x> | -
| - | -Sound frequency: 6000-50066. "off" disables the sound and speeds up -the emulation. To prevent extra sound artifacts, the frequency should be -selected so that it either matches evenly with the STE/TT/Falcon sound -DMA (6258, 12517, 250033, 50066 Hz) or your sound card frequencies -(11025, 22050, 44100 or 6000...48000 Hz). Check what your sound card -supports. - | -
| - | ---sound-buffer-size <x> | -
| - | -SDL's sound buffer size : 10-100, or 0 to use default buffer size. -By default Hatari uses an SDL buffer size of 1024 samples, which -gives approximatively 20-30 ms of sound depending on the chosen sound -frequency. Under some OS or with not fully supported sound card, this -default setting can cause a bigger delay at lower frequency (nearly 0.5 sec). -In that case, you can use this option to force the size of the sound -buffer to a fixed number of milliseconds of sound (using 20 is often -a good choice if you have such problems). Most users will not need this option. - | -
| - | ---ym-mixing <x> | -
| - | -Select a method for mixing the three YM2149 voice volumes together. -"table" uses a lookup table of audio output voltage values measured -on STF and "linear" just averages the 3 YM voices. - | -
| - | ---timer-d <bool> | -
| - | -Patch redundantly high Timer-D frequency set by TOS. This about doubles -Hatari speed (for ST/e emulation) as the original Timer-D frequency causes -most of the interrupts. - | -
| - | ---rtc <bool> | -
| - | -Enable real-time clock - | -
+--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)
+--timer-d +<bool>
+Patch redundantly high Timer-D +frequency set by TOS. This about doubles Hatari speed (for ST/e +emulation) as the original Timer-D frequency causes most of the +interrupts.
+--fast-boot +<bool>
+Patch TOS and initialize the so-called +"memvalid" system variables to by-pass the memory test of TOS, so +that the system boots faster.
+--rtc +<bool>
+Enable real-time clock
+ +Sound options
+--mic +<bool>
+Enable/disable (Falcon only) +microphone
+--sound +<x>
+Sound frequency: 6000-50066. "off" +disables the sound and speeds up the emulation. To prevent extra +sound artifacts, the frequency should be selected so that it either +matches evenly with the STE/TT/Falcon sound DMA (6258, 12517, +250033, 50066 Hz) or your sound card frequencies (11025, 22050, +44100 or 6000...48000 Hz). Check what your sound card supports.
+--sound-buffer-size +<x>
+SDL’s sound buffer size: 10-100, +or 0 to use default buffer size. By default Hatari uses an SDL +buffer size of 1024 samples, which gives approximatively 20-30 ms +of sound depending on the chosen sound frequency. Under some OS or +with not fully supported sound card, this default setting can cause +a bigger delay at lower frequency (nearly 0.5 sec). In that case, +you can use this option to force the size of the sound buffer to a +fixed number of milliseconds of sound (using 20 is often a good +choice if you have such problems). Most users will not need this +option.
+--sound-sync +<bool>
+The emulation rate is nudged by +100 or
+0 or -100 micro-seconds on occasion. This prevents the sound buffer
+from overflowing (long latency and lost samples) or underflowing
+(short latency and repeated samples). The emulation rate smoothly
+deviates by a maximum of 0.58% until synchronized, while the
+emulator continuously generates every sound sample and the crystal
+controlled sound system consumes every sample.
+(on|off, off=default)
--ym-mixing +<x>
+Select a method for mixing the three +YM2149 voice volumes together. "model" uses a mathematical model of +the YM voices, "table" uses a lookup table of audio output voltage +values measured on STF and "linear" just averages the 3 YM +voices.
-Debug options
-| - | --D, --debug | -
| - | -Toggle whether CPU exceptions invoke the debugger - | -
| - | ---bios-intercept | -
| - | -Toggle Bios/XBios call interception and BIOS CON: output -(e.g. EmuTOS console) redidirection to host terminal. -Needed for Bios/XBios call tracing. Allows Atari programs -to modify Hatari state through XBios 255 calls. - | -
| - | ---trace <trace1,...> | -
| - | -Activate debug traces, see --trace help for available tracing options - | -
| - | ---trace-file <file> | -
| - | -Save trace output to <file> (default=stderr) - | -
| - | ---parse <file> | -
| - | -Parse/execute debugger commands from <file> - | -
| - | ---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 - | -
| - | ---run-vbls <x> | -
| - | -Exit after X VBLs - | -
-D, +--debug
+Toggle whether CPU exceptions invoke +the debugger
+--debug-except <flags>
+Specify which exceptions invoke debugger, see +"--debug-except help" for available (comma separated) exception +flags.
+--bios-intercept
++Toggle XBios command parsing. Allows Atari programs to use all Hatari +functionality and change Hatari state through Hatari specifit +XBios(255) calls. XBios(20) printscreen calls produce also Hatari +screenshots.
+--conout <device>
+Enable console (xconout vector functions) output +redirection for given <device> to host terminal. Device 2 is for +the (CON:) VT52 console, which vector function catches also EmuTOS panic +messages and MiNT console output, not just normal BIOS console output.
+--disasm <x>
+Set disassembly options. 'uae' and 'ext' select +the dissasembly engine to use, bitmask sets output options for the +external disassembly engine and 'help' lists them.
+--natfeats <bool>
+Enable/disable (basic) Native Features support. +E.g. EmuTOS uses it for debug output.
+--trace +<flags>
+Activate debug traces, see +"--trace help" for available tracing flags
+--trace-file +<file>
+Save trace output to <file> +(default=stderr)
+--parse +<file>
+Parse/execute debugger commands from +<file>
+--saveconfig
+Save Hatari configuration and exit. +Hatari UI needs Hatari configuration file to start, this can be +used to create it automatically.
+--no-parachute
+Disable SDL parachute to get Hatari +core dumps. SDL parachute is enabled by default to restore video +mode in case Hatari terminates abnormally while using non-standard +screen resolution.
+--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
+--run-vbls +<x>
+Exit after X VBLs
Type hatari --help to list all the command line options supported by a given version of Hatari.
-Using the emulated system
-Once you've started Hatari succesfully, you can use the emulator as +
Using the emulated system
+ +Once you've started Hatari successfully, you can use the emulator as an almost complete Atari ST computer system.
-The GUI
+The GUI
Press F12 to enter the GUI. Navigate it with the mouse. The GUI is rather self explanatory.
-The Main Menu
+The Main Menu
+
@@ -1664,10 +870,11 @@ changes that you have made.
-The File Selector Dialog
+The File Selector Dialog
+
@@ -1675,118 +882,190 @@ changes that you have made. or folder.
- To enter a folder or choose a file, simply click on the entry in the main box - of the dialog. You can use the arrows at the right, the cursor up and down - keys and the page up and down keys to navigate through the list. + To enter a folder or choose a file, simply click on the entry in the + main box of the dialog. To navigate in the file list, you can use the + scrollbar on the right with mouse, or use keyboard up + down arrow, + page up + down, Home and End keys.
You can use the three buttons in the upper right corner for additional folder - navigation. Use the button to go up one level - in the directory tree. Use the button to return - to your home directory. The button can be used + navigation. Click the button to go up one level + in the directory tree. Click the button to return + to your home directory. The button can be clicked to go to the root directory of the file system.
-The System Dialog
+The System Dialog
+
- First you can select the CPU type here. Here are some important hints for - choosing the correct CPU type: + The system dialog can be used to define the basic hardware attributes of + the machine that should be emulated.
--
-
- - Atari ST and STE have only been shipped with a 68000 CPU, so for best - compatibility with old programs, choose this CPU type. - -
- - Atari TT and Falcon computers were using the 68030 CPU, so you should switch - use 68EC030+FPU (Hatari doesn't support 030 with MMU and some programs don't - work with 68020 so this is the best choice). - -
- - TOS 1.0x only works with 68000, while TOS 3.0x and 4.0x work only with a CPU - >= 68020. - -
- - 68010 and 68040 have never been used in official Atari computers, so don't - use these CPU types unless you've got some good reasons. - -
- Beside the CPU type, you can also choose the machine type to emulate.
- The ST was the very first 16/32-bit computer from Atari. Most older games
- and demos require an ST. The STE was introduced some years later and had
- some more advanced hardware features. There are not that many demos or
- games that really require an STE but since most normal ST games/demos also
- work with an STE, it's normally safe to always work in STE mode.
-
+ The machine type option is used to select the type of Atari computer to
+ be emulated. The ST was the very first 16/32-bit computer from Atari.
+ Most older games and demos require an ST. The STE was introduced some years
+ later and had some more advanced hardware features. There are not that many
+ demos or games that really require an STE but since most normal ST games/demos
+ also 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. 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 incomplete. They may not work
- very well.
+
+ Note: Falcon and especially TT emulation are still considered as
+ experimental and incomplete.
+ Quite a bunch of programs do not work very well yet.
For STE emulation a STE compatible TOS image, e.q. version 1.06, 1.62 or 2.x, is strongly recommended. For TT emulation you need TOS 3.0x and for Falcon emulation you need TOS 4.0x. EmuTOS can be used on all machine types.
+- Select the CPU clock you want to use. 8Mhz is ST standard and the most - compatible. Use 16MHz for Mega STE and Falcon emulation. + The CPU type option can be used to select the level of the central processing + unit. If you are not sure what to use, simply select 68000 for ST and STE + machines and 68030 for TT and Falcon emulation, since this were the original + configurations used in the Atari computers. In case you want to vary + the CPU type, you have got to be aware of some constraints: +
+-
+
- + Atari ST and STE have only been shipped with a 68000 CPU, so for best + compatibility with old programs, you should choose this CPU type. + +
- + If you are going to use TOS 1.0x, you also have to select the 68000 CPU, + since these TOS versions are not aware of the higher CPU levels yet. + If you want to use a higher CPU level with the ST or STE machine type, + you've got to use TOS 2.0x instead. + +
- + Atari TT and Falcon computers were using the 68030 CPU, so you should select + the 68030 CPU type for these machines. + +
- + TOS 3.0x and 4.0x also only work with a CPU >= 68020. + +
- + 68010 and 68040, 68060 have never been used in official Atari computers, + so don't use these CPU types unless you've got some good reasons. + +
- + The 68060 option is only available in the "WinUAE" builds of + Hatari, and is currently also considered as experimental, so do not use + this option unless you know what you are doing. + +
+ The CPU clock option can be used to select the frequency that is used + to clock the CPU. 8 Mhz is the standard for ST and STE and the most + compatible frequency for old software. + Use 16 MHz for Mega STE and Falcon emulation. The CPU in the TT was clocked with 32 MHz.
-With the "Slower but more compatible CPU" option, you can enable - the emulation of 68k address errors and the CPU prefetch buffer. This is needed - for best compatibility, but it slows down emulation a little bit so you can - disable it if you don't need it.
- For Falcon mode, you can choose whether you want to enable DSP emulation, - fake it or completely disable it. Most Falcon programs only play sound or work + For Falcon mode, you can choose whether you want to disable DSP emulation, + fake it or enable full emulation. Most Falcon programs only play sound or work correctly when you enable the DSP emulation, but it needs a lot of host CPU - power (more than 2 GHz). So if you have a slow host CPU, you can try if your - Falcon program also runs with DSP disabled or in "dummy" mode. + power (more than 2 GHz) for full emulation. So if you have a slow host CPU, + you can try if your Falcon program also runs with DSP disabled or in + the "dummy" fake mode. Note that you can not change this option while the DSP based program already runs.
-You can also enable/disable Blitter emulation here. The Blitter is a custom - chip that accelerates some graphical operations. This switch only toggles the - Blitter in plain ST mode. In STE mode, the Blitter is always enabled (since all - STEs have been sold with a Blitter chip).
-If you enable the "Real time clock emulation" switch, a RTC will - be emulated based on the time of the host computer. Note that you need at least - TOS 1.02 for proper RTC emulation, TOS 1.00 does not support this.
-The Timer-D patch changes the Timer-D initialization from TOS. TOS uses - the MFP timer D as a baudrate generator for RS232. However, the TOS default - 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.
-NOTE: The emulated Atari is very very sensitive to these options - and it is strongly recommended to reset the emulation after changing - them (for most things that's done automatically). The correct - CPU type and clock are automatically selected when one uses the - --machine command line option.
++ The check boxes in the "CPU and system parameters" section can + be used to fine-tune the machine and CPU types. +
++ If you enable the "Real time clock emulation" switch, a RTC (like the ones + that could be found in the Mega-ST and Mega-STE computers) will be emulated + based on the time of the host computer. + This option is only affects the emulation of ST and STE machines. TT and + Falcon used a different kind of RTC (which is not optional and thus always + enabled in Hatari). + Note: You need at least TOS 1.02 for proper RTC emulation, TOS 1.00 does + not support this. +
++ The next check box can be used to enable/disable Blitter emulation. + The Blitter is a custom chip that accelerates some graphical operations. + This switch only toggles the Blitter in plain ST mode. In STE and Falcon mode, + the Blitter is always enabled (since these machines have always been sold + with a Blitter chip). The TT was always shipped without the Blitter chip. +
++ The "Patch Timer-D" option changes the Timer-D initialization from + TOS. TOS uses the MFP timer D as a baudrate generator for RS232. However, the + TOS default 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 better. +
++ With the "Boot faster" option, Hatari patches the TOS ROM and some + system variables, to speed up the boot process of the emulated system, e.g. + by simulating a warm reset. This is a convenient option, but some very few old + programs rely on an unmodified boot process, so in rare cases this option has + to be switched off to get those programs running. +
++ The "Prefetch mode" option is used to enable the emulation of 68k + address errors and the so-called CPU prefetch buffer. This is needed for best + compatibility, but it slows down emulation a little bit so you can disable it + if you don't need it and if you have a slow host system. +
++ The "Cycle exact", the "MMU emulation" and + "24-bit addressing" option are only available in the + "WinUAE" builds + of Hatari. They are considered as experimental and should be switched off + unless you know what you are doing. +
++ The FPU settings are also only available with the "WinUAE" builds + of Hatari. They can be used to select the type of floating point unit of CPUs + >= 68020. In the normal builds of Hatari, the FPU is always enabled for + 68030 and 68040 CPUs. +
++ NOTE: The emulated Atari system is very very sensitive to all of + these options and it is strongly recommended to reset the emulation after + changing them (for most things that's done automatically). + The correct CPU type and clock are automatically selected when one uses the + --machine command line option. +
-The Floppy Disks Dialog
+The Floppy Disks Dialog
+
This dialog can be used to choose which floppy disks should be emulated in the disk drives. 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. + "Floppy disk images" for details. +
++ Each drive can be enabled or disabled (as if it was not connected or turned + off). You can also choose to emulate a single sided drive instead of a double + sided one (some games or demos will have a different behaviour in single sided + mode).
Click on the button next to the
@@ -1804,33 +1083,39 @@ insert the second disk of a two disk gam
Some games then use the second drive automatically.
In the case that a game is not able to find the disk in the second drive,
you have to insert the second disk in drive A: manually when prompted.
-
+
NOTE: This option only works properly if the file name of the
first disks ends with an 'a' before the extension and the second disk name
ends with a 'b'.
- Select if you want to use slow FDC (Floppy Disk Controller) emulation. - "Slow floppy access" is normally not required, except for some few - slideshows / intros which run too fast without this option. + Select if you want to use fast FDC (Floppy Disk Controller) emulation. + + "Fast floppy access" option will speed up disk accesses, but this can + cause incompatibilities with programs that expect correct delays + (some games/demos don't expect data to be read too fast from the + disk). For example, when using STX images, most protections will fail + if fast floppy access is enabled.
- You can choose if you want Hatari to write-protect your disks. Atari ST virii - can spread on disk images too so it might be a good idea to enable the write - protection option. However you can't save highscores or games to your disk - images in that case. + If you want, you can set Hatari to write-protect your disks. Atari ST + virii can spread on disk images, so that can be a good idea. However, + note that some programs won't work correctly (or at all) with write + protected disks, and things like saving highscores in games will fail.
+
If you need to create a new blank disk image, click on . - Parameters for the new image can be set in the following dialog. - HD and ED disk sector counts are for non-Atari disk sizes, but such - disks are useful for programs that don't work with GEMDOS emulation. + Parameters for the new image can be set in the following dialog. HD + and ED disk sector counts are for larger, non-Atari disk sizes, they + can be useful with programs that don't work from hard drive, or with + with GEMDOS HD emulation. Click on to save the new image or on to return to the disk dialog.
@@ -1847,41 +1132,42 @@ ends with a 'b'. -The Hard Disks Dialog
+The Hard Disks Dialog
+
- This dialog can be used to change the harddisk settings. + This dialog can be used to change the hard disk settings.
- You can select a harddrive image for ACSI, IDE master or slave hard drive - emulation via image file here or you may select a directory of your local - filesystem to be emulated as the harddrive of the emulated system. + Here you can select a hard disk image file for ACSI, IDE master or + slave hard drive emulation, or you can select a host directory to be + emulated as the Atari hard drive.
- Check "Boot from HD" if you want Hatari to execute the AUTO folder - on the harddrive. - This option is checked by default if you specify a harddrive image or - a directory via the command line. + Check "Boot from HD" if you want Hatari to execute the AUTO folder on + the hard disk. This option is checked by default if you specify a + hard disk image or a directory via the command line.
Removing the check from the "Allow GEMDOS drive modification" option - will prevent Atari programs from modifying the files in GEMDOS HDD + will prevent Atari programs from modifying the files in GEMDOS HD emulation directory or creating new files under it.
- Note that for IDE hard disk emulation you also need a TOS version >= 2.05. - And ACSI hard disk emulation does not work with TOS 4.0x in Falcon mode. + Note that for IDE hard drive emulation you also need a TOS version >= 2.05. + And ACSI hard drive emulation does not work with TOS 4.0x in Falcon mode.
-The Memory Dialog
+The Memory Dialog
+
You can select the amount of RAM for the emulated ST here. Only @@ -1900,10 +1186,11 @@ different versions of Hatari. E.q. if yo cannot load your old memory snapshots back.
-The ROM Dialog
+The ROM Dialog
+
Here you can select the TOS image to use. Click on
Keep in mind that any custom cartridge image will not work together with
-GEMDOS hard disk emulation or the VDI extended resolution emulation
+GEMDOS HD emulation or the VDI extended resolution emulation
since some additional driver code will be used in the cartridge memory
space for these emulations.
The Joystick Dialog
+The Joystick Dialog
+
In this dialog, you can configure the emulated joysticks. @@ -1967,11 +1255,11 @@ certain games. In some other games, it g
See also the chapter "Emulated Joystick" for details.
-The Atari Monitor Dialog
+The Atari Monitor Dialog
+
@@ -1986,7 +1274,7 @@ GUI - the Atari monitor dialog">
switch to ST medium resolution, you will get a TV-like screen rendering
which is a little bit faster but darker compared to the normal "RGB"
monitor mode. Switching between mono and a color monitor acts like a monitor
- switch on a real ST - so beware, this will reboot your emulated system!
+ switch on a real ST - so beware, this will reboot your emulated system!
In TT mode, you can only choose between TT-high resolution ("Mono")
and normal modes (select one of the other monitor types).
Finally the Falcon mode supports all four types of monitors. Note that most
@@ -2005,19 +1293,18 @@ Extended VDI resolutions will emulate a
card in the emulated ST which give you larger resolutions with a higher
colordepth for GEM. Select a resolution and color depth. Check to
activate. It will disable all other video options mentioned above.
-Uncheck to get back to a normal ST behaviour.
+Uncheck to get back to a normal ST behaviour.
Note: Using an extended resolution will only work with GEM
conformant applications. 99% of all games and demos will not run if you
activate any extended resolution here.
The Hatari -Screen Dialog
+The Hatari Screen Dialog
+
@@ -2035,7 +1322,7 @@ on your screen.
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.
+ how many frames will be skipped.
Note: The frameskip option also affects the frame rate of the
screen animation recording!
+ 
+ 
+ 
+ 
+