-Earlier versions of Hatari have successfully been tested by various people on
+In the course of time Hatari has successfully been tested by various people on
the following systems:
|
---mic <bool> |
+--timer-d <bool>
|
-Enable/disable (Falcon only) microphone
+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.
|
|
---sound <x> |
+--fast-boot <bool>
|
-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.
+Patch TOS and initialize the so-called "memvalid" system variables to
+by-pass the memory test of TOS, so that the system boots faster.
|
|
---sound-buffer-size <x> |
+--rtc <bool>
|
-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.
+Enable real-time clock
|
+
+
+Sound options
|
---ym-mixing <x> |
+--mic <bool>
|
-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.
+Enable/disable (Falcon only) microphone
|
|
---timer-d <bool> |
+--sound <x>
|
-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.
+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.
|
|
---rtc <bool> |
+--sound-buffer-size <x>
|
-Enable real-time clock
+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.
+ |
+
+
+
+
+ |
+
+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.
|
@@ -1810,9 +1892,10 @@ first disks ends with an 'a' before the
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" will speed up disk accesses, but this could give
+ some incompatibilities with some programs that expect correct delays.
+ (some games/demos don't expect data to be read too fast from the disk)
You can choose if you want Hatari to write-protect your disks. Atari ST virii
@@ -2512,8 +2595,10 @@ while the emulator is running.
On a 32-bit host system, the size of a hard disk image is limited to 2 GB.
-On 64-bit host systems, bigger images might be possible but the support for
-bigger images is not tested very well yet.
+On 64-bit host systems, bigger images might be possible but the support
+for bigger images is not tested very well yet. How large partition sizes
+are supported inside the hard disk (images) depends on the TOS version.
+TOS 1.0x supports up to 256MB partitions and TOS 4.0x up to 1GB ones.
@@ -2529,11 +2614,11 @@ length limit.
If you provide --harddisk option
-a directory containing only single letter 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.
+a directory containing 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.
GEMDOS drive emulation is an easy way to share files between the
@@ -2813,6 +2898,7 @@ Generic commands:
cd ( ) : change directory
evaluate ( e) : evaluate an expression
help ( h) : print help
+ history (hi) : show last CPU & DSP PC values & executed instructions
info ( i) : show machine/OS information
lock ( ) : specify information to show on entering the debugger
logfile ( f) : open or close log file
@@ -3259,8 +3345,8 @@ when you start a program.
To find out current program DATA and BSS segment contents,
use the corresponding variables:
-m data
-m bss
+m DATA
+m BSS
If you want to stop at a specific cycle within a frame (that is,
@@ -3279,14 +3365,6 @@ b HBL = "HBL+20"
b AesOpcode ! AesOpcode && AesOpcode < 0xffff :trace
-
@@ -3527,7 +3605,7 @@ sections.
trace gemdos,io_all
Please see Tracing section for more information
-on tracing, what's possible with in and what are its limitations.
+on tracing, what's possible with it and what are its limitations.
Stopping when certain PC address is passed Nth time
@@ -3600,6 +3678,30 @@ b d0 = "d0 + 10"
+Seeing code leading to a breakpoint
+To see the instructions executed before debugger was entered,
+you need to enabled history tracking beforehand and then whenever the
+debugger is entered, you can request given number (here 16) of past
+instructions to be shown:
+
+history on
+c
+[breakpoint is hit and debugger entered]
+history 16
+
+
+
+Getting instruction execution history for every breakpoint
+
+To see last 16 instructions whenever (a normal or tracing) breakpoint
+is hit:
+
+history on
+lock history 16
+c
+
+
+
Single step so that new register values are shown after each step
@@ -3956,7 +4058,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">
|
- June 2011
+ December 2011
|