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