• Advertisement

Possible bug in 3.61

Post a reply


Enter the code exactly as it appears. All letters are case insensitive.

For protection against spam, Answer the above question.
Smilies
:D :) :( :o :shock: :? 8) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :!: :?: :idea: :arrow: :| :mrgreen: :clap: :hum: :gnak: :lol: :super: :uh: :toobad:
View more smilies
BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON
Topic review
   

Expand view Topic review: Possible bug in 3.61

Re: Possible bug in 3.61

Post by RomCenter on Sat Jun 09, 2012 9:30 am

Yes, chd are not intended to be used compressed (in zip or 7z).
Anyway, I will give a try and see if I can fix it.

About the 7z problem, I don't actually have anough 7z. So let me add the 'convert to 7z' function and I will test.

Re: Possible bug in 3.61

Post by MELERIX on Fri Jun 08, 2012 11:16 pm

2gb+ roms ? Oo

I hope you are not using compressed Mame CHDs xD

Possible bug in 3.61

Post by fbrd on Fri Jun 08, 2012 12:07 am

Hi

zipped 2Gb roms are not being recognised, the CRC is correct but the size is showing up as -2147483648

bigger roms are not working either, e.g. a 3Gb rom is showing up as 0 length

unzipped the roms are recognised correctly.

Also found when processing a few hundred 7zipped files that RC gets upset and says "error 8007000e: Not enough storage is available to complete this operation". Using 10 threads on Win7 64, 4Gb RAM. Seems it runs OK for a while then suddenly starts guzzling RAM. All the archives unpack just fine when I use the commandline. When this happens RC concludes that the files are bad and deletes them (if fix preferences are set that way). RC does not appear to release the memory when it has finished either.

-F

Top