- Message Boards
- Package KB
- Software KB
- Free Videos
- MSI Errors
- Tools
- Tech Home Pages
- Reviews
- Downloads
- Articles
- FAQs
- Tips & Tricks
- Services
- News
- Newsletter
Search AppDeploy
Photoshop CS 8.x
| Company: | Adobe |
| Setup Type: | Legacy setup with answer file support |
| Package Difficulty Rating: |
[ Rate It or View Ratings ]
|
| Most Commonly Reported Method: | Windows Installer (with Custom Transform) |
| Record Created On: | 3/9/2004 |
| Number of Views: | 17,163 |
Software Knowledge Base: The software knowledge base contains details on over 60,000. The closest record matching this software package is displayed here. Browse the Software KB directly to find similar records.
Software Knowledge Base
Software Knowledge BaseFull Name: Adobe Photoshop CS
Version: 8.0 (8.0x119)
Publisher: 8.0 (8.0x119), Copyright ©1990-2003 Adobe Systems Incorporated
Uninstall String: /Applications/Adobe Photoshop CS/Adobe Photoshop CS.app
Categories: Unknown
Threat: Unknown
Command Lines: Command line details for installation and removal of this software. Details may include available command line arguments and/or public properties.
| Not sure why everyone is going to so much effort... I just did it with a "setup.exe /r" to create a setup.iss file and then did the install with "setup.exe /s"... works fine. | ||||
| Above Entry Provided on 12/12/2006 by thewspot | Rate It | Rating 119 | ||
Notes: Shared "notes from the field" covering how to handle the automated installation of this software.
| Repackage this software to MSI for GPO Deployment was not easy. I hope Adobe would consider making any future installers in MSI format with GPO support. Here is what I did in step by step to make it happen. 1. Launch a clean XP image from Microsoft Virtual PC. 2. Launch InsteallShield Repackager from a network share, and follow the standard procedures to capture the software. 3. Go through the captured information and exclude information that you do not want to be part of the package. The entire HKCU can be excluded. Also exclude two log files - wiadebug.log/wiaservc.log - found in the WINDOWS folder. 4. Before shutting down the Virtual PC, export following keys to a file and save it to the host machine. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{EFB21DE7-8C19-4A88-BB28-A766E16493BC} 4. Have Repackager to build an InstallShield Developer project file. 5. Open the project file. 6. Go to Direct Editor, expand Tables, and click on Component. 7. Navigate to Folder_Automate_COM and empty out the KeyPath field (delete string contactsheetii.8li). 8. Open up the registry you saved from step 4, and copy Serial, RegCompany and RegOwner to your project file. Make sure those three string values are stored under [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{EFB21DE7-8C19-4A88-BB28-A766E16493BC}]. It is not necessary to change your product GUID to be the same as the original software GUID. 9. Compile the MSI file and test it on a clean [virtual] machine. Make sure that both installation and uninstallation work without any errors. I hope this information is valuable to you. | ||||
| Above Entry Provided on 3/10/2004 by puppy | Rate It | Rating 118 | ||
| In item 8. it is not necessary to delete the string..just go into the Folder_Automate_COM component and set the Pri. key to ScriptingSupport.8li and click No to remove the COM information...that should do the trick..! | ||||
| Above Entry Provided on 3/25/2004 by Rico | Rate It | Rating 117 | ||
| If you recieve the following error "Could not register type library for file C:\Program Files\Adobe\Photoshop CS\TypeLibrary.tlb. Contact your support personnel." on install, remove the three rows under the typelib table. Successfully tested with no adverse effect. | ||||
| Above Entry Provided on 8/31/2004 by scorpianfrog | Rate It | Rating 118 | ||
| To resolve the problem with the TypeLibrary.tlb, it is not necessary to delete all entries in the Typelib table. Only the GUID {4B0AB3E1-80F1-11CF-86B4-444553540000} is associated with Typelibrary.tlb, so this is the only one you need to remove. If you do not mind ICE33 warnings, and you like the tlb to be registered just as it is in the manual installation, you could add HKCR\Typelib\{4B0AB3E1-80F1-11CF-86B4-444553540000} and its subkeys and values to the registry table. I just did this and tested it, it worked fine. | ||||
| Above Entry Provided on 10/31/2005 by cs_m_si | Rate It | Rating 120 | ||
| You should not delete the TypeLib. Instead delete all registry within the component TypeLibrary.tlb. Use WiseComCapture to register the file and capture the registry. Import this registry into the package under the TypeLibrary.tlb component. This will the install without error. The TypeLib's are there for a reason - not to be deleted when an error occurs! | ||||
| Above Entry Provided on 8/2/2006 by d2bromwi | Rate It | Rating 118 | ||
| The file ~e5d141.tmp dynamically created in the users %TEMP% folder also require permissions to execute as I recently found out after applying software restrictions. It is part of the macrovision protection used only in CS. | ||||
| Above Entry Provided on 12/11/2006 by michaelc | Rate It | Rating 118 | ||
Virtualization: Information regarding how to work with this software in creating a virtual deployment package for products like Altiris SVS and Microsoft SoftGrid.
Terminal Services: Notes on how to address problems working with this software in a Terminal Services session as with Citrix shared environments.
Related Links: Additional resources to reference in regards to the deployment and configuration of this software.
Security Information: Details covering which files, directories and/or registry entries must be opened to standard users for operation in a locked down environment.
Discussion threads: Discussion topics in the AppDeploy message boards that have been linked as relevant information to this entry.
