My program's size is larger than 2GB. So, I set the DiskSpanning option to true and uploaded the divided 'bin' files to 'S3'. The 'bin' files are automatically downloaded to the tmp folder. I failed to move or copy files to 'Downloads' folder and failed to change default path in 'Setup Needs the Next Disk' printed 'Installing' previous wizard. So I would like to know how to change the default path or move the files in tmp to the 'Downloads' folder.
Thank you.
You cannot change the path and the default path is not the "Downloads" folder either. The default path is the location of the installer .exe file. Basically the {src}.
For moving the downloaded files elsewhere, see:
Change download location for Inno Setup TDownloadWizardPage
Related
I have successfully installed aws cli, but I'm getting
"'aws' is not recognized as an internal or external command,
operable program or batch file."
I think it is problem with the path settings. How do I know the path of AWSCLI for windows?
Ideally, it should be configured with the installation.
Please try the following.
On my system for version
The path entry is
C:\Program Files\Amazon\AWSCLIV2\
Check that this path "C:\Program Files\Amazon\AWSCLIV2" exists on your system. If it's nonexistent then search for aws.exe in C:\Program Files. The folder in which aws.exe is present will be your base path. If you don't find the aws.exe do a re-install.
If the path "C:\Program Files\Amazon\AWSCLIV2" exists on your system. Or there is some other folder in which aws.exe is present then that path needs to be configured manually.
Set the path manually. by following steps.
Steps to add this entry in a path environment variable.
Click on windows and search edit environment.
In the System variable section click on the path.
Add the path "C:\Program Files\Amazon\AWSCLIV2"
Save. Open a new command line and type aws.
Whats the proper way to form relative file path/ or file path for the runsettings parameter
<SettingsFile>xxxxxAutomation.testsettings</SettingsFile>
In my local environment this works but when i push it to build release agents it fails since
its looking for the file in a different directory which is my release folder
but instead its looking for this file in what appears to be in a folder directory.
This is the directory its looking at E:\Agent_work\r10\a\xxxxxxxxx.testsettings,
here is my current way i have it set
<SettingsFile>xxxxxAutomation.testsettings</SettingsFile>
here is the error message
Error: The test settings file E:\Agent_work\r10\a\xxxxxxxxxx.testsettings, specified in the MSTestAdapter settings, is not available. Either access to the file is denied or the file does not exist. Ensure that the test settings file is available and try again.
instead of
E:\Agent_work\r10\a_XXXXX CI Build\drop\XXXXX_Automation_Test\bin\Release\xxxxxxxxx.testsettings
There is no documentation that states how to formulate the file path on msdn and didn't see
anything online.
I suggest you can add a Copy Files task to copy the missing file from .../bin/release folder(Use the browse option) to default working directory:
I suggest you resolve this issue via modifying your pipeline instead of settings file, so that you can also work well locally with the unchanged runsettings file.
In addition: Clean Target Folder input should be disabled(unchecked) cause our target folder is the default working folder. Deleting all files in that folder would cause unexpected issues.
It is possible to change name only of .bin files and left setup as a setup.exe?
I mean:
setup.exe
data1.bin
data2.bin
etc...
No it's not possible.
Both .exe and .bin output file names are based on OutputBaseFilename.
During install, the installer creates a backup directory with a timestamp added to make it unique if installer is started multiple times.
During uninstall I need to process some files (not placed by [Files] and [Dir] section) to be restored in the usUninstall or usPostUninstall. These files are placed in sub-directories in the backup directory.
For this, I need my location where the uninstaller is started so I can restore the files.
I found and tried the GetCurrentDir function. But during uninstall the GetCurrentDir function returns the location c:\WINDOWS\system32.
I tested it also during install, but in that case the GetCurrentDir function returns the location where the installer is started.
How to get the proper location from where the uninstall is started?
The {uninstallexe} constant resolves to a path to the uninstaller.
If you combine that with ExtractFilePath, you get a path to the uninstaller folder:
ExtractFilePath(ExpandConstant('{uninstallexe}'))
Though actually, the path will typically be the installation path. So you can use {app} constant directly.
Do not use GetCurrentDir! It returns the current working directory. What does not have to be the path to the installer.
Use {src} constant.
How to change names, extensions and locations of setup-*.bin (Inno Setup internal compression archive file)
Default archive location: {src}
Location where I want: {src}\Data (Data is a folder.)
There are many way to change the output folder and base file name here are a few:
In inno setup
[Setup]
OutputDir={userdocs}\Data({userdocs}means my document,change this if you want another folder)
To change Output Base File name that is setup-*.bin in your case
[Setup]
OutputBaseFilename=setup(change setup to any name)
To change the size of setup-*.binyou can use
[Setup]
DiskSpanning=true
DiskSliceSize=2000000000(as your preference).
{src} is nothing but a directory constants which mean
"The directory in which the Setup files are located".
PS: If you want to create script for inno setup you can use ISTool instead then use the script in inno setup.
Thanks if you like my answer then accepted it.
By the setup-*.bin, I assume you refer to output files resulting from disk spanning. I do not know what "Inno Setup internal compression archive file" is.
Default location for Inno Setup output files is not {src} (it wouldn't make sense) but subfolder "Output" under the directory containing the script."
You can change this using OutputDir directive.
Quoting Inno Setup documentation:
Specifies the "output" directory for the script, which is where the Setup Compiler will place the resulting SETUP.* files. By default, it creates a directory named "Output" under the directory containing the script for this.