/build/static/layout/Breadcrumb_cap_w.png

Flash 7

I have created a simple package for flash 7. It just requires a /Q switch which was the same for flash 6. It installs fine, yet I get a program error message under advertisement status and it doesn't show any programs as successful:

The program for advertisement "6201F5" failed ("Flash 7" - "Setup"). A non-zero exit code of 1 was returned.

As far as I can tell the plugin is installed fine (It places a macromedia folder under SYSTEM32) and when I test it shows as installed.

I am just wondering if this is anything I should be concerned about. Has anybody else seen this behavior?

Thanks

0 Comments   [ + ] Show comments

Answers (4)

Posted by: womp 20 years ago
Senior Yellow Belt
2
i didnt have any problems creating and distributing flash 7, but i'm using our software deployment tool to supress any dialogue boxes.
Posted by: duke22 20 years ago
Yellow Belt
1
Heads up to the Macromedia backdoor. If you are in a locked down environment, beware the Macromedia internet update check that will occur every thirty days by default. We had huge issues because users were trying to download it as the message from Macromedia said they should. It is not documented how to disable this feature, but here is what you have to do.

Add the following file to your MSI. (You will have to create it.)

1. Open a Text Editing Tool (NotePad, WordPad, etc).
2. Create a file named mms.cfg
a. In this file you simply need to add a single set of value pairs per line like the following:
AutoUpdateDisable=1

Save this file in the System32 directory.
Posted by: usachrisk 20 years ago
Purple Belt
1
I was able to setup the settings I wanted for the Flash Player on one machine, then send around the SETTINGS.SOL file to accomplish this. Anyone know of any issues this might cause over the way it was explained? If not, it's a nice way to do it for those who have had problems post-deploy.
Posted by: craig16229 20 years ago
Third Degree Brown Belt
1
This is slightly off the original post for Flash 7, but still might save someone some headaches.

There is a "serialization hotfix" from Macromedia for the MX 2004 products here: http://www.macromedia.com/support/service/ts/documents/serial_prompt.htm

It addresses the problem some volume licensing customers have where the serial number does not "stick". The symptom is that the first logged in user can run Flash (or Dreamweaver, Fireworks, or Freehand) without issue, but subsequent user accounts are prompted for the serial number again.

The download searches for a program folder for each of the 4 core applications in the Studio MX 2004 suite, and adds two .dll files into each that it finds.

craig --<>.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
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