Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[against03]

hello,

i use the latest version 4.012a and i have some problems witch the option "ignore filesize" in the rebuilder. allways no matching hash found, if the dat says "<romSize> 0 </ ROMSize>".  seems thats the option doesnt like "0", any other value works fine. please check this.

greets

[Roman]

can you send me the dat and a file which does not seem to work?

[against03]

can you send me the dat and a file which does not seem to work?

i have added an attachment in the first post.

greets

[Roman]

thanks...I try to look at it tonight...

[Roman]

ah...the problem is not the "ignore file size option" it's more related how the datfile is initially parsed.
A set romsize = 0 sets the rom to "no dump" status (which also cleans up the actual crc32) and so the file won't be checked by the rebuilder at all...

It will work if you remove the <romSize>0</romSize> from the datfile...which is more a "romsize unknown" (while = 0 -> nodump)

[against03]

ah...the problem is not the "ignore file size option" it's more related how the datfile is initially parsed.
A set romsize = 0 sets the rom to "no dump" status (which also cleans up the actual crc32) and so the file won't be checked by the rebuilder at all...

It will work if you remove the <romSize>0</romSize> from the datfile...which is more a "romsize unknown" (while = 0 -> nodump)

ok, thanks for clearing this. hope they fix the dat file soon!

greets

[Roman]

well...it's not really their fault....it's more a general question of how to interpret the given data....
in cmpro I've decided to handle given rom size = "-" or not given rom size as a valid file (with crc) with an unknown size, while a given rom size of 0 will be transformed into a known nodump file.....(without a crc...)