| 1 |
<!DOCTYPE html> |
| 2 |
<html lang="en"> |
| 3 |
<head> |
| 4 |
<meta charset="utf-8"> |
| 5 |
<link title="Purple" rel="stylesheet" href="manual-purple.css" type="text/css"> |
| 6 |
<link title="Minty" rel="alternate stylesheet" href="manual-minty.css" type="text/css"> |
| 7 |
<link title="Plain" rel="alternate stylesheet" href="manual.css" type="text/css"> |
| 8 |
<title>openMSX FAQ</title> |
| 9 |
</head> |
| 10 |
|
| 11 |
<body> |
| 12 |
|
| 13 |
<h1>openMSX FAQ</h1> |
| 14 |
|
| 15 |
<h2>Contents</h2> |
| 16 |
<ul class="toccat"> |
| 17 |
<li><a class="internal" href="#install">Installing openMSX</a>: |
| 18 |
<ul class="toc"> |
| 19 |
<li><a class="internal" href="#easyinstall">What is the easiest way to install openMSX?</a></li> |
| 20 |
<li><a class="internal" href="#ziporinstaller">Should I download the Zip or the Installer for Windows?</a></li> |
| 21 |
<li><a class="internal" href="#roms">Why doesn't openMSX come with system ROMs?</a></li> |
| 22 |
<li><a class="internal" href="#whereroms">Where do I install the system ROMs?</a> </li> |
| 23 |
<li><a class="internal" href="#blackscreen">Why do I only get a black screen?</a> </li> |
| 24 |
</ul></li> |
| 25 |
<li><a class="internal" href="#use">Using openMSX</a>: |
| 26 |
<ul class="toc"> |
| 27 |
<li><a class="internal" href="#easyuse">Is openMSX easy to use?</a></li> |
| 28 |
<li><a class="internal" href="#c-bios">All I get is "No cartridge found." What's wrong?</a></li> |
| 29 |
<li><a class="internal" href="#nodrive">I get "Fatal error: No drive named 'diska'." What's wrong?</a></li> |
| 30 |
<li><a class="internal" href="#rundiskstapes">It looks like only ROMs are supported. How can I run disk and tape software?</a></li> |
| 31 |
<li><a class="internal" href="#savegame">How do I save my game?</a></li> |
| 32 |
<li><a class="internal" href="#harddisk">What about openMSX harddisk support?</a></li> |
| 33 |
<li><a class="internal" href="#videosource">It seems the MSX hangs when running GFX9000 software; what's wrong?</a></li> |
| 34 |
<li><a class="internal" href="#leds">Great, those on-screen LEDs! How do I get rid of them?</a></li> |
| 35 |
<li><a class="internal" href="#commands">Where is the full list of commands and settings?</a></li> |
| 36 |
<li><a class="internal" href="#slow">How can I speed up openMSX? How hard is it to emulate an old MSX on a modern PC?</a></li> |
| 37 |
<li><a class="internal" href="#perfect_videos">How do I create perfect play videos, like Vampier's YouTube videos?</a></li> |
| 38 |
<li><a class="internal" href="#tas">How do I use openMSX for TAS (Tool-Assisted Speedruns)?</a></li> |
| 39 |
<li><a class="internal" href="#disablereverse">How can I disable reverse or the reverse bar time line?</a></li> |
| 40 |
</ul></li> |
| 41 |
<li><a class="internal" href="#other">Other</a>: |
| 42 |
<ul class="toc"> |
| 43 |
<li><a class="internal" href="#codec">What codec do you use to record videos and where do I get it (because I only get eternal darkness in my videos)?</a> </li> |
| 44 |
<li><a class="internal" href="#soundproblems">Why do I hear serious sound glitches and/or stuttering, especially when using Windows?</a> </li> |
| 45 |
<li><a class="internal" href="#techinfo">Where can I find more technical info about openMSX?</a> </li> |
| 46 |
<li><a class="internal" href="#tworeversebars">Why do I see/get two reverse bars in openMSX?</a> </li> |
| 47 |
<li><a class="internal" href="#twolediconbars">Why do I see/get two LED/icon bars in openMSX?</a> </li> |
| 48 |
<li><a class="internal" href="#otherquestion">My question is not listed here. Help me.</a> </li> |
| 49 |
</ul></li> |
| 50 |
</ul> |
| 51 |
|
| 52 |
<h2><a id="install">Installing openMSX</a></h2> |
| 53 |
|
| 54 |
<h3><a id="easyinstall">What is the easiest way to install openMSX?</a></h3> |
| 55 |
|
| 56 |
<p> |
| 57 |
The easiest way to install openMSX is to use a ready-made package. Whether or not one |
| 58 |
is available depends on your operating system: |
| 59 |
</p> |
| 60 |
|
| 61 |
<dl> |
| 62 |
<dt>Windows</dt> |
| 63 |
<dd>The easiest way to install openMSX is by running the installer. Download the |
| 64 |
installer from |
| 65 |
<a class="external" href="http://openmsx.org/">our website</a> (check out the |
| 66 |
Download box), unpack the <code>.zip</code> file, and double-click on the |
| 67 |
resulting <code>.msi</code> file. After this, you should have a working openMSX |
| 68 |
and openMSX Catapult.<br /> |
| 69 |
<br /> |
| 70 |
You can also download the Zip distribution which contains only the emulator |
| 71 |
files (no installer) and unpack it to the directory of your choice.</dd> |
| 72 |
<dt>macOS</dt> |
| 73 |
<dd>The easiest way is to get the <code>.dmg</code> file from <a |
| 74 |
class="external" href="http://openmsx.org/">our website</a> (check the Download |
| 75 |
box). There is no Catapult for macOS, but Catapult isn't adding much value |
| 76 |
anyway nowadays, as there is a built-in GUI now. </dd> |
| 77 |
<dt>Linux</dt> |
| 78 |
<dd> |
| 79 |
<dl> |
| 80 |
<dt>Debian GNU/Linux</dt> |
| 81 |
<dd>Install the <code><a class="external" |
| 82 |
href="http://packages.debian.org/openmsx">openmsx</a></code>, |
| 83 |
<code>openmsx-data</code>, <code>cbios</code> and <code>openmsx-catapult</code> |
| 84 |
packages. The simplest way is to run <code>apt install |
| 85 |
openmsx-catapult</code>, APT will install the other needed packages as well. |
| 86 |
</dd> |
| 87 |
<dt>Ubuntu</dt> |
| 88 |
<dd>The <a class="external" |
| 89 |
href="https://launchpad.net/ubuntu/+source/openmsx">Ubuntu packages</a> are |
| 90 |
similar to the Debian ones. You can find them in the "universe" repository, so |
| 91 |
make sure you have that enabled in your <code>/etc/apt/sources.list</code>. |
| 92 |
</dd> |
| 93 |
<dt>Fedora</dt> |
| 94 |
<dd>Fedora has <a class="external" |
| 95 |
href="http://koji.fedoraproject.org/koji/packageinfo?packageID=4949">packaged</a> |
| 96 |
openMSX in the main archive since Fedora 7. You can just run <code>yum install |
| 97 |
openmsx</code> to install openMSX.</dd> |
| 98 |
<dt>Gentoo</dt> |
| 99 |
<dd>You can find an ebuild for openMSX in the "games-emulation" category. |
| 100 |
</dd> |
| 101 |
<dt>openSUSE</dt> |
| 102 |
<dd>openSUSE 10.3 (and 11.x) contains an openMSX package, but it seems to be somewhat outdated.</dd> |
| 103 |
<dt>Mandriva</dt> |
| 104 |
<dd>Source RPMs occasionally appear on the <a class="external" href="http://rpmfind.net/linux/rpm2html/search.php?query=openmsx">RPMFind.net search for openMSX</a>, but we don't know how to use them exactly or if they are also included in the official distribution.</dd> |
| 105 |
<dt>ArchLinux</dt> |
| 106 |
<dd>Packages are available for <a class="external" href="https://aur.archlinux.org/packages/openmsx">openMSX</a> and <a class="external" href="https://aur.archlinux.org/packages/openmsx-catapult">Catapult</a> in the <a class="external" href="http://aur.archlinux.org/packages">ArchLinux User-community Respository (AUR)</a>.</dd> |
| 107 |
<dt>other</dt> |
| 108 |
<dd>It is possible that openMSX has been packaged for other Linux systems as |
| 109 |
well, but we are not able to keep track of all of them. Search for openMSX in your package management system and there's a fair chance that openMSX will pop |
| 110 |
up. If it doesn't, look for "other", a few lines below.</dd> |
| 111 |
</dl> |
| 112 |
</dd> |
| 113 |
<dt>FreeBSD</dt> |
| 114 |
<dd>There is a <a class="external" href="https://cgit.freebsd.org/ports/tree/emulators/openmsx">port for openMSX</a> in FreeBSD. It is simply called "openmsx". There is also a <a class="external" href="https://cgit.freebsd.org/ports/tree/emulators/catapult/">port for Catapult</a>.</dd> |
| 115 |
<dt>NetBSD</dt> |
| 116 |
<dd>There is a <a class="external" href="http://cdn.netbsd.org/pub/pkgsrc/current/pkgsrc/emulators/openmsx/">port for openMSX</a> in NetBSD, but it seems to be somewhat outdated. |
| 117 |
</dd> |
| 118 |
<dt>other</dt> |
| 119 |
<dd>Right. Sorry, but you'll have to install openMSX from source. This is not as complicated as it may sound, because we have automated most of the process and documented the rest. For clarity's sake: we're talking about the <a class="external" href="compile.html">Compilation Guide</a>. |
| 120 |
</dd> |
| 121 |
</dl> |
| 122 |
|
| 123 |
<p> |
| 124 |
Note that in any case, no system ROMs are ever installed, so only the C-BIOS |
| 125 |
machines work out-of-the-box. See also the next couple of questions. |
| 126 |
</p> |
| 127 |
<p> |
| 128 |
If you still think openMSX is difficult to install, <a class="external" href="compile.html#contact">please tell us why</a>! |
| 129 |
</p> |
| 130 |
|
| 131 |
<h3><a id="ziporinstaller">Should I download the Zip or the Installer for Windows?</a></h3> |
| 132 |
|
| 133 |
<p> |
| 134 |
We strongly recommend to use the installer. It contains a straightforward |
| 135 |
Windows Installer package. |
| 136 |
With the installer, your openMSX experience is only about 3 clicks away. The |
| 137 |
Zip file is meant for experienced users and those familiar with openMSX and |
| 138 |
emulators in general. |
| 139 |
</p> |
| 140 |
|
| 141 |
<p> |
| 142 |
The zip file may suggest that it is a "portable" version of the emulator, but |
| 143 |
it isn't. It's exactly the same thing, just not packaged in the installer. The zip file |
| 144 |
still assumes the same paths as described in the <a class="external" |
| 145 |
href="setup.html#romlocations">Setup Guide</a>. |
| 146 |
</p> |
| 147 |
|
| 148 |
<h3><a id="roms">Why doesn't openMSX come with system ROMs?</a></h3> |
| 149 |
|
| 150 |
<p> |
| 151 |
The MSX system ROMs are copyrighted. In other words: it's illegal to include |
| 152 |
them in our software package without a license. The Setup Guide contains a <a |
| 153 |
class="external" href="setup.html#systemroms">section about system ROMs</a>. |
| 154 |
</p> |
| 155 |
|
| 156 |
<h3><a id="whereroms">Where do I install the system ROMs?</a></h3> |
| 157 |
|
| 158 |
<p>System ROMs should be put in <code>share/systemroms</code>. Please see |
| 159 |
the <a class="external" href="setup.html#romlocation">Setup Guide</a> for the |
| 160 |
exact location for your operating system. |
| 161 |
</p> |
| 162 |
<p> |
| 163 |
The quickest way to see where openMSX is searching for system ROMs on your |
| 164 |
installation is via the GUI under <span class="menu-reference">Main menu bar |
| 165 |
→ Machine → Test MSX hardware...</span>. At the bottom of this dialog |
| 166 |
you can find buttons to quickly open a (native) file browser on the locations |
| 167 |
where the ROMs are searched for, both for the user folder and the system-wide |
| 168 |
folder. We recommend to use the user folder, so that your system-wide folder |
| 169 |
only contains the files that come with the openMSX installation. |
| 170 |
</p> |
| 171 |
|
| 172 |
<h3><a id="blackscreen">Why do I only get a black screen?</a></h3> |
| 173 |
|
| 174 |
<p> |
| 175 |
You may also see errors like "Error compiling shader". |
| 176 |
</p> |
| 177 |
|
| 178 |
<p> |
| 179 |
You are probably mixing two installations of openMSX. Make sure that your |
| 180 |
openMSX user directory (see <a class="external" |
| 181 |
href="setup.html#romlocation">this overview where it is for your platform</a>) |
| 182 |
does not have any openMSX installation stuff, only your own files, like system |
| 183 |
ROMs and whatnot. Make sure no other folders (like |
| 184 |
<code>share/shaders</code> or <code>share/scripts</code>) are there, as they may |
| 185 |
interfere with the files that we ship with openMSX. |
| 186 |
</p> |
| 187 |
|
| 188 |
<h2><a id="use">Using openMSX</a></h2> |
| 189 |
|
| 190 |
<h3><a id="easyuse">Is openMSX easy to use?</a></h3> |
| 191 |
|
| 192 |
<p> |
| 193 |
We sure hope so, especially with the built-in GUI nowadays. Still encountering problems using openMSX? We'd <a class="external" href="user.html#contact">love to hear about it</a>. |
| 194 |
</p> |
| 195 |
|
| 196 |
<p> |
| 197 |
Although the GUI is quite comprehensive, it doesn't give you access to all |
| 198 |
features of openMSX. Get access to all the features by using the openMSX built-in |
| 199 |
console, and find out in <a class="external" |
| 200 |
href="user.html#controlling">the User's Manual</a> how this works. It's not a GUI, but we still did |
| 201 |
our best to make this console as easy to use as possible. |
| 202 |
</p> |
| 203 |
|
| 204 |
<p> |
| 205 |
If you think openMSX is not easy to use, please tell us why! Contact info is in |
| 206 |
<a class="external" href="user.html#contact">the manuals</a>. |
| 207 |
</p> |
| 208 |
|
| 209 |
<p> |
| 210 |
Oh, you might wonder: why isn't the GUI looking more like other applications of |
| 211 |
my operating system, like with (most) other emulators? We chose this GUI |
| 212 |
toolkit, because it's independent of the operating system and it is easily |
| 213 |
integrated into our code. This way we can support more operating systems with |
| 214 |
the same amount of work (and developers) and make it easy for us to add new |
| 215 |
features for everyone. |
| 216 |
</p> |
| 217 |
|
| 218 |
<h3><a id="c-bios">All I get is "No cartridge found." What's wrong?</a></h3> |
| 219 |
|
| 220 |
<p>You are probably talking about this:</p> |
| 221 |
|
| 222 |
<p class="image"> |
| 223 |
<img src="nocartfound.png" width="640" height="480" alt="No cartridge found."> |
| 224 |
</p> |
| 225 |
|
| 226 |
<p>openMSX doesn't come with any system ROMs, see <a class="internal" |
| 227 |
href="#roms">Why doesn't openMSX come with system ROMs?</a>. To have something |
| 228 |
to be able to run some software, openMSX comes with a free replacement of an |
| 229 |
MSX BIOS ROM called <a class="external" |
| 230 |
href="http://cbios.sourceforge.net/">C-BIOS</a>, written by BouKiChi, Reikan |
| 231 |
and nowadays the C-BIOS Association. This is also what you can see in the |
| 232 |
screen: C-BIOS 0.25. |
| 233 |
</p> |
| 234 |
|
| 235 |
<p> |
| 236 |
The message, in other words, does not come from openMSX, but rather from C-BIOS, an MSX program which |
| 237 |
tries to start a cartridge that is inserted in the MSX that is being emulated |
| 238 |
by openMSX. And it seems you didn't insert any cartridge for it... So, either |
| 239 |
run openMSX with a ROM image or <a class="internal" |
| 240 |
href="setup.html#installrom">install real MSX system ROMs</a> for a particular |
| 241 |
machine and run that one. |
| 242 |
</p> |
| 243 |
|
| 244 |
<p>Note that the current version of C-BIOS can only run cartridges and does not |
| 245 |
support disk or tape usage. More information can be found in the <a |
| 246 |
class="external" href="setup.html#cbios">Setup Guide</a>. |
| 247 |
</p> |
| 248 |
|
| 249 |
<p>As C-BIOS does not contain an implementation of MSX-BASIC at the moment, ROM cartridges that rely on MSX-BASIC also do not work on a C-BIOS machine and C-BIOS will report "Cannot execute a BASIC ROM":</p> |
| 250 |
|
| 251 |
<p class="image"> |
| 252 |
<img src="cannotexecuteabasicrom.png" width="640" height="480" alt="Cannot execute a BASIC ROM."> |
| 253 |
</p> |
| 254 |
|
| 255 |
<p>And there are also ROM cartridges that are actual conversion from disk images and these usually also rely on MSX-BASIC, and they usually stop with this screen:</p> |
| 256 |
|
| 257 |
<p class="image"> |
| 258 |
<img src="callednonexistingbasic.png" width="640" height="480" alt="Called non-existing BASIC."> |
| 259 |
</p> |
| 260 |
|
| 261 |
<p> |
| 262 |
In these cases, the only solution is to <a class="internal" |
| 263 |
href="setup.html#installrom">install real MSX system ROMs</a> for a particular |
| 264 |
machine and run that one. |
| 265 |
</p> |
| 266 |
|
| 267 |
<h3><a id="nodrive">I get "Fatal error: No drive named 'diska'." What's wrong?</a></h3> |
| 268 |
|
| 269 |
<p>You are probably using Catapult with C-BIOS and you're trying to run a program on a disk image.</p> |
| 270 |
|
| 271 |
<p>Unfortunately, the C-BIOS machines that come with openMSX do not support |
| 272 |
disk or tape usage. Please see the <a class="external" |
| 273 |
href="setup.html#cbios">Setup Guide</a>.</p> |
| 274 |
|
| 275 |
<p>The tricky thing is that Catapult always shows the disk, tape and cartridge |
| 276 |
controls, ignoring if the machine you're emulating actually supports |
| 277 |
them. However, the built in GUI menus show |
| 278 |
exactly what you can do with the currently running MSX: it only shows options |
| 279 |
to insert a disk drive if there is actually a disk drive present on the system. |
| 280 |
Please give it a try! It's the future of openMSX!</p> |
| 281 |
|
| 282 |
<p>Until C-BIOS supports disks or tapes, you will have to |
| 283 |
install the system ROMs of a real MSX (one with a disk drive!) and emulate that machine. More about this in the <a |
| 284 |
class="external" href="setup.html#systemroms">Setup Guide</a>.</p> |
| 285 |
|
| 286 |
<h3><a id="rundiskstapes">It looks like only ROMs are supported. How can I run disk and tape software?</a></h3> |
| 287 |
|
| 288 |
<p>You are probably running the C-BIOS machines that came with openMSX and did |
| 289 |
not install any system ROMs of other machines (or did not choose to emulate |
| 290 |
another machine). The C-BIOS machines rely on the freely available C-BIOS ROMs |
| 291 |
and that's why we can ship them with openMSX. However, C-BIOS only supports ROM |
| 292 |
images for now. More information about that in the <a class="external" |
| 293 |
href="setup.html#cbios">C-BIOS section of the Setup Guide</a>. |
| 294 |
</p> |
| 295 |
|
| 296 |
<p>If you want to run software from other media (disks, tapes, etc.), you will |
| 297 |
have to install other system ROMs, originating from real, existing MSX machines. |
| 298 |
Then you can run MSX machines other than the C-BIOS machines, and which do support |
| 299 |
tape and/or disk software (depending on the emulated MSX model). More about |
| 300 |
this in the <a class="external" href="setup.html#systemroms">Setup Guide</a>. |
| 301 |
</p> |
| 302 |
|
| 303 |
<h3><a id="savegame">How do I save my game?</a></h3> |
| 304 |
|
| 305 |
<h4><a id="savegame-general">In General</a></h4> |
| 306 |
|
| 307 |
<p> |
| 308 |
You've been playing a game and want to continue another time, so you want to |
| 309 |
save your progress. You can either save your game as you would on a real MSX, |
| 310 |
or you can use the built in <a class="external" href="user.html#savestate">save |
| 311 |
state mechanism</a>, which is explained in the manual. |
| 312 |
</p> |
| 313 |
|
| 314 |
<p>If you consider that cheating, or are interested in how you could save your |
| 315 |
game on a real MSX, read on... How it works, depends on the game: |
| 316 |
</p> |
| 317 |
|
| 318 |
<dl> |
| 319 |
<dt>Game Disk</dt> |
| 320 |
<dd>Some disk-based games save on one of the game disks. Make sure the disk is |
| 321 |
not write protected; in openMSX this means the disk image must be an ordinary |
| 322 |
DSK image (not compressed as ZIP or XSA) and not read-only. |
| 323 |
</dd> |
| 324 |
<dt>Separate Disk</dt> |
| 325 |
<dd>Some games save on a separate disk. You can create an empty disk for this |
| 326 |
purpose by clicking on the plus-icon in the Disk Drive dialog (<span |
| 327 |
class="menu-reference">Main menu bar → Media → Disk Drive A</span>). |
| 328 |
Since many games save in fixed sector locations instead of files, it is best to |
| 329 |
reserve a separate save game disk for each game. |
| 330 |
</dd> |
| 331 |
<dt>PAC SRAM</dt> |
| 332 |
<dd>The PAC and FMPAC contain a bit of battery-powered memory that can be used |
| 333 |
for saving games. Make sure you insert the <code>pac</code> or |
| 334 |
<code>fmpac</code> extension when you start openMSX.<br /> |
| 335 |
The SRAM is divided into 8 blocks and different games typically use different |
| 336 |
blocks. However, there are many games using the SRAM, so it is unavoidable that |
| 337 |
some games use the same block. If you play more than one game and want to be |
| 338 |
on the safe side, copy the <code>.pac</code> file from "persistent/fmpac/untitled1" in your |
| 339 |
openMSX user directory (see <a class="external" |
| 340 |
href="setup.html#romlocation">this overview where it is for your platform</a>) |
| 341 |
to a safe location. |
| 342 |
</dd> |
| 343 |
<dt>Game Master 2</dt> |
| 344 |
<dd>The Game Master 2 can be used to save many Konami games. Insert both the |
| 345 |
game cartridge and the Game Master 2 cartridge. |
| 346 |
</dd> |
| 347 |
<dt>Embedded SRAM</dt> |
| 348 |
<dd>Some cartridges games, for example the strategic games from Koei, have SRAM |
| 349 |
inside the cartridge. You don't have to do anything special to use this.</dd> |
| 350 |
<dt>Tape</dt> |
| 351 |
<dd>Saving to tape is a bit clumsy, but for some games it's the only way. |
| 352 |
<br />Note that the current version of C-BIOS does not have tape support, so if |
| 353 |
you want to save to tape, make sure you use a machine based on the original MSX |
| 354 |
system ROMs. |
| 355 |
</dd> |
| 356 |
<dt>Password</dt> |
| 357 |
<dd>Some games show a password that you can enter to resume the game at the |
| 358 |
same point. You can write down the password of course, or type it into a text |
| 359 |
file, but if you're really lazy, just make a screenshot (press PrtScr)!</dd> |
| 360 |
</dl> |
| 361 |
|
| 362 |
<h4><a id="savegame-mg">In Metal Gear</a></h4> |
| 363 |
|
| 364 |
<p> |
| 365 |
Many people wonder how to save in Metal Gear. Here we will explain how that is |
| 366 |
done on a real MSX, which is also the way to go about it if you don't want to use the |
| 367 |
built in <a class="external" href="user.html#savestate">save state |
| 368 |
mechanism</a> of openMSX. |
| 369 |
</p> |
| 370 |
|
| 371 |
<p> |
| 372 |
Metal Gear has two ways of saving games: |
| 373 |
</p> |
| 374 |
<ol> |
| 375 |
<li> The usual way. This is the save option from the game itself: |
| 376 |
<ol class="alpha"> |
| 377 |
<li> Press <strong>F1</strong> and then <strong>F5</strong> and you can |
| 378 |
save on tape. <br /> |
| 379 |
For this to work, you need to use an MSX machine with a cassette port. |
| 380 |
(So, you cannot use C-BIOS machines, because they do not have a |
| 381 |
cassette port (yet)!)</li> |
| 382 |
<li> Insert a tape using the GUI: click <span class="menu-reference">Main |
| 383 |
menu bar → Media → Tape Deck</span> to open the Tape Deck |
| 384 |
control window. Press the button on the right with the circle |
| 385 |
and browse to the location where you want to create the new tape file |
| 386 |
with the name <code>my_save_game.wav</code>.</li> |
| 387 |
<li> Type the file name in the Metal Gear game (can be any name, but you |
| 388 |
need to remember it! Choose something easy. It's not related to the |
| 389 |
filename of the WAV file you just chose) and press enter.<br /> |
| 390 |
The game will now save to that <code>my_save_game.wav</code> cassette |
| 391 |
image file, under the name you just entered.</li> |
| 392 |
<li> To verify: in Tape Deck window click the rewind button and then press |
| 393 |
"<strong>Y</strong>" in the game to verify.<br /> |
| 394 |
You can also skip this step.</li> |
| 395 |
</ol> |
| 396 |
<p> |
| 397 |
Note that saving in this way is only useful after reaching the elevator. You |
| 398 |
will continue in the last elevator you were in.</p> |
| 399 |
</li> |
| 400 |
<li> The special way. This is done with the Game Master 2 cartridge. You will |
| 401 |
have to start openMSX with both the Metal Gear cartridge and the Game Master 2 |
| 402 |
cartridge. The Game Master 2 cartridge should be in a lower slot than Metal |
| 403 |
Gear (if you use the command line, mention it before Metal Gear). |
| 404 |
<ol class="alpha"> |
| 405 |
<li> After booting, select "<strong>GAME</strong>" to start Metal |
| 406 |
Gear.</li> |
| 407 |
<li> At any time during the game, press the MSX <strong>STOP</strong> key |
| 408 |
(<strong>F8</strong> in openMSX). <br /> |
| 409 |
The CAPS LED will light, which means you are now in the Game Master mode.</li> |
| 410 |
<li> Press <strong>CTRL</strong> to open the save and load menu.<br /> |
| 411 |
For this to work, you need to use an MSX with a diskdrive (again: not C-BIOS, yet!). </li> |
| 412 |
<li> Insert a (blank) disk in the openMSX diskdrive.<br /> |
| 413 |
This can be a disk image you created with some external tool, but you |
| 414 |
can also create one from within openMSX itself: click on the plus-icon |
| 415 |
in the Disk Drive dialog (<span class="menu-reference">Main menu bar |
| 416 |
→ Media → Disk Drive A</span>). Then click Apply to insert |
| 417 |
the disk image in the drive. </li> |
| 418 |
<li> Choose "<strong>DISK SAVE</strong>" in the game from the menu.</li> |
| 419 |
<li> Choose "<strong>GAME DATA</strong>" in the DISK-SAVE menu.</li> |
| 420 |
<li> Input a filename for your save game. This will be the name of the file |
| 421 |
that that will end up on your disk image called <code>filename.dsk</code>.<br /> |
| 422 |
The game will now be saved to disk.</li> |
| 423 |
<li> After saving, choose "<strong>END</strong>" and press the |
| 424 |
<strong>STOP</strong> key again (<strong>F8</strong>).<br /> |
| 425 |
The game will resume. </li> |
| 426 |
</ol> |
| 427 |
</li> |
| 428 |
</ol> |
| 429 |
|
| 430 |
<p> |
| 431 |
For loading back your game: |
| 432 |
</p> |
| 433 |
<ol> |
| 434 |
<li>The usual way: |
| 435 |
<ol class="alpha"> |
| 436 |
<li> Press <strong>F1</strong> and then <strong>F4</strong> in the game and you can load from tape.</li> |
| 437 |
<li> Insert the tape image into the cassetteplayer by clicking <span |
| 438 |
class="menu-reference">Main menu bar → Media → Tape |
| 439 |
Deck</span> to open the Tape Deck and browsing for the previously |
| 440 |
created WAV tape image under "Select new tape" and then press Apply |
| 441 |
to insert it.</li> |
| 442 |
<li> Type the filename you choose for the save game in step 1c above. The |
| 443 |
game will now load the save game and start. If you want to retry, don't |
| 444 |
forget to rewind the cassette by clicking the rewind button in the |
| 445 |
Tape Deck window.</li> |
| 446 |
</ol> |
| 447 |
</li> |
| 448 |
<li>The special way: |
| 449 |
<ol class="alpha"> |
| 450 |
<li> Start Metal Gear as described in steps 2a to 2c above in the saving |
| 451 |
instructions. </li> |
| 452 |
<li> In the save and load menu, choose "<strong>DISK LOAD</strong>". </li> |
| 453 |
<li> Insert the disk image which you inserted in step 2d above, to save |
| 454 |
your game on: in the Disk Drive dialog (<span class="menu-reference">Main menu bar |
| 455 |
→ Media → Disk Drive A</span>), browse for the disk image |
| 456 |
and click Apply to insert the disk image in the drive. </li> |
| 457 |
<li> Choose "<strong>GAME DATA</strong>". </li> |
| 458 |
<li> The game will list the files on the disk that are save game files. |
| 459 |
Select the one you want to load and it will be loaded. </li> |
| 460 |
<li> Choose "<strong>END</strong>" and press the <strong>STOP</strong> key |
| 461 |
(<strong>F8</strong>) to resume the game. </li> |
| 462 |
</ol> |
| 463 |
</li> |
| 464 |
</ol> |
| 465 |
|
| 466 |
<h3><a id="harddisk">What about openMSX harddisk support?</a></h3> |
| 467 |
|
| 468 |
<p> |
| 469 |
This is explained in the <a class="external" href="user.html#harddisks">User's |
| 470 |
Manual</a>. |
| 471 |
</p> |
| 472 |
|
| 473 |
<h3><a id="videosource">It seems the MSX hangs when running GFX9000 software; what's wrong?</a></h3> |
| 474 |
|
| 475 |
<p>You need to switch the video source of the emulated monitor to show the GFX9000 image.</p> |
| 476 |
|
| 477 |
<p>For details, please see the corresponding section in the <a class="external" |
| 478 |
href="user.html#gfx9000">User's Manual</a>. </p> |
| 479 |
|
| 480 |
<h3><a id="leds">Great, those on-screen LEDs! How do I get rid of them?</a></h3> |
| 481 |
|
| 482 |
<p> |
| 483 |
Use the GUI menu: <span class="menu-reference">Main menu bar → Settings |
| 484 |
→ Misc → Configure OSD icons...</span> and uncheck "Show OSD icons". |
| 485 |
You can use this window also to configure them to your liking. |
| 486 |
</p> |
| 487 |
|
| 488 |
<h3><a id="commands">Where is the full list of commands and settings?</a></h3> |
| 489 |
|
| 490 |
<p> |
| 491 |
The full list of commands and settings that are available in the console can be found in the |
| 492 |
<a class="external" href="commands.html">Console Command Reference</a>. Check it out, it's really useful! |
| 493 |
</p> |
| 494 |
<p> |
| 495 |
There is also a full alphabetical list of settings in the GUI under Settings |
| 496 |
→ Advanced. This is a very long list though, and we might remove it later |
| 497 |
as it is not very easy to use. |
| 498 |
</p> |
| 499 |
|
| 500 |
<h3><a id="slow">How can I speed up openMSX? How hard is it to emulate an old MSX on a modern PC?</a></h3> |
| 501 |
|
| 502 |
<p> |
| 503 |
Actually, openMSX is quite fast, depending on what you ask it to do. If you |
| 504 |
have minimal hardware, you should use minimal settings as well, to get decent |
| 505 |
speed. This was proven by Karloch who ran openMSX 0.6.0 on a 206MHz HP Jornada |
| 506 |
720, see <a class="external" |
| 507 |
href="https://www.msx.org/forum/semi-msx-talk/emulation/openmsx-arm-without-x-window">this |
| 508 |
thread on MRC</a>. On PCs, it really helps if your graphics card |
| 509 |
(or actually, the pipe between the CPU and the graphics card) is not slow. Tips on how to |
| 510 |
performance tune openMSX can be found in the <a class="external" |
| 511 |
href="setup.html#tuning">Setup Guide</a>. The developers do their best to keep |
| 512 |
the performance of openMSX as good as possible, while still achieving the |
| 513 |
highest possible level of accuracy. |
| 514 |
</p> |
| 515 |
<p> |
| 516 |
People often wonder why you would need 200MHz+ machines to emulate computers |
| 517 |
based on 3.5MHz CPUs. The thing is, there's not only the CPU you have to emulate, you also |
| 518 |
have to emulate the VDP (21MHz), the monitor (writing at least 50 times per |
| 519 |
second at least 256×192 pixels to a window), the sound chips, etc. This |
| 520 |
is relatively simple hardware, but having that run in software with clock cycle |
| 521 |
accuracy is quite heavy. In general, it is a lot of work for a general purpose |
| 522 |
CPU to emulate functionality that was originally made in dedicated hardware. |
| 523 |
Rebuilding an MSX in general purpose hardware (using VHDL on FPGA) is already a |
| 524 |
lot less demanding. An example of this is the One Chip MSX. |
| 525 |
</p> |
| 526 |
|
| 527 |
<h3><a id="perfect_videos">How do I create perfect play videos, like Vampier's YouTube videos?</a></h3> |
| 528 |
|
| 529 |
<p> |
| 530 |
The trick is to use the <a class="external" |
| 531 |
href="user.html#reverse">reverse</a> feature to correct any mistakes you make |
| 532 |
during game play. You just play, play, play, correcting all mistakes you make |
| 533 |
by going back in time a bit (using PageUp) when you (e.g.) die and doing it |
| 534 |
better. |
| 535 |
</p> |
| 536 |
<p>As soon as you get to the end of the game, we recommend to save the whole |
| 537 |
replay with <span |
| 538 |
class="menu-reference">Main menu bar → Save state → Save |
| 539 |
replay...</span>, so that you |
| 540 |
can always load it and play it again (using <span |
| 541 |
class="menu-reference">Main menu bar → Save state → Load |
| 542 |
replay...</span>). |
| 543 |
</p> |
| 544 |
<p>Next step is to pause openMSX, load back the replay (if you saved it) or |
| 545 |
simply go back to the complete start (click at the start of the reverse bar, or |
| 546 |
use the command <a class="external" href="commands.html#reverse"><code>reverse |
| 547 |
goto 0</code></a>). Now you're ready to record your heroic movie! (Note: if you |
| 548 |
want to record a video from a later point in time, just let it play until it |
| 549 |
reaches the right position, or click on another part of the reverse bar, or |
| 550 |
just search a bit with PageUp/PageDown.) |
| 551 |
</p> |
| 552 |
<p>As a final step, <a class="external" href="user.html#recording">start |
| 553 |
recording</a> and unpause openMSX. If you want the video quickly, run in <a |
| 554 |
class="external" href="commands.html#throttle">full throttle</a> (F9 by |
| 555 |
default) to speed things up. The resulting movie will be the same. If you want |
| 556 |
to split up the recorded video in chunks of under 15 minutes that are accepted |
| 557 |
by YouTube on unverified channels, you'll probably want to have a look at the <a class="external" |
| 558 |
href="commands.html#record">record_chunks</a> command. |
| 559 |
</p> |
| 560 |
|
| 561 |
<p> |
| 562 |
Easy! Now fill up YouTube with MSX material! |
| 563 |
</p> |
| 564 |
|
| 565 |
<h3><a id="tas">How do I use openMSX for TAS (Tool-Assisted Speedruns)?</a></h3> |
| 566 |
|
| 567 |
<p>If just creating <a href="#perfect_videos">perfect play videos</a> isn't |
| 568 |
enough for you, you are probably going for Tool-Assisted Speedruns - more |
| 569 |
information on <a class="external" |
| 570 |
href="http://tasvideos.org">tasvideos.org</a>. The rest of this item gives you |
| 571 |
some hints to help you with this. |
| 572 |
</p> |
| 573 |
|
| 574 |
<p>First of all, the basics are explained in the previous section, of course. |
| 575 |
But you can get extra tools if you enable the <a class="external" |
| 576 |
href="commands.html#mode">TAS mode</a>, we're just not going to repeat the |
| 577 |
explanation here. |
| 578 |
If you need also a live RAM watch, check out the <code><a class="external" |
| 579 |
href="commands.html#other">ram_watch</a></code> command. It enables you to add |
| 580 |
live views of values on multiple addresses with several view options, like |
| 581 |
titles, formats and data types. Please also try the similar functionality under <span |
| 582 |
class="menu-reference">Main menu bar → Debugger → Watch |
| 583 |
expression</span>, which is even more powerful. |
| 584 |
</p> |
| 585 |
|
| 586 |
<p>For MSX TASing, we recommend to not use the (default) C-BIOS based machines, |
| 587 |
but real machines, because C-BIOS is still in development and this means your |
| 588 |
replay (called "movie" in most other TASing emulators) won't be easy to get |
| 589 |
working again once a new version of C-BIOS has been released. Also, MSX turboR |
| 590 |
machines are not recommended, because their emulation has a relatively large amount of |
| 591 |
timing inaccuracies. So which machines do we recommend? Here's a table with |
| 592 |
some very rough directions:</p> |
| 593 |
<table> |
| 594 |
<tr> <th>game type</th> <th>machine</th> </tr> |
| 595 |
<tr> <td>Japanese/Korean (MSX/MSX2/MSX2+)</td> <td>Panasonic FS-A1WSX</td></tr> |
| 596 |
<tr> <td>European (MSX/MSX2)</td> <td>Philips NMS 8250 + FMPAC</td></tr> |
| 597 |
</table> |
| 598 |
|
| 599 |
<p>This is mostly motivated by the fact that Japanese machines run at 60Hz |
| 600 |
interrupt frequency and the Japanese games are made for that. Besides, you will |
| 601 |
get proper Japanese characters with a Japanese machine, which are often used in |
| 602 |
such games. The mentioned machine can run practically all Japanese |
| 603 |
MSX/MSX2/MSX2+ games and has FM on board. For European games, the 50Hz (PAL) |
| 604 |
Philips NMS 8250 is recommended, just because it's very common and runs most |
| 605 |
European MSX and MSX2 software. The FMPAC extension is for better sound. There |
| 606 |
are no native European MSX2+ machines.</p> |
| 607 |
|
| 608 |
<p>When doing MSX TASing, be aware that (unlike consoles), MSX machines have |
| 609 |
a full keyboard attached, and touching the keyboard provides input to the MSX, which in turn |
| 610 |
means you will interrupt the replay if it's playing. You can avoid this (when |
| 611 |
merely viewing a replay) by using the <code>-viewonly</code> option when using |
| 612 |
the <a class="external" href="user.html#reverse">reverse loadreplay</a> |
| 613 |
command. The keyboard problem also means that it's a bit tricky to assign |
| 614 |
keyboard shortcuts (with the <code><a class="external" |
| 615 |
href="commands.html#bind">bind</a></code> command) to (e.g. TAS) functions, |
| 616 |
without also blocking MSX keys. So, be careful which keyboard shortcuts you |
| 617 |
configure and which keys you press.</p> |
| 618 |
|
| 619 |
<p>Now it's time to make a TAS and submit your entry on <a class="external" |
| 620 |
href="http://tasvideos.org">tasvideos.org</a>!</p> |
| 621 |
|
| 622 |
<p>A final note: if you have problems replaying other people's TAS (or other |
| 623 |
openMSX replays), because openMSX can't find the required media (ROMs, disks, |
| 624 |
tapes, etc.), make sure you put the required media in the proper <code><a |
| 625 |
class="external" href="commands.html#filepool">filepool</a></code>; by default |
| 626 |
<code>share/software</code>.</p> |
| 627 |
|
| 628 |
<h3><a id="disablereverse">How can I disable reverse or the reverse bar time line?</a> </h3> |
| 629 |
|
| 630 |
<p> |
| 631 |
Using reverse in combination with large (hard disk or SD card) media can be |
| 632 |
slow at start-up, as openMSX needs to calculate a hash of the media to know |
| 633 |
whether it changed. Moreover, if you reverse and the hard disk image changed, |
| 634 |
openMSX will switch to read-only mode for the media. This is because currently, |
| 635 |
when reversing, openMSX does not revert changes to media, so replaying these |
| 636 |
may cause corruption on the media e.g. due to double writes. |
| 637 |
</p> |
| 638 |
|
| 639 |
<p>In other words, if you are using large media and you don't really need the reverse |
| 640 |
feature, you probably want to disable it: use the <span |
| 641 |
class="menu-reference">Main menu bar → Save state → Reverse/replay |
| 642 |
settings → Enable reverse/replay</span> checkbox. And if you don't want it |
| 643 |
to restart again anymore, uncheck <span class="menu-reference">Main menu bar |
| 644 |
→ Save state → Reverse/replay settings → Auto enable |
| 645 |
reverse</span>. |
| 646 |
</p> |
| 647 |
|
| 648 |
<p>Perhaps you don't want to disable reverse necessarily, but |
| 649 |
you're working with the mouse a lot and the reverse bar shown on the screen is getting in |
| 650 |
the way. In such a case you can get rid of the bar by toggling the setting using <span |
| 651 |
class="menu-reference">Main menu bar → Save state → Reverse/replay |
| 652 |
settings → Show reverse bar</span>. Alternatively, if you still |
| 653 |
want to see it, but not in the area where the MSX display is shown, you can |
| 654 |
move it out of the main window by right-clicking the bar, unchecking "Hide |
| 655 |
title", checking "Allow move" and then drag the whole bar out of the main |
| 656 |
window. |
| 657 |
<p> |
| 658 |
|
| 659 |
<p> |
| 660 |
More details about reverse are in the <a class="external" |
| 661 |
href="user.html#reverse">User's Manual</a>. |
| 662 |
</p> |
| 663 |
|
| 664 |
<h2><a id="other">Other</a></h2> |
| 665 |
|
| 666 |
<h3><a id="codec">What codec do you use to record videos and where do I get it (because I only get eternal darkness in my videos)?</a></h3> |
| 667 |
|
| 668 |
<p> |
| 669 |
The ZMBV (Zip Motion Blocks Video) codec is used, which has been developed in |
| 670 |
the <a class="external" href="http://dosbox.sourceforge.net/">DosBox |
| 671 |
project</a>. It enables openMSX to encode video in real time (on most systems), |
| 672 |
has a very good compression ratio and gives excellent video quality, because it |
| 673 |
is a lossless codec. Razor sharp movies! Also, because the encoder is built in, |
| 674 |
it doesn't make openMSX depend on an external codec to be installed for |
| 675 |
recording video. |
| 676 |
</p> |
| 677 |
|
| 678 |
<p> |
| 679 |
A developer of DosBox built a Win32 binary of the codec for our users. It is |
| 680 |
included with openMSX 0.6.2 (and up) for Win32. Note that the installer does |
| 681 |
not install the codec by default, so you will need to enable this option when |
| 682 |
installing. You can also <a class="external" |
| 683 |
href="http://openmsx.org/util/zmbv_codec_win32.zip">download the codec |
| 684 |
separately from our web site</a>. After unzipping the file, use the .INF file |
| 685 |
to install the codec (<code>zmbv.dll</code>) by right-clicking on it and |
| 686 |
selecting Install. Note that other binaries of this codec that you can find on |
| 687 |
the internet may not work, as not all of them have support for more than 8 bits |
| 688 |
per pixel recordings. |
| 689 |
Also note that this is a 32-bit codec, so it will not run inside 64-bit Windows |
| 690 |
Media Player or Windows Media Center. |
| 691 |
</p> |
| 692 |
|
| 693 |
<p> |
| 694 |
You only need this codec installer to be able to replay the videos on a Windows |
| 695 |
system. (Although a workaround could be to upload it to YouTube, where it |
| 696 |
is re-encoded into a lossy MPEG-4 format.) Programs like Virtual Dub can use |
| 697 |
the codec and re-encode it in another way. On other operating systems, you can |
| 698 |
use any video player which supports this codec; e.g. <code>mplayer</code>. |
| 699 |
Re-encoding can be done with e.g. <code>mencoder</code>. |
| 700 |
</p> |
| 701 |
|
| 702 |
<h3><a id="soundproblems">Why do I hear serious sound glitches and/or stuttering, especially when using Windows?</a></h3> |
| 703 |
|
| 704 |
<p> |
| 705 |
Not sure, but for some reason, especially on Windows, we can't find default |
| 706 |
settings that work for everyone. If you indeed have glitches like sound delay |
| 707 |
or stuttering, you can try the following. </p> |
| 708 |
|
| 709 |
<ul> |
| 710 |
<li>Chances are that your CPU load is very high, which may cause stutters. |
| 711 |
Check the <a class="external" href="setup.html#tuning">Performance Tuning</a> |
| 712 |
section of the Setup Guide to see what you can do to get it lower. Also, peaks |
| 713 |
in CPU usage (e.g. caused by certain P2P programs) can cause stuttering, in |
| 714 |
some cases.</li> |
| 715 |
<li>Try to tune the value of the <a class="external" |
| 716 |
href="commands.html#samples"><code>samples</code></a> setting. If you have |
| 717 |
stutters, double it and see if that helps. If you have delays, halve it and |
| 718 |
see if that helps.</li> |
| 719 |
</ul> |
| 720 |
|
| 721 |
<h3><a id="techinfo">Where can I find more technical info about openMSX?</a></h3> |
| 722 |
|
| 723 |
<p> |
| 724 |
Next to the <a class="external" href="index.html">openMSX manuals</a> (which |
| 725 |
include documentation on how you can control openMSX from an external |
| 726 |
application, so that you can make your own GUI, launcher or debugger), also |
| 727 |
check out the doc directory of your openMSX distribution. |
| 728 |
</p> |
| 729 |
|
| 730 |
<h3><a id="tworeversebars">Why do I see/get two reverse bars in openMSX?</a></h3> |
| 731 |
|
| 732 |
<p> |
| 733 |
This has the same cause and solution as <a class="internal" href="#blackscreen">Why do I only get a black screen?</a>. |
| 734 |
</p> |
| 735 |
|
| 736 |
<h3><a id="twolediconbars">Why do I see/get two LED/icon bars in openMSX?</a></h3> |
| 737 |
|
| 738 |
<p> |
| 739 |
This has the same cause and solution as <a class="internal" href="#blackscreen">Why do I only get a black screen?</a>. |
| 740 |
</p> |
| 741 |
|
| 742 |
<h2><a id="otherquestion">My question is not listed here. Help me.</a></h2> |
| 743 |
|
| 744 |
<p> |
| 745 |
You can look in the following places for answers: |
| 746 |
</p> |
| 747 |
<dl> |
| 748 |
<dt><a class="external" href="index.html">openMSX manuals</a></dt> |
| 749 |
<dd>We have a nice set of manuals describing most of the functionality in openMSX. |
| 750 |
</dd> |
| 751 |
<dt><a class="external" href="http://openmsx.org/catapult-manual/">Catapult manuals</a></dt> |
| 752 |
<dd>The manuals of Catapult, a somewhat obsolete graphical interface to openMSX.</dd> |
| 753 |
<dt><a class="external" href="http://faq.msxnet.org/">The Ultimate MSX FAQ</a></dt> |
| 754 |
<dd>Look here if you have a question that is not specific to openMSX, but about the MSX system itself.</dd> |
| 755 |
<dt><a class="external" href="http://www.msx.org/forum/semi-msx-talk/openmsx">openMSX Forum on MRC</a></dt> |
| 756 |
<dd>You can post your questions here. |
| 757 |
</dd> |
| 758 |
<dt><a class="external" href="ircs://irc.libera.chat:6697/#openMSX">openMSX IRC channel</a></dt> |
| 759 |
<dd>The openMSX developers and testers hang out on this channel (chat room). If the link doesn't work, try the <a class="external" href="https://web.libera.chat/#openMSX">webchat</a> or get an IRC client, go to server <code>libera.chat</code> and join channel <code>#openMSX</code>. It is possible you will not get a reaction immediately, so please ask your question, stay logged in and check from time to time if someone is active. |
| 760 |
</dd> |
| 761 |
</dl> |
| 762 |
|
| 763 |
</body> |
| 764 |
</html> |