Technical Note #5419 Version :Acrobat 5 - adobe.com · Extending The Adobe Acrobat Installer On The Windows Platform 5 Preface This document explains how to use several extensible

ADOBE SYSTEMS INCORPORATED

Corporate Headquarters

345 Park AvenueSan Jose, CA 95110-2704

(408) 536-6000http://partners.adobe.com

bbc

October, 2001

Technical Note #5419

Version :Acrobat 5.0

Extending The Adobe Acrobat Installer On The Windows Platform

Copyright 2001 Adobe Systems Incorporated. All rights reserved.

NOTICE: All information contained herein is the property of Adobe Systems Incorporated. No part of this publication (whether in hardcopy or electronic form) may be reproduced or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written consent of the Adobe Systems Incorporated.

PostScript is a registered trademark of Adobe Systems Incorporated. All instances of the name PostScript in the text are references to the PostScript language as defined by Adobe Systems Incorporated unless otherwise stated. The name PostScript also is used as a product trademark for Adobe Systems’ implementation of the PostScript language interpreter.

Except as otherwise stated, any reference to a “PostScript printing device,” “PostScript display device,” or similar item refers to a printing device, display device or item (respectively) that contains PostScript technology created or licensed by Adobe Systems Incorporated and not to devices or items that purport to be merely compatible with the PostScript language.

Adobe, the Adobe logo, Acrobat, the Acrobat logo, Acrobat Capture, Acrobat Catalog, Acrobat Reader, Acrobat Search, Distiller, PostScript, and the PostScript logo are trademarks of Adobe Systems Incorporated.

Apple, Macintosh, and Power Macintosh are trademarks of Apple Computer, Inc., registered in the United States and other countries. PowerPC is a registered trademark of IBM Corporation in the United States. ActiveX, Microsoft, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and other countries. UNIX is a registered trademark of The Open Group. All other trademarks are the property of their respective owners.

This publication and the information herein is furnished AS IS, is subject to change without notice, and should not be construed as a commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or inaccuracies, makes no warranty of any kind (express, implied, or statutory) with respect to this publication, and expressly disclaims any and all warranties of merchantability, fitness for particular purposes, and noninfringement of third party rights.


3

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

What Is In This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Who Should Read This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Other Useful Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Conventions Used In This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 1 Extending Acrobat Installers . . . . . . . . . . . . . . . . 7

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Configuration Files used by Adobe Installers . . . . . . . . . . . . . . . . . . . . . . . . . 8

Blind Copy Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

The Main Section of ABCPY.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

OEM Install Section of ABCPY.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Product Specific Portion of ABCPY.INI . . . . . . . . . . . . . . . . . . . . . . . . . 18

Group Actions within configuration files . . . . . . . . . . . . . . . . . . . . . . . . . 18

Program Shortcut Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Blind-copy Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Launch Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Launching the Acrobat Installer From Another Installer . . . . . . . . . . . . . . . . . . . 37

Using InstallShield’s DoInstall() Function . . . . . . . . . . . . . . . . . . . . . . . . 37

Using Win32 API functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Seamless Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Record a response file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Example SETUP.ISS file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Playback a response file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

SETUP.EXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 2 Example ABCPY.INI Files . . . . . . . . . . . . . . . . . . 45

Adding Acrobat Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

PDF Viewing Without Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Online Comments Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Contents

4


Custom Installing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Controlling Internet Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Silently Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64


5

Preface

This document explains how to use several extensible features in Adobe Acrobat (full product, including Fill In, Distiller, Reader, PCPI, etc.) installations. This document does not override the necessary legal agreements required for distributing Adobe software, and in no way does the possession of this document provide a substitute for the legal contract required to distribute Adobe software. This document does not grant any permissions or rights in regards to using the Adobe installer and its underlying technology provided by InstallShield®.

What Is In This Document

This document covers three types of installation strategies wherein you can install Adobe products without having to create separate installation programs for them:

●

“Blind Copy Installation” on page 8

●

“Seamless Installation” on page 38

●

“Silent Installation” on page 38

Who Should Read This Document

This document explains how to manually set values to install Acrobat in a variety of circumstances. You can also use Adobe’s Enetrprise Installation Tool (see Technical Note #5422) to go through a number of commonly-used procedures to customize your installation. Then, if you want to make further adjustments and customizations, you can use this document to do so.

Prerequisites

You should already be familiar with the concept of installing applications on your systems.

Other Useful Documentation

You may have various installation and deployment strategies in mind for your Adobe products. For information concerning these topics, please visit:

Preface

Conventions Used In This Document

6


http://partners.adobe.com/asn/developer/technotes/acrobatpdf.html , where you will find:

●

Technical Note #5422, Adobe Enterprise Installation Tool, which guides you step-by-step through customizing your Acrobat installation.

●

Technical Note #5420, Deploying Adobe Acrobat Installers Using SMS.

●

Technical Note #5421, Deploying Adobe Acrobat Installers Using Microsoft Windows Terminal Service.

Conventions Used In This Document

The Acrobat documentation uses certain text styles to identify various operators, keywords, terms, and objects

T

ABLE

P.1 Acrobat Document Conventions

Item Use and Examples

File names

C:\templates\Acrobat_docs

Code items within plain text; parameter names in reference documents

The

GetExtensionID

method returns an

ASAtom

object

Code examples set off from plain text

These are variable declarations:

AVMenu commandMenu,helpMenu;

Pseudocode

ACCB1 void ACCB2 ExeProc(void){

do something

}

Cross references to Web pages The Acrobat Solutions Network URL is:http://partners.adobe.com/asn/

Cross references to titles of other Acrobat documents

See the

Acrobat Core API Overview

.

Cross references within a document

See Section 3.1, “Using the SDK.”Test whether an

ASAtom

exists.

PostScript language operators, PDF operators, keywords, dictionary key names;user interface names

The

setpagedevice

operatorThe

File

menu

Document titles that are not cross-reference links, new terms, PostScript variables

Acrobat Core API Overviewfilename

deletefile

http://partners.adobe.com/asn/developer/technotes/acrobatpdf.html


7

1

Extending Acrobat Installers

Overview

The installation features discussed in this document include “blind copy” – a feature that allows third parties to add files to an existing installation, “seamless” installation, and “silent” installation. All of these features affect the user experience as well as provide a means to alter the installer provided by Adobe Systems, Inc. within certain limitations. All of these features are implemented via external configuration files, the details of which are described in detail later in this document.

Blind Copy Installation capability provides a mechanism for an Adobe OEM, VAR, or VPP customer to add files, registry entries, INI settings, and shortcut links to an Adobe product installation without needing to create their own installer. Using this capability you can modify the Adobe Acrobat installer to display default values within dialogs. You can also modify the display of dialogs, within certain limitations.

To perform a Blind Copy installation, you must have a file called

ABCPY.INI

in the same directory as the Adobe Installer setup file.

ABCPY.INI

is formatted similar to any Windows-based

.INI

file, with sections and key-value pairs within the sections. The section names are either pre-determined or based on installer defined components, and are described in further detail in this section of this document.

Seamless Installation

is a way for Adobe products to be installed “seamlessly” by other installers. Note that only some Adobe products (e.g. Acrobat Reader, Acrobat Distiller, etc.) support this type of installation. Seamless installation requires either the use of

LaunchApp

or the

DoInstall()

function (provided by InstallShield, the company that supplies the installation engine used by Adobe product installations on the Windows platforms) within another InstallShield® installer to launch the Acrobat installer. If you use

LaunchApp

, you can use any version of InstallShield. However, if you use

DoInstall()

, you must match the InstallShield version between the main controlling installer and the sub-launched installer. Adobe Acrobat 5.0 installers have been built using InstallShield® 5.5 with service pack 3. Seamless installation requires the use of particular keys within an external configuration file that is passed in as an argument to the Acrobat installer.

Silent Installation

allows you to modify Adobe product installers to provide default values to dialogs so that no user interface appears during the installation. This feature is supported via functionality provided by

InstallShield. If your goal is to install Acrobat "silently", use the SETUP.EXE command line options discussed on page 41.

N

OTE

:

These various features and capabilities cannot always be used together. Although you can combine the blind copy mechanism with a silent installation, you should not mix a seamless install with either blind copy or a silent install due to conflicts in the conceptual goals of these installation types. A seamless

http://installshield.com/

http://installshield.com/

Extending Acrobat Installers

Configuration Files used by Adobe Installers

1

8


installation is not silent by definition, and a seamless installation can incorporate all functionality provided by the blind copy mechanism within the main installer.

Configuration Files used by Adobe Installers

All configuration files used by Adobe installers are written as standard Windows

INI

files. These files use key value pairs within various logical sections for settings that define the behavior of the installer. Acrobat installers use three types of configuration files – internal, external, and dynamic. All of these files can have section names with the exact same name, which is why there is a need for determining the order of precedence. The order of precedence for settings within these files is dynamic, then external, and finally internal. The internal configuration file contains the defaults for the installer and is not discussed in this document. The main external configuration file is named

ABCPY.INI

, and is described in detail in the following section. The dynamic configuration file is a powerful new feature you can use to provide a seamless installation experience for the user. See the section on


for more details on the dynamic configuration file.

Blind Copy Installation

You can add files and registry names unknown to Adobe Acrobat with Blind Copy installaion. To do this, you must set up your

ABCPY.INI

file

The Main Section of ABCPY.INI

ABCPY.INI

requires a section named

[Main] that contains at least one key named Product. All other keys are ignored. The Product key does not require any specific value, but it must contain at least one character. The following is an example of the Main section.

;***************************************************************;Main Section;The (Product) key is a required key;***************************************************************[MAIN]Product=Adobe(R) Acrobat(R) 5.0

OEM Install Section of ABCPY.INI

You can use the section [OEM Install] to create most of the user experience during the Acrobat installation, determining which dialogs are displayed, the default

Extending The Adobe Acrobat Installer On The Windows Platform 9

Extending Acrobat InstallersBlind Copy Installation

1

destination directory, and the default "program group" (i.e. where Acrobat icons or shortcuts are created).

The key names defined in [OEM Install] are pre-defined, therefore additional keys will not be recognized. Key names starting with <Display…> control which dialogs appear; set them by using the words YES or NO.

The other keys need values that are valid strings for the object being set.

The following is an example of the list of the recognized keys and their values within the [OEM Install] section of the ABCPY.INI file. The values shown here are the default values in the normal Acrobat 5.0 installation. If you do not set any or all of these keys, Acrobat installs using the defaults within the normal installation.

NOTE: Do not use spaces in ABCPY.INI after the equal sign in any statements unless the spaces are part of the value!

;***************************************************************;OEM Installation Options;***************************************************************[OEM Install]SetupTitle=SetupCaptionBarTitle=DisplayWelcomeDlg=YESDisplayEULA=YESDisplayTypeOfInstallDlg=YESDisplaySelectDestDirDlg=NODisplayCustomDlg=YESDisplayUserInfoDlg=YESDisplayConfirmRegDlg=YESDisplayStartCopyDlg=YESDisplayFinalMessage=YESDisplayRebootDlg=YESDisplayMaintUIDlg=NODisplayBillboards=YESProgGroupName=DefaultDestDir=UserName=UserCompanyName=UserSerialNumber=DisplayBackGround=YESDisplayProgressBar=ProgressBarStart=ProgressBarEnd=CloseRunningApps=YESInstallModeSilent=NOUninstallCombineVersions=YESPDFOutputFolder=


1

10 Extending The Adobe Acrobat Installer On The Windows Platform

DisplayWelcomeDlg

This key controls whether the Welcome dialog appears. This dialog contains messages instructing the user to shut down other applications when installing, a legal reminder that the software is copyrighted, etc.

Valid entries are:

YES -> display this dialogNO -> do not display this dialog

DisplayEULA

This key controls whether the country selection (determines which EULA is displayed) and the end-user license agreement dialogs appear.

Valid entries are:

YES -> display these dialogsNO -> do not display these dialogs

DisplayTypeOfInstallDlg

This key controls whether the Setup Type dialog appears. This dialog allows the user to choose the type of installation and the default destination path. The setup types are Typical, Compact, and Custom. To modify the default destination path, the user must click the Browse button. This setting should always be the opposite of DisplaySelectDestDirDlg.

Valid entries are:


DisplaySelectDestDirDlg

This key controls whether the Select Destination Directory dialog appears. This dialog is used with Adobe products that do not have more than one component constituting the product (e.g. Acrobat Reader). This setting should always be the opposite of the DisplayTypeOfInstallDlg setting.

Valid entries are:




1

DisplayCustomDlg

This key controls whether the Select Components dialog appears, and should always be set to the same value as DisplayTypeOfInstallDlg

Valid entries are:


DisplayUserInfoDlg

This key controls whether the User Information dialog appears. This dialog gathers the user’s registration and serial number information. A valid Adobe product serial number must be entered in this dialog for the installation to continue. Do not use this dialog with freely licensed products such as Acrobat Reader.

Valid entries are:


NOTE: For products that require a serial number, either this dialog must be used to allow the user to enter the serial number, or the installation must be pre-serialized which must be done legally with Adobe’s knowledge. In addition, if this dialog is disabled, then the “UserSerialNumber” key must contain a valid serial number. Please see the UserSerialNumber key for more information.

DisplayConfirmRegDlg

This key controls whether the dialog requesting confirmation of the user registration information appears.

Valid entries are:


DisplayStartCopyDlg

This key controls whether the dialog displaying what choices the user has made (just prior to actually copying the files) appears.

Valid entries are:


DisplayFinalMessage

This key controls the appearance of the final "Thank you..." message.

Valid entries are:

YES -> display this messageNO -> do not display this message


1


DisplayRebootDlg

This key controls the appearance of a Reboot dialog or a Reboot message if the Acrobat installation detected the need for the user to reboot their machine due to an event in the installation (e.g. a file is locked and will be replaced at reboot).

Valid entries are:


ProgGroup

This key controls whether a program group is created in the Start Menu by this installation.

Valid entries are:

YES -> do the normal creation of program group in Start Menu.NO -> do not create the program group.

ProgGroupName

This key controls the program group name within the Start Menu used by this installation.

Valid entries are:

<program group name>-> Any valid program group name.

Examples of usage:

ProgGroupName=Adobe Acrobat 5.0ProgGroupName=Adobe\Acrobat 5.0 (for that layered effect)

DefaultDestDir

This key controls the default destination directory for the installation. For the Acrobat 5.0 installation this directory is the top-level directory for all of the products.

Valid entries are:

<directory name>-> Any valid directory or path name.$ProgramFiles-> This prefix means to prepend the <PROGRAM FILES> location to the specified directory path.



1

Example:

DefaultDestDir=C:\Adobe\Acrobat 5.0

This entry is using an explicit drive.

DefaultDestDir=Adobe\Acrobat 5.0

This entry will default to the user’s drive containing Windows (i.e. if Windows is loaded on drive C:, this is equivalent to the first example)

DefaultDestDir=$ProgramFiles\Adobe\Acrobat 5.0

This entry will use the system’s definition for where the “Program Files” directory is located and then append \Adobe\Acrobat 5.0 to that location.

UserName

This key specifies the user name associated with this installation. This name will be used if this installed product is registered with Adobe.

Valid entries are:

<user name> -> Any valid user name

Example:

UserName =John Doe

NOTE: : The Adobe Acrobat Reader installer does not support this key.

UserCompanyName

This key specifies the user’s company name associated with this installation. This field can be blank for user’s who will register this product as an individual.

Valid entries are:

<company name> -> Any valid company name

Example:

UserCompanyName=Adobe Acrobat 5.0


UserSerialNumber

This key specifies a valid Adobe Acrobat serial number. This serial number will be validated by the installer; therefore only valid Adobe Acrobat serial numbers should be enter here.

Valid entries are:

<serial number> -> A valid Adobe serial number specific to the product being installed.



1


SetupTitle

Use this key to set the title of the main installation window. The main purpose for this key is to coordinate installer windows when doing a “seamless” installation, so that the sub-launched installer has the same title as the main installer.

Valid entries are:

<title> -> Any text string that does not exceed the length allowed on a 640 x 480 screen

Example:

Adobe Acrobat 5.0

SetupCaptionBarTitle

Use this key to set the title bar caption. The main purpose for this key is to coordinate installer windows when doing a “seamless” installation, so that the sub-launched installer has the same title as the main installer.

Valid entries are:

<title caption> -> Any text string that does not exceed the length allowed.

DisplayBackGround

This key controls the setup background window display. When set to YES, this key causes the sublaunched installer to take over the background of the parent installer, and return to the parent background when finished. You normally use this key (set to NO) in the “seamless” installation so that the sub-launched installer does not replace the background (in case of differences between the main installer and the sub-launched installer).

Valid entries are:

YES -> display the backgroundNO -> do not display the background

DisplayProgressBar

This key controls the progress bar (i.e. the Status dialog) display. This key is normally used in the “seamless” installation so that the sub-launched installer picks up the “progress” where the main installer left off.

Valid entries are:

YES -> display the progress barNO -> do not display the progress bar

ProgressBarStart:

This key controls the progress bar start value. This value must be greater than 0 and less than the ProgressBarEnd value. This key is normally used in the “seamless” installation so that the sub-launched installer picks up the “progress” where the main installer left off.



1

Valid entries are:

<Number> -> the progress bar start value.

Example:

ProgressBarStart =75

ProgressBarEnd

This key controls the progress bar end value. This value must be greater than the ProgressBarStart value and less than 100. This key is normally used in the “seamless” installation so that the main installer picks up the “progress” where the sub-installer installer left off

Valid entries are:

<Number> -> The progress bar end value.

Example:

ProgressBarEnd =85

NOTE: : The keys used to support the “seamless” install are only supported by Adobe installers that are configured for being sub-launched.

CloseRunningApps

Use this key to tell the installer to close all running Acrobat applications before it does the install. It closes the Acrobat, Acrobat Reader and Acrobat Distiller applications.

Valid entries are:

YES -> close any running Acrobat applications (Acrobat, Reader, and Distiller)NO -> do not close any Acrobat applications (Acrobat, Reader, and Distiller)

InstallModeSilent

This key suppresses all pop-up environmental dialogs. For example, say a user has an older version of Acrobat installed on their systems and needs to uninstall it first. By turning this key on, you can supress dialogs requiring user input and uninstall the older Acrobat applications. This key defaults to YES.

Valid entries are:

YES -> suppress all environmental pop-up dialogsNO -> do not suppress environmental pop-up dialogs

NOTE: :If you want to run in silent mode, set this key to YES.

UninstallCombineVersions

This key controls the behavior of uninstalling from the control panel. By turning this key on, the Installer combines the uninstall for Acrobat 5.0 and Acrobat 4.x to one


1


uninstall. If the key is NO, when you uninstall Acrobat 4.x while 5.0 exists on the machine, Acrobat 5.0 will not function properly.

Valid entries are:YES -> combine uninstall keys into one keyNO -> do not combine uninstall keys.

PDFOutputFolder

This key controls the location for PDFOutput folder. PDFOutput folder is the port location for the distiller printer. By specifying the PDFOutput folder name, you can control where the PDFOutput port is.

Valid entries are: Any valid folder name with *.pdf. (e.g., C:\\Windows\My Documents\*.pdf)

OEM Setup Type

This section allows the user to specify:

Type=Typical;Type=Compact;Type=Custom;

For any Setup Type, turn off these dialogs:

DisplayTypeOfInstallDlg=NODisplaySelectDestDirDlg=YES –unless you specified the DefaultDestDir.DisplayCustomDlg=NO

Specify Setup Type in this if you want to customized the components that you want to turn on during the silent install, or if the setup type and component dialog are disabled. By specifying Type=Typical, you are using the default setting. If Type=Compact, you will get the Compact type of Acrobat default installation. If Type=Custom; then the user needs to set the desired components in the OEM Component Selection section.

OEM Component Selection

To use this section, you must set TYPE=Custom in SetupType.

To deselect a component, set CompXEnabled=NO.

Valid entries are (the table below lists the values of the entries):



1

IMPORTANT: Do not change these numbers.

[Components]NUMBER=18

Acrobat FilesComp1=Acrobat Program FilesComp1Enabled=YES

Comp2=Netscape Plug-in FileComp2Enabled=YES

Comp3=Search and Index filesComp3Enabled=YES

Comp4=Acrobat Online DocumentationComp4Enabled=YES

Comp5=InterTrust Plug-inComp5Enabled=YES

Comp6=PhotoShop 5.x PDF Plug-inComp6Enabled=YES

Acrobat Distiller FilesComp7=Acrobat Distiller FilesComp7Enabled=YES

Comp8=Acrobat Distiller PrinterComp8Enabled=YES

Comp9=Acrobat Distiller Help FilesComp9Enabled=YES

Adobe SVG Viewer 2.0Comp11=Adobe SVG Viewer 2.0Comp11Enabled=YES

AccessoriesComp12=Acrobat PDFMakerComp12Enabled=YES

Comp13=QuickTime 4.0Comp13Enabled=YES

Asian Language SupportComp14=Japanese Language FilesComp14Enabled=YES

Comp15=Korean Language FilesComp15Enabled=YES


1


Comp16=Traditional Chinese Language FilesComp16Enabled=YES

Comp17=Simplified Chinese Language FilesComp17Enabled=YES

Comp18=Distiller Asian Language PDF GenerationComp18Enabled=YES

Product Specific Portion of ABCPY.INI

To "trigger" file copying, registry entries and/or INI settings, you must have a section name in ABCPY.INI that matches values set in the Adobe Acrobat installations. These sections are only triggered if the user has selected the product for installation. Otherwise, the product specific portions of ABCPY.INI are not invoked. The Acrobat Installers have the following section names defined:

Acrobat Installer[AcrobatBlindCopy][DistillerBlindCopy][PDFWriterBlindCopy]

Acrobat Reader Installer[ReaderBlindCopy]

Acrobat Distiller Installer[DistillerBlindCopy]

Group Actions within configuration files

There are seven types of "blind-copy actions" that can be executed:

1. Requirement Action - A "requirement" may be performed

2. File Copy Action - Files and Folders can be copied.

3. Program ShortCut Action - Program items or shortcuts can be created.

4. Registry Entry Action - Registry entries can be created.

5. INI Entry Action - INI entries can be created.

6. File Removal – Delete any files underneath TargetDir, and CommonDir.

7. Shortcut Removal – Delete any Acrobat 5.0 shortcut ie: (Acrobat, Reader, and Distiller)

To perform an action on these blind-copy objects, you must make several entries within the product's blind-copy section. Below is a description of each of the group entries and their values.



1

NumberOfGroups

This key determines the number of blind-copy groups to process. This key must have a value of 1 or more.

Valid entries are:

<Number> -> The number of groups to process.

Example:

NumberOfGroups=1

For each group corresponding to the NumberOfGroups,you must create entries for the supported operating system, target destination location, source location and supported language.

Group<X>Platform

This key determines the Windows operating system this group <X> supports.

Valid entries are:

ALL -> means this group is targeted to all Windows operating system. Win95 -> means only Windows 95 operating systemWinNT5-> means only Windows 2000 operating systemsWinNT4-> means only Windows NT 4.0 operating systemWinNT -> means all Windows NT operating systemsWin9x -> means all Windows 9x (Win95,Win98 etc.) operating systems<x,x,x>-> means any comma delimited combination of the above entries.

Example:

Group1Platform=ALLGroup1Platform=WinNT4Group1Platform=Win9X,WinNT4

Group<X>Language

This key determines the Installer language this group <X> supports. This value represents the language the installer is running under, not the operating system language. The Adobe product installer must exist in this language.


1


Valid entries are:

ALL -> means this group supports all languagesENGLISH -> ENGLISHBASQUE-> BASQUECATALAN -> CATALANCHINESE -> CHINESECHINESE_T -> CHINESE TAIWANCHINESE_S -> CHINESE PRC CZECH -> CZECHDANISH -> DANISHDUTCH -> DUTCHFINNISH -> FINNISHFRENCH -> FRENCH ( STANDARD and CANADIAN )FRENCH_S -> FRENCH STANDARDFRENCH_C -> FRENCH CANADIANGERMAN -> GERMANGREEK -> GREEKHUNGARIAN -> HUNGARIANINDONESIAN -> INDONESIANITALIAN -> ITALIANJAPANESE -> JAPANESEKOREAN -> KOREANNORWEGIAN -> NORWEGIANPOLISH -> POLISHPORTUGUESE -> PORTUGUESE ( BRAZILIAN and STANDARD )PORTUGUESE_B-> PORTUGUESE BRAZILIANPORTUGUESE_S -> PORTUGUESE STANDARDRUSSIAN-> RUSSIANSLOVAK-> SLOVAKSLOVENIAN -> SLOVENIANSPANISH-> SPANISHSWEDISH -> SWEDISHTHAI -> THAITURKISH -> TURKISH<x,x,x>-> means any comma delimited combination of the valid entries.

Example:

Group1Language=ALLGroup1Language=NORWEGIANGroup1Language=ENGLISH,SPANISH,GERMAN,ITALIAN

Group<X>DestDir

This key contains the target destination directory name relative to the product's installation directory. This entry does not control where the product is installed, but rather where the “extra” files associated with this group will be installed.



1

Valid entries are:

<Path>-> any valid path relative to the product's installation directory. $Windows-> means target this file for the Windows directory$WindowsSystem-> means target this file for the Windows System directory

Example:

Group1DestDir=Plug-ins\OEM InstallGroup1DestDir=Adobe Acrobat 5.0Group1DestDir=$Windows

Group<X>Loc

This is the source location relative to the main installation directory. This is on the source media of the installation set where the (SETUP.EXE) program resides, not where the user chose to install Acrobat.

Valid entries are:

<Path>-> any valid path relative to the main installation directory.

Example:

Group1Loc=Plug-in\OEM FilesGroup1Loc=OEM\Scanners\WinNT

Group Requirement Actions

To perform a Requirement Action, you must define the following keys:

● Group<X>NumberOfRequirements=<Y>, where <X> is the group number and <Y> is the number of requirement actions to be performed for this group. At this time, the only supported requirement is running the Windows application REGEDIT.EXE, which can be used to add registry entries using a pre-defined registry file.

● Group<X>NumberOfRequirements

This key specifies the number of requirements to process.

Valid entries are:

<Number> -> the number of requirements

Example:

Group1NumberOfRequirements =1

Group<X>Requirement<Y>

This key specifies the type of requirement to perform.

Valid entries are:

REGEDIT-> Load a .REG file into the registry via the REGEDIT.EXE application.

Example:

Group1Requirement1= REGEDIT


1


Group<X>RegEditFile

This key specifies the .REG file name and location relative to the Acrobat installed path.

Valid entries are:

<Path>->.REG file name and installed location.

Example:

Group1RegEditFile = Extra\Extra32.REG

Group File Actions

To copy files and folders “blind copied” during the installation, you must define the following keys:

Group<X>NumberOfFiles

This key specifies the number of files to process for this group <X>.

Valid entries are:

<Number> -> the number of files to copy

Example:

Group1NumberOfFiles=15

Group<X>FileName<Y>

For each file to be copied, this key specifies the file name.

Valid entries are:

<FileName>-> File name to copy *.*-> Wildcard copy. All of the files in this location will be copied

NOTE: For wildcard copying of an entire tree (directories and subdirectories) the "...SubDir" type must be specified for the file expand type (See Group<X>File<Y>ExpandType.)

NOTE: There is no mechanism to rename files as they are copied.

Example:

Group1FileName1=Match.exeGroup1FileName1=Match Dir\Match.exeGroup1FileName1=Match Dir\*.*Group1FileName1=*.*

Group<X>File<Y>ExpandType

This key specifies the expand type to apply to each file to be copied .



1

Valid entries are:

Normal -> Updating existing same-named files regardless of date, time, or version information.Date -> Updates the files based on the file date and time. This option updates the file if the source file is newer than the target file.Version -> Updates the files based on the file version.SharedVersion -> Shared and locked file handling with (Version) attribute.SharedDate-> Shared and locked file handling with (Date) attribute. LockedVersion-> Locked file handling with (Version) attribute.LockedDate-> Locked file handling with (Date) attributes.VersionWithSubDir-> Copy all subdirectories using (Version) attributes.DateWithSubDir-> Copy all subdirectories using (Date) attributes.SameVersion-> Update the files even if the version of the source file is identical to the target fileSameDate-> Update the files even if the date, time of the source file is identical to the target fileSameSharedVersion-> Shared and locked file with (SameVersion) attributes.SameSharedDate-> Shared and locked file with (SameDate) attributes.SameLockedVersion-> Locked file with (SameVersion) attributes.SameLockedDate-> Locked file with (SameDate) attributes.SameVersionWithSubDir -> Copy all subdirectories with (SameVersion) attributes.SameDateWithSubDir-> Copy all subdirectories with (SameDate) attributes.

Example:

Group1File1ExpandType=NormalGroup1File1ExpandType=SharedVersionGroup1File1ExpandType=DateWithSubDir

Program Shortcut Actions

To create shortcut links other than those created by the Adobe installer, the following keys must be defined:

Group<X>NumberOfIcons

This key specifies the number of shortcuts to process.

Valid entries are:

<Number> -> the number of shortcut objects to process

Example:

Group1NumberOfIcons=4

Group<X>Icon<Y>Style

There are two types of shortcut actions supported.


1


Valid entries are:

STYLE1-> Used when the object referred to is an executable or an automatically launched file (i.e. if the file's extension automatically launches the correct executable).STYLE2-> Used when the object referred to requires a primary executable to launch the second file (i.e. NOTEPAD.EXE is often used for launching a ReadMe text file). When this style is applied the following two keys are required for defining the application and its location( Group<X>Icon<Y>App & Group<X>Icon<Y>AppLoc ).

Example:

Group1Icon1Style=STYLE1Group1Icon1Style=STYLE2

Group<X>Icon<Y>Folder

This key specifies the root folder in which to create the shortcut object.

Valid entries are:

$PRODUCT -> Adds the item to the Acrobat product folder. (In most cases this will be defined as Start Menu\Programs\Adobe Acrobat 5.0).$FOLDER_DESKTOP -> Adds the item to the Desktop folder.$FOLDER_STARTMENU -> Adds the item to the Start Menu folder.$FOLDER_STARTUP-> Adds the item to the Startup menu folder.$FOLDER_PROGRAMS-> Adds the item to the Start Menu\Programs folder.

Example:

Group1Icon1Folder=$PRODUCTGroup1Icon1Folder=$FOLDER_STARTMENUGroup1Icon1Folder=$FOLDER_PROGRAMS

Group<X>Icon<Y>SubFolder

This key specifies the subfolder for this shortcut object. If this key is left blank, then the shortcut is created in the root location defined by the (Group<X>Icon<Y>Folder) key.

Valid entries are:

<Subfolder> -> any valid sub-folder name.

Example:

Group1Icon1SubFolder=Adobe Acrobat 5.0Group1Icon1SubFolder=Adobe Acrobat 5.0\OEM Links

Group<X>Icon<Y>Exe

This key specifies the shortcut executable name.

Valid entries are:

<Filename> -> any valid executable file name.



1

Example:

Group1Icon1Exe=Match.exeGroup1Icon1Exe=MyApp.exe

Group<X>Icon<Y>ExeSubDir

This key specifies the sub-directory to the installed executable file. This path is relative to the location of the installed product directory. Valid entries are:

<Path>-> any valid path relative to the product's installation directory.

Example:

Group1Icon1ExeSubDir=OEM PluginsGroup1Icon1ExeSubDir=Plugins\My Directory

Group<X>Icon<Y>Description

This key specifies the shortcut description.

Valid entries are:

< Description >-> any valid shortcut text description

Example:

Group1Icon1Description=Match ReadMe

Group<X>Icon<Y>Number

This key specifies the icon index in the executable specified by this shortcut object. This value is typically 0 (zero)

Valid entries are:

< Number > -> Any number value.

Example:

Group1Icon1Number=0

Group<X>Icon<Y>App

This key is only used with STYLE2. It specifies the primary executable to launch the associated file (e.g. NOTEPAD.EXE is often used for launching a ReadMe text file)

Valid entries are:

< Filename> -> Any valid executable name.

Example:

Group1Icon1App=Notepad.exeGroup1Icon1App=Write.exe

Group<X>Icon<Y>AppLoc

This key is only used with STYLE2. It specifies the primary executable location.


1


Valid entries are:

<Path>-> Any valid path relative to the product's installation directory.

$PRODUCT -> The installed product directory$WINDOWS -> The windows directory$WINDOWSYSTEM -> The windows system directory

Example:

Group1Icon1AppLoc=OEM PluginsGroup1Icon1AppLoc=$PRODUCTGroup1Icon1AppLoc=$WINDOWSYSTEM

Registry Entry Actions

To create registry entries the following keys must be defined:

Group<X>NumberOfRegEntries

This key specifies the number of registry entries to process. In the related registry entry actions, <X> is the number of the group and <Y> is the specific number of which registry entry is being referred to.

Valid entries are:

<Number> -> the number of registry entries to process

Example:

Group1NumberOfRegEntries=4

Group<X>RegEntry<Y>Platform

This key specifies the target platform. The platform defined at the group level may be broader than the registry entry, so there is another means of differentiating settings based on the operating system of the end-user.

Valid entries are:

ALL -> means this registry entry is targeted for all Windows operating systems. Win95 -> means only Windows 95 operating systemWinNT4-> means only Windows NT 4.0 operating systemWinNT -> means all Windows NT operating systemsWin9x-> means all Windows 9x (Win95,Win98 etc.) operating systems<x,x,x>-> means any comma delimited combination of the valid entries.

Example:

Group1RegEntry1Platform=ALLGroup1RegEntry1Platform=WinNT4Group1RegEntry1Platform=Win9x,WinNT4



1

Group<X>RegEntry<Y>ParentKey

This key specifies the parent class where the registry entry will be created.Valid entries are:

HKEY_LOCAL_MACHINE -> HKEY_LOCAL_MACHINEHKEY_CLASSES_ROOT -> HKEY_CLASSES_ROOTHKEY_CURRENT_USER -> HKEY_CURRENT_USER

Example:

Group1RegEntry1ParentKey=HKEY_LOCAL_MACHINE

Group<X>RegEntry<Y>Key

This key specifies the subkey within the registry where the entry will be created

Valid entries are:

<Registry key>-> any valid registry key.

Example:

Group1RegEntry1Key=SOFTWARE\Adobe\Acrobat Distiller

Group<X>RegEntry<Y>ValueName

This key specifies the "named value" portion of the registry key. Leave this key blank to specify the default named value section.

Valid entries are:

<String> -> any registry Value Name

Example:

(The first example is deliberately left blank for "Default" name value)

Group1RegEntry1ValueName=Group1RegEntry1ValueName=BlindCopyEntry

Group<X>RegEntry<Y>ValueType

This key specifies the registry value type.

Valid entries are:

STRING -> this registry type is a string value.MULTIPLE_STRING -> Used when the string data has new lines embedded EXPANDABLE_STRING -> Used when the string data contains an expandable environment variable such as "%PATH%".NUMBER -> this registry type is a number value.

Example:

Group1RegEntry1ValueType=STRINGGroup1RegEntry1ValueType=NUMBER

Group<X>RegEntry<Y>ValueData

This key specifies the registry value data.


1


Valid entries are:

<Registry data>-> Any valid registry data$ProductDir-> This option means the Acrobat product directory. It can be used by itself or it can be the prefix for a valid path existing within the Acrobat product directory. (e.g. $ProductDir\Extra\Util.exe)$ProductApp -> This option means the full path and executable of the Acrobat product associated with this section.$Source-> This option means the source media directory. It can be used by itself or it can be the prefix for a valid path existing on the installation source media (e.g. $Source\ExtraTXT)$Windows -> This option means the window directory where the user's operating system is located$WindowsSystem -> This option means the Windows System directory (for NT systems this directory is named SYSTEM32)

Example:

Group1RegEntry1ValueData=$ProductAppGroup1RegEntry1ValueData=$ProductDir\Extra\Util.exe

Example Using Registry Entry Keys

You can see most of these keys used in this typical example:

Group1NumberOfRegEntries=1Group1RegEntry1Platform=ALLGroup1RegEntry1ParentKey=HKEY_CURRENT_USERGroup1RegEntry1Key=Software\Adobe\Adobe Acrobat\5.0\Collab\cServerSettingsGroup1RegEntry1ValueName=tDAVFDFGroup1RegEntry1ValueType=STRINGGroup1RegEntry1ValueData=http://intranet/Collab

INI Entry Action

You must define the following keys to create INI entries:

Group<X>NumberOfIniEntries

This key specifies the number of INI entries to process. For related INI entry actions, <X> is the number of the group and <Y> is the INI entry associated with the action.

Valid entries are:

<Number> -> the number of INI entries to process

Example:

Group1NumberOfIniEntries =4

Group<X>IniEntry<Y>Platform

This key specifies the target platform. The platform defined at the group level may be broader than the INI entry, so this is another means of differentiating settings based on the operating system of the end-user.



1

Valid entries are:

ALL -> means this INI entry is targeted to all Windows operating systems. Win95 -> means only Windows 95 operating systemWinNT4-> means only Windows NT 4.0 operating systemWinNT -> means all Windows NT operating systemsWin9x-> means all Windows 9x (Win95,Win98 etc.) operating systems<x,x,x>-> means any comma delimited combination of the valid entries.

Example:

Group1IniEntry1Platform=ALLGroup1IniEntry1Platform=WinNT4Group1IniEntry1Platform=Win95,WinNT4

Group<X>IniEntry<Y>FileLoc

This key specifies the INI data file directory location.

Valid entries are:

$ProductDir-> This option means the Acrobat product directory. It can be used by itself or it can be the prefix for a valid path existing within the Acrobat product directory. $Windows -> This option means the window directory where the user's operating system is located$WindowsSystem -> This option means the window System directory (for NT systems this directory is named SYSTEM32)

Example:

Group1IniEntry1FileLoc=$ProductDir\ExtraGroup1IniEntry1FileLoc=$Windows

Group<X>IniEntry<Y>FileName

This key specifies the name of the INI data file.

Valid entries are:

<Filename> -> any valid file name

Example:

Group1IniEntry1FileName=OEMDATA.INI

Group<X>IniEntry<Y>Section

This key specifies the section name in the INI data file.

Valid entries are:

<Section Name> -> any valid section name

Example:

Group1IniEntry1Section=DATA

Group<X>IniEntry<Y>Key

This key specifies the key name in the INI data file.


1


Valid entries are:

<Key Name> -> any valid key name

Example:

Group1IniEntry1Key=BlindCopyEntry

Group<X>IniEntry<Y>Value

This key specifies the value for the related key in the INI data file.

Valid entries are:

<String> -> Any valid value name

Example:

Group1IniEntry1Value=BlindCopyData

Example Using IniEntry Keys

You can see most of these keys in this typical example:

Group1IniEntry1FileLoc=$ProductDir\ExtraGroup1IniEntry1FileLoc=$WindowsGroup1IniEntry1Section=DATAGroup1IniEntry1Key=BlindCopyEntryGroup1IniEntry1Value=BlindCopyData

OEM Delete Files

This key specifies the number of files that you want to delete and the name of the files. The filename does not need to have the full path to the filename.

NUMBER=File1=File2=File3=

OEM Remove Shortcut

This key allows user to remove shortcut on their desktop and their start menu. By specifying yes to any of the component below, you will remove the shortcut of the component from both the desktop and the start menu.

ACROBAT=READER=DISTILLER=

Blind-copy Example

At this time, this is the current functionality of the blind-copy mechanism that can be used with Adobe Acrobat installations.The following entries can be used as examples for the correct syntax for performing the various blind-copy actions. These examples



1

should not be used literally, unless by some miracle, your installation has these exact same files and settings.

[ReaderBlindCopy]NumberOfGroups=5

Group1Platform=Win9x,WinNT4Group1Language=AllGroup1DestDir=OrgGroup1Loc=OrgGroup1NumberOfFiles=3Group1FileName1=Match.exeGroup1File1ExpandType=NormalGroup1FileName2=Match.hlpGroup1File2ExpandType=NormalGroup1FileName3=ReadMe.txtGroup1File3ExpandType=Normal

Group1NumberOfIcons=2Group1Icon1Style=STYLE1Group1Icon1Folder=$PRODUCTGroup1Icon1SubFolder=OEM InstallGroup1Icon1Exe=Match.exeGroup1Icon1ExeSubDir=Viewer PluginsGroup1Icon1Description=Match Shortcut link Style 1Group1Icon1Number=0

Group1Icon2Style=STYLE2Group1Icon2Folder=$FOLDER_DESKTOPGroup1Icon2SubFolder=Group1Icon2Exe=Match.exeGroup1Icon2ExeSubDir=Viewer PluginsGroup1Icon2Description=Match Shortcut line Style 2Group1Icon2Number=0Group1Icon2App=Write.exeGroup1Icon2AppLoc=$Windows

Group1NumberOfRegEntries=1Group1RegEntry1Platform=ALLGroup1RegEntry1ParentKey=HKEY_LOCAL_MACHINEGroup1RegEntry1Key=Software\Adobe Acrobat\BlindCopyGroup1RegEntry1ValueName=BlindCopyValueNameGroup1RegEntry1ValueType=STRINGGroup1RegEntry1ValueData=BlindCopyValueData

Group1NumberOfIniEntries=1Group1IniEntry1Platform=AllGroup1IniEntry1FileLoc=$WindowsGroup1IniEntry1FileName=OEMDATA.iniGroup1IniEntry1Section=BlindCopyGroup1IniEntry1Key=BlindCopyEntry


1


Group1IniEntry1Value=BlindCopyData

Group2Platform=Win9xGroup2Language=AllGroup2DestDir=Group2Loc=ExtraGroup2NumberOfRequirements=0Group2NumberOfFiles=1Group2FileName1=*.*Group2File1ExpandType=DateWithSubDirGroup2NumberOfIcons=0Group2NumberOfRegEntries=0Group2NumberOfIniEntries=0

Group3Platform=Win9x,WinNT4Group3Language=AllGroup3DestDir=Group3Loc=Group3Name=Group3NumberOfRequirements=1Group3Requirement1=REGEDITGroup3RegEditFile=Extra\Extra.REGGroup3NumberOfFiles=0Group3NumberOfIcons=0Group3NumberOfRegEntries=0Group3NumberOfIniEntries=0

Group4Platform=Win9xGroup4Language=ENGLISH,FRENCH,GERMANGroup4DestDir=Group4Loc=ExtraGroup4Name=Group4NumberOfRequirements=0Group4NumberOfFiles=1Group4FileName1=Extra\Extra9x.REGGroup4NumberOfIcons=0Group4NumberOfRegEntries=0Group4NumberOfIniEntries=0

Group5Platform=WinNTGroup5Language=ENGLISH,FRENCH,GERMANGroup5DestDir=Group5Loc=Group5Name=Group5NumberOfRequirements=1Group5Requirement1=REGEDITGroup5RegEditFile=ExtraNT\Extra.REGGroup5NumberOfFiles=0Group5NumberOfIcons=0Group5NumberOfRegEntries=0Group5NumberOfIniEntries=0



1

Launch Section

The [Launches] section of ABCPY.INI provides the capability of launching either another InstallShield script or another Windows application from the Acrobat installer. This section (as similar to [OEM Install]) is not dependent on any product or component being selected by the user.

The keys that are necessary for this mechanism to work are:

NumberOfLaunchesLaunch<X>PlatformLaunch<X>LanguageLaunch<X>TypeLaunch<X>ProgramLaunch<X>CmdLineLaunch<X>ChangeDirLaunch<X>Wait

NumberOfLaunches

The NumberOfLaunches key is defined only once and sets the value for how many applications are to be launched via the blind copy mechanism. This value must be one or larger.

Launch<X>Platform

This key determines the Windows operating system this launch action <X> supports.

Valid entries are:

ALL -> means this group is targeted to all Windows operating system. Win95 -> means only Windows 95 operating systemWinNT4-> means only Windows NT 4.0 operating systemWinNT -> means all Windows NT operating systemsWin9x-> means all Windows 9x (Win95,Win98 etc.) operating systems<x,x,x>-> means any comma delimited combination of the above entries.

Example:

Launch1Platform=ALLLaunch1Platform=WinNT4Launch1Platform=Win95,WinNT4

Launch <X>Language

This key determines the Installer language this launch action <X> supports. This value represents the language the installer is running under and not the operating system language.


1


Valid entries are:

ALL -> means this launch action supports all languagesENGLISH -> ENGLISHBASQUE-> BASQUECATALAN -> CATALANCHINESE -> CHINESECHINESE_T -> CHINESE TAIWANCHINESE_S -> CHINESE PRC CZECH -> CZECHDANISH -> DANISHDUTCH -> DUTCHFINNISH -> FINNISHFRENCH -> FRENCH ( STANDARD and CANADIAN )FRENCH_S -> FRENCH STANDARDFRENCH_C -> FRENCH CANADIANGERMAN -> GERMANGREEK -> GREEKHUNGARIAN -> HUNGARIANINDONESIAN -> INDONESIANITALIAN -> ITALIANJAPANESE -> JAPANESEKOREAN -> KOREANNORWEGIAN -> NORWEGIANPOLISH -> POLISHPORTUGUESE -> PORTUGUESE ( BRAZILIAN and STANDARD )PORTUGUESE_B-> PORTUGUESE BRAZILIANPORTUGUESE_S -> PORTUGUESE STANDARDRUSSIAN-> RUSSIANSLOVAK-> SLOVAKSLOVENIAN -> SLOVENIANSPANISH-> SPANISHSWEDISH -> SWEDISHTHAI -> THAITURKISH -> TURKISH<x,x,x>-> means any comma delimited combination of the above entries.

Example:

Group1Language=ALLGroup1Language=NORWEGIANGroup1Language=ENGLISH,SPANISH,GERMAN,ITALIAN

Launch<X>Type

This key determines whether the “application” to be launched is an InstallShield script (launched via the DoInstall () function), or an executable (launched via the LaunchAppAndWait () function).

Valid entries are:

INS -> means this launch action is an InstallShield script. The setup called by this option must have been created with the same major version, minor version and build number of InstallShield as the



1

setup that is launching it. Attempts to use DoInstall to launch a setup created with any other version of InstallShield may not be successful.EXE -> means this launch action is an application (EXE) file.

Example:Launch1Type=INSLaunch1Type=EXE

Launch<X>Program

This key defines the launched application file name. It must point to a valid file name. Do not use the full path here, just the file name.

Valid entries are:

<Filename> -> any valid executable name.

Example:

Group1Icon1App=QT.EXEGroup1Icon1App=Install.exe

Launch<X>CmdLine

This key defines the command line parameters to be used when launching the application.

Valid entries are:

<Filename> -> any valid executable name.

Example:

Launch1CmdLine=-E Launch1CmdLine=-DINSTALL

Launch<X>ChangeDir

This key specifies the full path of the directory where the launched program resides. This is used to perform a ChangeDirectory command to insure that the program can be launched.

Valid entries are:

< path >-> Any valid path relative to the installer source location.$ProductDir-> This option means the Acrobat product directory. It can be used by itself or it can be the prefix for a valid path existing within the Acrobat product directory (e.g. $ProductDir\Extra).$Source-> This option means the source media directory. It can be used by itself or it can be the prefix for a valid path existing on the installation source media (e.g. $Source\ExtraTXT)$Windows -> This option means the window directory where the user's operating system is located$WindowsSystem -> This option means the window System directory (for NT systems this directory is named SYSTEM32)


1


Example:

Launch1ChangeDir=OEM InstallerLaunch1ChangeDir=$Source\MatchDirLaunch1ChangeDir=$Windows

Launch<X>Wait

This key defines whether the installer script should wait for the launched program to quit before continuing.

Valid entries are:

YES -> means wait for the launched program to quitNO -> means do not wait for the launched program to quit

Example:

Launch1Wait=YESLaunch1Wait=NO

Launch Example

The following is an example for using the [Launch] section.

[Launches]NumberOfLaunches=3Launch1Platform=AllLaunch1Language=AllLaunch1Type=INSLaunch1Program=Setup2.insLaunch1CmdLine=Launch1ChangeDir=$Source\Disk1Launch1Wait=YES

Launch2Platform=Win9xLaunch1Language=ENGLISHLaunch2Type=EXELaunch2Program=QTEng.exeLaunch2CmdLine=Launch2ChangeDir=$SourceLaunch2Wait=YES

Launch3Platform=WinNT,Win95Launch1Language=FRENCHLaunch3Type=EXELaunch3Program=QT32.exeLaunch3CmdLine=Launch3ChangeDir=$Source\QT32DirLaunch3Wait=YES


Extending Acrobat InstallersLaunching the Acrobat Installer From Another Installer

1

Launching the Acrobat Installer From Another Installer

The Adobe Acrobat 5.0 installers, as well as several other Adobe products, can be launched from another installer in more than one way. Adobe Acrobat 5.0 installation can be launched as a separate process or it can visually integrated into another InstallShield® installer. If you choose to integrate the Acrobat installer into another, the main installer and the Acrobat installer must use the exact same installer engine.

Using InstallShield’s DoInstall() Function

As of this writing, the Adobe Acrobat 5.0 installer for Windows platforms uses InstallShield® 5.5 with service pack 3, and so as long as your product’s installer is using this same version of InstallShield®, you can launch the Acrobat installation using InstallShield’s DoInstall() function within your own InstallShield script. You should use the DoInstall() function with the appropriate command line option (e.g. the WAIT/NOWAIT state), as well as specifying an external configuration file if you are attempting to create a seamless installer. If you need more information on DoInstall() or other InstallShield® functionality, visit InstallShield’s web site (http://www.installshield.com). The site has a wealth of information, including many articles that can lend information on how to properly use InstallShield.

Using Win32 API functions

If you do not use InstallShield®, you can also launch the installer using the WinExec() or CreateProcess() Windows APIs. If you wish to have your application wait until Adobe Acrobat installation is done, you must have access to the SETUP.EXE executable. If you only have access to a single file, self-extracting installer or Acrobat Reader, you will not be able to have the calling application wait for the Adobe installer to finish. If your application must wait and you only have access to the single file, self-extracting installer, you will need to run that installer and while it is running, copy the “real” installer files to another location. The installer files are copied to a temporary location by the self-extracting installer. Then with the uncompressed installer files, you can use the command line with –SMS, which will force InstallShield’s SETUP.EXE to remain active (normally it is only a bootstrap program) until the main installer quits. (You can get detailed explanations of this from the InstallShield® web site.)

When your application launches the Adobe installer, it can get the PROCESS_INFORMATION passed back from the CreateProcess() function. It is more difficult to use WinExec(), because you will need to determine the main window used by the Adobe installer using GetModuleHandle(), so that you can determine when SETUP.EXE has finished.

You can use an external configuration file as well as ABCPY.INI to configure the Acrobat installer launched externally, but this method does not provide as many options as using DoInstall() from another InstallShield® installer.

http://www.installshield.com

Extending Acrobat InstallersSeamless Installation

1



Seamless installation provides a means to integrate some Adobe installers directly into another installer and have the visual effect of only one installer. All Adobe Acrobat 5.0 installers support this feature. To launch the Acrobat installer properly as a seamless installation, the main installer should dynamically build an external configuration file. The main installer can ask the user where Acrobat should be installed and store that value in the dynamic file. This dynamic configuration file is also used to store the exit code of the sub-launched installer.

To define the dynamic configuration file, the main installer should write out the appropriate values into this file, and then pass a command line argument to the Acrobat installer when it is launched via the DoInstall() function. The command line is entered as the second parameter to this function. The syntax that the Acrobat installer expects for the command line follows.

ConfigFile <filename>

where <filename> is the full path to the dynamic configuration file.

NOTE: There needs to be a space between ConfigFile and the file name. If the <filename> contains a long path, the file name should be double-quoted as per Windows conventions.

When the seamless Acrobat installer quits, it will write out an entry to the [Seamless Install] key using the ExitCode key. If the Acrobat installer aborted, the value is –1. Otherwise, the value will be 0 (zero). In either case, the Acrobat installation has completed. If the main installer will be using this value (e.g. to put up some helpful instructions on how to launch the Acrobat installer manually), the main installer must wait until the Acrobat installer has completed before checking for this value.

Silent Installation

As an OEM or VAR, you may wish to install Acrobat silently (i.e. with absolutely no user interface). This is also handy for system administrators.

Adobe Acrobat 5.0 installers uses the InstallShield® 5.5 installation engine which provides a mechanism for "recording" a response file and "playing back" this file to produce the same installation.

NOTE: Changing all of the <Display…> keys to NO in the [OEM Install] section of the external configuration file, ABCPY.INI will NOT result in a silent installation! You must use the command line options supported by InstallShield to launch an Adobe installer silently.


Extending Acrobat InstallersSilent Installation

1

Record a response file

To record an installation, run the Acrobat installation (SETUP.EXE) on a 32-bit Windows operating system and use the command line option -r. On Windows 95, Windows 98 or Windows NT 4.0, use the Start Menu->Run menu item type, or browse to the directory where the Acrobat installation is located and select SETUP.EXE. Before running this program, add a space and -r similar to the following example.

E:\Acrobat\SETUP.EXE -r

You will be installing Acrobat and recording a response file. This response file is named SETUP.ISS and is created in your Windows directory. Every selection you make will be recorded.

IMPORTANT: When you "record" the installation, DO NOT use the BACK button in dialogs, because this confuses the installation script, and you will not get the installation you intended.

When you have finished the installation, you will need to copy SETUP.ISS to the same directory containing the Acrobat installation files (i.e. the same location as SETUP.EXE).

Depending on the Acrobat installation you are performing and which dialogs are displayed, there are many variations for the contents of SETUP.ISS and which specific keys will be written in SETUP.ISS. For instance, if you use ABCPY.INI to modify which dialogs are displayed, the contents of SETUP.ISS reflects only those dialogs that were displayed. The general rule for silent installation is that for every dialog in the installation, there are settings that are listed in the SETUP.ISS file.

The following uses the Adobe Acrobat Viewer installer as an example.


1


Example SETUP.ISS file

[InstallShield Silent]Version=v5.00.000File=Response File

[DlgOrder]Dlg0=SdWelcome-0Count=8Dlg1=SdAskOptionsList-0Dlg2=SdLicense-0Dlg3=SdSetupType-0Dlg4=CUSTOM_USERINFO-0Dlg5=SdConfirmRegistration-0Dlg6=SdStartCopy-0Dlg7=SdFinishReboot-0

[SdWelcome-0]Result=1

[SdAskOptionsList-0]Component-type=stringComponent-count=1Component-0=United StatesResult=1

[SdLicense-0]Result=1

[SdSetupType-0]szDir=C:\Program Files\Adobe\Acrobat 5.0Result=301

[CUSTOM_USERINFO-0]Business=-1001Individual=-1002Salutation=Mr.FirstName=JohnMiddleInitial=MLastName=DoeCompany=John Doe CompanySerialNumber=XXXXXXXXXXXXXXXXXX (This is just a placeholder – an authorized Adobe product serial number must be entered or the installation will fail!)

[SdConfirmRegistration-0]Result=1

[SdStartCopy-0]Result=1



1

[Application]Name=Acrobat ViewerVersion=5.0Company=Adobe

[SdFinishReboot-0]Result=1BootOption=0

Playback a response file

To play back this file, again run SETUP.EXE from the command line and use the option -s similar to the following example.

E:\Acrobat\SETUP.EXE -s

This installation will run silently with no user interface and produce an installation similar to the one created during the "record" installation (unless the response file was altered after the recorded installation).

SETUP.EXE

Usage Examples for Silent Installation:

setup -s

Launches InstallShield Silent and tries to load SETUP.INS and SETUP.ISS (see “Silently Installing” on page 64 for more details about SETUP.ISS fles) from the directory containing SETUP.EXE. The log file SETUP.LOG is created in the same directory. The command

setup -s -f1c:\mydir\mydir.iss

launches InstallShield Silent, tries to load SETUP.INS from the same directory, and uses MYDIR.ISS (from the C:\MYDIR directory) as the response file. This example also creates the log file SETUP.LOG in the same directory as that of the response file (C:\MYDIR).

NOTE: If you specify an alternate compiled script using the -f switch and you place -f1 before -f in the command line, Setup will ignore the -f1 switch and will create the response file (the .ISS file) in the Windows directory.

The command

setup -s -f1c:\mydir\mydir.iss -fc:\mydir\mydir.ins {Incorrect}

does not launch InstallShield Silent because the -f1 switch is used before the -f switch, and -f1 is therefore ignored. No log file is generated. However, the -fC:\MYDIR\MYDIR.INS portion of the command line is executed.

The command

setup -s -fc:\mydir\mydir.ins -f1c:\mydir\mydir.iss


1


launches InstallShield Silent , tries to load MYDIR.INS from the C:\MYDIR directory, uses MYDIR.ISS from the C:\MYDIR directory, and generates log file SETUP.LOG in the C:\MYDIR directory.

The command

setup -s -fc:\mydir\mydir.ins -f1c:\mydir\mydir.iss -f2c:\mydir\mydir.log

launches InstallShield Silent, tries to load MYDIR.INS from the C:\MYDIR directory, uses MYDIR.ISS from the C:\MYDIR directory, and generates log file MYDIR.LOG in the C:\MYDIR directory.


2 Example ABCPY.INI Files

This chapter provides a number of example ABCPY.INI files that aid in various tasks involved in installing Adobe Acrobat products:

● Adding Acrobat Files

● PDF Viewing Without Creation

● Online Comments Server

● Custom Installing

● Controlling Internet Access

● Silently Installing

Adding Acrobat Files

This section provides an example for adding files under the Acrobat target directory. This ABCPY.INI file provides the capability to add files:

● to the Help folder

● to the Resource folder

● to the Legal folder

● to the Acrobat\Plug_ins folder

● to the Distiller folder

You add these files in the Acrobat Blind Copy section. The default destination is the same location in the user directory where the Acrobat 5.0 folder is installed.

Example ABCPY.INI FilesAdding Acrobat Files

2


The example ABCPY.INI file:

;***************************************************************;Adobe Installer External Configuration File: Abcpy.ini;***************************************************************


;***************************************************************;OEM Installation Options;***************************************************************[OEM Install]SetupTitle=SetupCaptionBarTitle=DisplayWelcomeDlg=YESDisplayEULA=YESDisplayTypeOfInstallDlg=YESDisplaySelectDestDirDlg=NODisplayCustomDlg=YESDisplayUserInfoDlg=YESDisplayConfirmRegDlg=YESDisplayStartCopyDlg=YESDisplayFinishDlg=YESDisplayFinalMessage=YESDisplayRebootDlg=YESDisplayMaintUIDlg=NODisplayBillboards=YESProgGroupName=DefaultDestDir=UserName=UserCompanyName=UserSerialNumber=DisplayBackGround=YESDisplayProgressBar=ProgressBarStart=ProgressBarEnd=CloseRunningApps=YESInstallModeSilent=NOUninstallCombineVersions=YESPDFOutputFolder=



2

;***************************************************************;OEM Setup Type - Set "TYPE=Typical", "TYPE=Compact",;"TYPE=Custom" or leave blank. If used, set "DisplayTypeOfInstallDlg=NO" in OEM Install section;***************************************************************

[SetupType]TYPE=

;***************************************************************; OEM Component Selection Installation Options; (To use this section, must set "TYPE=Custom" in SetupType); (To deselect a component,set"CompXEnabled=NO"); (DO NOT CHANGE NUMBERS);***************************************************************


;---Acrobat FilesComp1=Acrobat Program FilesComp1Enabled=YES

Comp2=Netscape Plug-in FileComp2Enabled=YES

Comp3=Search and Index filesComp3Enabled=YES

Comp4=Acrobat Online DocumentationComp4Enabled=YES

Comp5=InterTrust Plug-inComp5Enabled=YES

;---Acrobat Distiller FilesComp6=Acrobat Distiller FilesComp6Enabled=YES

Comp7=Acrobat Distiller PrinterComp7Enabled=YES


;---Acrobat PDFWriterComp9=Acrobat PDFWriter FilesComp9Enabled=YES

;---Adobe SVG Viewer 2.0Comp10=Adobe SVG Viewer 2.0


2


Comp10Enabled=YES

;---AccessoriesComp11=Acrobat PDFMakerComp11Enabled=YES

Comp12=PhotoShop 5.x PDF Plug-inComp12Enabled=YES

Comp13=QuickTime 4.0Comp13Enabled=YES

;---Asian Language SupportComp14=Japanese Language FilesComp14Enabled=YES

Comp15=Korean Language FilesComp15Enabled=YES

Comp16=Traditional Chinese Language FilesComp16Enabled=YES


Comp18=Distiller Asian Language PDF GenerationComp18Enabled=YES

;***************************************************************; OEM Delete Files - add files to remove from initial install,; fill in total number;***************************************************************[OEM Delete Files]NUMBER=File1=File2=File3=

;***************************************************************; OEM Remove Shortcut;***************************************************************

[OEM Remove Shortcut]ACROBAT=READER=DISTILLER=



2

;***************************************************************;Acrobat BlindCopy;***************************************************************

[AcrobatBlindCopy]NumberOfGroups=5

Group1Platform=AllGroup1Language=All

;--Requirement ObjectsGroup1NumberOfRequirements=Group1Requirement1=Group1RegEditFile=

;--File ObjectsGroup1NumberOfFiles=2Group1DestDir=HelpGroup1Loc=Help

Group1FileName1=foo1.txtGroup1File1ExpandType=Normal


Group2Platform=AllGroup2Language=All;--File ObjectsGroup2NumberOfFiles=2Group2DestDir=Acrobat\Plug_insGroup2Loc=Plug_ins



Group3Platform=AllGroup3Language=All;--File ObjectsGroup3NumberOfFiles=2Group3DestDir=LegalGroup3Loc=Legal




2


Group4Platform=AllGroup4Language=All;--File ObjectsGroup4NumberOfFiles=2Group4DestDir=Resource\TestGroup4Loc=Resource





;--File ObjectsGroup5NumberOfFiles=2Group5DestDir=DistillrGroup5Loc=Distillr



;--Shortcut ObjectsGroup1NumberOfIcons=Group1Icon1Style=Group1Icon1Folder=Group1Icon1SubFolder=Group1Icon1Exe=Group1Icon1ExeSubDir=Group1Icon1Description=Group1Icon1Number=

Group1Icon2Style=Group1Icon2Folder=Group1Icon2SubFolder=Group1Icon2Exe=Group1Icon2ExeSubDir=Group1Icon2Description=Group1Icon2Number=Group1Icon2App=Group1Icon2AppLoc=



2

;--Registry ObjectsGroup1NumberOfRegEntries=Group1RegEntry1Platform=Group1RegEntry1ParentKey=Group1RegEntry1Key=Group1RegEntry1ValueName=Group1RegEntry1ValueType=Group1RegEntry1ValueData=

Group1RegEntry2Platform=AGroup1RegEntry2ParentKey=Group1RegEntry2Key=Group1RegEntry2ValueName=Group1RegEntry2ValueType=Group1RegEntry2ValueData=

;--INI ObjectsGroup1NumberOfIniEntries=Group1IniEntry1Platform=Group1IniEntry1FileLoc=Group1IniEntry1FileName=Group1IniEntry1Section=Group1IniEntry1Key=Group1IniEntry1Value=

;--Launch Objects[Launches]NumberOfLaunches=Launch1Platform=Launch1Language=Launch1Type=Launch1Program=Launch1CmdLine=Launch1ChangeDir=Launch1Wait=

[Startup]AppName=Adobe(R) Acrobat(R) 5.0FreeDiskSpace=2589[ISUPDATE]UpdateURL=http://

Example ABCPY.INI FilesPDF Viewing Without Creation

2


PDF Viewing Without Creation

This section provides an example ABCPY.INI files that allows you to:

● Compact Install by setting the SetupType to have TYPE=Compact

● Remove a set of plug-ins that would normally be installed. :– acccheck– catalog– scrubber– exportps– touchup

Set the registry entry so that AcroForms authoring is turned off. Do this by updating HKEY_LOCAL_MACHINE\Software\Adobe\Adobe Acrobat\5.0\Installer to use the default string with the value "BTools".


***************************************************************;Adobe Installer External Configuration File: Abcpy.ini;***************************************************************

;***************************************************************;Main Section;The (Product) key is a required key;***************************************************************

[MAIN]Product=Adobe(R) Acrobat(R) 5.0

;***************************************************************;OEM Installation Options;***************************************************************

[OEM Install]SetupTitle=SetupCaptionBarTitle=DisplayWelcomeDlg=YESDisplayEULA=YESDisplayTypeOfInstallDlg=NODisplaySelectDestDirDlg=YESDisplayCustomDlg=NODisplayUserInfoDlg=YESDisplayConfirmRegDlg=YESDisplayStartCopyDlg=YESDisplayFinishDlg=YESDisplayFinalMessage=YESDisplayRebootDlg=NODisplayMaintUIDlg=NODisplayBillboards=YES



2

ProgGroupName=Adobe\Acrobat 5.0DefaultDestDir=UserName=UserCompanyName=UserSerialNumber=DisplayBackGround=YESDisplayProgressBar=ProgressBarStart=ProgressBarEnd=CloseRunningApps=YESInstallModeSilent=NO

;***************************************************************;OEM Setup Type - Set "TYPE=Typical", "TYPE=Compact",;"TYPE=Custom" or leave blank. If used, set ;"DisplayTypeOfInstallDlg=NO" in OEM Install section;***************************************************************

[SetupType]TYPE=Compact



;---Acrobat FilesComp1=Acrobat Program FilesComp1Enabled=YESComp1Parent=Acrobat Files

Comp2=Netscape Plug-in FileComp2Enabled=YESComp2Parent=Acrobat Files

Comp3=Search and Index filesComp3Enabled=YESComp3Parent=Acrobat Files

Comp4=Acrobat Online DocumentationComp4Enabled=YESComp4Parent=Acrobat Files

Comp5=InterTrust Plug-inComp5Enabled=NOComp5Parent=Acrobat Files


2


;---Acrobat Distiller FilesComp6=Acrobat Distiller FilesComp6Enabled=NOComp6Parent=Acrobat Distiller Files

Comp7=Acrobat Distiller PrinterComp7Enabled=NOComp7Parent=Acrobat Distiller Files

Comp8=Acrobat Distiller Help FilesComp8Enabled=NOComp8Parent=Acrobat Distiller Files

;---Acrobat PDFWriterComp9=Acrobat PDFWriter FilesComp9Enabled=NOComp9Parent=

;---Adobe SVG Viewer 2.0Comp10=Adobe SVG Viewer 2.0Comp10Enabled=YESComp10Parent=

;---AccessoriesComp11=Acrobat PDFMakerComp11Enabled=NOComp11Parent=Accessories

Comp12=PhotoShop 5.x PDF Plug-inComp12Enabled=NOComp12Parent=Accessories

Comp13=QuickTime 4.0Comp13Enabled=NOComp13Parent=

;---Asian Language SupportComp14=Japanese Language FilesComp14Enabled=YESComp14Parent=Far East Language Support

Comp15=Korean Language FilesComp15Enabled=YESComp15Parent=Far East Language Support

Comp16=Traditional Chinese Language FilesComp16Enabled=YESComp16Parent=Far East Language Support




2

Comp17Parent=Far East Language Support

Comp18=Distiller Asian Language PDF GenerationComp18Enabled=NOComp18Parent=Far East Language Support

;***************************************************************;OEM Delete Files - add files to remove from initial install, ;fill in total number;***************************************************************

[OEM Delete Files]NUMBER=5 File1=acccheck.apiFile2=catalog.apiFile3=exportps.apiFile4=touchup.apiFile5=scrubber.api

;***************************************************************;OEM Remove Shortcut;***************************************************************


;***************************************************************;Program Files BlindCopy;***************************************************************[AcrobatBlindCopy]NumberOfGroups=1



;--File ObjectsGroup1NumberOfFiles=Group1DestDir=Group1Loc=

Group1FileName1=Group1File1ExpandType=

Group1FileName2=


2


Group1File2ExpandType=

;--Shortcut ObjectsGroup1NumberOfIcons=Group1Icon1Style=Group1Icon1Folder=Group1Icon1SubFolder=Group1Icon1Exe=Group1Icon1ExeSubDir=Group1Icon1Description=Group1Icon1Number=


;--Registry ObjectsGroup1NumberOfRegEntries=2Group1RegEntry1Platform=ALLGroup1RegEntry1ParentKey=HKEY_CURRENT_USERGroup1RegEntry1Key=Software\Adobe\Adobe Acrobat\5.0\InstallerGroup1RegEntry1ValueName=Group1RegEntry1ValueType=STRINGGroup1RegEntry1ValueData=BTools

Group1RegEntry2Platform=ALLGroup1RegEntry2ParentKey=HKEY_LOCAL_MACHINEGroup1RegEntry2Key=Software\Adobe\Adobe Acrobat\5.0\InstallerGroup1RegEntry2ValueName=Group1RegEntry2ValueType=STRINGGroup1RegEntry2ValueData=BTools


;--Launch Objects[Launches]NumberOfLaunches=Launch1Platform=


Example ABCPY.INI FilesOnline Comments Server

2

Launch1Language=Launch1Type=Launch1Program=Launch1CmdLine=Launch1ChangeDir=

Launch1Wait=

Online Comments Server

This ABCPY.INI file provides:

1. Company name

Set the UserCompanyName=John Doe Company

2. Serial number

Set the UserSerialNumber=XXXXXXXXXXXXXXXXXX

(This is just a placeholder – an authorized Adobe product serial number must be entered or the installation will fail!).

3. Set the Online Comments server to http://YourCompany/collab (WebDav)

Example ABCPY.INI FilesCustom Installing

2


4. Under the Program Files BlindCopy set:NumberOfGroups=1Set the Registry Objects to:;--Registry ObjectsGroup1NumberOfRegEntries=4Group1RegEntry1Platform=ALLGroup1RegEntry1ParentKey=HKEY_CURRENT_USERGroup1RegEntry1Key=Software\Adobe\Adobe Acrobat\5.0\Collab\cServerSettingsGroup1RegEntry1ValueName=tDAVFDFGroup1RegEntry1ValueType=STRINGGroup1RegEntry1ValueData=http://YourCompany/Collab

Group1RegEntry2Platform=ALLGroup1RegEntry2ParentKey=HKEY_LOCAL_MACHINEGroup1RegEntry2Key=Software\Adobe\Adobe Acrobat\5.0\Collab\cServerSettingsGroup1RegEntry2ValueName=tDAVFDFGroup1RegEntry2ValueType=STRINGGroup1RegEntry2ValueData=http://YourCompany/Collab

Group1RegEntry3Platform=ALLGroup1RegEntry3ParentKey=HKEY_CURRENT_USERGroup1RegEntry3Key=Software\Adobe\Adobe Acrobat\5.0\CollabGroup1RegEntry3ValueName=aServerGroup1RegEntry3ValueType=STRINGGroup1RegEntry3ValueData=DAVFDF

Custom Installing

The example ABCPY.INI file in this section provides Custom Installation (Acrobat and Asian language support).

1. Under OEM Installation Options, set these keys:

● DisplayTypeOfInstallDig=NO

● DisplaySelectDestDirDlg=YES

● DisplayCustomDlg=NO



2

Specify YES for these components:

Asian Language Support

Comp14=Japanese Language FilesComp14Enabled=YESComp14Parent=Far East Language Support



Comp17=Simplified Chinese Language FilesComp17Enabled=YESComp17Parent=Far East Language Support

Disable these Components:

InterTrust Plug-inAcrobat Distiller FilesAcrobat Distiller PrinterAcrobat Distiller Help FilesAcrobat PDFWriterPhotoshop 5.x Plug-inQuickTime 4.0Distiller Asian Language PDF Generation

2. Set SetupType to have TYPE=Custom


2





;***************************************************************;OEM Installation Options;***************************************************************[OEM Install]DisplayWelcomeDlg=YESSetupTitle=SetupCaptionBarTitle=DisplayEULA=NODisplayTypeOfInstallDlg=NODisplaySelectDestDirDlg=YESDisplayCustomDlg=NODisplayUserInfoDlg=YESDisplayConfirmRegDlg=YESDisplayStartCopyDlg=YESDisplayFinishDlg=YESDisplayFinalMessage=YESDisplayRebootDlg=NODisplayMaintUIDlg=NODisplayBillboards=YESProgGroupName=Adobe\Acrobat 5.0DefaultDestDir=UserName=UserCompanyName=John Doe CompanyUserSerialNumber=XXXXXXXXXXXXXX(This is just a placeholder. You must enter a valid Adobe serial number or the installation will not work!)DisplayBackGround=YESDisplayProgressBar=ProgressBarStart=ProgressBarEnd=CloseRunningApps=YESInstallModeSilent=NO



2

;***************************************************************; OEM Setup Type - Set "TYPE=Typical", "TYPE=Compact",;"TYPE=Custom" or leave blank. If used, set ;"DisplayTypeOfInstallDlg=NO" in OEM Install section;***************************************************************[SetupType]TYPE=Custom

;***************************************************************; OEM Component Selection Installation Options; (To use this section, must set "TYPE=Custom" in SetupType); (To deselect a component,set"CompXEnabled=NO"); (DO NOT CHANGE NUMBERS);***************************************************************[Components]NUMBER=18





Comp5=InterTrust Plug-inComp5Enabled=NOComp5Parent=Acrobat Files

;---Acrobat Distiller FilesComp6=Acrobat Distiller FilesComp6Enabled=NOComp6Parent=Acrobat Distiller Files

Comp7=Acrobat Distiller PrinterComp7Enabled=NOComp7Parent=Acrobat Distiller Files

Comp8=Acrobat Distiller Help FilesComp8Enabled=NOComp8Parent=Acrobat Distiller Files


2


;---Acrobat PDFWriterComp9=Acrobat PDFWriter FilesComp9Enabled=NOComp9Parent=

;---AccessoriesComp11=Acrobat PDFMakerComp11Enabled=YESComp11Parent=Accessories

Comp12=PhotoShop 5.x PDF Plug-inComp12Enabled=NOComp12Parent=Accessories

Comp13=QuickTime 4.0Comp13Enabled=NOComp13Parent=





Comp18=Distiller Asian Language PDF GenerationComp18Enabled=NOComp18Parent=Far East Language Support


Example ABCPY.INI FilesControlling Internet Access

2

;***************************************************************; OEM Delete Files - add files to remove from initial install, ; fill in total number;***************************************************************[OEM Delete Files]NUMBER=

Controlling Internet Access

This ABCPY.INI file updates the registry to turn off internet access.There are three routes to the Internet that Acrobat allows users:

● Through Web Hosted APIs

● Through Adobe Online

● Through the Acrobat/Reader Update mechanism

For users that do not have internet access, you can turn off access or redirect the URL to point at an intranet web site:

● To redirect the URL for Acrobat/Reader Update to an intranet website:

in HKEY_CURRENT_USERS\Software\Adobe\Acrobat Reader or (Adobe Acrobat)\5.0\AdobeViewer set DWORD name to DisableAcrobatUpdate.

● To overwrite the URL for redirection to an intranet website:

set the value of OverrideAcrobatUpdateURL to 1 in HKEY_CURRENT_USERS\Software\Adobe\Acrobat Reader\5.0\AdobeViewer

● To Disable Web Services Update:

set the value of DisableWebServicesUpdate to 1 in HKEY_CURRENT_USERS\Software\Adobe\Acrobat Reader\5.0\AdobeViewer

● To block Downloads of Adobe Online executables, – set the value of NODOWNLOAD to 1 in

HKEY_CURRENT_USER\Software\Adobe\Registration\User\

Example ABCPY.INI FilesSilently Installing

2


– Examples of the codes for the above registry update are:;--Registry ObjectsGroup1NumberOfRegEntries=4Group1RegEntry1Platform=ALLGroup1RegEntry1ParentKey=HKEY_CURRENT_USERGroup1RegEntry1Key=Software\Adobe\Adobe Acrobat\5.0\AdobeViewerGroup1RegEntry1ValueName=DisableAcrobatUpdateGroup1RegEntry1ValueType=NUMBERGroup1RegEntry1ValueData=1

Group1RegEntry2Platform=ALLGroup1RegEntry2ParentKey=HKEY_CURRENT_USERGroup1RegEntry2Key=Software\Adobe\Adobe Acrobat\5.0\AdobeViewerGroup1RegEntry2ValueName=OverrideAcrobatUpdateURLGroup1RegEntry2ValueType=NUMBERGroup1RegEntry2ValueData=1

Group1RegEntry3Platform=ALLGroup1RegEntry3ParentKey=HKEY_CURRENT_USERGroup1RegEntry3Key=Software\Adobe\Adobe Acrobat\5.0\AdobeViewerGroup1RegEntry3ValueName=DisableWebServicesUpdateGroup1RegEntry3ValueType=NUMBERGroup1RegEntry3ValueData=1

Group1RegEntry4Platform=ALLGroup1RegEntry4ParentKey=HKEY_CURRENT_USERGroup1RegEngtry4Key=Software\Adobe\Acrobat5\5.0\RegistrationGroup1RegEntry4ValueName=NOTENEVGroup1RegEntry4ValueType=STRINGGroup1RegEntry4ALLValueData=1

Silently Installing

This ABCPY.INI file provides the answers to the configuration files dialogs so that the user performs a silent install.You can record an installation and use the resulting file, called a SETUP.ISS file to provide the values to all of the keys so that the user never needs to see any dialogs in the installation. The setup -s command uses the SETUP.ISS file when performing a silent installation. (See “SETUP.EXE” on page 41 for more information about this command.)

1. Answer NO to all field OEM Installation Options

2. Specify the DefaultDestDir=d:\Acrobat5

3. Specify UserName=Test

4. Specify UserCompanyName=John Doe Company



2

5. Specify UserSerialNumber=XXXXXXXXXXXXXXXX

(This is just a placeholder – you must enter an authorized Adobe product serial number or the installation will fail!)

6. Set TYPE=Typical under the [SetupType] section.

7. Run setup -r to record the installation and create SETUP.ISS file.

An example SETUP.ISS file:

[InstallShield Silent]Version=v5.00.000File=Response File[File Transfer]OverwriteReadOnly=YesToAll[Application]Name=AcrobatVersion=5.0Company=AdobeLang=0009[DlgOrder]Count=0


2





;***************************************************************;OEM Installation Options;***************************************************************[OEM Install]SetupTitle=SetupCaptionBarTitle=DisplayWelcomeDlg=NODisplayEULA=NODisplayTypeOfInstallDlg=NODisplaySelectDestDirDlg=NODisplayCustomDlg=NODisplayUserInfoDlg=NODisplayConfirmRegDlg=NODisplayStartCopyDlg=NODisplayFinishDlg=NODisplayFinalMessage=NODisplayRebootDlg=NODisplayMaintUIDlg=NODisplayBillboards=NOProgGroupName=Acrobat 5.0DefaultDestDir=d:\Acrobat5UserName=TestUserCompanyName=John Doe CompanyUserSerialNumber=XXXXXXXXXXXXXX(This is just a placeholder – you must enter an authorized Adobe product serial number or the installation will fail!)DisplayBackGround=NODisplayProgressBar=NOProgressBarStart=NOProgressBarEnd=NOCloseRunningApps=YESInstallModeSilent=YES



2

;***************************************************************; OEM Setup Type - Set "TYPE=Typical", "TYPE=Compact","TYPE=Custom"; or leave blank.If used, set "DisplayTypeOfInstallDlg=NO"; in OEM Install section;***************************************************************

[SetupType]TYPE=Typical







Comp5=InterTrust Plug-inComp5Enabled=YESComp5Parent=Acrobat Files

;---Acrobat Distiller FilesComp6=Acrobat Distiller FilesComp6Enabled=YESComp6Parent=Acrobat Distiller Files

Comp7=Acrobat Distiller PrinterComp7Enabled=YESComp7Parent=Acrobat Distiller Files



2


Comp8Parent=Acrobat Distiller Files

;---Acrobat PDFWriterComp9=Acrobat PDFWriter FilesComp9Enabled=YESComp9Parent=

;---Adobe SVG Viewer 2.0Comp10=Adobe SVG Viewer 2.0Comp10Enabled=YESComp10Parent=

;---AccessoriesComp11=Acrobat PDFMakerComp11Enabled=YESComp11Parent=Accessories

Comp12=PhotoShop 5.x PDF Plug-inComp12Enabled=YESComp12Parent=Accessories

Comp13=QuickTime 4.0Comp13Enabled=YESComp13Parent=





Comp18=Distiller Asian Language PDF GenerationComp18Enabled=YESComp18Parent=Far East Language Support



2

;***************************************************************; OEM Delete Files - add files to remove from initialinstall,; fill in total number

;***************************************************************[OEM Delete Files]NUMBER=File1=File2=File3=

;***************************************************************;**** OEM Remove Shortcut;***************************************************************


;***************************************************************;****Acrobat BlindCopy;***************************************************************

[AcrobatBlindCopy]NumberOfGroups=



;--File ObjectsGroup1NumberOfFiles=Group1DestDir=Group1Loc=



;--Shortcut ObjectsGroup1NumberOfIcons=Group1Icon1Style=Group1Icon1Folder=Group1Icon1SubFolder=


2


Group1Icon1Exe=Group1Icon1ExeSubDir=Group1Icon1Description=Group1Icon1Number=


;--Registry ObjectsGroup1NumberOfRegEntries=Group1RegEntry1Platform=Group1RegEntry1ParentKey=Group1RegEntry1Key=Group1RegEntry1ValueName=Group1RegEntry1ValueType=Group1RegEntry1ValueData=

Group1RegEntry2Platform=AGroup1RegEntry2ParentKey=Group1RegEntry2Key=Group1RegEntry2ValueName=Group1RegEntry2ValueType=Group1RegEntry2ValueData=


;--Launch Objects[Launches]NumberOfLaunches=Launch1Platform=Launch1Language=Launch1Type=Launch1Program=Launch1CmdLine=Launch1ChangeDir=Launch1Wait=