<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content="HTML Tidy for Cygwin (vers 1st September 2004), see www.w3.org" />
<title>MESS Guide</title>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
<link href="../style.css" rel="stylesheet" type="text/css" />
</head>
<body>
<h1>Managing ROM Files</h1>
<p class="normal">This page will help you manage your collection of ROM files.<br /></p>
<hr align="center" width="98%" />
<h2>Updating ROM files<br />
<br /></h2>
<p class="normal">As new versions of MESS come out, the authors sometimes change the system ROM files in order to make them work properly. As a
by-product of this you can sometimes have to update several files.</p>
<p class="normal">The simplest way is to use a ROM manager such as <a href="http://www.clrmame.com/" target="_blank">clrmamepro</a> with a MESS ROM DATFile as it will identify problems and fix many of them too.</p>
<p class="normal">Updated ROM files can be obtained by dumping them from the original machine or downloading them from the Internet. See the help section "Installing ROM Files and Software Images" for more details.</p>
<hr align="center" width="98%" />
<h2><br />Verifying ROM Files</h2>
<p class="normal">You can let the command line version of MESS audit its own ROM files using this command...</p>
<p align="center"><span class="command">MESS -verifyroms >missing.txt</span></p>
<p class="normal">This will generate a text file that contains information about all the ROM files you have problems with and what the problem is.</p>
<p class="normal">For MESSGUI it's even easier. On the File menu there is an option called "Audit all systems". If you hit it this window opens...</p>
<p align="center" class="Tutorial"><img src="images/guiaudit.gif" width="437" height="339" border="0" alt="Screenshot of MESSGUI audit window" /></p>
<p class="normal">The list shown is the same as the one generated by the command line version and again shows all of the errors in your ROM files.
The only errors that can be resolved in the list are "NOT FOUND" and "CRC ERROR" as the other errors normally mean there is a problem with the only ROM files available to the MESS team.</p>
<p class="normal">If a system has stopped working after an update and you can't find anything wrong with the zip file then either there could be a
bug in MESS or there has been new development on the game driver. The mess.txt file contains a list of working and non-working systems and is a good
start. If this is no good then you can check out the <a href="http://bugzilla.mess.org/" target="_blank">MESS Bugzilla</a> page and see if any news
has been posted about it.</p>
<p class="normal">Always make sure you scan your ROM files with a ROM management utility after an update to make sure your set is correct.</p>
</body>
</html>
distrib
>
Mandriva
>
cooker
>
x86_64
>
media
>
plf-non-free-release-binary
>
by-pkgid
>
ce786273fe57b4dc401e482e21a4de20
>
files
>
48
