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.

Consider the following scenario. You install Adobe Dreamweaver on a Windows Vista-based computer. Additionally, you accept the option to make Dreamweaver the default editor for XML files. In this scenario, Windows Vista Help and Support stops working. When you try to run Windows Vista Help and Support, you receive the following error message:

Internet Explorer cannot download / from windows. Internet Explorer was not able to open this Internet site. The requested site is either unavailable or cannot be found. Please try again later.

You may also receive an error message that states that Windows Vista cannot find the file when you try to open XML files in the Windows Vista file browser.

When you Put or Synchronize files after time changes occur in the Spring or Fall (for example U.S. Daylight Savings Time), Dreamweaver displays the following false warning messages:

“my_file.htm has changed on the remote server since your last get or put operation. Putting it may overwrite changes to the file. Do you wish to put the file anyway?”

This warning only occurs the first time you try to upload each file. Subsequent uploads do not give this warning.

You may also experience similar problems with the Dreamweaver synchronize feature if you change the time zone of your client machine, for example, while traveling. (Ref. 202143)

In version 8 and earlier of most Studio products, the Windows keyboard shortcut Control-Alt-Tab activates the accessibility feature of navigating the different panels without using a mouse. This Studio key combination no longer works in Microsoft Windows Vista; instead, it activates a new Vista operating-system-wide feature. (Ref. 209768)

The specific products affected by this issue include:

• Dreamweaver 8 and earlier
• Flash 8 and earlier
• Contribute 3 and earlier

Note: Windows Vista is still in beta and is not supported or tested with Dreamweaver, Flash or Contribute. For supported operating systems, see the System Requirements.

When you install Dreamweaver, if you accept the default selection to make Dreamweaver the default editor for XML files, the Windows Vista help system stops working. When you try to run Vista “Help and Support”, the following error occurs:

“Internet Explorer cannot download / from windows. Internet Explorer was not able to open this Internet site. The requested site is either unavailable or cannot be found. Please try again later.”

You may also see an error saying that Windows cannot find the file when trying to open XML files from within the Windows file browser. (Ref. 224272).

Some Dreamweaver 8 users running on Windows Vista are reporting that Dreamweaver crashes while performing actions that involve browsing for files. Some examples include:

• Using File > Open to browse the hard drive to open a file.
• Inserting an image and using the file browser to select the image.
• Creating a hyperlink and using the file browser to select the target file.
• Creating a site definition and using the file browser to select the local root folder or remote folder.

Different users are seeing different behavior:

• Some users report the crashes happen every time, while others report the crashes are random and sporadic.
• Some users report the crashes happen right when a file browsing dialog appears, while others report the crashes only occur when browsing two or more folders away.
• Some users report the crashes only occur after inserting four images.
• Some users report the crashes only occur if you leave the file browsing dialog box open for a little while.