CS4/G5/Tiger/OpenGL

It all started when I tried to use the feature in CS4 for changing the brush head size.
Instead of using the bracket keys, one is able to hold down Control+Alt and slide the mouse/pen. What then happens is the brush head size alters accordingly and is shown in Red. Accept when I do it, I can see the size of the brush enlarging or reducing, but there is no red colour.  In fact there is no colour at all during the process, just a round circle.
Someone suggested that my Graphics card was not up to date, I checked and it is.
Next I updated my copy of CS4 to the current version.
I then went into preferences to enable OpenGL but It was 'Greyed Out'. I was told that I needed to upgrade from Tiger to Leopard or Snow Leopard for all the CS4 feature to work.
I didn't want to upgrade to Snow Leopard as I understand that there may still be some bugs. Secondly my G5 is not equipped with Intel, so wouldn't be compatible anyway.
I said that I would happily upgrade to Leopard, my local dealer told me to get in touch with Apple, pay £20.00 and they would send me the upgrade disk. Except when I tried to do this, they said that the upgrade is no longer available and, if I wanted to upgrade to Leopard it would cost me £83.00! I said how can you expect me to pay that amount for an OS that is actually an older version (Snow being the current), they couldn't or wouldn't answer. I then asked if, as I also owned a brand new MacBook Pro with Leopard, could I not use those disks on my G5 Desktop.  After all the OS is mine! I bought it when I bought the MacBook Pro.  Surely I can do what I like with it. I was told that the disks that come with the Laptop are different and I would not be able to use the MacBook Pro Leopard Disks on my G5 to go from Tiger up. I even offered to pay a fee for using my own Leopard disks on my other machine. But all I got was NO you have to buy a boxed version at £83.
Not only that, but if I did spend the £83 I not sure that will allow me to enable OpenGL anyway, and if does, will that cure my problem with the brush!
I also have a feeling that there are a number of other features in CS4 that I am unable to use, because of the lack of OpenGL. Such as being able to revolve the layer you are working on, if (for example) you were using a Pen tool and the angle was awkward, you could rotate or slide, move around the picture to assist you.
What's the general thinking guys? Would Leopard improve my G5? And could I use my MacBook Pro disks to install Leopard on my G5 or are they specific to the laptop?
Many thanks
Mark

I'm running CS4 (11.0.1) on a G5 Quad 2.5Ghz under Mac OS X 10.4.11 (i.e. Tiger), with an Nvidia GeForce 6600LE graphics card.
I can use the the OpenGL features fine, including changing the brush size as you describe. So I don't think it's necessarily an issue with it being a G5 or running Tiger, but might be a graphics card issue if it's not on the "approved list":
http://kb2.adobe.com/cps/405/kb405711.html
...and yes, I know my card isn't on the list.
Have to say that I normally run with OpenGL off as most of the "features" are either irrelevant to what I use Photoshop for, actually detremental for me (e.g. the way zoom levels are displayed) or cosmetic interface frippery...

Similar Messages

  • PS CS4 problems with OpenGL drawing enabled

    I've just upgraded from PS CS3 to PS CS4 (default 32 and 64 versions) and I'm having problems with seeing image files above a certain size (even moderate size) with OpenGL Drawing enabled. Disabling OpenGL Drawing results in very slow image display (very easy to see the blocks being drawn one at a time), much slower than with PS CS3.
    I'm running Vista 64 with latest updates. I'm trying to get PS CS4 32 running properly first, but PS CS4 64 seems to be having similar problems.
    GeForce 9600 GT video card with latest driver 178.24 (updated yesterday and rebooted many times since then). That card is in Adobe's list of tested cards.
    Main monitor (where I display Photoshop images) selected as primary in the driver dialog.
    I put palettes/panes on my 2nd monitor.
    I use Ultramon for 2nd monitor taskbar functionality. Turning Ultramon off doesn't seem to help, although I may need to disable Ultramon from launching on reboot.
    No plugins installed yet in PS CS4 (32), as per Adobe kb advice.
    4GB of RAM with Memory Usage set within Photoshop's Ideal Range.
    For testing, I've been opening a few different size (px and bytes) RGB image files in Photoshop by dragging them from an Explorer window into the Photoshop window, then clickin in the Photoshop window to make Photoshop active and show its palettes.
    First with OpenGL Drawing enabled in Performance, default Advanced Settings.
    JPEG, 3600 x 2600 px, 4.5MB
    - opens and displays ok (short delay before palettes appear)
    - zooms and rotates smoothly
    TIFF, 2 layers, 800 x 600 px, 16 bits, 2.5MB
    - opens and displays ok (short delay before palettes appear)
    - zooms and rotates smoothly
    TIFF, 1 layer, 3600 x 2600 px, 16 bits, 54MB
    - doesn't open properly, shows checkerboard instead of image, with checkerboard in navigator and layer icon in layers pane
    - histogram is fine
    - zooming and rotation are not smooth (jumps to new position/size)
    - duplicate layer caused PS CS4 to stop working, with a close program dialog
    - open PS CS4 32 again, no OpenGL message today, and OpenGL Drawing is still enabled (although I got the OpenGL Drawing message more than once yesterday)
    TIFF, several layers, 3600 x 2600 px, 16 bits, 306 MB
    - doesn't open properly, shows checkerboard instead of main image
    - icons in layers pane look fine, same as navigator image
    - checkerboard zooms and rotates smoothly
    - duplicate layer is still checkerboard, back one history state stopped working / close program dialog
    - started PS again, opened 1 layer TIFF, closed and tried to open multi layer TIFF again, but stopped working / close program dialog again
    I then tried the same images with OpenGL Drawing disabled in Performance.
    3600 x 2600 px JPEG
    - ok, but slow, blocky redraw
    2 layer 800 x 600 px TIFF
    - ok, but slight delay in redraw (smallest of all the files, both in px and bytes)
    1 layer 3600 x 2600 px TIFF
    - opened ok, but slow, blocky redraw
    multi layer 3600 x 2600 px TIFF
    - opened ok, but slow, blocky redraw
    From what I've read in various Adobe kb notes, it sounds like there's some kind of conflict with my video driver, but I haven't been able to figure it out. I even tried the registry plugin from the Adobe kb to disallow OpenGL Windows, but that didn't seem to make any difference. It didn't even stop me being able to select and use OpenGL Drawing in PS CS4.
    Any help would be much appreciated. I'm tearing my hair out here and I'm feeling a bit like I've blown my money on the upgrade so far.

    I had another look at PS CS4 64 and those smaller (by file size) images that I can see with OpenGL Drawing on rotate and resize in a jumpy way, not smoothly like in PS CS4 32.
    The multi layer TIFF that showed the images in at least the layers pane and navigator when using PS CS4 32 only shows the checkerboard in the layers pane and navigator in PS CS4 64.
    Either way, neither version is anywhere near working properly.
    Oh yeah, and I made a typo on the RAM. It's 6GB and not 4GB, not that I think that would make any difference.

  • AE CS4 and the OpenGL error

    I am experiencing thesame issues Martins92 had with my AE CS4, An openGL error - [a texture in your file is too small to render] keeps poppin up anytime I try scrubbing on the timeline. I've tried disabling OpenGL in the edit>preference>preview dialogue box, but it still comes up with that error and tells me to close the program. I have even talen the plug-ins out of the adobe folder as directed in the OpenGL troubleshooting page, but no change, the error still pops up? Dont know what to do.

    Well, if Matrox advise it, then there must be a reason for it. If it realyl bothers you, I recommend you create a second hardware profile for your Windows. Go to your device manager (right-click My Computer --> Manage), disable the Matrox card, safe this set as a new configuration. Then in your startup options (right-click My Computer --> Properties) make sure it is set to show the menu during boot so you can chose a configuration. You can also simply press F8 during startup to get access to the hardware configs selection. Without the card being active, you should be free in your decision to set the comp length, you just won't be able to use the Matrox stuff...
    Mylenium

  • CS4 Redraw without OpenGL

    Hi I just installed the CS4 Photoshop and have a major issue which makes it impossible for me to use cs4. I used to work with cs3 on the same machine and had not a single problem:
    Even though I disabled the OpenGL Feature I have an about 100 pixel redraw when I use a brush. Everything else is fine! When I turn OpenGL on it gets even worse.
    Is there any solution for this?
    (Yes I already downloaded the latest drivers and downloaded the patch and resteted all settings)

    I am running ps on a notebook with quiet good hardware:
    2.4 Ghz Dual Core
    3 Gb RAM
    Nvidia GeForce 8600M GS 512 MB
    Vista 32bit
    I already switched from Aero to standard-style but again no changes.
    Just to say it again: The problem is not OpenGL related. At least not in the first place. It also occurs when I disable OpenGL. And that is what botheres me!

  • CS4 eating Tiger HD

    I know I'm not really supposed to be running CS4 on a 867 mhz G4 Tiger - so it's not surprising I'm having problems
    and I keep asking my boss to buy me a new computer but so far no joy
    Anyway when I open a large psd e.g. 1.5 gb it immediately eats up 10 gb of hard disk space on the start up HD.
    Thing is I do not have my start up disk designated as a scatch disk.
    Only my external FW which has about 800 gb spare.
    I only have 20 gb spare on the start up HD so I keep getting warnings my start up disk is full.
    Why is this happening when it is not a scratch disk?
    thanks
    Pete

    Not sure what you mean by 'memory settings'.
    I have maximum RAM installed for this computer which is 1.25 gig.
    RAM usage set to 900 mb in Photoshop.
    Yes there are 3 or 4 smart objects in each psd file.
    Would this cause the problem?
    thanks
    Pete

  • CS4: no image in main window when using openGL

    I am using Photoshop CS4 on a 32bit vista Q6600. When I installed CS4, I had a graphics card based on a 8600GS. Photoshop run fine, even in openGL.
    Not I upgraded the graphics card to a 9600GT for better performance. CS4 still starts, but when a photo is loaded, the photo appears correctly in the navigator, but the main window where the photo usually appeared remains grey, as the background. When moving around this window, the photo appear, but as soon as I release the mouse button, the window turn grey again...
    When I deactivate openGL in CS4, everything seems to work.
    I am having the latest NVidia drivers installed 178.24 (with both graphics cards).
    I tried to reinstall the driver, no change.
    I tried to reinstall CS4, no change.
    Anyway of getting CS4 work in openGL with this 9600GT?

    You are right.
    As the old graphics card based on 8600GS used the same driver as the 9600GT I started to have a closer look and found the only difference, the additional ASUS tools. Once uninstalled, using just plain nvidia drivers, CS4 worked as expected.

  • CS4 NOT capable of sharp displays at all zoom levels

    I must have been asleep, until now, and missed the significance and importance of what follows.
    In post #11 here:
    http://forums.adobe.com/thread/375478?tstart=30
    on 19 March 2009 Chris Cox (Adobe Photoshop Engineer - his title on the old forums) said this, in a discussion regarding sharpness in CS4:
    "You can't have perfectly sharp images at all zoom levels.". Unfortunately, my experience with CS4 since its release late last year has repeatedly confirmed the correctness of this statement.
    What makes this statement so disturbing is that it contradicts an overwhelming amount of the pre- and post-release promotional advertising of CS4 by Adobe, to the effect that the OpenGL features of CS4 enable it to display sharp images at all zoom levels and magnifications. What is surprising is that this assertion has been picked up and regurgitated in commentary by other, sometimes highly experienced, Ps users (some unconnected with, but also some directly connected with, Adobe). I relied upon these representations when making my decision to purchase the upgrade from CS3 to CS4. In fact, they were my principal reason for upgrading. Without them, I would not have upgraded. Set out in numbered paragraphs 1 to 6 below is a small selection only of this material.  
    1. Watch the video "Photoshop CS4: Buy or Die" by Deke McClelland (inducted into the Photoshop Hall of Fame, according to his bio) on the new features of CS4 in a pre-release commentary to be found here:
    http://fyi.oreilly.com/2008/09/new-dekepod-deke-mcclelland-on.html
    Notice what he says about zooming with Open GL: "every zoom level is a bicubically rendered thing of beauty". That, when viewed with the zooming demonstrated, can only be meant to convey that your image will be "sharp" at all zoom levels. I'm sure he believes it too - Deke is someone who is noted for his outspoken criticism of Photoshop when he believes it to be deserved. It would seem that he must not have experimented and tested to the extent that others posting in this forum have done so.
    2. Here's another Adobe TV video from Deke McClelland:
    http://tv.adobe.com/#vi+f1584v1021
    In this video Deke discusses the "super smooth" and "very smooth" zooming of CS4 at all zoom levels achieved through the use of OpenGL. From the context of his comments about zooming to odd zoom levels like 33.33% and 52.37%, it is beyond doubt that Deke's use of the word "smooth" is intended to convey "sharp". At the conclusion of his discussion on this topic he says that, as a result of CS4's "smooth and accurate" as distinct from "choppy" (quoted words are his) rendering of images at odd zoom levels (example given in this instance was 46.67%), "I can actually soft proof sharpening as it will render for my output device".
    3. In an article by Philip Andrews at photoshopsupport.com entitled 'What's New In Adobe Photoshop CS4 - Photoshop 11 - An overview of all the new features in Adobe Photoshop CS4',
    see: http://www.photoshopsupport.com/photoshop-cs4/what-is-new-in-photoshop-cs4.html
    under the heading 'GPU powered display', this text appears :
    "Smooth Accurate Pan and Zoom functions – Unlike previous versions where certain magnification values produced less than optimal previews on screen, CS4 always presents your image crisply and accurately. Yes, this is irrespective of zoom and rotation settings and available right up to pixel level (3200%)." Now, it would be a brave soul indeed who might try to argue that "crisply and accurately" means anything other than "sharply", and certainly, not even by the wildest stretch of the imagination, could it be taken to mean "slightly blurry but smooth" - to use the further words of Chris Cox also contained in his post #11 mentioned in the initial link at the beginning of this post.
    4. PhotoshopCAFE has several videos on the new features of CS4. One by Chris Smith here:
    http://www.photoshopcafe.com/cs4/vid/CS4Video.htm
    is entitled 'GPU Viewing Options". In it, Chris says, whilst demonstrating zooming an image of a guitar: "as I zoom out or as I zoom in, notice that it looks sharp at any resolution. It used to be in Photoshop we had to be at 25, 50 , 75 (he's wrong about 75) % to get the nice sharp preview but now it shows in every magnification".
    5. Here's another statement about the sharpness of CS4 at odd zoom levels like 33.33%, but inferentially at all zoom levels. It occurs in an Adobe TV video (under the heading 'GPU Accererated Features', starting at 2 min 30 secs into the video) and is made by no less than Bryan O'Neil Hughes, Product Manager on the Photoshop team, found here:
    http://tv.adobe.com/#vi+f1556v1686
    After demonstrating zooming in and out of a bunch of documents on a desk, commenting about the type in the documents which is readily visible, he says : "everything is nice and clean and sharp".
    6. Finally, consider the Ps CS4 pdf Help file itself (both the original released with 11.0 and the revised edition dated 30 March 2009 following upon the release of the 11.0.1 update). Under the heading 'Smoother panning and zooming' on page 5, it has this to say: "Gracefully navigate to any area of an image with smoother panning and zooming. Maintain clarity as you zoom to invididual pixels, and easily edit at the highest magnification with the new Pixel Grid." The use of the word "clarity" can only mean "sharpness" in this context. Additionally, the link towards the top of page 28 of the Help file (topic of Rotate View Tool) takes you to yet another video by Deke McClelland. Remember, this is Adobe itself telling you to watch this video. 5 minutes and 40 seconds into the video he says: "Every single zoom level is fluid and smooth, meaning that Photoshop displays all pixels properly in all views which ensures more accurate still, video and 3D images as well as better painting, text and shapes.". Not much doubt that he is here talking about sharpness.
    So, as you may have concluded, I'm pretty upset about this situation. I have participated in another forum (which raised the lack of sharp rendering by CS4 on several occasions) trying to work with Adobe to overcome what I initially thought may have been only a problem with my aging (but nevertheless, just-complying) system or outdated drivers. But that exercise did not result in any sharpness issue fix, nor was one incorporated in the 11.0.1 update to CS4. And in this forum, I now read that quite a few, perhaps even many, others, with systems whose specifications not only match but well and truly exceed the minimum system requirements for OpenGL compliance with CS4, also continue to experience sharpness problems. It's no surprise, of course, given the admission we now have from Chris Cox. It seems that CS4 is incapable of producing the sharp displays at all zoom levels it was alleged to achieve. Furthermore, it is now abundently clear that, with respect to the issue of sharpness, it is irrelevant whether or not your system meets the advertised minimum OpenGL specifications required for CS4, because the OpenGl features of CS4 simply cannot produce the goods. What makes this state of affairs even more galling is that, unlike CS3 and earlier releases of Photoshop, CS4 with OpenGL activated does not even always produce sharp displays at 12.5, 25, and 50% magnifications (as one example only, see posts #4 and #13 in the initial link at the beginning of this post). It is no answer to say, and it is ridiculous to suggest (as some have done in this forum), that one should turn off OpenGL if one wishes to emulate the sharp display of images formerly available.

    Thanks, Andrew, for bringing this up.  I have seen comments and questions in different forums from several CS4 users who have had doubts about the new OpenGL display functionality and how it affects apparent sharpness at different zoom levels.  I think part of the interest/doubt has been created by the over-the-top hype that has been associated with the feature as you documented very well.
    I have been curious about it myself and honestly I didn't notice it at first but then as I read people's comments I looked a little closer and there is indeed a difference at different zoom levels.  After studying the situation a bit, here are some preliminary conclusions (and I look forward to comments and corrections):
    The "old", non-OpenGL way of display was using nearest-neighbor interpolation.
    I am using observation to come to this conclusion, using comparison of images down-sampled with nearest-neighbor and comparing them to what I see in PS with OpenGL turned off.  They look similar, if not the same.
    The "new", OpenGL way of display is using bilinear interpolation.
    I am using observation as well as some inference: The PS OpenGL preferences have an option to "force" bilinear interpolation because some graphics cards need to be told to force the use of shaders to perform the required interpolation.  This infers that the interpolation is bilinear.
    Nothing is truly "accurate" at less than 100%, regardless of the interpolation used.
    Thomas Knoll, Jeff Schewe, and others have been telling us that for a long time, particularly as a reason for not showing sharpening at less than 100% in ACR (We still want it though ).  It is just the nature of the beast of re-sampling an image from discrete pixels to discrete pixels.
    The "rule of thumb" commonly used for the "old", non-OpenGL display method to use 25%, 50%, etc. for "accurate" display was not really accurate.
    Those zoom percentages just turned out to be less bad than some of the other percentages and provided a way to achieve a sort of standard for comparing things.  Example: "If my output sharpening looks like "this" at 50% then it will look close to "that" in the actual print.
    The "new", OpenGL interpolation is certainly different and arguably better than the old interpolation method.
    This is mainly because the more sophisticated interpolation prevents drop-outs that occurred from the old nearest-neighbor approach (see my grid samples below).  With nearest-neighbor, certain details that fall into "bad" areas of the interpolated image will be eliminated.  With bilinear, those details will still be visible but with less sharpness than other details.  Accuracy with both the nearest-neighbor and bilinear interpolations will vary with zoom percentage and where the detail falls within the image.
    Since the OpenGL interpolation is different, users may need to develop new "rules of thumb" for zoom percentages they prefer when making certain judgements about an image (sharpening, for example).
    Note that anything below 100% is still not "accurate", just as it was not "accurate" before.
    As Andrew pointed out, the hype around the new OpenGL bilinear interpolation went a little overboard in a few cases and has probably led to some incorrect expectations from users.
    The reason that some users seem to notice the sharpness differences with different zooms using OpenGL and some do not (or are not bothered by it) I believe is related to the different ways that users are accustomed to using Photoshop and the resolution/size of their monitors.
    Those people who regularly work with images with fine details (pine tree needles, for example) and/or fine/extreme levels of sharpening are going to see the differences more than people who don't.  To some extent, I see this similar to people who battle with moire: they are going to have this problem more frequently if they regularly shoot screen doors and people in fine-lined shirts.   Resolution of the monitor used may also be a factor.  The size of the monitor in itself is not a factor directly but it may influence how the user uses the zoom and that may in turn have an impact on whether they notice the difference in sharpness or not.  CRT vs LCD may also play a role in noticeability.
    The notion that the new OpenGL/bilinear interpolation is sharp except at integer zoom percentages is incorrect.
    I mention this because I have seen at last one thread implying this and an Adobe employee participated who seemed to back it up.  I do not believe this is correct.  There are some integer zoom percentages that will appear less sharp than others.  It doesn't have anything to do with integers - it has to do with the interaction of the interpolation, the size of the detail, and how that detail falls into the new, interpolated pixel grid.
    Overall conclusion:
    The bilinear interpolation used in the new OpenGL display is better than the old, non-OpenGL nearest-neighbor method but it is not perfect.  I suspect actually, that there is no "perfect" way of "accurately" producing discrete pixels at less than 100%.  It is just a matter of using more sophisticated interpolation techniques as computer processing power allows and adapting higher-resolution displays as that technology allows.  When I think about it, that appears to be just what Adobe is doing.
    Some sample comparisons:
    I am attaching some sample comparisons of nearest-neighbor and bilinear interpolation.  One is of a simple grid made up of 1 pixel wide lines.  The other is of an image of a squirrel.  You might find them interesting.  In particular, check out the following:
    Make sure you are viewing the Jpegs at 100%, otherwise you are applying interpolation onto interpolation.
    Notice how in the grid, a 50% down-sample using nearest-neighbor produces no grid at all!
    Notice how the 66.67% drops out some lines altogether in the nearest-neighbor version and these same lines appear less sharp than others in the bilinear version.
    Notice how nearest-neighbor favors sharp edges.  It isn't accurate but it's sharp.
    On the squirrel image, note how the image is generally more consistent between zooms for the bilinear versions.  There are differences in sharpness though at different zoom percentages for bilinear, though.  I just didn't include enough samples to show that clearly here.  You can see this yourself by comparing results of zooms a few percentages apart.
    Well, I hope that was somewhat helpful.  Comments and corrections are welcomed.

  • Printing too dark in CS4

    I have CS4 on Tiger 10.4.11 on a completely color managed system, Epson 4800 printer. Printing seems to be broken in the new version. Prints are very dark. I know to select "Photoshop Manages Color" in Color Handling, and "No Color Management" in the printer color management dropdown. The procedure works fine in CS3.
    That something is up is suggested by this wrinkle. In this case I am printing using advanced b/w. If under color handling I choose "Printer Manages Color" and go into the b/w advanced setup, it's still too dark. If instead I choose "No color management", then make my choices in advanced b/w, it works fine.
    One would first think that it's a double color management problem, but I'm turning it off anywhere I can see it in CS4, and still having problems. Is there a new secret handshake I haven't puzzled out yet?

    > So, Eric, you are saying we need to Convert to a space (or gamma) in
    > Photoshop before Command+P -- because the Epson Adv B&W driver will
    > assume a color space/gamma -- what would that assumption be based on
    > (gamma of our Mac default MonitorRGB)? Assuming I am not talking
    > about feeding the Epson grayscale.
    Yes.
    The ABW driver wants to be fed gamma 2.2-encoded image data.
    This is why my standard recommendation for printing to the ABW driver __ONLY__ is to use:
    Color Handling = Photoshop Manages Colors
    Printer Profile = Adobe RGB
    Rendering Intent = Relative Colorimetric
    Black Point Compensation = Enabled
    Why does this work? Because no matter what your image working space is (e.g., sRGB, Adobe RGB, ProPhoto RGB, Apple RGB, ColorMatch RGB, etc.), doing this will cause your image data to be encoded in gamma 2.2 before the data gets passed off to the driver. (Adobe RGB has a gamma encoding of 2.2.)
    The same workflow will work in Lightroom, too. You just need to check the "Display Profiles" checkbox in Lightroom to access Adobe RGB when selecting a printer profile.
    If you are in grayscale mode instead of RGB mode, choose "Gray Gamma 2.2" instead of "Adobe RGB" for the printer profile.
    However, the catch is that -- as noted in this thread -- there is currently a glitch, which we (Adobe + Apple + Epson) are investigating. One of the symptoms of that glitch is that the above suggested workflow does not work on Leopard.
    > Does this CS4-Apple-Epson issue have anything to do with some users
    > reporting dark prints in Photoshop Manage Color - No Color
    > Adjustment Epson workflow? -- For example, someone using 1.8 gamma
    > Monitor RGB...
    Unlikely.

  • Problems with CS4 Locking up after File I/O

    I am running:
    Vista Ultimate Service Pack 2
    Photoshop CS4 with the opengl off
    Problem: When I either create a new file or open an already established file the program becomes unresponsive. It locks and hangs. I have read through and tried the KB article that I was giving by support. I have not been able to figure out what is going on. As far as I can tell all of the services that should be running are. Is this a permissions issue with the OS? Just don't know. Please help if you can.
    Thanks,

    You can right click on the .exe file and choose properties, then compatibility, and select run as administrator.
    Also try the ole fix all reset the prefs in this attachment:
    http://forums.adobe.com/thread/375776?tstart=0

  • Is DW CS4 Mac super buggy?

    Or do I need to reinstall it or something? Sometimes I can click on the css rule and click 'edit' and a window will come up. Other times it won't. Some times Live View will work sometimes not. And so on and so on.
    Are there a slew of existing bugs with the Mac version? I've run all the diagnostic utilities and my computer is fine G5 10.4.11 4gb ram. Loads of drive space.
    DW has been buggy since day 1. Yet the other programs in the package seem fine. Could it be that I never uninstalled DW 2004?
    Would like to hear from other Mac users.

    While 10.4.11 does meet the system requirements I will be honest that I've never had a problem with CS4 until I moved to a new Macbook Pro with Snow Leopard but those were patched by 10.6.2.  With that said, I never ran CS4 in Tiger, only in Leopard and never had an issue.

  • Travails on CS4 Trials

    Since I recently upgraded my HW , it seemed appropriate to try CS4 again.That turned out to be a real exercise!
    First off, I get an 0x50 Stop message as I was beginning to configure Bridge, when I did a quick exit to see what I set up in PS. It never happened again so I went on. The Stop messages now changed to 0x08E. Careful inspection of the message ID'd NV4_disp.dll, the nVidia driver which I updated when I configured the new installation. CS3 Bridge has no problem with it, but CS4 does. Since it is a BSOD continually, I rolled back the driver. Now, Bridge runs ok, CS4 still runs OpenGL, but now CS$ appears not to really like that driver as I get erratic behavior like when moving the Window after engaging Float all Windows (I hate the default opening!) the image disappears unless I open something else or after moving it around for a while and clicking like mad, I get the image back and it is stable.
    The second problem so far is the CS4 Bridge icon in the startup tray. If that is lit, I cannot open CS3 Bridge. Photoshop opens ok, but in order to open Bridge CS3, I have to exit CS4 Bridge first, which, incidentally is how I got the 0x08E stop! There is no way to permanently eliminate it from showing up because if you open CS4 Bridge at all, it sets the Startup icon no matter how Bridge  (and msconfig) is configured.
    Since I also have BSOD when I installed CS3 (see http://forums.adobe.com/thread/540226?tstart=60), which also was traced to starup problems, I can only conclude that for my system outlined in the link, inadequacies have crept in for older programs running on newer platforms, and some older peripherals as well.
    I have all the updates to CS4 and ACR.
    On a positive note, CS4 Trial installed without a hitch and fast, around 5 minutes or so, which was nice to see. Also, my complaint with the brush disappearing in cerain color and values seems to have abated.
    I guess I am stuck with CS3 for the forseeable future. That's not too bad, and hopefully, CS5 will cover all these bases nicely.

    Been there Done that. Makes matters worse.
    From what I can see, it seems to have to do with redraw, because as I decrease the acceleration, now it only redraws part of the image, tiling from top to bottom. Not all the tiles are present. If I drop to basic acceleration (one step above minimum) nothing redraws except box outlines.
    On another front, I mentioned the Bridge Startup problems. I have been looking at that too, and neither will open if the other already is. So I went into the prefs on both, had only Bridge and Photoshop checked in CS3, and most checked in CS4. So I picked only Bridge and PS there also.
    Problem went away.
    But hold on! There's more! Now if Bridge 4 is running and minimized, opening CS3 Bridge maximizes CS4 and doesn't open.If CS3 is open, nothing happens trying CS4. It doesn't maximize a minimized CS3 either.
    There's still more! Now enabling everything or most everything in CS4 Bridge does not restore the problem. I may consider the update again.
    This all can have roots in the video I suppose, but since I am going to wait for CS5 and Win7 and a real computer update, I'll have to wait for then. By that time, advances on all fronts are to be expected; a new video card is in the budget, but I haven't the foggiest which one!
    On second thought, I don't want BSOD again so forget the update to the video.

  • Bridge CS4 color management only works with GPU active

    When I turn hardware acceleration off (by selecting software rendering in Bridge advanced preferences) Bridge color management disappears and on my wide gamut display I get cartoon color thumbnails indicating that CM isn't working. With GPU rendering on and Bridge restarted, CM works as it should.
    It seems that Photoshop requires hardware acceleration with the "color compensation" option checked under the Performance/Enable OpenGL Drawing/Advanced settings preference.
    Is color management now only functional with OpenGL acceleration enabled? I can find no help documentation for the advanced OpenGL Drawing settings. What a huge can of hardware worms this is turning out to be.

    I wouldn't think that Bridge needed the GPU for CM, yet bypassing the GPU turns off CM in this installation.
    I'm still confused about what you indicate in the Photoshop CS4 thread on OpenGL.
    Chris Cox, "A few questions about OpenGl acceleration" #14, 11 Nov 2008 7:31 pm
    I interpret your comment as suggesting that disabling color compensation in the PS CS4 GPU debugging features should disable CM in Photoshop, but it doesn't, it just makes it unreliable in displaying images post profile conversion in my tests. I'm probably missing some nuance here.

  • Brush pressure and lag problem with CS4

    I've been having a huge problem with Photoshop CS4 and the brushes. Whenever I go to brush, the pressure will turn off and on randomly with each stroke, and it lags horribly. I've installed CS4 on two computers with Windows 7, and both have this problem, but my old computer which had Vista was perfectly fine. I've tried downloading new versions of CS4, turning the OpenGL on and off, updating the GPU, downloading the Windows 7 tablet driver (that made it worst), and a bunch of other things. Nothing has worked, and this problem has been going on for two months. I'm starting to think the only way to fix this problem is by switching back to Vista. Can anyone please help me solve this? Thank you.
    My computer is an HP that runs on Windows 7, my Tablet is a Wacom Intuos3, and I have Photoshop CS4 Extended 11.0.2

    Others have reported that completely removing the tablet driver(s) first, then installing the very latest from the Wacom web site have made things work.
    Good luck.
    -Noel

  • Photoshop cs4 doesn't refresh

    i'm having a problem with my photoshop extended cs4, it doesn't refresh by turning layers on and off, as well as undo and redo (can't see changes directly, have to click somewhere on the image before refresh)
    i tried to update my video drivers but still no luck, btw my gfx is ati radeon x1400 mobile (lenovo t60), i tried to turn it Enable OpenGL Drawing on, but by so, it causes my image to be broken (square everywhere), so i turn it off.
    anyone with the same problem here? adobe please release a fix for this.

    I am having the same problem as Adrian does. The thing is I'm using Nvidia GeForce GTX 260 and updated the driver. I have also reinstalled CS4, turned off OpenGL, and have tried everything but still it doesn't work. This problem occurred about a month ago but i didn't notice anything different before and after the occurrence of the problem. Please help.

  • CS4, GPU, and XP x64

    Looking at requirements I have some ?s:
    1. Can I run 64-bit CS4 on XP x64?
    2. Is CS4 supported on XP x64 or do I have to move to Vista x64?
    3. What GPU does CS4 recommend to use?
    Thanks!

    >Jeff Rozar:2. Is CS4 supported on XP x64 or do I have to move to Vista x64?
    Adobe engineers have answered that question on this forum in the past. To paraphrase, they say PS CS4 is
    not supported on XP64 because they have identified a lot of issues with XP64 and Microsoft's position is that they are not going to fix them. Many, but not all, of those issues are in the OpenGL arena--some are in basic areas of Windows--Adobe didn't elaborate on specifics.
    Basically the situation is that many users have said they are using XP64 with PS CS4. Some are having problems, some are not. Adobe does not support PS CS4 on XP64 so you will not get help from Adobe--though they did release a registry hack that
    may allow OpenGL features to work with
    certain video cards. This registry hack basically tells PS CS4 to use OpenGL even if the driver says it doesn't support it. However, if you do insist on staying with XP64 and do install PS CS4 you will likely have some problems and to solve those problems you're on your own.
    I didn't bother to try, I went from regular XP to Vista Ultimate 64 and PS CS4 runs just fine on my machine.

Maybe you are looking for