| 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> |
| 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 |
| 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.<P> |
| 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. Under emulation, the memory |
| 128 |
< |
test is not necessary and the reset (F12) becomes much faster when it is |
| 129 |
< |
disabled.<P> |
| 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 |
< |
The setting <B>"Clear CIA ICR on write"</B> is necessary to make some |
| 132 |
< |
programs (such as the games "Gyruss" and "Motos") run that would otherwise |
| 133 |
< |
hang in an endless interrupt loop because they use an unusual technique to |
| 134 |
< |
acknowledge CIA interrupts (sometimes even without the programmer knowing |
| 55 |
< |
it). It should normally be turned off.<P> |
| 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 |
< |
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> |
| 136 |
> |
<H2>Advanced</H2> |
| 137 |
|
|
| 138 |
< |
<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> |
| 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 |
| 156 |
|
The settings for the four "cycles" coming closest to an original PAL C64 |
| 157 |
|
are (63, 23, 63, 64).<P> |
| 158 |
|
|
| 159 |
< |
With <B>"Draw every n-th frame"</B> you can select if Frodo should skip |
| 160 |
< |
frames when displaying the C64 graphics. The normal setting is "1", that |
| 161 |
< |
is, every frame (every simulated raster beam sweep) is recalculated. If you |
| 162 |
< |
change this to "2", for example, then only every second frame is |
| 163 |
< |
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> |
| 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 |
< |
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> |
| 165 |
> |
<H2>Unix/BeOS/AmigaOS</H2> |
| 166 |
|
|
| 167 |
< |
If <B>"Enable 1541 processor emulation"</B> is turned on, the four emulated |
| 168 |
< |
1541s are disabled and replaced by a single 1541 emulation (drive 8) that |
| 169 |
< |
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> |
| 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 |
|
|
| 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 |
– |
|
| 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 |
|
|
| 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 |
– |
|
| 177 |
|
</BODY> |
| 178 |
|
</HTML> |
