Universal Accelerator - cls-mtx.dll

[Masquerade]

Originally Posted by BLACKFIRE69

guys, arc.exe and cls-mtx.dll must be in the same folder. it's not from me, it's from the FreeArc.

Yes, I already know this.

I have it this way, let me show an example:

Folder
---------> Binaries
|                    - - - - - - - - ->Arc.exe
|                    - - - - - - - - ->Arc.ini
|                    - - - - - - - - ->cls-mtx.dll
|                    - - - - - - - - ->rz.exe
|                    - - - - - - - - ->Pack.bat
|
----------> Alt
                 - - - - - - - - - ->Pack2.bat

Now, Pack2.bat is set to run arc.exe inside the binaries folder:

@echo off
..\Binaries\Arc a -wTemp -mmtx:c64m:t16:rz (as well as the input output files)

But if we run this, we get uknown method error from mtx.

If we run pack.bat inside the binaries folder, it runs normally. Arc.ini is written correctly. Other cls based compressors like bpk work just fine.

[BLACKFIRE69]

Originally Posted by Masquerade

Yes, I already know this.

I have it this way, let me show an example:

Folder
---------> Binaries
|                    - - - - - - - - ->Arc.exe
|                    - - - - - - - - ->Arc.ini
|                    - - - - - - - - ->cls-mtx.dll
|                    - - - - - - - - ->rz.exe
|                    - - - - - - - - ->Pack.bat
|
----------> Alt
                 - - - - - - - - - ->Pack2.bat

Now, Pack2.bat is set to run arc.exe inside the binaries folder:

@echo off
..\Binaries\Arc a -wTemp -mmtx:c64m:t16:rz (as well as the input output files)

But if we run this, we get uknown method error from mtx.

If we run pack.bat inside the binaries folder, it runs normally. Arc.ini is written correctly. Other cls based compressors like bpk work just fine.

@Masquerade,
this may work as expected

_pack.bat :-

@echo off

cd /d "Binaries"
arc.exe a -ep1 -r -ed -s; -w.\temp -m=mtx:c64m:t4:rz ..\Packed\Data5.bf "Pack5\*"

pause&exit

[Masquerade]

@BLACKFIRE69

Thanks for the addition of the tool, however there has not been a change as highlighted in the below image.



In the left panel we see my Temp Folder where the CLS-MTX unpack folder.

In CLS.ini we see that the temp path is in my install path, G:\Games\Minecraft Dungeons

There is no unpack folder in the G:\Games\Minecraft Dungeons Folder

[BLACKFIRE69]

Originally Posted by Masquerade

@BLACKFIRE69

Thanks for the addition of the tool, however there has not been a change as highlighted in the below image.



In the left panel we see my Temp Folder where the CLS-MTX unpack folder.

In CLS.ini we see that the temp path is in my install path, G:\Games\Minecraft Dungeons

There is no unpack folder in the G:\Games\Minecraft Dungeons Folder

@Masquerade
the slash which is at the end of the line shouldn't be there.

means,
cls.ini

TmpPath=G:\Games\Minecraft Dungeons

Not
TmpPath=G:\Games\Minecraft Dungeons\

because MTX detects it as G:\Games\Minecraft Dungeons\\. so finally he decides , "the TmpPath does not exist..."

that was my mistake, i'll correct it with another update...

and the other things is, the folder ( G:\Games\Minecraft Dungeons ) must be present when running MTX. because MTX doesn't create a folder other than "CLS-MTX".

just test it with already created folder....

[Masquerade]

Alright, I repaired the code line in my setup, but same problem, mtx folder is created in temp directory.



The folder always is created by the setup as decompression begins. Even still in the above example I used oggre in mask so the oggre decompressor works first - so the folder G:\Games\Factorio does definitely exist.

[BLACKFIRE69]

Originally Posted by Masquerade

Alright, I repaired the code line in my setup, but same problem, mtx folder is created in temp directory.



The folder always is created by the setup as decompression begins. Even still in the above example I used oggre in mask so the oggre decompressor works first - so the folder G:\Games\Factorio does definitely exist.

ok, I'll take a look.....

the drive G , is it a portable drive?

[Masquerade]

Yes sir, it is a USB3.0 drive plugged into USB3.0 motherboard port.

[BLACKFIRE69]

Originally Posted by Masquerade

Yes sir, it is a USB3.0 drive plugged into USB3.0 motherboard port.

Masquerade,
i did a few tests. but i never saw that issue.

could you do a little test to figure it out?
ok then follow the steps below... (i'll attach the test files.)



1. compress some files using my compressor and the compression method should be " bcm " only.

2. install "Data0.bf" with my test script. ( remember to never edit the test "Script.iss". )

3. select your USB drive as the installation directory. (F:\ or something).

let's see the results.