Bug detected, conversions are not working because of some illogical logics in code. Fix coming tomorrow I guess, and a example inno script too. Input directory set to src instead of desktop.

This is going to be a major update.
Changes:
1. Conversion bugs fixed
2. fazip removed
3. Methods and everything can be changed using ini
4. Finished page removed. A message box added instead of finished page.
5. Example Inno Setup Script.

Final update uploaded. MMC 2.0 is no more beta. Example script+MMC uploaded to first post.

Here is a small tutorial for using MMC.
1. Download and Run MMC
2. Select your desired compression method
3. If you want to split, set firat volume size and custom volume size(Note: Here the size is determined as megabytes. If you don't want to split, leave it blank)
4. Set archive name(Must be set)
5. Set source dir(The contents of the folder to compress)
6. Set destination dir(The folder to keep the compressed file/create conversions)
7. If you want to create conversion, select setup executable and icon file and disklabel, else not.
Let me make you understand how this works.
For example, you have 4 archives after splitting and you decided to create conversions. You selected setup executable named setup.exe, icon named icon.ico and disklabel to DISK. Then there will be four folders created.
Folder 1: DISK1, this folder will contain autorun.inf, setup.exe, icon.ico and first split volume
Folder 2/3/4: DISK2/3/4, these folders will contain the remaining split. volumes, icon.ico and autorun.inf
8. If you check the checkbox "Create iso", iso files will be created for every folder names.
9. If you save the settings to ini, the conversion/compression settings will be saved to mmc.ini and will be automatically loaded when you start MMC.
10. If you don't select any method, the default method is storing.

After you finished compressing, you can use any normal script to decompress if you didn't use split, just include the compressors there.
If you used splitting, use the one from MMC_example folder.
Edit the script and find data.bin.001, and replace it with your archive name.
Then set other settings and compile, rest is handled by itself.

Thanks to cls-diskspan from Razor12911 for everything.

Hi man

First of all, thank you for creating a useful, functional and free tool for everyone.

I have some doubts about your tool:

What are the advantages compared to UltraARC?

Is it compatible with any version of CIU?. If so, i have to manually create records.ini or something like that?


Thank you for your response.

It is compatible with any CIU version, but either way you have to create a records.ini (UltraARC script) or put the archives the old way in setup.ini (without UltraARC).

PS: And don't forget to edit arc.ini from CIU archive. I don't know what methods/settings MMC uses. It could be incompatible with the arc.ini from CIU.

Hmm...

Can you share any favorable advantage as compared with UltraARC, if it exists?

You can also try Arc Gui http://fileforums.com/showthread.php?t=98152

But other than that, there are no "favorable advantage as compared with UltraARC" out there i guess.

That's why I asked because I don't see one.

Anyway... Many thanks for you response.

It has some disadvantages though. But I plan to release a CIU version. The disadvantages are not much, and we can do the main job of ultraarc(splitting) better than ultraarc.

Records.ini is not needed actually, the CIU I am going to post is compatible with splitting capability of MMC, you just need to set the archive name before compiling and it will work. Will give a small update to MMC so the name of archive will be invisible to set if you set it in MMC.ini

Firstly, it is not compatible with any CIU version because it uses cls-diskspan, which is not included with any CIU version. Plus It has more compressors than ultraarc or ciu, so again, it doesn't work with CIU.

Thank you for clearing up my doubts.

I have tested it without disk spanning, means only 1 file (~1,3GB) with pz+sr+lz and extraction was ok with 2050 and even 2039 should'nt have any problems with it as long as disk spanning is not set.

Yep, but the main cause of creating MMC 2.0 is splitting, which works better in this program.

Ok, waiting for this.

Just needs MASK support, then i'm happy :D

You can try with the simple script included with MMC to see how splitting works here and detect bugs. About masks, well then I will create a separate exe for masked data compression 2.5(or else?)