Matthew Laun's dashboard

George,
I'm glad to hear I could be of help. I'm sorry for the inconvenience. Though I can't remember the problem that was solve, I remember it as being worse than this side effect of it.

While we're doing what we can to improve the abilities of our support agents, some things just come from experience and an agent supporting many products may never have as deep of knowledge as some customers, or someone like myself who's worked on developing InDesign since 1.0. So be sure to try our user to user forums:
http://forums.adobe.com/index.jspa

And keep using the GetSatisfaction community.

Cheers!
Matt

This is due to a change in behavior made to accommodate customer requests (the particulars are lost in my memory). When you change to a 0pt weight, it no longer removes the stroke color. A zero width stroke color on text can still produce a result because the shape is drawn based on the outline without the PS/PDF methods used to best render fonts at various sizes. The solution is to remove the stroke colorant using the color proxies on the tool panel and the color and/or swatches panels.

Sincerely,
Matthew

George,
Not sure what you mean by hints. I don't have sample code, I'm afraid. But I believe if you search the internet, you'll find some that do some action on a folder full of documents. You can follow their design, but replace the action with the find/change script you make.

Cheers!

You could write a script that does the find/change, then wrap it in a script that cycles through opening files and running the find/change script.

Or, you can simply open all the files, open Find/Change, and set the Search setting to "All Documents" which means all documents currently open.

Cheers!

Philipp,
If you have CEIP enabled, the the Win 7 beta solution might be worth testing. I think you're reaching the point where you'd be best off working with someone in real time. You can contact Adobe Tech Support for free support of installation issues:
http://www.adobe.com/support/contact/

Good luck!

Philipp,
You should only have to repeat the process for two folders
C:\Windows\Installer\
C:\Config.Msi\
The second of this is a hidden folder, so you'll need to use the Folder View control panel to enable display of hidden folders.

Here's an update to the steps for solution 1 to ensure the change is made to children of the folder as well:

1. Right-click the folder and choose Properties.
2. Under the Security tab, click Advanced button.
3. On the Permissions tabl, Check the "Replace permissions entries...." option
4. Select the System item in the Permission entries list
5. Click the Edit button
6. Click to enable Full Control in the Allow column.
7. Click OK.
8. Click OK again
9. At the Security prompt, click Yes.
10. Click OK to close the folder's properties window.

Good luck!
Matt

@Brian,
As I said, though the post is on an AIR branded blog, it's about work that the core Flash Player team is planning to do to address performance issues that affect both publishing workflows. I'm afraid I don't have a solution for you, as this is not my area of expertise. I just wanted to share with you the fact that Adobe is focused on solving the problem discussed here in this thread. – Matthew Laun, on August 18, 2009 17:09

Philipp,
The installer logs you sent had multiple instances of this type of error:

DEBUG: Error 2203: Database: C:\Windows\Installer\b2f200.ipi. Cannot open database file. System error -2147287035
Internal Error 2203. C:\Windows\Installer\b2f200.ipi, -2147287035
Action ended 23:28:06: InstallInitialize. Return value 3.

With one case of an additional type of error:

Error 1310.Error writing to file: C:\Config.Msi\47ca7.rbf. Verify that you have access to that directory.
Action ended 23:55:35: InstallFinalize. Return value 3.

The “System error –2147287035” means Access Denied. Both of these suggest that there is some parts of your drive that the System account, acting on behalf of the MSI (Microsoft Installer) is hitting a permissions restriction on.

See these MS tech docs for some additional background:
http://support.microsoft.com/kb/32485...
http://support.microsoft.com/kb/888310

Although the later of those tech docs has a hotfix, the error number is different, and I believe you’re more likely to solve things by fixing permissions.

Try the following Solution 1. If that doesn’t solve the problem, then additionally perform Solution 2:

Solution 1: Grant the SYSTEM account Full Control permissions.
Edit the directory permissions to grant the SYSTEM account Full Control permissions to the folder referenced in the log (e.g. C:\Windows\Installer\c5ab.msi). This is usually the directory that contains the installation point.

1. Right-click the folder and choose Properties.
2. Under the Security tab, choose SYSTEM and select Allow Full Control.
3. Click Apply and then OK.

Solution 2: Reinstall Microsoft Windows Installer 3.1 or 4.x.
You can download the appropriate versionfor your Windows version from the Microsoft Download Center at www.microsoft.com/downloads/.

Let me know if this helps. Good luck!

Sincerely,
Matthew

Phillip,
You can post it in the Adobe.com Creative Suite forum (allows file uploads), or find my account in there and get my email.

Win:
http://forums.adobe.com/community/cre...
Mac:
http://forums.adobe.com/community/cre...

Here are some good resources to show that Adobe is concerned about performance, and to help you understand how Adobe tries to help programmers using our platform to optimize their applications' performance as well. Though this is AIR branded, it speaks to the Player in general since it is much of the core of AIR.

http://blogs.adobe.com/air/performance/

Feel free to post information here and I'll try to help. The best thing is to post the information about the failure (what shows in the UI) any error numbers or exact error strings (even if not in English, I'll get it translated), and the installer log which if found here:
Mac: Users/[user]/library/logs/adobe/Installers/[product name][time stamp].log.gz
Win: C:\Program Files\Common Files\Adobe\Installer\[product name][time stamp].log.gz

Here's a good explanation of what a clipping path is:
http://en.wikipedia.org/wiki/Clipping...

And this page in the Acrobat 9.0 online help contains information on the Set Clip and Delete Clip commands:
http://help.adobe.com/en_US/Acrobat/9...

Cheers!

The PDF author can restrict editing capabilities. Use the Security pane in the Document Properties window to see if this is the cause.

If no restrictions are listed here, and you cannot modify a particular item, it's likely caused because the content is wrapped into a formX object. If this is the case, the touch up object tool or touch up text tool is limited from modifying content inside the formX object.

Or it could be wrapped inside of a clipping path. Using the touch up object tool, right click and choose release clip, see if that enables what you want to edit. If not, undo.

Good luck!

@r coach,
The PDF author can restrict editing capabilities. Use the Security pane in the Document Properties window to see if this is the cause. If no restrictions are listed here, and you cannot modify a particular item, it's likely caused because the content is wrapped into a formX object. Or it could be wrapped inside of a clipping path. Using the touch up object tool, right click and choose release clip, see if that enables what you want to edit. If not, undo. – Matthew Laun, on August 04, 2009 14:30

Great to hear! Now if we can get everyone taken care of, sigh....

Cabby,
We may have to agree to disagree, but to me, this further supports the theory that the applications are behaving badly. AIR application authors control how the applications read and write to their encrypted local store data. Programming error on their part can cause them to fail to read the data, corrupt the data, etc.
Or, one might believe that the the MS and/or Norton updates damaged the files, or disrupted the applications while read/writing to the files such that the became corrupt.

Either way, glad that the issue is solved. Cheers!

Hob,
Are the EPS files authored by Photoshop? If you choose to show import options when placing, and ask that the PostScript be rasterized to create the preview, does it still happen? Does it show when you enable Overprint Preview? When it shows in printing, are you printing to a postscript printer, or non-PS?

I've tried to reproduce the problem, but without success. If you can, please save a copy of the document that contains just the two instances of the image, confirm that it still shows the problem, especially in the print out, then package, compress, and send it to me, and I'll try to get to the bottom of it and report a bug as needed.

Sincerely,
Matthew
mlaun at adobe dot com

Cabby,
The logic you're offering about the order of the installations and updates, doesn't support a hypothesis that the problem is with the AIR platform itself.

Because the applications in question aren't authored by us, we're not in a position to troubleshoot them (we don't have the source code, etc). This is why I recommend reporting the issue to the authors first. They in turn can confirm if the issue is out of their hands and needs our attention, in which case they can make use of support sources that are geared for developers.

Obviously, if this is some core problem with AIR, then we would be flooded with reports from developers and end users, and we'd proactively investigate the issue. But I don't see that happening yet.

Sincerely,
Matthew

Cabby,
If only some of the AIR apps are showing problems, you might best report them to their authors. If their debugging shows that AIR has an error, they have avenues to report such things designed for Developers.

Matt

Doug,
Hang in there, the case was modified yesterday, so I can tell it's being worked on. The biggest problem (admittedly, of many) is that we've had a back log of this kind of work so cases have had to go without action. With consistent activity on the case, it should be resolved soon.

Regarding why it's not possible to simply cancel the order so soon after placing it, I don't know if this is because of something in our system, the partner we vendor with, or something about how they interact, but it's very disappointing. I personally recommend that people purchase our software from companies who are professionals at *selling* software, not *making* software.

Sincerely,
Matthew