NES dat/roms/header problem.
NES dat/roms/header problem.
Hi!
About two "Nintendo - Nintendo Entertainment System" updates ago clrmamepro started to show that all the roms I have has wrong ROM Size. Clrmamepro can fix the size (or try to fix) but after that every resized rom is marked as missing. So... I'd like to ask what is going on...
Thank you.
About two "Nintendo - Nintendo Entertainment System" updates ago clrmamepro started to show that all the roms I have has wrong ROM Size. Clrmamepro can fix the size (or try to fix) but after that every resized rom is marked as missing. So... I'd like to ask what is going on...
Thank you.
- kazumi213
- High Council
- Posts: 458
- Joined: 27 May 2008 12:20
Re: NES dat/roms/header problem.
Yes you are right, but the problem is not in our DAT or header. It's in CMPro, I'd say since v3.128:
3.128
* added: batcher-rebuilder always scan/never scan subfolder options
* misc: enhanced "Can't merge set due to equal names" check to work with chds, too
* misc: increased memoryfile size which is used for header support. This should increase speed when header detection is done on zipped files
* misc: added shareRead and shareWrite options to cmpro.ini. Setting them to "on" will allow generalfile read/write sharing. Use it on your own risk
* removed: fix missing scans all set. An old resource hog...rarely used
For some reason, now all NES ROMs are detected by CMPro as 8 MB, reporting as correct the smaller size in DAT.
3.128
* added: batcher-rebuilder always scan/never scan subfolder options
* misc: enhanced "Can't merge set due to equal names" check to work with chds, too
* misc: increased memoryfile size which is used for header support. This should increase speed when header detection is done on zipped files
* misc: added shareRead and shareWrite options to cmpro.ini. Setting them to "on" will allow generalfile read/write sharing. Use it on your own risk
* removed: fix missing scans all set. An old resource hog...rarely used
For some reason, now all NES ROMs are detected by CMPro as 8 MB, reporting as correct the smaller size in DAT.
-
- Datter
- Posts: 123
- Joined: 10 Sep 2008 16:16
- kazumi213
- High Council
- Posts: 458
- Joined: 27 May 2008 12:20
Re: NES dat/roms/header problem.
Thanks gigadeath. Once again, I should check external forums before testing myself. It would save me time...
- JacKc
- Posts: 20
- Joined: 25 May 2008 14:13
Re: NES dat/roms/header problem.
Great...Waiting for the fix
- alcoatjez
- Dumper
- Posts: 170
- Joined: 26 May 2008 19:29
Re: NES dat/roms/header problem.
Just replace your exectable with the one from the thread mentioned above and you're good to goJacKc wrote:Great...Waiting for the fix
- kazumi213
- High Council
- Posts: 458
- Joined: 27 May 2008 12:20
Re: NES dat/roms/header problem.
The fix is not working for me , so I've temporarily reverted to v3.127.alcoatjez wrote: Just replace your exectable with the one from the thread mentioned above and you're good to go
-
- Posts: 5
- Joined: 30 May 2008 22:30
Re: NES dat/roms/header problem.
Not working with 3.130a either.
I tried to let cmpro detect and rebuild all files, which it did, but upon doing a new scan, all files are flagged erroneous with some header error (I triple-checked the header xml and the path to it and whatnot).
Of course I've already deleted the zip of 3.127, so if anybody could mirror it, I'd be very grateful.
I tried to let cmpro detect and rebuild all files, which it did, but upon doing a new scan, all files are flagged erroneous with some header error (I triple-checked the header xml and the path to it and whatnot).
Code: Select all
"Archive Header CRC32 doesn't match CRC32 of decompressed data for file: .....\10-Yard Fight (Japan).nes"
Full archive integrity check reported errors or a header crc32 mismatch was found.
Re: NES dat/roms/header problem.
Since it's still not working on 3.130a, does someone have a copy of the patched 64bit file (link is dead in emulab forum) or a backup to 3.127? I've scoured the internet, and the only 64bit version I can find is 3.125
Thanks in advance
Edit: damn, I suck too.
For those that care, there is a mirror of all the versions on emuhq, for 32bit and 64bit versions of 3.127 (last known working version?) go here:
http://www.emuhq.com/utilities/rom-tool ... 06/10/9983
If someone has the patched 3.129 versions out there, please share!!
Thanks in advance
Edit: damn, I suck too.
For those that care, there is a mirror of all the versions on emuhq, for 32bit and 64bit versions of 3.127 (last known working version?) go here:
http://www.emuhq.com/utilities/rom-tool ... 06/10/9983
If someone has the patched 3.129 versions out there, please share!!
- Connie
- Datter
- Posts: 218
- Joined: 20 Jun 2008 12:15
Re: NES dat/roms/header problem.
I've never encountered any issues scanning my NES set with Romcenter and clrmamepro other than the non iNES format issues, so I decided to have a look into the issue.
I've always used the supplied no-intro header:
...and never had problems.
This time I loaded up Roman's:
...and I got 4 ROMs reporting that they were 16bytes too large - hence the header hadn't been skipped. These were:
Bigfoot (USA)
Devil World (Japan) (Rev A)
Magic Jewelry (Asia) (Unl)
Pegasus 5 in 1 (Unknown) (Unl)
So I looked at the ROMs and noticed that in each of the cases they didn't have the last 8 bytes of data filled with 0000000000000000 - "Devil World (Japan) (Rev A) good" has 4469736B4475646521 (DiskDude!) at the end!
Considering these are the only ROM issues I've come across, I think that it must have to do with your ROM set having incorrect headers i.e. they don't start with 4E4553.
I would also suggest changing to use Roman's NES iNES header pluggin because it helps to produce a 'cleaner' header by elimininating hacked crap like "DiskDude!".
I've always used the supplied no-intro header:
Code: Select all
<?xml version="1.0"?>
<detector>
<name>No-Intro NES Dat iNES Header Skipper</name>
<author>Yakushi~Kabuto</author>
<version>20070321</version>
<rule start_offset="10">
<data offset="0" value="4E4553"/>
</rule>
</detector>
This time I loaded up Roman's:
Code: Select all
<?xml version="1.0"?>
<detector>
<name>Nintendo Famicon/NES</name>
<author>Roman Scherzer</author>
<version>1.0</version>
<rule start_offset="10" end_offset="EOF" operation="none">
<data offset="0" value="4E45531A" result="true"/>
<data offset="8" value="0000000000000000" result="true"/>
</rule>
</detector>
Bigfoot (USA)
Devil World (Japan) (Rev A)
Magic Jewelry (Asia) (Unl)
Pegasus 5 in 1 (Unknown) (Unl)
So I looked at the ROMs and noticed that in each of the cases they didn't have the last 8 bytes of data filled with 0000000000000000 - "Devil World (Japan) (Rev A) good" has 4469736B4475646521 (DiskDude!) at the end!
Considering these are the only ROM issues I've come across, I think that it must have to do with your ROM set having incorrect headers i.e. they don't start with 4E4553.
I would also suggest changing to use Roman's NES iNES header pluggin because it helps to produce a 'cleaner' header by elimininating hacked crap like "DiskDude!".
-
- Posts: 5
- Joined: 30 May 2008 22:30
Re: NES dat/roms/header problem.
3.130 worked with neither the header-xml of no-intro nor the built-in one, and the fact, that the scan works with 3.127 is sign enough for me that the files have proper headers (at least as much as the no-intro-xml is concerned, haven't tried Roman's nes-xml with 3.127).
- Connie
- Datter
- Posts: 218
- Joined: 20 Jun 2008 12:15
Re: NES dat/roms/header problem.
clrmamepro is now v3.131 and using Roman's NES header plugin along with the manually downloaded Dat-o-Matic NES dat, I have no errors.
I'm not an update geek (anymore), so maybe I missed a revision that caused some of you problems. But I do recommend that No-Intro adds Roman's NES header because it will avoid people 'hacking' the iNES header with their own info's and then distributing - which No-Intro's current headerless dat wouldn't pickup on.
I'm not an update geek (anymore), so maybe I missed a revision that caused some of you problems. But I do recommend that No-Intro adds Roman's NES header because it will avoid people 'hacking' the iNES header with their own info's and then distributing - which No-Intro's current headerless dat wouldn't pickup on.
- kazumi213
- High Council
- Posts: 458
- Joined: 27 May 2008 12:20
Re: NES dat/roms/header problem.
According to Connie, latest CMPro (3.131) works again.
Re: NES dat/roms/header problem.
The problem happen only if you use roms with header (too happen with FDS/lynx) with CM 3.126 don`t happened this problem (warning message), files with header are rebuilt correctly by CM .
If you disable checksum in scan windows it is not shown more warning message.
If you disable checksum in scan windows it is not shown more warning message.