Adobe Reader 9 won't extract msi
I was just about to deploy Adobe Reader 8.1.2 update1 and noticed Reader 9 has just been released so I figured I'd send this out instead. I've downloaded the AdbeRdr90_en_US.exe and tried to extract the msi just as I did with version 8 using AdbeRdr90_en_US.exe -nos_ne from the directory where it resides but it doesn't extract the msi and data1.cab file to the %temp% dir, it just creates some small tmp file which gets deleted when the wizard finishes. Anyone else having problems with this? I'd prefer to package with the MSI using an MST rather than manipulate the exe wrapper with commandline parameters. I wish they'd just make the msi available.
EDIT:
The files are now extracted to the following path instead:
%Userprofile%\Local Settings\Application Data\Adobe\Reader 9.0\Setup Files\READER9
EDIT:
The files are now extracted to the following path instead:
%Userprofile%\Local Settings\Application Data\Adobe\Reader 9.0\Setup Files\READER9
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
ErinC
15 years ago
From the "Deploying Reader 9" guide (http://www.adobe.com/devnet/acrobat/pdfs/deploying_reader9.pdf?devcon=f3)
Expand the Nosso-compressed package
[font="myriad pro,myriad pro"][font="myriad pro,myriad pro"][align=left]Expand the Nosso-compressed file using the following from either the Run dialog or DOS command window:[/align][align=left] [/align][font="courier std,courier std"][font="courier std,courier std"][align=left]<path to>\AdbeRdr90_en_US.exe <switches> [/align][align=left] [/align][font="myriad pro,myriad pro"][font="myriad pro,myriad pro"][align=left]For example, the following command specifies that no files are to be executed after the expansion or installation, and the resulting files are to be placed in a folder named "Reader9":[/align][align=left] [/align][font="courier std,courier std"][font="courier std,courier std"][align=left]<path to>\AdbeRdr90_en_US.exe -nos_o"Reader9" -nos_ne [/align][align=left] [/align][font="myriad pro,myriad pro"][font="myriad pro,myriad pro"][align=left]where the switch "[font="courier std,courier std"][font="courier std,courier std"]-nos_ne" [font="myriad pro,myriad pro"][font="myriad pro,myriad pro"]specifies to not execute any file after installation, and "[font="courier std,courier std"][font="courier std,courier std"]Reader9" [font="myriad pro,myriad pro"][font="myriad pro,myriad pro"]is an example of a folder name for where to put the output files. It is best if you do not use an existing directory, and do not leave any spaces after "[font="courier std,courier std"][font="courier std,courier std"]-nos_o[font="myriad pro,myriad pro"][font="myriad pro,myriad pro"]".[/align]
A list of all command line switches for use in expanding the Nosso-compressed package is shown in Appendix A. If you are not using the U.S. English version of Reader, you must substitute the appropriate locale code for "[font="courier std,courier std"][font="courier std,courier std"]en_US[font="myriad pro,myriad pro"][font="myriad pro,myriad pro"]". A list of all locale codes is shown in Appendix D
A list of all command line switches for use in expanding the Nosso-compressed package is shown in Appendix A. If you are not using the U.S. English version of Reader, you must substitute the appropriate locale code for "[font="courier std,courier std"]
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.