- 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 7.x
| Company: | Adobe |
| Setup Type: | Legacy setup with no known support |
| Package Difficulty Rating: |
[ Rate It or View Ratings ]
|
| Most Commonly Reported Method: | Repackaged (MSI) |
| Record Created On: | 3/9/2005 |
| Number of Views: | 15,933 |
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 7
Version: 7.0.1
Publisher: 7.0.1, Copyright © 1990-2002 Adobe Systems Incorporated
Uninstall String: /Applications/Adobe Photoshop 7/Adobe Photoshop 7.0
Categories: Business
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.
| For Photoshop 7.0.1 I used the following... Run Parameters: -quiet Full Command Line: \\dfs\share\it\ | ||||
| Above Entry Provided on 8/4/2010 by KBOX User | Rate It | Rating 0 | ||
Notes: Shared "notes from the field" covering how to handle the automated installation of this software.
| 1. Use your favorite repackage application and capture the information. Make sure you do this on a clean installation machine. VMware will save you a lot of time :) 2. If you are using Wise Package Studio or Wise for Windows Installer, please continue follow this insturction; otherwise, please try to tell your repackage application that you do not want to advertising "TypeLibrary.tlb" component. 3. Launch the script and go to Setup Editor. 4. Click on the Components tab. 5. Browse through the list and locate "TypeLibrary.tlb component". Click on + to expand it. 6. Delete all entries (should be only one) in Advertising. If you don't do this, user will get a warning prompt saying it can't register this component during the installation... I haven't found any problem yet. It works in both standard installation and GPO deployment mode. You may also want to put in to the registry key so that the first user who launches Photoshop won't be asked whether or not he wants to register this product. | ||||
| Above Entry Provided on 8/19/2002 by puppy | Rate It | Rating 117 | ||
| I'd have to disagree with this methodology. Photoshop can be deployed silent by using a setup.iss response file or by editing the abcpy.ini file. One could also prepoplate the users' registry to avoid the registration dialog. | ||||
| Above Entry Provided on 8/31/2002 by dethomson | Rate It | Rating 118 | ||
| With this or any other application there may be several ways to generate a silent installation. When using group policy it is often necessary to repackage an application to an MSI regardless of any command line installation support provided by the vendor. What are most people doing? Use the "Rate This Package" link a the top of the page to say how you did it and how hard you thought it was! Is Photoshop easy or hard to remotely deploy? | ||||
| Above Entry Provided on 8/31/2002 by bkelly | Rate It | Rating 117 | ||
| Fixing error 1911 These are the steps I took to repackage PhotoShop 7: 1. Captured the installation on a clean VMware Windows 2000 workstation, using Wise Package Studio 3.2 MSI Capture tool. 2. Used CCRP to force the registration of the proprietary Adobe type library found at: C:\Program Files\Adobe\Photoshop (this step might not be necessary) 3. Executed the program once (normally I do not do this; this step may be un-necessary) 4. NO REBOOT - every time I attempted to build this package using a reboot as part of the process, I received an error upon compiling the .msi that "C:\Documents and Settings\%username%\local settings\temp\MSIA98.tmp\w1.cab" could not be closed. Skipping the reboot seems to have resolved this. 5. DID NOT DELETE THE ADOBE TYPELIB. The program may work initially without it, but this may cause unforseen problems down the road. 6. Compiled/Saved the .msi 7. Opened the .msi using Wise Package Studio 3.2 Windows Installer Editor. Went to "Tables" and found the line item for "TypeLib". Deleted the rows in that table, but not the table itself. Leaving these rows in will cause the installation to deliver the "1911" error. 8. Resaved the .msi and tested it via straight install and GP/AD And, once again as AppDeploy founder Bob Kelly noted above: " . . . With this or any other application there may be several ways to generate a silent installation. When using group policy it is often necessary to repackage an application to an MSI regardless of any command line installation support provided by the vendor." | ||||
| Above Entry Provided on 2/25/2005 by craig16229 | Rate It | Rating 118 | ||
| Re: The error with leaving the reboot in place and the temporary file (MSIA98.tmp). Best solution is to do the reboot and then to fix the associated error in the MSI by searching for the temp file. Wise should have picked it up and not included it by default. Simply go through the file list pane and drill down to that file and delete it. Wise will adjust the tables accordingly! | ||||
| Above Entry Provided on 8/2/2004 by ddback | Rate It | Rating 117 | ||
| Once again, you can use Abcpy.ini for silent installs, just fill in the details. Don't bother repackaging. | ||||
| Above Entry Provided on 10/14/2004 by raj_crc | Rate It | Rating 117 | ||
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.
