MTX - The Universal Accelerator

[BLACKFIRE69]

1. Created MTX2023 from scratch and optimized for speed and efficiency.
  - As a result, it isn't compatible with any previous versions.

2. The bugs experienced in previous versions have been addressed and fixed.

3. MTX can handle scenarios where the #userThreads > #compressionThreads.

4. Simultaneous reading and writing of data takes place.
  - Previous versions required extra waiting time that's no longer necessary in this version.
  - Make sure to specify the '-ds' parameter with the 'arc.exe a'. (arc.exe a -ds ...)

Remark:

1. '--TempPath=' parameter has been removed.
  - Tmp files will now be created in the freearc temp dir instead.

2. '%' sign has been removed from threads (100%).
3. Support for "MTX32.ini" and "MTX64.ini" files has been discontinued.
4. There won't be a 32-bit version of MTX.

1. Recommended setting (stdio mode) but no info will be displayed.

packcmd   = MTX64.exe a -mNz64 -c32m {options} - - <stdin> <stdout>
unpackcmd = MTX64.exe x -mNz64 {options} - - <stdin> <stdout>


2. Info will only be displayed for packing.

packcmd   = MTX64.exe a -mNz64 -c32m {options} - $$arcpackedfile$$.tmp <stdin>
unpackcmd = MTX64.exe x -mNz64 {options} - - <stdin> <stdout>


3. Info will only be displayed for unpacking.

packcmd   = MTX64.exe a -mNz64 -c32m {options} - - <stdin> <stdout>
unpackcmd = MTX64.exe x -mNz64 {options} - $$arcdatafile$$.tmp <stdin>


4. Info will be displayed for both packing and unpacking. 

packcmd   = MTX64.exe a -mNz64 -c32m {options} - $$arcpackedfile$$.tmp <stdin>
unpackcmd = MTX64.exe x -mNz64 {options} - $$arcdatafile$$.tmp <stdin>

.

[BLACKFIRE69]

If anyone wants an example of "Inno setup" for MTX.exe, just let me know.

[Balaji007]

MTX console version works perfectly. Also I was tested MCM works perfectly.

[BLACKFIRE69]

MTX.exe supports MASKS (Arc.Groups)

example:

[Compression Methods]
MASK = srep+razorx/$zlib=precompx+srep+bcmx/$other=srep+razorx/$lyrfile=precompx+srep+bcmx/$bmp=srep+razorx

[Balaji007]

Originally Posted by BLACKFIRE69

MTX.exe supports MASKS (Arc.Groups)

Can you explain about masks?

[Masquerade]

Originally Posted by Balaji007

Can you explain about masks?

Masks allow you to use more than one method for different files in an archive

Different methods are specified with groups, which you can write yourself into the file "arc.groups" next to your arc.exe for compression.

Write your group as example:

$nameofgroup
*.filename
*.otherfile

Then we can use this in our compression method:

srep+lolz/$nameofgroup=rzx

So here, all of the files defined in the $nameofgroup list will be compressed using rzx, where all other files will be compressed with srep+lolz.

[BLACKFIRE69]

MTX.exe Feature update v.3.0.0.0

What's New:

• Some improvements.
  
  
• A new key (MainPath) has been added to MTX.ini.
  -- this allows you to set the root directory manually.
  -- MTX.exe can be executed within a sub-folder.
  
  
• There is no need to rename "mtx.ini" (as before).
  -- before: MTX64.exe ---> MTX64.ini --> [MTX64]
  -- now : MTX64.exe ---> MTX.ini --> [MTX]
  
  
• Added an example for XLolz.
• Added an example for MASKS.

Additional Options For both Compression and the Decompression:

-----------------------------------------------------------------------------
[MTX]
MainPath=..\..\
Config=arc.ini
//TmpPath=C:\Users\Rexton\Desktop\temptest\
-----------------------------------------------------------------------------



// config := default is arc.ini (current directory).

// config = arc.ini			<--- MainPath\arc.ini
// config = cfg\config0.ini		<--- MainPath\cfg\config0.ini  



// TmpPath= full path.  ( with or without quotes (") )

_

[Nezha]

Oh, thank you!
Can I have an example or small guide to adapt Inno/ASIS to this please? I'm probably doing something wrong with my frankenstein script lol

Edit/question: Is Xlolz working multithreading via MTX? It doesn't seem for me.
Edit2: It works with fixed thread count and not % like default (?)

[BLACKFIRE69]

Originally Posted by Nezha

Oh, thank you!
Can I have an example or small guide to adapt Inno/ASIS to this please? I'm probably doing something wrong with my frankenstein script lol

Edit/question: Is Xlolz working multithreading via MTX? It doesn't seem for me.
Edit2: It works with fixed thread count and not % like default (?)

You can't use "XLolz" via "MTX" (because both are accelerators). but it supports "MTX + Lolz".

ok, I'll give you some examples for both INNO Setup and Lolz with MTX.

[Nezha]

Originally Posted by BLACKFIRE69

You can't use "XLolz" via "MTX" (because both are accelerators). but it supports "MTX + Lolz".

ok, I'll give you some examples for both INNO Setup and Lolz with MTX.

Oh, yea, my bad: I mean the one inside the default "arc.ini" with MTX, for reference this one:

[External compressor:XLolz, LolzMTX, xlolz]
header = 0
packcmd = bin\MTX\MTX.exe a:lolz -c:64m -t:100p - - <stdin> <stdout>
unpackcmd = bin\MTX\MTX.exe x:lolz -t:100p - - <stdin> <stdout>

___

So.. Something works but not well

Using unpack.bat

Extracted 6,874 files, 10,021,997,180 => 16,726,226,492 bytes. Ratio 59.92%
Extraction time: cpu 30.00 sec/real 469.39 sec = 6%. Speed 35.63 mB/s
All OK

Using my modified InnoSetup scripts with MTX gives "UnArc.dll -11 error: archive damaged" at ~80% but it actually extracts something

[BLACKFIRE69]

Originally Posted by Nezha

Oh, yea, my bad: I mean the one inside the default "arc.ini" with MTX, for reference this one:


___

So.. Something works but not well

Using unpack.bat


Using my modified InnoSetup scripts with MTX gives "UnArc.dll -11 error: archive damaged" at ~80% but it actually extracts something

ok, just wait for the example.

[BLACKFIRE69]

MTX v.5.0.0.0 - October Update

• MTX.ini

Example:=

exefile:  MTX64.exe
ini:      supports both MTX.ini or MTX64.ini    (next to the exe file)
section:  [MTX] or [MTX64]

exefile:  MTX32.exe
ini:      supports both MTX.ini or MTX32.ini    (next to the exe file)
section:  [MTX] or [MTX32]

• Percentage

Example:=

packcmd   = "MTX.exe" a:bcm -c:64m -t:100p - - <stdin> <stdout>

   or

packcmd   = "MTX.exe" a:bcm -c:64m -t:100% - - <stdin> <stdout>

• Supports Custom Input/Output

Example:=

[External compressor:bcm, bcm32]
header    = 0 
default   = -9

packcmd   = "Bcm\{compressor}" {options} MyInput.in MyOutput.out
unpackcmd = "Bcm\{compressor}" -d MyOutput.out MyInput.in
datafile   = MyInput.in
packedfile = MyOutput.out

• New Options

1. --help   (Show long help)
2. --logs   (Generate a log file)
3. --mainpath=< main path >
4. --config=< config file >
5. --tmppath=< temp path >


Example:=  (When not using MTX.ini.)


[External compressor:BscX, BscMTX, bscx]
header = 0
default   = --logs --mainpath=".\..\" --config="%MainPath%\confis\arc.ini" --tmppath="%ExePath%\TEMP"
packcmd   = MTX\MTX.exe a:bsc32 -c:64m -t:100% {options} - - <stdin> <stdout>
unpackcmd = MTX\MTX.exe x:bsc32 -t:100p  {options} - - <stdin> <stdout>

• MTX.ini Configuration

 MTX Variables:
    1. %MainPath%
         -- default is the directory that containing MTX.exe.
            ex: C:\Testing\mtxTest\Res\MTX\MTX.exe  then %MainPath% = C:\Testing\mtxTest\Res\MTX\

         -- Users can change manually.

    2. %ExePath%
         -- the directory that containing MTX.exe.
            ex: C:\Testing\mtxTest\Res\MTX\MTX.exe  then %ExePath% = C:\Testing\mtxTest\Res\MTX\


 Other
    1. MainPath
        -- default is 	%ExePath%

        -- Users can change manually.

        -- MainPath = (full path)
            ex:	MainPath=C:\Testing\mtxTest\Res\

        -- MainPath = (short path)
            ex:	MainPath=.\..\
              > MainPath is centered on ExePath. (for short paths)
              > If ExePath = C:\Testing\mtxTest\Res\MTX\  then  MainPath = C:\Testing\mtxTest\Res\  (MainPath=.\..\)

        -- MainPath = (alternatively)
            ex: 	MainPath=%ExePath%


    2. Config
        -- default is	%ExePath%\Arc.ini

        -- Users can change manually.

        -- Config = (full path)
            ex:	Config=C:\Testing\mtxTest\Res\Arc.ini

        -- Config = (short path)
            ex:	Config=.\..\Arc.ini
               > Config is centered on MainPath. (for short paths)
               > If MainPath = C:\Testing\mtxTest\Res\MTX\  then  Config = C:\Testing\mtxTest\Res\Arc.ini  (Config=.\..\Arc.ini)

        -- Config = (alternatively)
            ex:	Config=%MainPath%\Arc.ini
            ex:	Config=%ExePath%\Arc.ini


    3. TmpPath
        -- default is	%ExePath%

        -- Users can change manually.

        -- TmpPath = (full path)
            ex:	TmpPath=C:\Testing\mtxTest\Res\TEMP\

        -- TmpPath = (short path)
            ex:	TmpPath=.\..\TEMP\
               > TmpPath is centered on MainPath. (for short paths)
               > If MainPath = C:\Testing\mtxTest\Res\MTX\  then  Config = C:\Testing\mtxTest\Res\TEMP\  (TmpPath=.\..\TEMP\)

        -- TmpPath = (alternatively)
            ex:	TmpPath=%MainPath%\TEMP\
            ex:	TmpPath=%ExePath%\TEMP\

Will show some errors in nanozip decompression with MTX.exe. therefore it is better to use cls-nzx.dll instead of MTX.exe.


guys, I don't have enough space to upload it here. so use this link....


MTX v5.0.0.0 + Full Examples.rar




_

[Cesar82]

@BLACKFIRE69, very good the new key default options in example 5.
It will be very useful for the need to use MRX.ini.
Thanks for the great job.

If you have both configurations, which one will be used?
I mean if you have MTX.ini configured in one way and use the key default with --mainpath, etc. in another way, which one will be used?

[BLACKFIRE69]

Originally Posted by Cesar82

@BLACKFIRE69, very good the new key default options in example 5.
It will be very useful for the need to use MRX.ini.
Thanks for the great job.

If you have both configurations, which one will be used?
I mean if you have MTX.ini configured in one way and use the key default with --mainpath, etc. in another way, which one will be used?

first configured file (MTX.ini) then checks the default keys (--mainpath , ...).

means,

If MTX.ini is not configured, it uses the default keys.

[Cesar82]

Originally Posted by BLACKFIRE69

first configured file (MTX.ini) then checks the default keys (--mainpath , ...).

means,

If MTX.ini is not configured, it uses the default keys.

Just out of curiosity, if I use it like this:

DiskSpan_x64.ini:

[External compressor:mpz,MPZ,mpzapi,MPZAPI]
header    = 0
packcmd   = "MEDIA\MPZ\mpzapi.exe" c <stdin> <stdout>
unpackcmd = "MEDIA\MPZ\mpzapi.exe" d <stdin> <stdout>

[External compressor:mpz_mtx,MPZ_MTX,mpzapi_mtx,MPZAPI_MTX]
header    = 0
default   = -c:64m -t:100p --mainpath=".\..\..\..\" --config="%MainPath%\DiskSpan_x64.ini" --tmppath="%MainPath%\..\TEMP"
packcmd   = "OTHERS\MTX\Win64\MTX.exe" a:mpz {options} - - <stdin> <stdout>
unpackcmd = "OTHERS\MTX\Win64\MTX.exe" x:mpz {options} - - <stdin> <stdout>

And add MTX.ini file next to MTX.exe with the config:

MTX.ini

[MTX]
MainPath=.\..\..\..\
Config=%MainPath%\DiskSpan_x64.ini
TmpPath=%MainPath%\..\TEMP

Question is as follows:
Will the "-c:64m -t:100p" settings be applied to MTX.exe, or will they be ignored?

Thanks!