FileForums - Universal Accelerator

Page 3 of 5

Show 40 post(s) from this thread on one page

FileForums (https://fileforums.com/index.php)

- Conversion Tutorials (https://fileforums.com/forumdisplay.php?f=55)

- - Universal Accelerator - cls-mtx.dll (https://fileforums.com/showthread.php?t=103664)

BLACKFIRE69

10-09-2020 11:26

Quote:

Originally Posted by Masquerade (Post 487856)

@BLACKFIRE69

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

https://i.imgur.com/SQ3xieL.png

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..." :cool:

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

10-09-2020 11:37

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

https://i.imgur.com/7FF4eKA.png

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

11-09-2020 06:32

Quote:

Originally Posted by Masquerade (Post 487859)

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

the drive G , is it a portable drive?

Masquerade

11-09-2020 08:10

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

BLACKFIRE69

12-09-2020 09:07

1 Attachment(s)

Quote:

Originally Posted by Masquerade (Post 487875)

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.

Masquerade

12-09-2020 15:13

@BLACKFIRE69

Following your instruction, it works:

https://i.imgur.com/gsSjAVK.png

BLACKFIRE69

12-09-2020 21:21

Quote:

Originally Posted by Masquerade (Post 487898)

@BLACKFIRE69

Following your instruction, it works:

https://i.imgur.com/gsSjAVK.png

cls-mtx.dll that i gave is original (v2.0.0.4), i didn't change anything.

so i think you need to double check your "Script.iss". :D

or you forgot to replace the old "cls-mtx.dll" with the new version (v2.0.0.4). :cool:

BLACKFIRE69

13-09-2020 11:55

mcm

cls-mtx.dll also supports "mcm".

arc.ini:

Code:

[External compressor:mcm]

header = 0

packcmd   = Resources\Mcm\{compressor} -x6 $$arcdatafile$$.tmp $$arcpackedfile$$.tmp

unpackcmd = Resources\Mcm\{compressor} d $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

Pack.bat

Code:

arc.exe a -ep1 -r -ed -s; -w.\temp -m=srep+mtx:c128m:t100p:mcm "..\Packed\Data0.bf" "..\Pack0\*"

BLACKFIRE69

13-09-2020 11:57

Next Update

any suggestions for the next update of "cls-mtx"? :D

Cesar82

13-09-2020 12:35

Quote:

Originally Posted by BLACKFIRE69 (Post 487929)

any suggestions for the next update of "cls-mtx"? :D

If you are not going to increase the size of your library a lot, even if it does not serve to increase performance, it could include support for all the most used methods that would dispense with the use of other CLS.

Does your cls-mtx.dll library allow me to extract using executables in folders?
I want to include a mode with decompressors in folders in the CIU and I think that the other CLS don't work the way I need.

Creating folder structures as:

Code:

Compressors\PRECOMP\<precomp files>

Compressors\MPZAPI\<mpz files>

Compressors\RAZOR\<rz files>

In the Arc.ini file informing the folder containing the executables, like this:

Code:

[External compressor:precomp]

header    = 0

unpackcmd = "PRECOMP\{compressor}" -r -o$$arcdatafile$$.tmp $$arcpackedfile$$.tmp



[External compressor:mpz]

header    = 0

unpackcmd = "MPZAPI\{compressor}" d <stdin> <stdout>



[External compressor:rz]

header    = 0

unpackcmd = "RAZOR\{compressor}" e -y $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

Using in the Inno Setup script like this:

Code:

[Files]

Source: cls-mtx.dll; Flags: dontcopy;

Source: CLS.ini; Flags: dontcopy;

Source: Arc.ini; Flags: dontcopy;

Source: UnARC.dll; Flags: dontcopy;

Source: ISDone.dll; Flags: dontcopy;

Source: "Compressors\*"; Flags: dontcopy createallsubdirs recursesubdirs;



[code ]

function InitializeSetup(): Boolean;

begin

   ExtractTemporaryFile('cls-mtx.dll');

   ExtractTemporaryFile('CLS.ini');

   ExtractTemporaryFile('Arc.ini');

   ExtractTemporaryFile('UnARC.dll');

   ExtractTemporaryFile('ISDone.dll');



   ExtractTemporaryFiles('{tmp}\Compressors\*');

end;

BLACKFIRE69

13-09-2020 20:37

Quote:

Originally Posted by Cesar82 (Post 487930)

Code:

Compressors\PRECOMP\<precomp files>

Compressors\MPZAPI\<mpz files>

Compressors\RAZOR\<rz files>

In the Arc.ini file informing the folder containing the executables, like this:

Code:

[External compressor:precomp]

header    = 0

unpackcmd = "PRECOMP\{compressor}" -r -o$$arcdatafile$$.tmp $$arcpackedfile$$.tmp



[External compressor:mpz]

header    = 0

unpackcmd = "MPZAPI\{compressor}" d <stdin> <stdout>



[External compressor:rz]

header    = 0

unpackcmd = "RAZOR\{compressor}" e -y $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

Using in the Inno Setup script like this:

Code:

[Files]

Source: cls-mtx.dll; Flags: dontcopy;

Source: CLS.ini; Flags: dontcopy;

Source: Arc.ini; Flags: dontcopy;

Source: UnARC.dll; Flags: dontcopy;

Source: ISDone.dll; Flags: dontcopy;

Source: "Compressors\*"; Flags: dontcopy createallsubdirs recursesubdirs;



[code ]

function InitializeSetup(): Boolean;

begin

   ExtractTemporaryFile('cls-mtx.dll');

   ExtractTemporaryFile('CLS.ini');

   ExtractTemporaryFile('Arc.ini');

   ExtractTemporaryFile('UnARC.dll');

   ExtractTemporaryFile('ISDone.dll');



   ExtractTemporaryFiles('{tmp}\Compressors\*');

end;

Cesar,
"cls-mtx.dll" supports this feature, since v2.0.0.3.

and unpackcmd should be like, ( without inverted commas (") ) (i'll fix this issue in the next update.)

Code:

[External compressor:bcm]

header    = 0 

unpackcmd = Res\Bcm\{compressor} -d $$arcpackedfile$$.tmp $$arcdatafile$$.tmp



not



unpackcmd = "Res\Bcm\{compressor}" -d $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

here is the full example, ;)

cls-mtx Example - Cesar.rar

Cesar82

13-09-2020 21:36

Quote:

Originally Posted by BLACKFIRE69 (Post 487934)

Cesar,
"cls-mtx.dll" supports this feature, since v2.0.0.3.

and unpackcmd should be like, ( without inverted commas (") ) (i'll fix this issue in the next update.)

Code:

not



unpackcmd = "Res\Bcm\{compressor}" -d $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

Without double quotes (") in the path names, if the path has spaces then I think it will detect the path to the space and the rest will be interpreted as another parameter causing errors.

Code:

[External compressor:bcm]

header    = 0 

unpackcmd = Res\Bcm Compressor\{compressor} -d $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

I will look forward to future updates.
Thank you.

BLACKFIRE69

13-09-2020 22:51

Quote:

Originally Posted by Cesar82 (Post 487936)

Without double quotes (") in the path names, if the path has spaces then I think it will detect the path to the space and the rest will be interpreted as another parameter causing errors.

Code:

[External compressor:bcm]

header    = 0 

unpackcmd = Res\Bcm Compressor\{compressor} -d $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

I will look forward to future updates.
Thank you.

that's not a problem. you can set the path without ("). (note that: for cls-mtx :cool:)

like this..

Code:

[External compressor:bcm]

header    = 0 

packcmd   = Res\Bcm Compressor\{compressor} -9 $$arcdatafile$$.tmp $$arcpackedfile$$.tmp

unpackcmd = Res\Bcm Compressor\{compressor} -d $$arcpackedfile$$.tmp $$arcdatafile$$.tmp



works well....

Cesar82

13-09-2020 23:19

Quote:

Originally Posted by BLACKFIRE69 (Post 487937)

that's not a problem. you can set the path without ("). (note that: for cls-mtx :cool:)

like this..

Code:

[External compressor:bcm]

header    = 0 

packcmd   = Res\Bcm Compressor\{compressor} -9 $$arcdatafile$$.tmp $$arcpackedfile$$.tmp

unpackcmd = Res\Bcm Compressor\{compressor} -d $$arcpackedfile$$.tmp $$arcdatafile$$.tmp



works well....

Thank you!
But if the path was something like that, would it work too?

Code:

[External compressor:bcm]

header    = 0 

packcmd   = Res\Bcm compressor\bcm -9 $$arcdatafile$$.tmp $$arcpackedfile$$.tmp

unpackcmd = Res\Bcm -decompressor\bcm -d $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

BLACKFIRE69

14-09-2020 01:48

Quote:

Originally Posted by Cesar82 (Post 487938)

Thank you!
But if the path was something like that, would it work too?

Code:

[External compressor:bcm]

header    = 0 

packcmd   = Res\Bcm compressor\bcm -9 $$arcdatafile$$.tmp $$arcpackedfile$$.tmp

unpackcmd = Res\Bcm -decompressor\bcm -d $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

yup, of course ;).
those characters must be valid characters.

but this is wrong.

Code:

packcmd   = Res\Bcm compressor\bcm -9 $$arcdatafile$$.tmp $$arcpackedfile$$.tmp



for cls-mtx:



[External compressor:bcm]

header    = 0

packcmd   = Res\Bcm compressor\{compressor} -9 $$arcdatafile$$.tmp $$arcpackedfile$$.tmp

All times are GMT -7. The time now is 07:34.

Page 3 of 5

Show 40 post(s) from this thread on one page