kb403122

When a link is clicked on Windows Vista, the page opens in Internet Explorer even if another browser is selected as the default.

This issue occurs when using links <a href=""></a> in the htmlText attribute of the <mx:Text> component.

Windows Vista does not make the required additional registry entries correctly when a browser other than Internet Explorer is set as the default browser. When an attempt to load the URL is made, Adobe AIR uses Dynamic Data Exchange (DDE) to connect to an open instance of the browser registered for URL requests. If that fails, Adobe AIR falls back on Shell Execution.

kb402644

This document can help you resolve problems that interrupt the installer for Adobe Technical Communication Suite 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 Service. To contact Adobe Customer Service in your region for assistance, visit the Adobe website at www.adobe.com, select your region from the top of the page, and then click Contact.

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 Technical Communication Suite, Technical Communication Suite may not necessarily be the cause-it may be the only application that uses enough memory or processor cycles to expose the problem.

kb402671

This document can help you to resolve system errors that occur while you use Technical Communication Suite 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 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.”
    • “General Protection Fault in module [filename].”
    • “Invalid Page Fault in module [filename].”
    • “Application Error.”
    • “Unhandled exception detected. Application will be terminated.”
    • “Illegal Instruction.”
    • “Segment load failure in [filename].”
    • “Application has encountered a problem and needs to close.”
    • “Fatal System Error.”
    • A STOP error

cpsid_50938

An Adobe Captivate published *.exe file does not run on Windows Vista.

A sample error message is: “This program requires flash.ocx which is no longer included in this version of Windows”.

kb402738

After you download an Adobe product on Windows Vista, the installer does not start and you can not find the downloaded file in the folder where you downloaded it to. The Launch button in the Akamai Download Manager window does not do anything.

kb406966

When you try to create a slide show or open an existing slide show in Adobe Photoshop Elements 6 on Windows, the Organizer closes and Windows returns one of these error messages:

  • “Adobe Photoshop Elements 6.0 (Organizer) has stopped working.”
  • “Adobe Photoshop Elements 6.0 (Organizer) has encountered a problem and needs to close.”

kb408352

This document can help you resolve problems that interrupt the installer forAdobe eLearning Suite 1.0on Windows Vista. Adobe eLearning Suite 1.0 applications include:

  • Adobe Captivate 4
  • Adobe Flash CS4 Professional
  • Adobe Photoshop CS4 Extended
  • Adobe Dreamweaver CS4
  • Adobe Acrobat 9 Pro
  • Adobe Soundbooth CS4
  • Adobe Presenter 7
  • Adobe Bridge CS4
  • Adobe Device Central CS4

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 http://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 withAdobe eLearning Suite 1.0, Adobe eLearning Suite 1.0 may not necessarily be the cause–it may be the only application that uses enough memory or processor cycles to expose the problem.

kb408350

This document can help you to resolve system errors that occur while you use Adobe eLearning Suite 1.0 on Windows Vista. Adobe eLearning Suite 1.0 applications include:

  • Adobe Captivate 4
  • Adobe Flash CS4 Professional
  • Adobe Photoshop CS4 Extended
  • Adobe Dreamweaver CS4
  • Adobe Acrobat 9 Pro
  • Adobe Soundbooth CS4
  • Adobe Presenter 7
  • Adobe Bridge CS4
  • Adobe Device Central CS4

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:
    • “This program has performed an illegal operation and will be shut down. If the problem persists, contact the program vendor.”
    • “General Protection Fault in module [filename].”
    • “Invalid Page Fault in module [filename].”
    • “Application Error.”
    • “Unhandled exception detected. Application will be terminated.”
    • “Illegal Instruction.”
    • “Segment load failure in [filename].”
    • “Application has 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 theeLearning Suite 1.0, the eLearning Suite 1.0 may not necessarily be the cause–it may be the only application that uses enough memory or processor cycles to expose the problem.

kb406897

The performance of Adobe FrameMaker 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.

Before you perform the steps below, make sure to install the latest version of FrameMaker or any FrameMaker updates to the version you are using. FrameMaker updates often include performance-related fixes or enhancements. Current version information and updates are available on the Adobe web site at www.adobe.com .

kb406893

This document can help you to resolve system errors that occur while you use Adobe FrameMaker 9.0. 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:
    • “Internal Error [number],[number],[number],[number]”
    • “This program has performed an illegal operation and will be shut down. If the problem persists, contact the program vendor.”
    • “FrameMaker caused a General Protection Fault in module [filename].”
    • “FrameMaker caused an Invalid Page Fault in module [filename].”
    • “Application Error.”
    • “Unhandled exception detected. Application will be terminated.”
    • “Illegal Instruction.”
    • “Segment load failure in [filename].”
    • “FrameMaker has 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 FrameMaker, FrameMaker may not necessarily be the cause; it may be the only application that uses enough memory or processor cycles to expose the problem.