Makes me thinking of an option to optionally mark them as unneeded.... however, for now you can rebuild the sets to a new place to clean them... ...or check what the datfile export from the set-information screen exports...maybe it excludes the non-active sets and you have a filtered dat which then can be used to remove the unneeded ones (then they are unneeded). Can't check the source at the moment....
Hmm...no screenshot of the scan results tree output window...(screw stats....) and show me what you got in your rompath....(also you disabled some sets...this does not make them unneeeded)
well, can't you somehow test if it works with a non-network drive? And let me know more details...e.g. what is used as rompath....some screenshots...etc..etc...
[edit] ...what do you need exactly? Only the warning that files were not removed from the subarchive or generally the functionality of removing files from the subarchive...
As I said...if you got a valid setname with random files which have nothing to do with MAME, it won't be put in miss.txt but in have.txt. The check only checks the setname, nothing inside the set is being checked.
Actually it's just a quick set lookup in your rompaths. If the setname is there (can be an empty archive) it's put into the have list, otherwise in the miss list....
So...if you got a pacman.zip with 0 bytes in there, you will find it in have.txt ....
well....7z support could be improved when I find the time to have a look at the 7z 9 sdk....and actually 64bit zip support (allowing >4gb) is possible, too.....but hey....I simply don't have time
Which version of 7z are you using and did you change the 7z settings in cmpro's settings/Compressor/7z?
They are set to not use any solid compressing...so actually if you used this to create the 7z they should work fine when being altered from within the scanner. If your 7zs come from a different source, they are most likely solid... ...but maybe 7z 9.x allows some altering of solid archives...will do some tests
...or is it a general issue with 7z files for you? maybe you can test it with some self-made small 7zs and a modified dat?
update...not a general thing....tested it with non-solid files and renaming inside 7z archives works fine
and another update...I tested a small but fully solid archive and renaming inside works fine, too (with 7z 9.20)....so which version are you using and maybe you can somehow provide me access to the files which cause issues?!
*Solid* 7z archives can't be updated/changed. Why do you expect "Fix missing" to solve wrong named files? Fix name does this... (Official) Zip only supports file sizes up to 4GB.
So...maybe some more details from your side (like what is stored where, what do you expect to get fixed, any error messages?) helps me to give a better reply...
Ah...I guess I see now what you mean...well, actually the >4GB support of 7z files works fine.
The problem is more likely that when you got the "Decompress Rom & check crc32" or similar options enabled which try to decompress files into memory, you run into an out of memory error of 7z since it tries to decompress the full file into memory. You should see an error like "7z: ERROR SZ_ERROR_MEM -> ...." in the warnings window.
So...solution is: if you work with such big files, don't use such options...or switch to decompressed files. For 7z you currently got the limitation that it tries to decompress the full file.
I don't know if I find the time to look at the lates 9.x versions of 7z before xmas...
64 bit version of 7z works fine. Im using it myself. The problem is not in the external packer Guess the 4gb limit is based within the 7z reader which comes from an old 7z sdk....which lacks all kind of stuff not to even mention the code quality of the sdk.