[CIUv3] Custom Installer Ultimate v3

[amin fear]

Originally Posted by Cesar82

I think there is no limitation in the CIU source that prevents it from working.
If it works like processors like i5, i7 i think it should work. But maybe because it has several nuclei, ZTool/XTool(old vesrion) can crash (I don't know), maybe Razor12911 can answer that.
Experiment with the Light Installer. If it is something in the CIU code, it is a chance to discover the error.

Do other methods work normally?

Thanks! other methods works flawlessly, i think the answer lies within ZTOOL(x64) as @Razor12911 replied here today :

https://fileforums.com/showpost.php?p=488922&postcount=230

My setup is based on ZTOOL !

Will use Light Installer for experimental test!

[amin fear]

https://www.amazon.com/AMD-Ryzen-3900X-24-Thread-Processor/dp/B07SXMZLP9

[amin fear]

@Cesar82

Is "newer xtool 2020" already implemented in CIU 3.x ?

As advised by @Razor12911

my tools can handle up to 256 threads, if you have problems it's mainly because you're using ztool instead of the newer xtool which had MT bugs fixed.

[KaktoR]

I would like to wait a bit with including the new XTool version (bug fixing, development, ...).

However, you can always add it for yourself to DiskSpan and CIU installations.

[Cesar82]

In response to the "@amin fear" request, I changed the CIU and Light Installer source code for use with XTool 2020.
I decided to share it here so others who are interested can also use it.

To include other methods supported by XTool 2020, go to the UltraArc "Resources" folder and just add the section containing the new method to the "DiskSpan_x64.ini" file and also include the method name in the "Methods_x64.txt" file.

P.S: The XTool version 2011 (R1) whas included, so it only supports installation on 64-bit systems.
You must use the value "1" in the key 64BitOnly= of the file Setup.ini.

[alucard1973]

Originally Posted by Cesar82

In response to the "@amin fear" request, I changed the CIU and Light Installer source code for use with XTool 2020.
I decided to share it here so others who are interested can also use it.

To include other methods supported by XTool 2020, go to the UltraArc "Resources" folder and just add the section containing the new method to the "DiskSpan_x64.ini" file and also include the method name in the "Methods_x64.txt" file.

P.S: The XTool version 2011 (R1) whas included, so it only supports installation on 64-bit systems.
You must use the value "1" in the key 64BitOnly= of the file Setup.ini.

Hello
I tested and worked fine except for a minor but annoying problem, the registry all clears perfectly except what is in HKCU

Thanks

[amin fear]

Originally Posted by alucard1973

Hello
I tested and worked fine except for a minor but annoying problem, the registry all clears perfectly except what is in HKCU

Thanks

The commands in "Registry.iss" belong to Inno setup core, please post your "Registry.iss" scripts here, maybe you are mistyping & break proper inno format!

[alucard1973]

Originally Posted by amin fear

the commands in "registry.iss" belong to inno setup core, please post your "registry.iss" scripts here, maybe you are mistyping & break proper inno format!

i don't think there is an error but here is

for GameSaveFolder1 = command {userappdata} does not work

[alucard1973]

Originally Posted by Cesar82

1) This GameSaveFolder1= key does not exist.
Maybe you used it wrong. The correct one is SaveGameFolder1=.
Or maybe you're not using the correct constant for the directory that the save game is in.

2) The registry keys on the wrong path may be because you do not have full administrator privileges.
Here it works perfectly, watch the video HERE.
Try running Setup.exe as an administrator.
P.S: Here I use to disable UAC on my PC.

Yes sorry, that was SaveGameFolder1
my backup is in AppData\Roaming\Tropico 3 and I believe in innosetup the constant is {userappdata}, but it doesn't work while userdocs no problem
I will follow the video to see

[amin fear]

Originally Posted by Cesar82

In response to the "@amin fear" request, I changed the CIU and Light Installer source code for use with XTool 2020.
I decided to share it here so others who are interested can also use it.

To include other methods supported by XTool 2020, go to the UltraArc "Resources" folder and just add the section containing the new method to the "DiskSpan_x64.ini" file and also include the method name in the "Methods_x64.txt" file.

P.S: The XTool version 2011 (R1) whas included, so it only supports installation on 64-bit systems.
You must use the value "1" in the key 64BitOnly= of the file Setup.ini.

I have tested "eFootball PES 2021 Season Update" with both CIU & Light installer [XTOOL-2020] uploaded by you & it extracts very well without any problem!

Thanks @Cesar82

[Cesar82]

Hello people.
I developed a DiskSpan_GUI to create ARC files together with CLS-DiskSpan.dll (by Razor12911)
DiskSpan_GUI is similar to Disk_Span_BAT functions
I have not yet changed the CIU code to work with the new functions, so for now I ask you to test it with the "Light Installer Script".
- Now the compressors will not be internally in the Setup.exe.
- An external file "Setup.dll" will be created (Same name as Setup.exe with extension ".dll").
- This file must be together with Setup.exe when initializing the installation (DVD_1).
- To configure the GUI for its conversion, execute the file "_DiskSpan_GUI_Config.bat".
- To create a conversion with UltraArc it is necessary to create the DLL.
* It can be done by enabling the line ";#define CreateDLL" of the ".iss" script of the Light Installer, or by the "Create DLL" button of "COMPRESSOR_GUI.exe".
* In both options, the DLL will be created with the compressors selected in "COMPRESSOR_GUI.exe".
- When compressing the game using DiskSpan_GUI.exe, the DLL will be created with only the compressors needed to extract the game.
- XDelta3 serves only as a patch and works only in the [ExtractSettings] section of CIU/LIS, so it has been moved and can now be used (it will include XDelta3.dll) just checked the - - - Added loading of the list of keys directly into the combobox of the ue4dt configuration window. The names in the list must obey <GameName>|0x<Key>|<Method=1,2,m1,m2>
P.S: If anyone has information about which games on the list use ue4dt with parameter -m1 or -m2 please share.
- Fixed compression with password on zip file.
- Added Auto LOG checkbox option on Settings Mode (If checked, the log will be saved with DiskSpan_GUI.exe).
- Added Unpack function on finish page of compression.
- Added "UltraArc MODE" checkbox in Settings Mode individual to each Data file (If checked it will not use CLS-DiskSpan.dll).

[KaktoR]

I will do a test over night (with 2 list files and different methods).

Will post results when I wake up

PS: Maybe add "Test conversion" (decompress archives) button or something when compression is finished.

[KaktoR]

Test: Halo The Master Chief Collection
Single game
2 archives (Include1.txt, Include2.txt, Exclude1.txt)
Include1.txt method: bpk (picked from list, no manual writing)
Include2.txt method: xzlib+srep_new+LZMA-MT (picked from list, no manual writing)

Compression: Done
Create ISO: Checked and created
Shutdown PC: Checked and shutted down

Installation: Done with Lite Installer without errors

Suggestion:
Create a LOG file (like it is for DiskSpan.bat if possible
Add "Test conversion" when compression is done (button/checkbox or something) which extract archive to OUTPUT/TEST folder.
Add "No DiskSpan Mode", which allows us to use masked data compression (it is not possible with diskspan), maybe with split archives (same as UltraArc). This way we can replace UltraArc finally 100% :D

[KaktoR]

Originally Posted by Cesar82

1) I didn't understand about the log. A LOG similar to that of DiskSpan.bat is generated in the memo of the finish page. You only need to use the COPY or EXPORT buttons (To Save to file).

Yeah, well, if I run this over night while I sleep and I checked "Shutdown PC" then I will never see this window

PS: In all config files, change UELR

default    = -ulv

to

default    = ulv

[KaktoR]

Thanks. Export LOG works. Just a typo in filename if you export (Conversion_LOG.txt).

Unpack works fine too.

I think the 'Retry' button is only visible if you click on 'Unpack' on succesull conversion (I didn't remember).

'Unpack' button should only be visible/enabled if conversion is succesfull. It is visible/enabled if conversion is not successfull.

------------------

Just use the optimal arc.ini