--- hatari/doc/manual.html 2019/04/01 07:12:52 1.1.1.5 +++ hatari/doc/manual.html 2019/04/01 07:15:04 1.1.1.8 @@ -4,7 +4,7 @@ Hatari User's Manual - + @@ -14,27 +14,25 @@ + + +

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 +
+ + + + +
+−−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.

Using the emulated system

@@ -450,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 @@ -475,19 +1198,62 @@ 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
-

Select the CPU type to use here. For best Atari ST compatibility choose a - plain 68000.

-

Choose whether you want to emulate a normal ST or an STE. - Note: STE emulation is very incomplete. It may not work very well.

-

For STE emulation a STE compatible TOS image, e.q. version 1.06, 1.62 or 2.x, is strongly recommended.

-

Select the CPU clock you want to use. 8Mhz is ST standard and the most - compatible, 16MHz is for Mega STE emulation.

+

+ First you can select the CPU type here. Here are some important hints for + choosing the correct CPU type: +

+ + +

+ 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. +
+ 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 very incomplete. They may not work + very well. +

+

+ 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 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 @@ -502,36 +1268,36 @@ that you have made.

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 save to enable the patch, but if you encounter a program that + 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 @@ -539,15 +1305,16 @@ from the emulated drive. The emulated ST disk in its drive.

You can specify a default directory where Hatari will start to browse the filesystem.

-

Check the "Auto insert B" option if you want Hatari to be smart and -insert the second disk -of a two disk game automatically. This option will insert the second -disk in drive B and some -games may not be able to find the disks there. In that rare case you -will need to insert the -second disk manually when prompted.

-NOTE: This option does not always work properly. +Check the "Auto insert B" option if you want Hatari to be smart and +insert the second disk of a two disk game automatically. +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'.

If you need to create a new blank disk image, click on Create disk image. @@ -577,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 @@ -598,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 Browse to select one via the fileselector. Click on Eject to disconnect the custom cartridge image.

-

Keep in mind that any custom cartridge image will not work together with +

+For ST mode, use TOS 1.00, 1.02, 1.04 or 2.06. +For STE mode, use TOS 1.06, 1.62, 2.05 or 2.06. +If you want to use the TT mode, you must specify a TOS 3.06 image here. +And in Falcon mode, you have to use either TOS 4.00, 4.02, 4.04 or 4.92. +However, you should always use TOS 4.04 for Falcon mode, it's the most common one. +Also note that TOS 4.92 can not be booted from a boot disk (like it's done on a +real Falcon), you have to specify it directly in the TOS ROM setup dialog here. +

+

+Keep in mind that any custom cartridge image will not work together with GEMDOS hard disk emulation or the VDI extended resolution emulation since some additional driver code will be used in the cartridge memory -space for these emulations.
-

Note: These options are critical and you are strongly +space for these emulations. +

+

+Note: These options are critical and you are strongly advised to reset the emulated ST -when changing one of these option.

+when changing one of these option. +

+ -

The Joystick Dialog

+

The Joystick Dialog

Hatari's GUI - the joystick dialog @@ -650,35 +1432,66 @@ 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

-
-Hatari's GUI - the screen dialog +

The Screen Dialog

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

Here you control the video output of the emulated ST.

-

Check "Fullscreen" to run Hatari fullscreen, default is windowed.

-

Check "Interleaved mode" if you wish to have that old TV feeling in -Hatari. Every second line will be black. -This will only work in ST-MEDIUM or ST-LOW in scaled up resolutions.

-

Check "Frame Skip" to speed Hatari up if emulation is too slow. This -will only draw every second ST frame -instead of the default of drawing every ST frame. Uncheck if you have a -fast PC.

-

Check "Use Borders" if you wish to have the borders around the ST -screen.

-

"Force 8Bpp" will force SDL to use an 8bit video mode. You don't -need this for modern video cards.

-

You can select which sort of monitor to use. Check "Color" for games -and demos. If you check "Mono" here, -Hatari will emulate the good old SM124 and will not allow you to switch -to color modes from the running ST. -This toggle acts like a monitor switch with a color and monochrome -monitor connected.

-

"Zoom ST-Low res." will control if Hatari renders ST-LOW to a -320x200 or 640x400 PC display (with borders turned off) or 384x267 or -768x534. -Basically select this to toggle between a small or a large window.

+

+ Here you control the video output of the emulated Atari. +

+

+ Check "Fullscreen" to run Hatari fullscreen, default is windowed. +

+

+ "Use Borders" toggles the displaying of the borders around the ST + screen. Some few demos/games use the borders for displaying additional + graphics. However, when you enable this option, it increases CPU computing + time, so you should not enable it if you have a slow computer. + Please note that this option also only affects the ST and STE mode, TT and + Falcon modes are always displayed without borders. +

+

+ "Zoom ST-Low res." controls whether Hatari doubles the low + resolutions. For example Hatari then zooms the ST low resolution 320x200 to + 640x400 and it doubles 384x267 (ST low with borders) to 768x534. + Note that zooming also takes a lot of CPU computing time and should not be + enabled on slow computers. +

+

+ "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. 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 + machine type which you have selected in the "System options" + dialog. In ST and STE mode, you can choose between monochrome mode (select + "Mono") and color mode (select one of the other monitor types). + Note that when you select "TV" and use zoomed low resolution or + 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!
+ 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 + Falcon demos/games require a RGB or TV mode and do not work with VGA. +

+

Extended GEM resolutions will emulate some sort of extended graphics card in the emulated ST giving you larger resolutions and a higher colordepth in GEM. Select a resolution and color depth. Check to @@ -686,18 +1499,20 @@ activate. It will disable all other vide 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.
+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 @@ -714,14 +1529,22 @@ screen content really changed. mapping. Note that you also need a TOS version with the right language (e.g. use a French TOS if you are using a French keyboard).

You can also load a custom keyboard mapping file here if you wish. Please - note that the custom keyboard mapping will use the "symbolic" mapping - for all keys that are not defined by your map file. Have a look at the supplied - example mapfile to see how to create your own keyboard mapping.

+ note that the custom keyboard mapping will use the "symbolic" + 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.

@@ -730,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 @@ -770,10 +1590,12 @@ 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 the following keyboard shortcuts.

+features via Hatari keyboard shortcuts. Below are listed the default +shortcut key bindings:

@@ -786,20 +1608,21 @@ features via the following keyboard shor - + - + - + - + @@ -811,6 +1634,10 @@ window switch) + + + + @@ -827,21 +1654,34 @@ switch) + + + + + + + + - + - + - +
ALTGR+ggrabs a screenshotgrab a screenshot
ALTGR+iboss key: leave full screen mode and iconify -windowboss key: leave full screen mode, pause Hatari +and iconify its window
ALTGR+jactivates joystick emulation via cursor keystoggle 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
ALTGR+dopen dialog to select/change disk A
ALTGR+s enable/disable sound
enable/disable sound recording
ALTGR+ksave memory snapshot
ALTGR+lload memory snapshot
ALTGR+f or F11toggles fullscreen and windowed modetoggle between fullscreen and windowed mode
ALTGR+o or F12activate the GUIactivate the options GUI
PAUSEwill go to the debugger if Hatari was started with - the -D optionpause 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/).

+ +

Emulated Atari ST keyboard

All other keys on the keyboard act as the normal Atari ST keys so @@ -880,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

@@ -899,6 +1737,7 @@ the Hatari window. Do this by pressing t hotkey combination. Press it again to go back to normal mouse behaviour which allows you to work in other X11 windows while Hatari is up and running.

+

Mouse scrollwheel will act as cursor up and down keys.

Emulated joystick

@@ -914,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 @@ -922,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 socalled "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 socalled "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 @@ -1044,14 +1883,36 @@ 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.

-

To use the ACSI hard disk emulation, you need a hard disk image file +

+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. There is a HD image on the -Hatari web page for download. Perhaps we'll also provide a tool for -creating HD images one day.

+ST hard disk or grab one from the internet (e.g. from the Hatari website). +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 +you have for example created with the following command: +dd if=/dev/zero of=hd.img bs=512 count=xxx. +Then copy the complete AHDI 5.0 package to a floppy disk image, and enable +this floppy disk image and the fresh hard disk image in the emulator. +Start HDX.PRG from the floppy disk and format and partition the hard disk +with this tool. When you're finished, you have to restart the emulated system, +run AHDI.PRG from the floppy disk and HINSTALL.PRG afterwards. +With HINSTALL.PRG you can install the hard disk driver to the fresh HD image, +so you can directly boot from the hard disk image in the future. +

+ +

GEMDOS based hard disk emulation

With the GEMDOS based drive emulation, you can easily "mount" a folder from the host file system to a drive of the emulated Atari. To use the GEMDOS based drive emulation, you should use a folder on your @@ -1063,19 +1924,20 @@ 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.

-

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

@@ -1137,737 +1999,6 @@ emulation of the various custom chips an parts of the emulated system is much trickier.

-

Software compatibility list

- -

This is a little compilation of what Atari software does work in -Hatari. It is by no means finished.

- -

First is listed software (games, demos and applications) that work -on normal STs, after them is listed STE only software that has been -tested with the current STE hardware emulation.

- -

ST games

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
tested games
GameWorkingSoundComment
Eliminatoryesperfect 
Speedballyesperfect 
Xenonyesmusic ok - fx dodgybullets and explosions sound weired
Bubble Bobbleyes  
F15 Strike Eagle 2yesokkeyboard emulation seems to be dodgy
Rick Dangerousyesperfect 
Slayeryesokraster fx at highscore entry dodgy
Lethal Xcessno crashes while loading, sync scrolling will not work properly
Star Gooseyesmusic ok - bullet sound dodgy 
Xenon 2 - Megablastyesnearly perfect (including sampled intro) 
Metal Mutantyesseems oksome color effects in the lower screen seem buggy
Defenders Of The Earthyes  
Nebulusyesmusic ok; snowball, balls and trapdoors dodgyotherwise working to a playable extend
Leanderyes  
Navy Sealsyes  
Armalyteyes  
Wings Of Deathyes works in STE mode too
Tokiyes  
Alien Worldyes Only works with "--slowfdc"
Skweekyes Does not work with cartridge / HD emulation
- -

ST demos

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
tested demos
DemoWorkingSoundComment
Fantasia (by Dune)yes Only works with "--slowfdc"
Oddstuff (by Dune/SectorOne)yes Only works with "--slowfdc". - Enable "frameskip" to avoid the flicker.
If pigs could fly (by Syndicate)yes Only works with "--slowfdc"
LongScreen (by X-Troll)yes Only works with "--slowfdc"
Overdose (by Aggression)yes Does not work with cartridge / HD emulation
Virtual Escape (by Equinox)yes  
Posh (by Checkpoint)yes  
Flipo (by Oxygene)yes  
Syntax Terror (by DeltaForce)yes  
Sweety (by DHS)yes Does not work with HD emulation
B.I.G-demo (musicdemo by Exceptions)partially Flickers and colors in 3 of the screens don't look right
SoWatt (by CareBears)partially Colors and scrolling in the main menu are broken
Punish your machinepartially Colors and scrolling in the main menu are broken
Froggies over the Fence
Oh no more Froggies		No Stop when the main menu loads
- -

ST applications

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
tested applications
ApplicationWorkingComment
Programming
DevPac 2.2yesMonST crashy
Turbo AssembleryesDue to a bug you need to have a proper disk image inserted into drive A. Works otherwise!
GFABASIC 3.6TTyesMENU.PRG does not like harddisks. Use diskimages for -compiling.
ST Basicyes 
Orcs Resource editoryes 
Graphics
Mgifyes 
Neochromeyesrasters sometimes unstable
CrackartyesHarddisk access does not work with GEMDOS emulation - fine -with disk images
Speed Of Lightyes 
Sound
SidSound Designeryes 
MusicMon 2yes 
Protrackeryes 
Accompanist
(Henry Cosh Sequencer)		yesProgram works, but couldn't get Hatari midi output to work
Sequencer OneyesProgram and sample sounds work, but couldn't get Hatari midi - output to work
Cubase LiteyesProgram works, but couldn't get Hatari midi output to work
Text Editors
Tempusyes 
Qed editoryes 
Everest editoryes 
Business applications
Opus spreadsheetyes 
SBase databaseyes 
Communications
CAB browseryes 
Kivi QWK Readeryes 
Desktops
Teradesk desktopyes 
Thing desktopyes 
Others
ST-Guideyes 
Sagrotan viruskilleryes 
- -

STE games

- -

First are some STE games that do work with the STE features -in Hatari. Most of these games work only on STE, but here are also some -games which work (or have a version that works) also on ST, i.e. they -are just STE enhanced. These are marked with '*'.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
tested STE games
TitleWorkingSoundComment
Alien Blastyes  
Astrodia*yes Blitter support doesn't work with EmuTOS, only real STE TOS
Battletris+yes  
Blat!yes  
Bombamanyes  
Breakdanceyes THE ultimate scene game
ChuChu Rocketyes needs to be run from disk image
Dynabusters+yes  
H.E.R.O. 2yes Requires 4MB RAM
Manga Puzzleyes  
Penta*yes Blitter, DMA audio and STE fadings do work properly
No Limit IIyes  
Obsessionyes opens top & bottom border, but part from the right is not visible on screen
Operation Garfieldyes  
Pacman on Eyes  
Power Up*yes Problems with music, but DMA sound effects work
Rogerpartially Blitter timings inaccurate - game is too fast, - needs to be run from disk image
Skullsyes part from the right border is not visible on screen
Starball*yes  
Stardustyes  
Stupid Balloon gameyes  
Substationyes  
TomTaryes  
Utopospartially screen corrupted
Ultimate Arenayes  
Wolfenstein 3D*yes STE DMA sound does work
Zoolpartially screen corrupted, scrolling fails
- -

STE demos

- -

Some tested STE demos and intros

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
tested STE demos
TitleWorkingSoundComment
Aggression: Braindamageyes Colors in the last 2 screens don't look right
Armada: Armada is Deadyes bottom border broken
DHS: Tyranny & Massacreyes  
GGN: Aliveyes  
Ice: Extacyyes  
Imagina: 1992 X-mas demoyes flickers without frameskip
MJJ-Prod: 1st Stepyes  
New Core: Beyond Deadlineyes  
Omega: Grotesqueyes  
Paradox: X-mas 1994 demoyes  
Reservoir Gods: Mind Rewindyes opens all borders
Reservoir Gods: Grimeyyes  
Syntax: Reanimationyes  
MJJ-Prod: Tribute To Rainbow Tospartially screen corrupted, Blittermania does not work but the code does not crash nor lockup
Armada: RGBRuler demopartially doesn't look right
New Core: Core Flakespartially doesn't look right
Percy of Light: VGA slideshowpartially doesn't look right
- -

STE applications

- -

Finally some tested STE applications

- - - - - - - - - - - - - - - - - - - - - -
tested STE applications
TitleWorkingSoundComment
Octalyzeryes part from the right is not visible on screen
Protracker STEyes garbage at screen bottom, 50KHz replay duff
-
@@ -1878,8 +2009,7 @@ are just STE enhanced. These are marked src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" border="0" height="31" width="88"> -
Matthias Arndt -August 31 2005
+ November 23rd 2008