| 1 |
<HTML> |
| 2 |
<HEAD> |
| 3 |
<TITLE>Settings</TITLE> |
| 4 |
</HEAD> |
| 5 |
<BODY> |
| 6 |
|
| 7 |
<H1>Settings</H1> |
| 8 |
|
| 9 |
<HR> |
| 10 |
|
| 11 |
Under BeOS, the settings window appears directly after starting Frodo, or |
| 12 |
by selecting the "Settings..." menu item in the running emulation. Under |
| 13 |
Unix, the settings window is permanently visible.<P> |
| 14 |
|
| 15 |
With <B>"Sprite display"</B>, you can switch the display of sprites on and |
| 16 |
off. Turning them off speeds up the emulation a little when there are a lot |
| 17 |
of sprites on the screen.<P> |
| 18 |
|
| 19 |
<B>"Sprite collisions"</B> determines whether collisions between sprites |
| 20 |
and between sprites and graphics should be detected. Turning off collisions |
| 21 |
will make you invincible in some games (sadly, your enemies are likely to |
| 22 |
become invincible, too <TT>:-/</TT>.<P> |
| 23 |
|
| 24 |
<B>"Joystick on Port 1/2"</B> specifies on which ports you have real |
| 25 |
joysticks connected (as opposed to the <A HREF="keyboard.html">joystick |
| 26 |
emulation</A> on the numerical keypad). Joysticks are only supported under |
| 27 |
BeOS, Linux, RiscOS and AmigaOS (only one joystick). The port numbers relate |
| 28 |
to the host machine ports. On the BeBox, port 1 is the upper one and port 2 |
| 29 |
the lower one. You should only turn on the ports to which you have actually |
| 30 |
joysticks connected, or the keyboard will behave erratically. Frodo has an |
| 31 |
automatic joystick calibration. If you plug in a new joystick or change the |
| 32 |
joystick settings, you should first move the joystick once in each direction.<P> |
| 33 |
|
| 34 |
With <B>"Swap joysticks"</B> you can swap the assignment of the joystick |
| 35 |
ports of the host machine to the C64 ports without having to plug out and |
| 36 |
in your joysticks. E.g. if a C64 game is using a joystick on C64 port 1 you |
| 37 |
can simply activate "Swap joysticks" and use a joystick in port 2 on your |
| 38 |
machine to play the game.<P> |
| 39 |
|
| 40 |
When the field <B>"Limit speed"</B> is active, the emulation is slowed down |
| 41 |
when its relative speed exceeds 100%. If you set the value in "Every (n)th |
| 42 |
frame" so that the speed is just over 100% and activate the speed limiter, |
| 43 |
the emulation always runs at the original C64 speed, with the highest |
| 44 |
possible precision.<P> |
| 45 |
|
| 46 |
With the setting <B>"Fast Reset"</B> you can disable the memory test that |
| 47 |
is normally performed by the C64 on a reset. Under emulation, the memory |
| 48 |
test is not necessary and the reset (F12) becomes much faster when it is |
| 49 |
disabled.<P> |
| 50 |
|
| 51 |
The setting <B>"Clear CIA ICR on write"</B> is necessary to make some |
| 52 |
programs (such as the games "Gyruss" and "Motos") run that would otherwise |
| 53 |
hang in an endless interrupt loop because they use an unusual technique to |
| 54 |
acknowledge CIA interrupts (sometimes even without the programmer knowing |
| 55 |
it). It should normally be turned off.<P> |
| 56 |
|
| 57 |
The <B>"SID Filters"</B> field enables the emulation of the SID filters. |
| 58 |
The sound emulation is slightly faster, but worse, when the filters are |
| 59 |
disabled.<P> |
| 60 |
|
| 61 |
<B>"Doublescan lines"</B> is only available under BeOS for the "Screen" |
| 62 |
display type. It removes the black lines between scanlines, but makes |
| 63 |
the emulation a bit slower.<P> |
| 64 |
|
| 65 |
<B>"Cycles per line (CPU)"</B> and <B>"Cycles per Bad Line (CPU)"</B> set |
| 66 |
the number of clock cycles available to the CPU per normal raster line and |
| 67 |
per Bad Line. If a program is showing flickering lines or graphical flaws |
| 68 |
you should try to slightly alter both values. For "Bruce Lee" you must |
| 69 |
enter "62" for the "Cycles per line (CPU)".<P> |
| 70 |
|
| 71 |
With <B>"Cycles per line (CIA)"</B> you can control the speed of the CIA |
| 72 |
timers. Entering a higher value increases the frequency of cursor blinking |
| 73 |
and key repeat. Some programs don't run correcly with the default value |
| 74 |
(e.g. "Ballblazer" which needs a value of 65).<P> |
| 75 |
|
| 76 |
<B>"Cycles per line (1541)"</B> sets the number of cycles available to the |
| 77 |
1541 processor emulation per raster line. There is normally no need to |
| 78 |
change this value. This setting has no effect if 1541 processor emulation |
| 79 |
is turned off.<P> |
| 80 |
|
| 81 |
The settings for the four "cycles" coming closest to an original PAL C64 |
| 82 |
are (63, 23, 63, 64).<P> |
| 83 |
|
| 84 |
With <B>"Draw every n-th frame"</B> you can select if Frodo should skip |
| 85 |
frames when displaying the C64 graphics. The normal setting is "1", that |
| 86 |
is, every frame (every simulated raster beam sweep) is recalculated. If you |
| 87 |
change this to "2", for example, then only every second frame is |
| 88 |
calculated, immensely speeding up the display, though some raster effects |
| 89 |
may look a bit jerky. This setting can also be changed while the emulation |
| 90 |
is running with the '+' and '-' keys on the numerical keypad.<P> |
| 91 |
|
| 92 |
<B>"Display type"</B> is only available under BeOS. You can choose between |
| 93 |
running the emulation in a window or in full-screen mode (using the |
| 94 |
Game Kit).<P> |
| 95 |
|
| 96 |
The <B>"SID emulation type"</B> controls the sound emulation and has two |
| 97 |
settings: <EM>"None"</EM> and <EM>"Digital"</EM>. <EM>"None"</EM> means no |
| 98 |
sound (faster), <EM>"Digital"</EM> turns on the digital sound emulation |
| 99 |
(only available under BeOS, Linux and HP-UX). Future versions of Frodo may |
| 100 |
support more emulation types such as the use of a real SID chip on an |
| 101 |
expansion card or across a network.<P> |
| 102 |
|
| 103 |
<B>"REU size"</B> sets the size of the REU (RAM Expansion Unit) emulated by |
| 104 |
Frodo or turns the REU emulation off ("None"). Only few programs actually |
| 105 |
use the REU (operating systems like ACE and GEOS, and some utilities).<P> |
| 106 |
|
| 107 |
In the box <B>"Drives"</B>, there are four rows, each corresponding to one |
| 108 |
of four emulated 1541 drives with the drive numbers 8, 9, 10 and 11. For |
| 109 |
every drive, there is a <EM>popup control</EM>, a <EM>path entry field</EM> |
| 110 |
and a <EM>button</EM>:<P> |
| 111 |
|
| 112 |
With the <B>popup control</B>, you select the emulation mode of the |
| 113 |
respective disk drive (for more detailed information, see <A |
| 114 |
HREF="files.html">here</A>). There are three choices: <EM>"Dir"</EM>, |
| 115 |
<EM>"D64"</EM> and <EM>"T64"</EM>. <B>"Dir"</B> emulates the drive in a |
| 116 |
directory of the BeOS/Unix file system. <B>"D64"</B> accesses a .d64 or x64 |
| 117 |
disk image file. <B>"T64"</B> is the setting for accessing a .t64 or C64 |
| 118 |
LYNX archive file.<P> |
| 119 |
|
| 120 |
The <B>path entry field</B> holds either the path name of the directory for |
| 121 |
the "Dir" mode, the path name of the .d64/x64 image file for the "D64" |
| 122 |
mode, or the path name of the .t64/LYNX archive file for the "T64" mode. |
| 123 |
Under BeOS, you may also drop Tracker icons to the entry field.<P> |
| 124 |
|
| 125 |
The <B>button labeled "B"</B> opens a file panel/requester for a more |
| 126 |
comfortable selection of directories and .d64/x64/.t64/LYNX files.<P> |
| 127 |
|
| 128 |
With <B>"Map '/' <-> '\' in file names"</B> you control whether the |
| 129 |
'/' in C64 filenames will be translated to '\' and vice versa for "Dir" |
| 130 |
mode drives. The '/' character is used to access subdirectories under |
| 131 |
BeOS/Unix, but as the C64 doesn't have subdirectories, it's a valid part of |
| 132 |
a C64 file name. This is a problem if a program wants to create a file with |
| 133 |
'/' in it as BeOS/Unix would interpret the part before the '/' as a |
| 134 |
directory name and, finding no such directory, would return an error and |
| 135 |
the operation would fail. Now simply activate this gadget and all '/'s will |
| 136 |
transparently be translated into '\', so in directory listings the '/' will |
| 137 |
still appear. If you turn off this option, you can of course use the '/' to |
| 138 |
access files in subdirectories from the C64.<P> |
| 139 |
|
| 140 |
If <B>"Enable 1541 processor emulation"</B> is turned on, the four emulated |
| 141 |
1541s are disabled and replaced by a single 1541 emulation (drive 8) that |
| 142 |
only operates on .d64/x64 files, but emulates the 1541 processor and is |
| 143 |
compatible with about 50% of all fast loaders. However, it slows down the |
| 144 |
emulation considerably. If you have a .d64 with a program that doesn't load |
| 145 |
with the normal emulation (see above), you may have better luck with the |
| 146 |
1541 processor emulation instead. The path name of the disk image file to |
| 147 |
be used must be entered into the path entry field of drive 8.<P> |
| 148 |
|
| 149 |
<H2>BeOS/AmigaOS</H2> |
| 150 |
|
| 151 |
Clicking <B>"Start"/"OK"</B> will start the actual emulation (resp. return |
| 152 |
to it) and <B>"Quit"/"Cancel"</b> will discard your changes to the settings |
| 153 |
and quit Frodo (resp. discard the changes and return to the emulation).<P> |
| 154 |
|
| 155 |
With the menu items <B>"Open..."</B>, <B>"Save"</B>, <B>"Save As..."</B> |
| 156 |
and <B>"Revert"</B> you can load and save the settings from and to |
| 157 |
arbitrary files.<P> |
| 158 |
|
| 159 |
<H2>Unix</H2> |
| 160 |
|
| 161 |
Clicking <B>"Apply"</B> applies the settings of the "Cycles" controls to |
| 162 |
the running emulation (all other settings are applied automatically). |
| 163 |
<B>"Defaults"</B> reverts to the default settings, <B>"Quit"</B> quits |
| 164 |
Frodo and <B>"Reset"</B> resets the emulation.<P> |
| 165 |
|
| 166 |
</BODY> |
| 167 |
</HTML> |
