Photoshop Color Settings bug?; LiveMotion and Netscape

Photoshop Color Settings bug? Jon Kane discovered a Photoshop Color Settings bug, that has been confirmed by Adobe Tech Support. He writes: "If you change your color setting to anything other than the default setting (web), the new color settings are not applied to an existing image with a different color space. An example would be when you change your color settings from SWOP Coated to SWOP uncoated, the image on your screen should darken slightly to show the difference in dot gain. This way you can correct the image if necessary. Now if you open an existing image that is not in the current color space (or grayscale image), any change to the color space (or grayscale dot gain) will not show on screen for correcting. Adobe Tech said that this bug should be fixed in a future update." Update: Despite Adobe's confirmation, reader Andrew Rodney claims that this is not bug. He writes: "Photoshop 6 supports Document Specific Color. If you have a file that's in SWOP, that's what's being used to preview the file to screen. Changing the Color Settings don't affect the currently open file because Photoshop is still using the embedded profile in the document (SWOP) to produce the preview. If the file has no embedded profile, things are different. Here, Photoshop 6 has to assume something about this untagged file. It assumes the current Working Space. So, if you had a file that was in CMYK (or any colorspace) and no embedded profile and you change the Working Space in the color prefs, Photoshop believes something different about this untagged file. It thus will use whatever settings the user now sets to preview the file. Photoshop 5 worked differently. A PDF that explains all this is available here." LiveMotion and Netscape alias error Jim Isaac writes: "When I tried to preview a LiveMotion 1.0.2 file in Netscape 4.76 via LiveMotion, I kept getting a message that the Netscape Essential Files could not be found. To cut to the chase, the Netscape alias that the LiveMotion installer created in its Preview In folder was the problem. When I double-click that alias, I received the same message. If you trash that alias and create another alias, it works fine."