stickfun Posted August 17, 2004 Posted August 17, 2004 hey everybody. this is my first post so my question is that i have some programs that are setup using the "setup factory" type installers.out of the installers listed on the site, this one wasn't on it. this also seems to be how many of my programs are installed. can anyone help me out here? thanks in advance
1chaoticadult Posted August 18, 2004 Posted August 18, 2004 /S /W - switches for silent installation. Check unattended.msfn.org for more information.
Alex_N Posted March 10, 2005 Posted March 10, 2005 I'm glad this thread exists because I didn't see any reference to Setup Factory on unattended.msfn.org
Alex_N Posted March 10, 2005 Posted March 10, 2005 Is there any way to pass destination parameter for example?
oioldman Posted March 10, 2005 Posted March 10, 2005 some do allow this.The most common being msi installer files. if you use TARGETPATH=<path> as part of switch it can install to there.Have seen other refs and complete topics to this within forum
Alex_N Posted March 10, 2005 Posted March 10, 2005 Thanks, but I was talking about Setup Factory only, not any other installer. I didn't see on their help documents how to pass defined values like 'Yes I want a shortcut in program menu' and such
totoymola Posted March 10, 2005 Posted March 10, 2005 I think there is a way to do that.. I will check the documentation of setup factory when I get home.
Alex_N Posted March 11, 2005 Posted March 11, 2005 I think there is a way to do that.. I will check the documentation of setup factory when I get home.<{POST_SNAPBACK}>You might have forgotten
totoymola Posted March 12, 2005 Posted March 12, 2005 No buddy. I didn't forget that. Here's what the help file says.The following command line options are supported by the Setup Factory installer:/S:<<optional ini file>>Allow an install to be run in silent mode. As a result, no screens or dialogs will be shown. If /S is passed on the command line it will set the global variable _SilentInstall to true if the Enable silent/unattended install option is selected in project settings.This command line option also has an optional INI file that can be passed containing session variable values. For example:"C:\output\setup.exe" "/S:C:\setupvars.ini"This will cause the session variables in the INI file to be used for the setup. The INI file should be in the format:[setupValues]%AppFolder%=C:\Program Files\Your Product 2%UserName%=Joe Blow%Whatever%=Who knows/T:<<file path>>Every setup executable requires some temporary space on the user's hard drive during the installation process. By default, Setup Factory uses the user's TEMP directory for extracting temporary files and other miscellaneous operations. You can force the setup executable to use an alternate directory by using the /T command line option.The syntax for the /T option is:/T:<<file path>>Replace "<<file path>>" with the path to the folder you want the setup executable to use for its temporary files. (Be sure to put quotes around the entire argument if the path includes any spaces.) If the folder doesn't already exist on the user's system, it will be created automatically.For example: "C:\Downloads\setup.exe" "/T:C:\My Temp Dir"(forces the installer to use "C:\My Temp Dir" for temporary files)/NOINITThis command line option hides the "initializing..." dialog that appears when extracting dependency or primer files at the beginning of the install.Uninstall Command Line OptionsThe following command line options are supported by the Setup Factory uninstall program:/S:<<optional ini file>>Allow an uninstall to be run in silent mode. As a result, no screens or dialogs will be shown. If /S is passed on the command line it will set the global variable _SilentInstall to true if the Allow silent uninstall option is selected in uninstall settings.This command line option also has an optional INI file that can be passed containing session variable values. For example:Note: The /U command line option also must be used when calling the uninstall program. See /U for details."C:\Windows\MyProduct\uninstall.exe" "/U:C:\Program Files\MyProduct\MyProduct.xml" "/S:C:\setupvars.ini"This will cause the session variables in the INI file to be used for the uninstall. The INI file should be in the format:[uninstallValues]%UserName%=Joe Blow%Whatever%=Who knows/U:<<INI config file>>This command line option must be used when calling the uninstall program from the command line. This command also has an optional INI file that can be passed containing session variable values. For example:"C:\Windows\MyProduct\uninstall.exe" "/U:C:\Program Files\MyProduct\MyProduct.xml"This will cause the session variables in the INI file to be used for the uninstall. The INI file should be in the format:[uninstallValues]%UserName%=Joe Blow%Whatever%=Who knowsHope this helps.
totoymola Posted March 12, 2005 Posted March 12, 2005 Setup variables might interest you.%AppFolder%Your application's main directory, where all of your files and folders will be installed. For example, by default Setup Factory's main directory is C:\Program Files\Setup Factory 7.0.%AppFolder% is initially set to the default value that you give it on the Session Variables tab of the Project Settings dialog. However, in most installations, the value of %AppFolder% will ultimately be set by the user on the Select Install Folder screen, overriding the default value.%ApplicationDataFolder%The path to the Application Data folder on the user's system. This folder serves as a common repository for application-specific data. Typically, this path is something like "C:\Documents and Settings\YourName\Application Data."%AppShortcutFolderName%The name of the shortcut folder on the Start menu where your application's shortcuts will be stored.%AppShortcutFolderName% is initially set to the default value that you give it on the Session Variables tab of the Project Settings dialog. However, in many installations, the value of %AppShortcutFolderName% will ultimately be set by the user on the Select Shortcut Folder screen, overriding the default value %ProductName%.%AppDrive%The drive letter of %AppFolder%. You should not set this variable explicitly. It is reset every time that %AppFolder% is re-assigned. For example, if %AppFolder% is C:\Program Files\My Program, %AppDrive% will be C:.%CommonFilesFolder%The user's Common Files folder. Typically, this is something like: C:\Program Files\Common Files.%CompanyName%Your company’s name. The value of this variable is set on the Session Variables tab of the Project Settings dialog.%CompanyURL%Your company’s URL. The value of this variable is set on the Session Variables tab of the Project Settings dialog.%Copyright%The copyright message for your product. The value of this variable is set on the Session Variables tab of the Project Settings dialog.%DAOPath%The path to the user's DAO (Data Access Objects) directory.%DesktopFolder%The path to the user's Desktop folder. On Windows NT/2000/XP, this is the path from the per-user profile.%DesktopFolderCommon%The path to the user's Desktop folder. On Windows NT/2000/XP, this is the path from the All Users profile. On a non-Windows NT system, this will simply be the path to the user's Desktop folder (the same as _DesktopFolder).%FontsFolder%The path to the user’s font directory (e.g. "C:\Windows\Fonts").%MyDocumentsFolder%The user's personal (My Documents) folder on their system. Usually this is something like "C:\Documents and Settings\YourName\My Documents" on Windows 2000/XP and "C:\My Documents" on Windows 98/ME.Note: Windows 95 did not have the My Documents folder and this variable will return "C:" if run on such a system.%ProductName%The name of the product that you are installing. The value of this variable is set on the Session Variables tab of the Project Settings dialog.%ProductVer%The version number of the product that you are installing. The value of this variable is set on the Session Variables tab of the Project Settings dialog.%ProgramFilesFolder%The user's Program Files folder (typically, this is something like "C:\Program Files").%RegOwner%The name of the registered user of the system.%RegOrganization%The organization of the registered user of the system.%SourceDrive%The drive that the installation executable was run from (e.g. "C:" or "D:").%SourceFolder%The full path to the folder that the installation executable was run from (e.g. "C:\Downloads" or "D:\").%SourceFilename%The full path, including the filename, for the current setup executable.For example, if the user was running "setup.exe" from "C:\Downloads", %SourceFilename% would be expanded to "C:\Downloads\Setup.exe".%StartFolder%The path to the user's Start menu folder. On Windows NT/2000/XP, this is the path from the per-user profile.%StartFolderCommon%The path to the user's Start menu folder. On Windows NT/2000/XP, this is the path from the All Users profile. On a non-Windows NT system, this will simply be the path to the user's Start menu folder (the same as %StartFolder%).%StartProgramsFolder%The path to the Programs folder in the user's Start menu. On Windows NT/2000/XP, this is the path from the per-user profile.%StartProgramsFolderCommon%The path to the Programs folder in the user's Start menu. On Windows NT/2000/XP, this is the path from the All Users profile. On a non-Windows NT system, this will simply be the path to the Programs folder in the user's Start menu (the same as %StartProgramsFolder%).%StartupFolder%The path to the user's Startup folder. On Windows NT/2000/XP, this is the path from the per-user profile.%StartupFolderCommon%The path to the user's Startup folder. On Windows NT/2000/XP, this is the path from the All Users profile. On a non-Windows NT system, this will be the path to the user's Startup folder (the same as %StartupFolder%).%SystemFolder%The path to the user’s Windows System folder (e.g. "C:\Windows\System").%SystemDrive%The drive that the user's Windows System directory is located on (usually "C:").%TempFolder%The path to the user's Temp folder.%TempLaunchFolder%The path to the temporary directory where Setup Factory extracts the files it will need for the installation. (For example, this is the directory where Primer files are extracted to.)Usually this directory will be the user's temporary directory, unless the user overrides the temporary directory with the /T command line option.%WindowsFolder%The path to the user’s Windows folder (e.g. "C:\Windows").%WindowTitle%The text that will appear on the windows task bar while the installation is running. The value of this variable is set on the Session Variables tab of the Project Settings dialog.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now