Go Back   FileForums > Game Backup > PC Games > PC Games - CD/DVD Conversions > Conversion Tutorials
Register FAQ Community Calendar Today's Posts Search

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 16-05-2022, 11:16
Spotless's Avatar
Spotless Spotless is offline
Registered User
 
Join Date: Nov 2021
Location: Egypt
Posts: 28
Thanks: 0
Thanked 2 Times in 2 Posts
Spotless is on a distinguished road
Thank you guys for Help
i want to combine records.ini to setup
and i want to add component archive name
and Redists does not work
__________________
Be kind so that people be kind with you

Last edited by Spotless; 17-05-2022 at 12:22.
Reply With Quote
Sponsored Links
  #2  
Old 20-05-2022, 00:18
L33THAK0R's Avatar
L33THAK0R L33THAK0R is offline
Registered User
 
Join Date: Feb 2021
Location: Saudi Arabia
Posts: 406
Thanks: 137
Thanked 117 Times in 70 Posts
L33THAK0R is on a distinguished road
What'd be the best solution for being able to use a custom directory constant for a component file? I'm interested in looking into using something like the "{sd}" constant for a given component entry.

I know such functionality is supported for specifying the path of an ".ini" file under [INISettings], but I'm not too sure how to implement it.

I believe this is the section of the script I should be looking at, with the highlighted text being the value that I THINK indicates the working directory for where the file should be.

Code:
            ComponentFile := ExpandConstant('{src}\' + GetIniString('ComponentsSettings', 'Component' + IntToStr(CompIndexList[I]) + '.File', '', ExpandConstant('{tmp}\Settings.ini')));
            if (ISDoneError = False) and FileExists(ComponentFile) then
              if not ISArcExtract(0, 0, ComponentFile, ExpandConstant('{app}'), '', false, '', ExpandConstant('{tmp}\arc.ini'), ExpandConstant('{app}'), false) then
                ISDoneError := True;
I thought about using "{#.File}" or "{#File}", (as seen when used for "{#INIFile}") but this doesn't seem to be a valid solution, would anyone be able to suggest a method that I can look into?
Reply With Quote
  #3  
Old 20-05-2022, 00:39
Cesar82's Avatar
Cesar82 Cesar82 is offline
Registered User
 
Join Date: May 2011
Location: Brazil
Posts: 1,074
Thanks: 1,814
Thanked 2,304 Times in 787 Posts
Cesar82 is on a distinguished road
Quote:
Originally Posted by L33THAK0R View Post
What'd be the best solution for being able to use a custom directory constant for a component file? I'm interested in looking into using something like the "{sd}" constant for a given component entry.

I know such functionality is supported for specifying the path of an ".ini" file under [INISettings], but I'm not too sure how to implement it.

I believe this is the section of the script I should be looking at, with the highlighted text being the value that I THINK indicates the working directory for where the file should be.

Code:
            ComponentFile := ExpandConstant('{src}\' + GetIniString('ComponentsSettings', 'Component' + IntToStr(CompIndexList[I]) + '.File', '', ExpandConstant('{tmp}\Settings.ini')));
            if (ISDoneError = False) and FileExists(ComponentFile) then
              if not ISArcExtract(0, 0, ComponentFile, ExpandConstant('{app}'), '', false, '', ExpandConstant('{tmp}\arc.ini'), ExpandConstant('{app}'), false) then
                ISDoneError := True;
I thought about using "{#.File}" or "{#File}", (as seen when used for "{#INIFile}") but this doesn't seem to be a valid solution, would anyone be able to suggest a method that I can look into?
This is an old version of ASIS and I don't even remember anymore, but I think you can use any constant supported by Inno Setup, but all components will be redirected to new constant.
P.S: The current version you configure directly in the Records.ini file for each component.
Reply With Quote
  #4  
Old 20-05-2022, 04:36
L33THAK0R's Avatar
L33THAK0R L33THAK0R is offline
Registered User
 
Join Date: Feb 2021
Location: Saudi Arabia
Posts: 406
Thanks: 137
Thanked 117 Times in 70 Posts
L33THAK0R is on a distinguished road
I am able to change all components to use a given constant, was hoping though to be able to use a different constant for each component, thanks for the help nonetheless.

All the new functionality in newer versions of the script really have me seriously considering making the move from v7.2.0, honestly though the only thing stopping me is the super convenient "Compressor GUI", its a shame it was phased out after v7.2.0 .
Reply With Quote
  #5  
Old 20-05-2022, 07:57
Cesar82's Avatar
Cesar82 Cesar82 is offline
Registered User
 
Join Date: May 2011
Location: Brazil
Posts: 1,074
Thanks: 1,814
Thanked 2,304 Times in 787 Posts
Cesar82 is on a distinguished road
Compressor GUI was eliminated to make way for DiskSpan GUI which has much more features and ease of compression doing everything automatically.

Why don't you use DiskSpan GUI?
Reply With Quote
  #6  
Old 20-05-2022, 09:08
L33THAK0R's Avatar
L33THAK0R L33THAK0R is offline
Registered User
 
Join Date: Feb 2021
Location: Saudi Arabia
Posts: 406
Thanks: 137
Thanked 117 Times in 70 Posts
L33THAK0R is on a distinguished road
Quote:
Originally Posted by Cesar82 View Post
Compressor GUI was eliminated to make way for DiskSpan GUI which has much more features and ease of compression doing everything automatically.

Why don't you use DiskSpan GUI?
Compressor GUI looks great, and honestly its a god send for many, but I just use my own little script to process archives using multiple compressors, since I'm often running at least 10-20 fairly large compression tests at any given moment, and having a simple terminal window is just less resource intensive and more easily readable for me personally.

Sorry if I offended you, DiskSpan GUI is a great tool, just not my personal cup of tea.
Reply With Quote
  #7  
Old 20-05-2022, 08:47
fabrieunko fabrieunko is offline
Registered User
 
Join Date: Sep 2021
Location: france
Posts: 218
Thanks: 515
Thanked 78 Times in 71 Posts
fabrieunko is on a distinguished road
hello I would like to add the equalizer if someone can give me a track? thank you in advance
Reply With Quote
  #8  
Old 20-05-2022, 09:35
KaktoR's Avatar
KaktoR KaktoR is offline
Lame User
 
Join Date: Jan 2012
Location: From outer space
Posts: 4,689
Thanks: 1,106
Thanked 7,336 Times in 2,838 Posts
KaktoR is on a distinguished road
You don't have to use DiskSpan GUI for ASIS. You can still create your own archive which whatever tool you like. The only thing is you have to create a Setup.dll manualy. All of this is explained in Help folder\Setup.dll.txt
__________________
Haters gonna hate
Reply With Quote
The Following User Says Thank You to KaktoR For This Useful Post:
Cesar82 (20-05-2022)
  #9  
Old 20-05-2022, 09:57
L33THAK0R's Avatar
L33THAK0R L33THAK0R is offline
Registered User
 
Join Date: Feb 2021
Location: Saudi Arabia
Posts: 406
Thanks: 137
Thanked 117 Times in 70 Posts
L33THAK0R is on a distinguished road
Quote:
Originally Posted by KaktoR View Post
You don't have to use DiskSpan GUI for ASIS. You can still create your own archive which whatever tool you like. The only thing is you have to create a Setup.dll manualy. All of this is explained in Help folder\Setup.dll.txt
Ah sick yeah checking out v7.3.3 right now, things seem a lot more streamlined than the last time I checked out a newer revision, think I'll migrate over, the eye-boggling amount of new features/QoL improvements is too good to pass up on, plus being able to aggressively compress all the required compressors into a separate archive is super convenient, very confident this'll save at least a couple GB in space once I've rebuilt all my setup executables that were built using v7.2.0 .

Last edited by L33THAK0R; 20-05-2022 at 10:01.
Reply With Quote
  #10  
Old 20-05-2022, 16:31
Cesar82's Avatar
Cesar82 Cesar82 is offline
Registered User
 
Join Date: May 2011
Location: Brazil
Posts: 1,074
Thanks: 1,814
Thanked 2,304 Times in 787 Posts
Cesar82 is on a distinguished road
Quote:
Originally Posted by L33THAK0R View Post
Ah sick yeah checking out v7.3.3 right now, things seem a lot more streamlined than the last time I checked out a newer revision, think I'll migrate over, the eye-boggling amount of new features/QoL improvements is too good to pass up on, plus being able to aggressively compress all the required compressors into a separate archive is super convenient, very confident this'll save at least a couple GB in space once I've rebuilt all my setup executables that were built using v7.2.0 .
I've been looking at my old source codes here and apparently the current ASIS (v7.3.3) works with the COMPRESSOR_ GUI included in ASIS v7.2.2 (also including the compressor files).

I attached the files referring to the old compressors that worked with the COMPRESSOR_GUI (They must be very outdated).
With this GUI compressor you create the Setup.dll file that can be used with current ASIS (I think).
It must be extracted to the ASIS folder.
P.S: Add the 64BitOnly=0 key in the [Settings] section of the ASIS Settings.ini file so that you can use 32-bit compressors.
To work on 32-bit systems, it is also necessary to remove the lines indicated below from the [Setup] section of the Script.iss of the ASIS v7.3.3 :
Code:
ArchitecturesInstallIn64BitMode=x64
ArchitecturesAllowed=x64
EDIT: From what you can see it should also work with DislSpan GUI 1.0.0.5, just copy the COMPRESSOR.ini file from the "DiskSpan_GUI\Resources" folder to the COMPRESSOR\Resources folder of DiskSpan GUI 1.0.0.5 and then delete the DiskSpan GUI folder and rename the "COMPRESSOR" folder (DiskSpan GUI 1.0.0.5) to "DiskSpan_GUI" and move the folder into the ASIS folder.

EDIT: I attached a new file.
Extract the COMPRESSOR (DSG) folder to the ASIS 7.3.3 folder.
- Added a combobox in the COMPRESSOR_GUI interface to select the method used to compress Setup DLL.

Last edited by Cesar82; 24-05-2022 at 14:05.
Reply With Quote
The Following 3 Users Say Thank You to Cesar82 For This Useful Post:
Gehrman (04-07-2022), Grumpy (22-05-2022), XxAZAxX (21-05-2022)
  #11  
Old 21-05-2022, 04:17
L33THAK0R's Avatar
L33THAK0R L33THAK0R is offline
Registered User
 
Join Date: Feb 2021
Location: Saudi Arabia
Posts: 406
Thanks: 137
Thanked 117 Times in 70 Posts
L33THAK0R is on a distinguished road
Quote:
Originally Posted by Cesar82 View Post
I've been looking at my old source codes here and apparently the current ASIS (v7.3.3) works with the COMPRESSOR_ GUI included in ASIS v7.2.2 (also including the compressor files).

I attached the files referring to the old compressors that worked with the COMPRESSOR_GUI (They must be very outdated).
With this GUI compressor you create the Setup.dll file that can be used with current ASIS (I think).
It must be extracted to the ASIS folder.
P.S: Add the 64BitOnly=0 key in the [Settings] section of the ASIS Settings.ini file so that you can use 32-bit compressors.
To work on 32-bit systems, it is also necessary to remove the lines indicated below from the [Setup] section of the Script.iss of the ASIS v7.3.3 :
Code:
ArchitecturesInstallIn64BitMode=x64
ArchitecturesAllowed=x64
EDIT: From what you can see it should also work with DislSpan GUI 1.0.0.5, just copy the COMPRESSOR.ini file from the "DiskSpan_GUI\Resources" folder to the COMPRESSOR\Resources folder of DiskSpan GUI 1.0.0.5 and then delete the DiskSpan GUI folder and rename the "COMPRESSOR" folder (DiskSpan GUI 1.0.0.5) to "DiskSpan_GUI" and move the folder into the ASIS folder.
Oh wow this is better than any gift I could possibly receive, thank you so much mate for going to the effort of doing this, this is honestly a lovely surprise to see after a rather long 14hr shift!

Thank you also for the config batch file, I think you had given me some advice on how to do the same a while back but I never managed to get it working.

Thanks again mate, with this I'll definitely be fully migrating to v7.3.3
Reply With Quote
  #12  
Old 22-05-2022, 06:37
L33THAK0R's Avatar
L33THAK0R L33THAK0R is offline
Registered User
 
Join Date: Feb 2021
Location: Saudi Arabia
Posts: 406
Thanks: 137
Thanked 117 Times in 70 Posts
L33THAK0R is on a distinguished road
Quick question about specifying a file for a given Task/Component, what value determines what file to use in v7.3.3? Had a look through the help documentation as well as the script but can't find any reference of whether something like "Component1.File=" / "Task1.File=" is still used, as in v7.2.0, or whether its put inside the Settings.ini / Records.ini file.
Reply With Quote
  #13  
Old 22-05-2022, 08:36
KaktoR's Avatar
KaktoR KaktoR is offline
Lame User
 
Join Date: Jan 2012
Location: From outer space
Posts: 4,689
Thanks: 1,106
Thanked 7,336 Times in 2,838 Posts
KaktoR is on a distinguished road
Code:
Component1.Name=Game 1
...
...
Code:
[Record1]
...
Component=1
The same with Tasks

Code:
[Record1]
...
Task=#
__________________
Haters gonna hate

Last edited by KaktoR; 22-05-2022 at 09:07.
Reply With Quote
The Following 2 Users Say Thank You to KaktoR For This Useful Post:
Cesar82 (22-05-2022), L33THAK0R (22-05-2022)
  #14  
Old 27-05-2022, 09:21
KaktoR's Avatar
KaktoR KaktoR is offline
Lame User
 
Join Date: Jan 2012
Location: From outer space
Posts: 4,689
Thanks: 1,106
Thanked 7,336 Times in 2,838 Posts
KaktoR is on a distinguished road
[Run] section will not work.

The welcome text use "msgWelcomeLabel1" and "msgWelcomeLabel2" which you can't edit inside a isl file because they are "hard coded" somewhat (at least I did not found the strings anywhere), but I think maybe you can change the caption of it with "msgWelcomeLabel1.Caption := abc"

Edit: I talk bullshit. I forgot that "msg" before the label name means something which I forgot in the meantime...

The label name which you are looking for is "WelcomeLabel1" and "WelcomeLabel2" in the *.isl files.
__________________
Haters gonna hate

Last edited by KaktoR; 27-05-2022 at 09:34.
Reply With Quote
The Following User Says Thank You to KaktoR For This Useful Post:
abror (27-05-2022)
  #15  
Old 27-05-2022, 17:33
abror's Avatar
abror abror is offline
Registered User
 
Join Date: May 2022
Location: indonesia
Posts: 33
Thanks: 19
Thanked 0 Times in 0 Posts
abror is on a distinguished road
thanks to both of you

Is there any difference between the inno setup in Resources\IS_Files\Compil32Ex.exe and the one I installed (version 6.2.1)?

I'm confused which one to use

Will compiling using script.iss and using inno setup version 6.2.1 run smoothly?
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
[Help] need Advanced Installer script with Razor1911's UltraArc module rez3vil Conversion Tutorials 3 15-04-2024 02:24
Portable Installer Inno Setup Script y_thelastknight Conversion Tutorials 59 23-10-2020 00:02
INDEX - Conversion Tutorial Index Razor12911 Conversion Tutorials 5 11-06-2020 02:05
Simple Arc Installer 78372 Conversion Tutorials 1 15-06-2017 15:37
MSC+Srep+lzma Simple Script Example gozarck Conversion Tutorials 10 07-09-2015 16:31



All times are GMT -7. The time now is 04:45.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
FileForums @ https://fileforums.com