site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SQARBGYyH7wwy/iivMixa70ag7GGJCo3nxRXvNALwjU=; b=OzUPS7UKDTVZNi/BAloeZlao6Y1KJcCpRUVVHFU9N7gyOZwCrTN/8+Ct+K0oYFgEbM a1OhJXja595EtrWtXzE2tw/Hd5Oa8hugO1MYczUmfeZObNz/4AxUDac8LZPc6a6mfUFk feAxWeuQ7yT3XobMCmZG6LnHti74hp8HloalQ=

Hi, I am getting the right path in those scripts.

Thats what i was looking for... :)

But how will I make use of the those path in preflight script?

Altough its not a very elegant solution, and doesnt solve the problem (its just a fix), you could do many things.

The preflight script is executed from the driver I mounted first. Following is one line from the log. I have called the OSX installer.pkg from /Volumes/User Software 1/OSX/Printer Driver/OSX installer.pkg

Ill try exporting an environment variable with the correct path and then use it on preflight more or less like this pseudo-code: if variable "installsource"="disc1" { target="$1" } else { target="installLocation" } //install on target I guess this is due to the whitespace, and shouldnt fail if you rename "User Software 1" to "User Software_1" or something like that. btw, i always recommend using s.sudre Packages, and avoid official (buggy) PackageMaker :P _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com