mirror of
https://github.com/Oibaf66/frodo-wii.git
synced 2024-11-14 07:35:12 +01:00
168 lines
8.2 KiB
HTML
168 lines
8.2 KiB
HTML
<HTML>
|
|
<HEAD>
|
|
<TITLE>Settings</TITLE>
|
|
</HEAD>
|
|
<BODY>
|
|
|
|
<H1>Settings</H1>
|
|
|
|
<HR>
|
|
|
|
Under BeOS, the settings window appears directly after starting Frodo, or
|
|
by selecting the "Settings..." menu item in the running emulation. Under
|
|
Unix, the settings window is permanently visible.<P>
|
|
|
|
With <B>"Sprite display"</B>, you can switch the display of sprites on and
|
|
off. Turning them off speeds up the emulation a little when there are a lot
|
|
of sprites on the screen.<P>
|
|
|
|
<B>"Sprite collisions"</B> determines whether collisions between sprites
|
|
and between sprites and graphics should be detected. Turning off collisions
|
|
will make you invincible in some games (sadly, your enemies are likely to
|
|
become invincible, too <TT>:-/</TT>.<P>
|
|
|
|
<B>"Joystick on Port 1/2"</B> specifies on which ports you have real
|
|
joysticks connected (as opposed to the <A HREF="keyboard.html">joystick
|
|
emulation</A> on the numerical keypad). Joysticks are only supported under
|
|
BeOS, Linux, RiscOS and AmigaOS (only one joystick). The port numbers relate
|
|
to the host machine ports. On the BeBox, port 1 is the upper one and port 2
|
|
the lower one. You should only turn on the ports to which you have actually
|
|
joysticks connected, or the keyboard will behave erratically. Frodo has an
|
|
automatic joystick calibration. If you plug in a new joystick or change the
|
|
joystick settings, you should first move the joystick once in each direction.<P>
|
|
|
|
With <B>"Swap joysticks"</B> you can swap the assignment of the joystick
|
|
ports of the host machine to the C64 ports without having to plug out and
|
|
in your joysticks. E.g. if a C64 game is using a joystick on C64 port 1 you
|
|
can simply activate "Swap joysticks" and use a joystick in port 2 on your
|
|
machine to play the game.<P>
|
|
|
|
When the field <B>"Limit speed"</B> is active, the emulation is slowed down
|
|
when its relative speed exceeds 100%. If you set the value in "Every (n)th
|
|
frame" so that the speed is just over 100% and activate the speed limiter,
|
|
the emulation always runs at the original C64 speed, with the highest
|
|
possible precision.<P>
|
|
|
|
With the setting <B>"Fast Reset"</B> you can disable the memory test that
|
|
is normally performed by the C64 on a reset. Under emulation, the memory
|
|
test is not necessary and the reset (F12) becomes much faster when it is
|
|
disabled.<P>
|
|
|
|
The setting <B>"Clear CIA ICR on write"</B> is necessary to make some
|
|
programs (such as the games "Gyruss" and "Motos") run that would otherwise
|
|
hang in an endless interrupt loop because they use an unusual technique to
|
|
acknowledge CIA interrupts (sometimes even without the programmer knowing
|
|
it). It should normally be turned off.<P>
|
|
|
|
The <B>"SID Filters"</B> field enables the emulation of the SID filters.
|
|
The sound emulation is slightly faster, but worse, when the filters are
|
|
disabled.<P>
|
|
|
|
<B>"Doublescan lines"</B> is only available under BeOS for the "Screen"
|
|
display type. It removes the black lines between scanlines, but makes
|
|
the emulation a bit slower.<P>
|
|
|
|
<B>"Cycles per line (CPU)"</B> and <B>"Cycles per Bad Line (CPU)"</B> set
|
|
the number of clock cycles available to the CPU per normal raster line and
|
|
per Bad Line. If a program is showing flickering lines or graphical flaws
|
|
you should try to slightly alter both values. For "Bruce Lee" you must
|
|
enter "62" for the "Cycles per line (CPU)".<P>
|
|
|
|
With <B>"Cycles per line (CIA)"</B> you can control the speed of the CIA
|
|
timers. Entering a higher value increases the frequency of cursor blinking
|
|
and key repeat. Some programs don't run correcly with the default value
|
|
(e.g. "Ballblazer" which needs a value of 65).<P>
|
|
|
|
<B>"Cycles per line (1541)"</B> sets the number of cycles available to the
|
|
1541 processor emulation per raster line. There is normally no need to
|
|
change this value. This setting has no effect if 1541 processor emulation
|
|
is turned off.<P>
|
|
|
|
The settings for the four "cycles" coming closest to an original PAL C64
|
|
are (63, 23, 63, 64).<P>
|
|
|
|
With <B>"Draw every n-th frame"</B> you can select if Frodo should skip
|
|
frames when displaying the C64 graphics. The normal setting is "1", that
|
|
is, every frame (every simulated raster beam sweep) is recalculated. If you
|
|
change this to "2", for example, then only every second frame is
|
|
calculated, immensely speeding up the display, though some raster effects
|
|
may look a bit jerky. This setting can also be changed while the emulation
|
|
is running with the '+' and '-' keys on the numerical keypad.<P>
|
|
|
|
<B>"Display type"</B> is only available under BeOS. You can choose between
|
|
running the emulation in a window or in full-screen mode (using the
|
|
Game Kit).<P>
|
|
|
|
The <B>"SID emulation type"</B> controls the sound emulation and has two
|
|
settings: <EM>"None"</EM> and <EM>"Digital"</EM>. <EM>"None"</EM> means no
|
|
sound (faster), <EM>"Digital"</EM> turns on the digital sound emulation
|
|
(only available under BeOS, Linux and HP-UX). Future versions of Frodo may
|
|
support more emulation types such as the use of a real SID chip on an
|
|
expansion card or across a network.<P>
|
|
|
|
<B>"REU size"</B> sets the size of the REU (RAM Expansion Unit) emulated by
|
|
Frodo or turns the REU emulation off ("None"). Only few programs actually
|
|
use the REU (operating systems like ACE and GEOS, and some utilities).<P>
|
|
|
|
In the box <B>"Drives"</B>, there are four rows, each corresponding to one
|
|
of four emulated 1541 drives with the drive numbers 8, 9, 10 and 11. For
|
|
every drive, there is a <EM>popup control</EM>, a <EM>path entry field</EM>
|
|
and a <EM>button</EM>:<P>
|
|
|
|
With the <B>popup control</B>, you select the emulation mode of the
|
|
respective disk drive (for more detailed information, see <A
|
|
HREF="files.html">here</A>). There are three choices: <EM>"Dir"</EM>,
|
|
<EM>"D64"</EM> and <EM>"T64"</EM>. <B>"Dir"</B> emulates the drive in a
|
|
directory of the BeOS/Unix file system. <B>"D64"</B> accesses a .d64 or x64
|
|
disk image file. <B>"T64"</B> is the setting for accessing a .t64 or C64
|
|
LYNX archive file.<P>
|
|
|
|
The <B>path entry field</B> holds either the path name of the directory for
|
|
the "Dir" mode, the path name of the .d64/x64 image file for the "D64"
|
|
mode, or the path name of the .t64/LYNX archive file for the "T64" mode.
|
|
Under BeOS, you may also drop Tracker icons to the entry field.<P>
|
|
|
|
The <B>button labeled "B"</B> opens a file panel/requester for a more
|
|
comfortable selection of directories and .d64/x64/.t64/LYNX files.<P>
|
|
|
|
With <B>"Map '/' <-> '\' in file names"</B> you control whether the
|
|
'/' in C64 filenames will be translated to '\' and vice versa for "Dir"
|
|
mode drives. The '/' character is used to access subdirectories under
|
|
BeOS/Unix, but as the C64 doesn't have subdirectories, it's a valid part of
|
|
a C64 file name. This is a problem if a program wants to create a file with
|
|
'/' in it as BeOS/Unix would interpret the part before the '/' as a
|
|
directory name and, finding no such directory, would return an error and
|
|
the operation would fail. Now simply activate this gadget and all '/'s will
|
|
transparently be translated into '\', so in directory listings the '/' will
|
|
still appear. If you turn off this option, you can of course use the '/' to
|
|
access files in subdirectories from the C64.<P>
|
|
|
|
If <B>"Enable 1541 processor emulation"</B> is turned on, the four emulated
|
|
1541s are disabled and replaced by a single 1541 emulation (drive 8) that
|
|
only operates on .d64/x64 files, but emulates the 1541 processor and is
|
|
compatible with about 50% of all fast loaders. However, it slows down the
|
|
emulation considerably. If you have a .d64 with a program that doesn't load
|
|
with the normal emulation (see above), you may have better luck with the
|
|
1541 processor emulation instead. The path name of the disk image file to
|
|
be used must be entered into the path entry field of drive 8.<P>
|
|
|
|
<H2>BeOS/AmigaOS</H2>
|
|
|
|
Clicking <B>"Start"/"OK"</B> will start the actual emulation (resp. return
|
|
to it) and <B>"Quit"/"Cancel"</b> will discard your changes to the settings
|
|
and quit Frodo (resp. discard the changes and return to the emulation).<P>
|
|
|
|
With the menu items <B>"Open..."</B>, <B>"Save"</B>, <B>"Save As..."</B>
|
|
and <B>"Revert"</B> you can load and save the settings from and to
|
|
arbitrary files.<P>
|
|
|
|
<H2>Unix</H2>
|
|
|
|
Clicking <B>"Apply"</B> applies the settings of the "Cycles" controls to
|
|
the running emulation (all other settings are applied automatically).
|
|
<B>"Defaults"</B> reverts to the default settings, <B>"Quit"</B> quits
|
|
Frodo and <B>"Reset"</B> resets the emulation.<P>
|
|
|
|
</BODY>
|
|
</HTML>
|