The performance of Adobe Illustrator depends on several factors, including the options you select, your workflow, and the operating system and hardware configuration. The performance improvements listed below are most noticeable when you work with larger files. Optimizing the operating system and hardware configuration improves performance in other applications as well.

This document can help you resolve problems that interrupt the installer for Adobe InCopy CS4 on Windows Vista. These problems can manifest themselves in many different ways, including (but not limited to) a frozen cursor or screen, or an error.

Please note that this document does not address problems related to serial numbers. For these problems, contact Adobe Customer Services. To contact Adobe Customer Service in your region for assistance, visit the Adobe website at www.adobe.com/, select your region from the menu at the top of the page, and then click Contact Us.

Different factors can interrupt the installation of an application, including the AutoPlay feature in Windows, a conflicting application, incorrect data in the Windows registry, or hardware problems. Although a system error may occur only when you work with Adobe InCopy CS4, Adobe InCopy may not necessarily be the cause–it may be the only application that uses enough memory or processor cycles to expose the problem.

This document can help you to resolve system errors that occur while you use Adobe InDesign/ InCopy CS4 on Windows XP or Windows Vista Operating system. System errors can manifest in many different ways, including (but not limited to) the following:

• A blank or flickering dialog box
• A frozen cursor or screen
• A blue screen
• An unexpected restart
• An error such as one of the following:
  • “Application Error”
  • “The instruction at ‘[memory address]‘ referenced memory at ‘[memory address]‘. The memory could not be ‘read’.”
  • “[filename] has generated errors and will be closed by Windows.”
  • “This program has performed an illegal operation and will be shut down. If the problem persists, contact the program vendor.”
  • “InCopy caused a General Protection Fault in module [filename].”
  • “InDesign caused a General Protection Fault in module [filename].”
  • “InCopy caused an Invalid Page Fault in module [filename].”
  • “InDesign caused an Invalid Page Fault in module [filename].”
  • “Unhandled exception detected. Application will be terminated.”
  • “Illegal Instruction.”
  • “Segment load failure in [filename].”
  • “InCopy has encountered a problem and needs to close.”
  • “InDesign has encountered a problem and needs to close.”
  • “Fatal System Error.”

Many different factors can cause system errors, including conflicts among device drivers, applications, operating system settings, hardware, and corrupt elements in specific files. Although a system error may occur only when you work with InDesign/InCopy, InDesign/InCopy may not necessarily be the cause–it may be the only application that uses enough memory or processor cycles to expose the problem.

To benefit most from this document, perform the tasks in order. Keep track of the tasks that you perform and the results of each, including errors and other problems. Adobe Technical Support can use this information to better assist you if you need to call.

Note: The procedures in this document are based on the default interface of Windows XP and Windows Vista. If the interface is customized, some procedures may vary. For example, a commonly encountered difference is the navigation to Control Panel from the Start menu: You may navigate Start > Settings > Control Panel instead of Start > Control Panel.

This document can help you to resolve system errors that occur while you use Adobe Dreamweaver CS4 on Windows Vista. System errors can manifest in many different ways, including (but not limited to) the following:

• A blank or flickering dialog box
• A frozen cursor or screen
• A blue screen
• An unexpected restart
• An error message such as one of the following:
  • This program has performed an illegal operation and will be shut down. If the problem persists, contact the program vendor.”
  • “Dreamweaver caused a General Protection Fault in module index.html.”
  • “Dreamweaver caused an Invalid Page Fault in module index.html.”
  • “Application Error.”
  • “Unhandled exception detected. Application will be terminated.”
  • “Illegal Instruction.”
  • “Dreamweaverhas encountered a problem and needs to close.”
  • “Fatal System Error.”
  • A STOP error

Many different factors can cause system errors, including conflicts among device drivers, applications, operating system settings, hardware, and corrupt elements in specific files. Although a system error may occur only when you work with Dreamweaver, Dreamweaver may not necessarily be the cause–it may be the only application that uses enough memory or processor cycles to expose the problem.

Adobe Creative Suite 4 offers a number of services that connect to the internet to provide enhanced functionality. These services can also download updates automatically. In certain circumstances system administrators may wish to disable these connections and updated downloads. The document lists the changes that have to be made to the registry (Windows XP/Vista) or preference files (Mac OS X) to disable these network activities. This applies to the following Creative Suite 4 services:

• Kuler (Extensions > Kuler)
• Adobe ConnectNow (File > Share my Screen)
• Service Manager (Extensions > Connections)
• Search for Help (Search field in the app bar)
• Help > [Product Name] Help

When you download and try to install Adobe Reader 9 on Windows Vista, the installer returns the error message:

Error 1311. Source file not found: C:\Users\[your user name]\AppData\Local\Adobe\Reader 9.0\Setup Files\READER9\Data1.cab. Verify that the file exists and that you can access it.

This document can help you to resolve system errors that occur while you use Adobe Premiere Pro CS3 on Windows Vista. System errors can manifest in many different ways, including (but not limited to) the following:

• A blank or flickering dialog box.
• A frozen cursor or screen.
• A blue screen.
• An unexpected restart.
• An error message such as one of the following:
  “The application Premiere Pro has stopped working.”
  “Premiere Pro has encountered a problem and needs to close.”
  “This program has performed an illegal operation and will be shut down. If the problem persists, contact the program vendor.”
  “Application Error.”
  “Unhandled exception detected. Application will be terminated.”
  “Illegal Instruction.”
  “Fatal System Error.”

Many different factors can cause system errors, including conflicts among device drivers, applications, operating system settings, hardware, and corrupt elements in specific files. Although a system error may occur only when you work with Premiere Pro, Premiere Pro may not necessarily be the cause–it may be the only application that uses enough memory or processor cycles to expose the problem.

When you print to a postscript print driver, including the AdobePDF printer, the application you are printing from sometimes fails unexpectedly or creates invalid results on Windows XP, Windows Vista, Windows Server 2003, or Windows Server 2008.

If you’re having problems running Adobe Premiere Elements 4 in Windows Vista, here are some troubleshooting techniques you can use to fix your problems. Keep reading →

When you launch Adobe Flex Builder 3 after installing the web version of Flex Builder 3, you receive a “No Disk” error message.