Post by Krusty on Sept 20, 2011 22:08:55 GMT -5
This advisory is now obsolete.
The conditions that prompted this advisory was resolved by Digitalghost not long after this post was created. An updated mess ROMs.xml.gz was committed by Digitalghost which removes the unicode characters in the fm16beta ROM description.
Symptoms:
You added the complete MESS 0.143 BIOS ROM set or the fm16beta system BIOS to MAMEHub's audit paths and then can't launch MAMEHub afterwards. This error message appears when trying to launch MAMEHub:
Criteria:
This advisory applies only if you have added either of the following items to MAMEHub's audit paths and then are unable to launch MAMEHub afterwards:
1. The complete MESS 0.143 BIOS ROM set (206 MB)
2. The fm16beta BIOS ROM (fm16beta.zip)
Prevention:
Do not attempt to audit the complete MESS 0.143 BIOS ROM set or the fm16beta system BIOS. Instead, copy MESS BIOS ROMs into your MAMEHub ROM folders only as needed.
Cause:
A unicode character within the messROMS.xml file is accidentally processed when MAMEHub recognizes the fm16beta BIOS file during an audit. This causes corruption to the MAMEHub ROM cache which prevents MAMEHub from starting up (and other errors).
See this post for a more detailed explanation with illustrations of the cause.
Impact:
MAMEHub will not launch if its ROM cache has been corrupted by attempting to audit the fm16beta system.
Resolution:
1. Delete the *.dmp files from your mamehub\dist folder. They should look like this in Windows:
Tip: Sort the folder by date to bring the cache files to the top.
2. Manually edit both the mame.ini and mess.ini files within the mamehub\dist folder and remove the path to the full MESS BIOS ROM set in the 'rompath' value.
3. Launch MAMEHub.bat which will force an audit. You should now be able to logon to MAMEHub again.
Deleting the *.dmp files in Step 1 will always be necessary to resolve this issue when it occurs. However, if you'd rather not edit the mame.ini/mess.ini in Step 2 then below are two separate alternative options to editing those files:
1. Move the fm16beta.zip file out of your MESS BIOS ROM set.
2. Unzip messROMs.xml.gz (located in mamehub\hash). Edit the messROMs.xml file (on line 26718) to remove the unicode character in the fm16beta description. Update the messROMs.xml.gz archive with the edited messROMs.xml file. (note: WinRAR may not work but 7-Zip will.)
The conditions that prompted this advisory was resolved by Digitalghost not long after this post was created. An updated mess ROMs.xml.gz was committed by Digitalghost which removes the unicode characters in the fm16beta ROM description.
Symptoms:
You added the complete MESS 0.143 BIOS ROM set or the fm16beta system BIOS to MAMEHub's audit paths and then can't launch MAMEHub afterwards. This error message appears when trying to launch MAMEHub:
Criteria:
This advisory applies only if you have added either of the following items to MAMEHub's audit paths and then are unable to launch MAMEHub afterwards:
1. The complete MESS 0.143 BIOS ROM set (206 MB)
2. The fm16beta BIOS ROM (fm16beta.zip)
Prevention:
Do not attempt to audit the complete MESS 0.143 BIOS ROM set or the fm16beta system BIOS. Instead, copy MESS BIOS ROMs into your MAMEHub ROM folders only as needed.
Cause:
A unicode character within the messROMS.xml file is accidentally processed when MAMEHub recognizes the fm16beta BIOS file during an audit. This causes corruption to the MAMEHub ROM cache which prevents MAMEHub from starting up (and other errors).
See this post for a more detailed explanation with illustrations of the cause.
Impact:
MAMEHub will not launch if its ROM cache has been corrupted by attempting to audit the fm16beta system.
Resolution:
1. Delete the *.dmp files from your mamehub\dist folder. They should look like this in Windows:
Tip: Sort the folder by date to bring the cache files to the top.
2. Manually edit both the mame.ini and mess.ini files within the mamehub\dist folder and remove the path to the full MESS BIOS ROM set in the 'rompath' value.
3. Launch MAMEHub.bat which will force an audit. You should now be able to logon to MAMEHub again.
Deleting the *.dmp files in Step 1 will always be necessary to resolve this issue when it occurs. However, if you'd rather not edit the mame.ini/mess.ini in Step 2 then below are two separate alternative options to editing those files:
1. Move the fm16beta.zip file out of your MESS BIOS ROM set.
2. Unzip messROMs.xml.gz (located in mamehub\hash). Edit the messROMs.xml file (on line 26718) to remove the unicode character in the fm16beta description. Update the messROMs.xml.gz archive with the edited messROMs.xml file. (note: WinRAR may not work but 7-Zip will.)
