EMULAB Forum

clrmamepro [English] => clrmame Discussion => Topic started by: FlightRisk on 16 March 2018, 15:28

Title: "unpack failed on file..." Error Msg rebuilding NeoGeo FBAlpha romset
Post by: FlightRisk on 16 March 2018, 15:28
I have what I believe was a .39 version of NeoGeo roms and was trying to rebuild them up to .42 as well as get rid of the chaff (demos, unplayable, mahjong, etc.) with an XML DAT file I found on retropie:

"FB Alpha v0.2.97.42 NEOGEO NOCLONES NOMAHJONG NOOMEBREW.xml"

I am using CMP v 4.033

kof2001.zip\262-c4-08-e0.cf
kof2002.zip\265-v2.v2
kof99.zip\252-c7.c7
rotd.zip\264-c6.c6

I searched, but can't find info on what is happening. In the kof2001, there is not .cf file, there is a .c4 file. In the kof2001 file, there IS a 265-v2.v2 file the exact same size as a 265-v2.bin file. Are these just corrupt roms? How do I fix it?
Title: Re: "unpack failed on file..." Errro Msg rebuilding NeoGeo FBAlpha romset
Post by: Roman on 16 March 2018, 15:40
"unpack failed on file" ...well, when cmpro tried to unpack the file (maybe to temp, maybe to a destination), something went wrong....could be a bad zip file (or .rar/.7z), could be something like not enough free disk space, could be anything....

So...most likely a bad archive file....hard to say. So if you say it was during rebuild, check the source file and check if the destination and cmpro's temp folder holds enough free space
Title: Re: "unpack failed on file..." Error Msg rebuilding NeoGeo FBAlpha romset
Post by: FlightRisk on 16 March 2018, 16:24
Thanks for he reply. No, this is a huge drive and there is plenty of free space. I wonder if the unpack is just unzipping or if it looks on a file by file basis for what should be in the archive? Because it gives the error on a file that does not exists in the first rom zip. The second one has a file by that name, but unzips just fine manually. I guess i can try to find the individual roms, replace them, and see what happens.
Title: Re: "unpack failed on file..." Error Msg rebuilding NeoGeo FBAlpha romset
Post by: Roman on 16 March 2018, 20:09
It's just about the unpack operation. Could be related to the archive....could be a not supported compression method (there are plenty out there...)...could be anything....so please try to figure out which file is affected (e.g. by turning on rebuilder logging if this happens during a rebuild).