Hello everyone. Just got into game compressing recently and found my way here. Great work and so far I have been learning a lot. Something I cannot seem to figure out is how to change the Autorun button font color. I am sure it some noob mistake but I just cannot figure it out.

This is using CIU 3.0.0.1.b7.u3 (2020.10.20) and running the _Create New CIU Project script and working inside that new project with the lego template. The width changed, and so did the font, but the font color is black no matter what color code I put in.

So what is it that I could have missed to cause the font color to remain black?

AR = Autorun

Color Code is $RRGGBB

Thanks for the reply Kaktor, and is what I was thining but when I change the color code it has no effect. This is my current [StandardButtonAR] settings.

And this is the results. If I am not misaken doesn't ffffff = white?

yes

That is what has me puzzled. It's set to white but is displaying black. Figuring I missed something somewhere. Driving me crazy.

yes $FFFFFF is the color white

Thanks for the replies, but it is still not working. For a better visual on the issue here is a screenshot of the setup.ini and the setup running autorun side by side. Font should be white right?

Did you changed colors of other Autorun buttons ([UnInstallButton], [Play#Button], ...) to black color maybe?

No, In fact I created a new project and did not touch the setup.ini just to be sure. Looks like even the font is not correct. For further testing I tried with CIU 3.0.0.0.u9 (2020-07-02) with same steps, make new project and compiled the InstallerScript_3.0.0.0.u9 [2020.07.02] and outcome was correct font and color. So I am guessing I missed something in the setup.ini? Attached setup if needed

T tried this setup.ini with CIU 3.0.0.0.u9 (2020-07-02) script and it work fine. you have to compile the AutorunScript_3.0.0.0.u9.iss and InstallerScript_3.0.0.0.u9.iss to get the font color, also i tried few color samples and it worked too.

Oh my god! I didn't know that about the ; but I do now. Thanks!

but that works fine for me. :confused:

I don't have a clue. I seen you were using 3.0.0.0.u9 and I was using 3.0.0.1.b7.u3 but I would not think that would make a difference when compiling the script. ¯\_(ツ)_/¯

Defiantly a learning moment for me.

Is there any incompatibility between "CIU 3.x+ZTOOL+XTOOL" extraction process & new AMD CPU series ?

Anybody have tested ZTOOL with below CPU ?

AMD Ryzen™ 9 3900X "12-Core 3.8 GHz" (4.6 GHz Max Boost) Socket AM4 105W

My installer created with "CIU 3.x+SrepInsidex64+ZToolx64+LOLZx64" works pretty well on ALL of mid range CPUs(Corei3+Corei5+Corei7) but when extracting on NEW AMD Ryzen™ 9 3900X, installer stuck on "0.0" percent progress bar & "ZTool.exe" won't launch on task manager!!!

Is "ZTool.exe" incompatible with new 12-Core CPUs ?

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

My setup is based on ZTOOL !

Will use Light Installer for experimental test!

@Cesar82

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

As advised by @Razor12911

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.

CIU with XTool 2020
 

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

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:)

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

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

DiskSpan_GUI
 

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).
https://i.imgur.com/M1Ctr0i.png

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.

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

PS: In all config files, change UELR
to

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

Moved previous post (merged) to this post...
KaktoR's answer came before this question.
Check in the update 2 file (It's already as you suggested).
If you choose PC shuntdown, then before shutting down it saves the external Conversion_LOG.log file.
If you check the LOG option on the SETTINGS page, each line when it is inserted in the MEMO is also saved in the external log, but not saved at shutdown PC because it will already be the same as the memo LOG.
It also includes an option to cancel the shuntdow by pressing and holding the CTRL key for 1 second, if you need to keep the pc on when done. You must press CTRL key while the time is decreasing.
What setting should I use to extract the game by pressing the Unpack button on the finish page?
Currently using CLS_Optimal.ini/ARC_Optimal_x##.ini (## = x86 or x64 according to the system).

I had already noticed the error in the exported file name.
I checked the script and it seems to be setting Enabled = True whenever it goes to the finish page.
Even so I put it to enable it before going to the finish page to avoid being disabled.
I did it. Now only if the conversion is successfully completed will the "Unpack" button be enabled.

hello my brother I thank you really very much for your efforts and your kindness with us.
thanks again:D:D

Maybe change title to wordwrap :D

One question:

If I choose global method (the upper one) does this overwrite Data1 method?

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

CIU 3.0.0.0.1 (beta 7, update 4)
 

:cool:New CIU 3.0.0.0.1.b7.u4 with support for DiskSpan_GUI tool. :D
The CIU 3.0.0.1 beta 8 version presented several bugs so I downgraded it to the previous version just keeping the necessary changes to use DiskSpan_GUI.
I believe that this version 3.0.0.1.b7.u4 is stable since all errors previously reported had been corrected and the changes made to DiskSpan_GUI were few.

This version includes the DiskSpan_GUI with support for Cyberpunk 2077 (XTool 2020).
The method is available in the "Razor Tool" category on the DiskSpan_GUI in "Custom" tab, but it can also be used using DiskSpan.bat: cp_2077+srep_new+...

I removed 3.0.0.1.b8 temporarily.
The CIU version 3.0.0.1.b8 will be fixed and later I will share it here. :mad:

Added HF1 (Fixed CREATOR mode error).

Both archives seem to not be diskspan archives. Installer merge Data2 (like a split ultraarc file)? Why?

And why Data1 has a password '123'? The input field is empty.

I made a second test with default settings and created archive is not a diskspan archive. Why?

Edit: I discovered this bug. Diskspan_GUI.exe make a wrong Records.ini if 'UltraArc MODE' Checkbox := not checked.

Here are the 2 files

I don't have set a password but '123' password is always set by default (I couldn't find the setting in any of the INI files either).

Yes.
Both mistakes happen here.
I'll fix it and then share the file here.

@KaktoR
I think the error regarding the password happened randomly.
The first time I ran it with the config files you shared it did not display the edit password when searching for the method.
After that the password always appeared. I do not know what happened.
Now I have removed the pasword from the default settings.
- The error creating ARC/DiskSpan has been fixed.
- It is now possible to break the title (Conversion Name) line into 2 parts using the character "|" in Edit "Conversion Name", but if the height space is not enough, only the first part will be displayed.
Conversion designers, please replace the contents of the first file attached to the CIU's "UltraARC 2900 R9" folder.

Thanks.

Does DiskSpan_GUI take required "oo2core_#_win64.dll" file?

Example: If I choose "oo2reck" with "Oodle4". I ask because all of the 3 codecs (k, m, s EXE files) don't work without the required DLL file next to it.

If DiskSpan_Gui does not do this automatically, then this is a request :D

The file "oo2core_#_win64.dll" will be copied to the directory of the selected executable before compressing the Data # .bin file and the copy will be deleted when the compression is finished (or go to the next data file).
For this reason the methods include the index like oo2reck5, or oo2recs4.

I found some bugs in DiskSpan_GUI.
One of them is the order of the compressors in the CUSTOM tab that broke when including the cp_2077 method (I forgot to update).
Also the extraction of the lolz_mtx method is in error (CLS.ini was missing from the exe).
I will soon share an updated version of the CIU source code including these fixes.