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=domainkey-signature:received:received:mime-version:in-reply-to :references:content-type:message-id:content-transfer-encoding:from :subject:date:to:x-mailer; bh=kxoEIBKL3Zr0zEquih0py2eUt3VNaqzZwK9xyFqwB/c=; b=bJzLw2GBKh34gLdvcty5EG4/vYE14Orx3Cz8DQVodDwYnIuBQF/WHmlwhS1iLnlw/F i2IZY3Y1Snj1xXy25SzeN8NbqCPTsM3C1jCQKrOh05sRPlTyS9SV2IcCPgXyGx92S7Lp 46ZtgI3mH2TrJfsPXKZLprf0q3MgUCNSH174M= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:content-type:message-id :content-transfer-encoding:from:subject:date:to:x-mailer; b=qz7BPijeeas2rjdPILEu0qtmLMmAF3dUgeoxnGisUVctZpV17h1YRSPDiQ8ctpN90C IxH7hUVCtGrrxXFkVpgMSD9pLIGesaitFV+ahAMLvMGW8rJJz+X5FZeJTqdHGiLyT96B hwilmeAv6C5p60DJUm+lAE+3fDmle+VxcViME= On Aug 20, 2010, at 8:52 PM, Bill Cheeseman wrote: When you write installer, do you mean package? I will probably write stupid suggestions but: _______________________________________________ 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... While developing an installer package with PackageMaker 3.0.4, one of my test computers seems to have become corrupted. The final version of the installer works perfectly on two Snow Leopard machines, but on the PPC/Leopard test machine it puts up a FAILED message when trying to run a preinstall script (or sometimes a postinstall script).The scripts are known to be good. They worked fine on this machine in previous versions of the installer, and they have not been changed. Installers for other products continue to work fine. Since the installer works correctly on other computers and other installers work correctly on this computer. - have you tried running the preinstall or postinstall script outside of the package? Directly from the Terminal? - could it be possible that this script is calling some external tools that are missing from this computer? I'm suggesting this because I was recently faced with a case that sounds like yours. On a computer, an uninstaller was not working. It was working on our computers but not on this computer. The uninstaller was calling a shell script which itself was using the rm tool. We found out that the origin of the issue was that the rm tool was "missing" from the computer. Since rm is in /bin/rm, this could have been an accidental corruption. Well, no. It turns out that the user had run a utility distributed in a Mac Magazine and the purpose of this utility is to "increase" the security of the Mac by renaming the rm tool to some other name... This email sent to site_archiver@lists.apple.com