Jump to content

command line to install flash from swflash.cab


david.lynch
 Share

Recommended Posts

hello! 2e5388h.gif

I would like to know what's the exact command line to install flash from swflash.cab. Seems that would be something like 'rundll32 advpack.dll...', and I know that FP_AX_CAB_INSTALLER.EXE uses the switch RegServer from the .inf.

A completely silent command line would be nice to!

O.S.: Windows XP Professional SP3 and Windows Server 2003.

*Huge* thanks! jq6u1h.gif & 2my68ba.gif

Link to comment
Share on other sites


hi X, thanks, I already know the installer method.

but since swflash.cab is the default way to install/update from browser (and windows setup, it seems) I've searched for the command line of it, without success.

also, when using installer, we don't have a easy method to update it since it isn't on 'Downloaded Program Files' for a right-click, 'Update'.

2my68ba.gif

You could use the installer from Adobe and use the -install switch.

Link to comment
Share on other sites

Perhaps something along this command:

rundll32.exe setupapi,InstallHinfSection DefaultInstall 128 yourApp.inf

or

rundll32.exe advpack.dll,LaunchINFSection yourApp.inf,SomesectionName

Edited by Geej
Link to comment
Share on other sites

Thanks Geek, but the command line should use swflash.cab directly, as done by Internet Explorer itself.

another interesting thing is that, when you use the install_flash_player_ax.exe installer from Adobe, Internet Explorer still asks to download and install it (always from swflash.cab).

Perhaps something along this command:

rundll32.exe setupapi,InstallHinfSection DefaultInstall 128 yourApp.inf

or

rundll32.exe advpack.dll,LaunchINFSection yourApp.inf,SomesectionName

Link to comment
Share on other sites

There is no proper document for using FP_AX_CAB_INSTALLER.EXE to install with swflash.cab.

As far as I know, FP_AX_CAB_INSTALLER.EXE /Regserver simply launch the Flash Installer in GUI mode.

User still need to click "I agree" & "Install" button before proceeding. And all these are in user-attended mode.

Then you still need to click "Done" button. It is not an unattended method.

Somehow, I believe Adobe create a different installer (ie. FP_AX_CAB_INSTALLER.EXE) that install thru the web page.

For unattended, I don't think FP_AX_CAB_INSTALLER.EXE is the right way.

Regards

Link to comment
Share on other sites

  • 5 weeks later...

FP_AX_CAB_INSTALLER.exe -install

Flash Player 10.1 (Argo)

With the release of Flash Player 10.1, the command line arguments have significantly changed. Users are no longer required to use the -clean/-force argument to force a complete uninstall of the Flash Player when using the standalone uninstaller. However, when using the FlashUtil.exe to uninstall, the user is still required to use the -force argument to perform a complete uninstall.

Note: The arguments listed below only apply to the EXE installer, not the MSI installer.

The new command line arguments are:

-install: Perform a silent install of the Flash Player.

-uninstall: Perform a silent uninstall of the Flash Player.

Note: These can be used with the standalone uninstaller, or with the FlashUtil .exe in \Macromed\Flash directory

-uninstall {activex | plugin}: Perform an uninstall of a specific player, either ActiveX (Internet Explorer) or plugin (other browsers).

Note: This can be used with the standalone uninstaller, or with the FlashUtil .exe in the \Macromed\Flash directory.

Note: When uninstalling a specific player, a specific player type must be used in conjunction with the silent -uninstall argument, else it will not work and both player types will be uninstalled.

Flash Player 9 (9.0.28.0) to 10.0.45.0 (Coral).

The utility file FlashUtil.exe is installed with Flash Player 9.0.28.0 to 10.0.45.0 in the C:\Windows\system32\Macromed\Flash directory. FlashUtil.exe includes functionality required by Windows Vista and by the auto-update notification process. The previous utility (UninstFl.exe) is no longer required by or installed with Flash Player.

The utility is versioned with the control. For example, FlashUtil9b.exe is installed with the control Flash9b.ocx. FlashUtil.exe also contains several options that developers can use to switch between player and debugger versions during testing. Developers can modify the default behavior by using the following command-line flags:

USAGE : %s [-uninstallUnlock] [-uninstallLock] [-uninstallControlPath] path]

If run with no flags , the auto-update notification dialog will appear.

-uninstallUnlock: unlock the control. Grant write/delete permission to OCX and registry keys without erasing files.

-uninstallLock: lock the control. Deny write/delete permission.

-uninstallControlPath path: Optional; override the default path to the control. Must be used in conjunction with one of the other flags. If omitted, the path is located based on registry information.

The default path is located in the registry key of:

HKCR\CLSID\{D27CDB6E-AE6D-11cf-96B8-444553540000}\InProcServer32

For example, C:\Windows\system32\Macromed\Flash\Flash8b.ocx

The use of FlashUtil*.exe with the locking control is best illustrated with an example situation: While developing and testing content, you would like to check playback in Flash Player 8 and Flash Player 9. You keep copies of the 8.0.24.0 and 9.0.28.0 controls in separate named directories. Version 9.0.28.0 is the currently registered control, and you would like to switch to version 8.

First, unlock the registered control without deleting it so that you can switch back to it later:

FlashUtil9b.exe -uninstallUnlock c:\WINDOWS\System32\Macromed\Flash\Flash9b.ocx

Next, register the version 8 control:

regsvr32.exe c:\windows\system32\Macromed\Flash\Flash8b.ocx

Now, version 8 is the currently registered Flash Player. The locking controls contain the self-registration code to lock the control.

Flash Player 9.0.16.0 and earlier.

Some versions of Flash Player earlier than 9.0.28.0 are installed with an uninstaller program, UninstFl.exe, which is placed in the C:\Windows\system32\Macromed\Flash directory.

Version Includes UninstFl.exe

Flash Player 7

7.0.63.0, 7.0.68.0 and later

Flash Player 8

8.0.24.0, 8.0.33.0 and later

Flash Player 9

9.0.16.0

The default behavior of UninstFl.exe is to prompt the user, unlock the control, unregister the control, and then delete the OCX, GetFlash.exe, and GetFlash.exe.manifest. UninstFl.exe does not remove itself and cannot remove files that are in use. UninstFl.exe only works on the new locking controls. Older controls do not contain the registration logic to lock or unlock the file and are not recognized by the UninstFl.exe for deletion. When run on older controls, GetFlash.exe and GetFlash.exe.manifest will be deleted, but the control remains. To ensure clean removal of Flash Player, you should run the general uninstaller, uninstall_flash_player.exe, available from "How to uninstall the Macromedia Flash Player plug-in and ActiveX control" (TechNote tn_14157).

UninstFl.exe also contains several options that developers can use to switch between player versions during testing. Developers can modify the default behavior by using the following command line flags:

USAGE : %s [-quiet] [-unlock] [-lock] [filename]

Only the first character of a flag is relevant.

-q: Suppress prompt.

-u: Unlock; grant write/delete permission to OCX and registry keys without erasing files.

-l: Lock; deny write/delete permission.

filename: Overrides the default path. The default path is located in registry key of HKCR\CLSID\{D27CDB6E-AE6D-11cf-96B8-444553540000}\InProcServer32. For example: C:\Windows\system32\Macromed\Flash\Flash85.ocx

The use of UninstFl.exe with the locking controls is best illustrated with an example situation: while developing and testing content, you would like to check playback in Flash Player 7 and Flash Player 8. You keep copies of the 7.0.63.0 and 8.0.24.0 controls in separate named directories. Version 8 is the currently-registered control, and you would like to switch to version 7.

First, unlock the registered control without deleting it so that you can switch back to it later:

UninstFl.exe -u c:\windows\system32\Macromed\Flash\Flash8.ocx

Next, register the version 7 control:

regsvr32.exe c:\windows\system32\Macromed\Flash\Flash.ocx

Now, version 7 is the currently registered Flash Player. The locking controls contain the self-registration code to lock the control.

Edited by Bilou_Gateux
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...