This is the prcedure I took to do a silent install. I was working with the academic version of Studio MX 2004. I did the same procedure for Fireworks MX 2004.
I first ran Install Flash MX 2004.exe from the Accessibility folder on the install cd. At the first screen where I had to press next to continue, I browsed to the temp folder under local settings for the currently logged in user. There is a folder called pftf.tmp. In that folder there is another fodler called Disk1. Copy that folder to an alternate location. Cancle the installation. from the Disk1 folder you copied, run setup /r. Install Flash. After the installation, you will find in your windows directory the silent install answer file setup.iss.
We are halfway there. With that file you can do a silent install : setup /s
besure to include the iss file in the same directory as setup.exe.
For the next step you will need to be able to capture registry settings. I use WinInstall LE 2003.
Install Flash. Take a "before" snapshot of the machine. Start Flash for the first time and enter the correct registration/licensing information. Close Flash. Take the "after" snapshot. You will only some of the reg file that was created to create an msi package. You may need to clear out any "junk" that might have shown up in the registry. Remove any key listed as: HKLM\SOFTWARE\Macromedia\<app name>\7.0
or for FreeHand 11.1
Do not confuse with just "7" or "111"
I then created a script that runs the setup and merges the reg file into the registry.
If you run the setup from a network location that is readonly, you will need to custmize the command line for setup:
\\<network location>\setup.exe /s /f1\\<network location>\setup.iss /f2c:\windows\temp\setup.log
If the setup.exe can't write to a location to create the setup.log file, it will fail.
I have used this method to install Flash MX 2004 and Fireworks MX 2004 to over 1500 client workstations.
When repackaging Flash MX 2004, I found that Wise Package Studio set Flash's executable as a keypath.
Therefore, when running Flash as a first time user - without the source .msi present - self heal/repair of FH's .exe is not possible, and the app can't be started. I also found this was the case repackaging the other apps in the Studio MX 2004 Suite.
If you need to insure self heal/repair without the presence of the source .msi, reset the keypath to another component - preferably a registry keypath. When you do this, you will also need to recreate any shortcuts you want on Start Menu\Programs, etc., because removing the keypath from the program's executable will break the original shortcut(s).
As someone has already posted in the Macromedia Freehand notes, I found that it is essential to do the following in order for this application to work in a locked down environment:
1. Enable access permissions to HKLM\Software\Macromedia for all users.
2. Set the Macromedia Licensing Service to "Automatic". Otherwise Flash will attempt to start the service and fail. There is no error message - Flash.exe just terminates before the splash screen even appears.
Questions & Answers related to Macromedia Flash MX
Blogs (0)
Blog posts related to Macromedia Flash MX
Links (0)
Links related to Macromedia Flash MX
Reviews (0)
Reviews related to Macromedia Flash MX
This website uses cookies.
By continuing to use this site and/or clicking the "Accept" button you are providing consent
Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our
websites or when you do business with us. For more information about our
Privacy Policy and our data protection
efforts, please visit
GDPR-HQ
