CS3 improvements ...

Can anyone tell me if there have been any improvments to the
code view in
CS3? Examples:
- a "Functions" panel for PHP, etc...
- Some way of connecting up my code to php.net for reference
(so I can
right-click a php function and bring up the php.net page)...
- code completion for PHP (in DW8 I need to press ctrl+space)
- anything else that looks promising for coding in PHP, CSS,
or JavaScript?

There have been minimal improvements in any of the coding
functions in CS3.
Paul Whitham
Certified Dreamweaver MX2004 Professional
Adobe Community Expert - Dreamweaver
Valleybiz Internet Design
www.valleybiz.net
"Alexander Ross" <[email protected]> wrote in message
news:f1kpvn$8ip$[email protected]..
> Can anyone tell me if there have been any improvments to
the code view in
> CS3? Examples:
>
> - a "Functions" panel for PHP, etc...
> - Some way of connecting up my code to php.net for
reference (so I can
> right-click a php function and bring up the php.net
page)...
> - code completion for PHP (in DW8 I need to press
ctrl+space)
> - anything else that looks promising for coding in PHP,
CSS, or
> JavaScript?

Similar Messages

Does DW CS3 write better php than DWMX2004?

I have been using DWmx2004 and been told that the User
Authentication code it writes for User Authentication (and other
Server Behaviours?) is outdated and incompatible with PHP5. It
certainly seems to lead to error reports and problems. Does DW CS3
improve on this?

Yes.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"smiffy47" <[email protected]> wrote in
message
news:ga1gov$qo3$[email protected]..
>I have been using DWmx2004 and been told that the User
Authentication code
>it
> writes for User Authentication (and other Server
Behaviours?) is outdated
> and
> incompatible with PHP5. It certainly seems to lead to
error reports and
> problems. Does DW CS3 improve on this?
>

Does DW CS3 write code to process CDO forms?

Thanks.

Yes.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"smiffy47" <[email protected]> wrote in
message
news:ga1gov$qo3$[email protected]..
>I have been using DWmx2004 and been told that the User
Authentication code
>it
> writes for User Authentication (and other Server
Behaviours?) is outdated
> and
> incompatible with PHP5. It certainly seems to lead to
error reports and
> problems. Does DW CS3 improve on this?
>

Color picker improvement after CS3?

Dear forum:
Am using ID3 (v5.0) for first time and like it alot. But color picker is obnoxious. Does this get better in CS4 or CS5? Also- text stroke: can I align text (center, inside, outside) stroke in CS4 or CS5? Only option in CS3 seems to be: stroke aligns on outside of font. Thanks, Kip............

Much thanks for replies.
At this point, color picker still seems counter-intuitive to me. My initial reaction was: probably after spending time learning it, I will figure out its concept, and be able to use it. I believe there must be reasons that make sense for its features. I've spent about 45 minutes more fiddling with it, and I still haven't got it. At least I see now that it's not just me- looking in this forum and randomly web-searching ID color picker opinions shows me that it is one of ID's most unpopular features. I am still going to keep trying- as I said earlier, there may be some logic to it: I just have to discover it.
My uses are relatively simple: the eye dropper is not as important to me because I'm trying to create/modify colors- not match them (yet). I am looking into more user friendly color picker plugins- any advice/success?
On the text inside stroke issue. I like fonts from movie titles and posters from 50's film noir and B movies. They seem to be bold Furura family fonts (BTW, does anyone know if there are names for these fonts- Adobe making them?). These are already so bold/wide that outside stroke only takes them over the edge. In these cases, stroke seems only appropriate inside. Also, outside stroke changes the shape of the actual font and its relationship to its neighboring letters. I know I can use some sort of outline/path process, but was hoping that the program would do it without us going thru the extra hoops. I may get CS4 or 5 for this reason. For those of you that want to do inside, outside, and center stroke on text, what is your favorite method?
Thanks, Kip...........

New, improved problem with Photoshop CS3 Clone Stamp Tool

After selecting the clone area with the Alt + L Click, I then release both and press the L Click to get the brush. The + symbol moves along beside the brush. It does not stick at the area that I alt clicked. I have reset the tool, but that has no effect. I have tried the alt-click more than once. Tha pallet does show an offset and has a clone source chosen. It just doesn't stick at the location.
Any help is appreciated.

If I understand you correctly, you may have a system problem (e.g., with OpenGL) if the clone stamp overlay is not confined to the brush shape.
Normally, this is what you see (cloning from the right to the left with a round brush):
If it's not working this way for you, I suggest downloading and installing the latest display driver from the web site of the maker of your video card, and also experimenting with the OpenGL settings in your Edit - Preferences - Performance menu.
CS3 did not offer the clipped Clone Stamp overlay. That's an OpenGL-specific feature, and only Photoshop CS4 and above have the OpenGL support needed.
-Noel

Photoshop CS3 - Program error. Crashes when working off active desktop

Unprovoked my version of photoshop CS3 has suddenly started to crash whenever I click off the active workspace (for example clicking on my desktop or moving into the dock).
After force quitting the application I can open photoshop again and continue working until I move onto another application or select any function outside photoshop. Then it crashes again.
Tried reinstalling but with no improvement.
OSX 10.5.2
G5 mac
lots of memory.
Thanks.
Any help or advice is appreciated.

Leopard is really sucky isn't it?

CS3 issues fixed in CS4?

Have the following issues in CS3 been fixed in CS4:
(Note: a few of these I've found already in the forum, but I am including an all comprehensive list anyway).
1. Self resizing title pane.
2. Still tiff image import incorrectly interpreted as an image sequence.
3. Crash when exporting timeline directly to encore for disc burning.
4. Audible clicks at audio edit points in final render.
5. Missing shortcut menu items.
6. Crash on rendering directly to cineform HD file (vs. AVI with cineform as compressor).
7. Crash on rendering tiff images when more than one layer of images overlaps, (work around is to render images as video clips and replace - a pain).
In the past three years I've upgraded three times and I'm getting tired of drinking the cool-aide.

I agree that moving AME to standalone was a good decision. But I've been cntl-shift-Ming frames for years. Handing that chore off to a separate application is like swatting flies with a canon.
How does CS4 handle single tiff images? I render animations as image sequences and edit in CS3. It's no issue if I import those sequences as image sequences (selecting the image sequence checkbox). However, CS3 treats single image files from sequences as single frame video clips. I have to copy the image to a separate folder and re-import.
The bigger issue is that I'm fed up with three complete upgrades and have not had any significant improvement. I recall having better results and smoother workflows with CS 1.3.1.
I'm only two projects left open on CS3, then I have to make a serious decision and maybe demo that Studio 2 package my local mac vendor has been bugging me to do.

OpenGL, nVidia 8600M GT 128mb and After Effects CS3 8.0.2

I've just sold my one year old macbook and bought a new (not so new now, revision C), 2.2 ghz nVidia 128 mb macbook pro.
I did that cause I work with After Effects and thought a bigger screen and dedicated graphics with OpenGL would improve my performance. Sure it did, mainly because I jumped from 1g RAM to 2g in the new computer.
But I'm experiencing a irritating bug that makes AE crash. I've searched in forums, adobe website itself, upgrade to 8.0.1, 8.0.2, made the Nvidia update via Software Update from Apple, and the problems keeps going.
It is mentioned in this document from Adobe: http://kb.adobe.com/selfservice/view...2244&sliceId=1
"After Effects error: AE_OpenGL: Create texture error. (5065 :: 0)"
In the solutions proposed in the document it says: "Disable OpenGL", "remove OpenGL plugin" and "Optimize the Texture Memory preference", among other things.
Disabling OpenGL wouldn't make my new graphic card useless in this case ? In the document, Adobe says I wouldn't have problems setting the Texture Memory preference because OSX makes it automatically. But at the same time says that the ideal should be 80% from my memory. If I have 128, 80% is 102.4, right ? My config is set to 114. Have OSX failed calculating ?
Thanks, and sorry for the long thread.

There is a lot of conflicting and/or otherwise terrible info being posted as workarounds to getting the ae cs3 801 and 802 update to actually install. I have read everything from reinstalling the entire creative suite, to writing a custom script that disables the app running list in the config.xml. Hahaha what?! Tech support seems to need a week off...
Ok here's how to get it to install:
#1: go here and delete everything in it--> **user>appdata>local>temp>patcher** (this is in Vista...xp users will get there via c:\docs and settings...)
#2: install the update (it will fail
#3: go to **user>appdata>local>temp>patcher** again and you will see 2 new folders named PATCHER[some number here; ex: Patcher470]. Look in these for a folder named INSTALLER. Once you find it, double click on:
PatcherApplication
Voila- ae cs3 will now update to 8.0.2.
It's as easy as that.

CS4, reverting to CS3 (and getting a refund!) but still interested in opinions

I've just spent the last 24 hours trying to muscle my way through the myriad of problems I'm finding with CS4. I've managed to alleviate some, but still can't produce my end video.
To start off, I'm running on Windows Vista. All the problems seem to centre around Media Encoder (although I didn't get far enough to play with Encore or On Location).
Initial problems where to do with installation. If CS3 is removed after CS4 is installed the link to Media Encoder fails, you then have to removed CS4 and reinstall. Uninstall doesn't work correctly or completely, it leaves a fair amount of files behind that have to be manually removed, failure to do so resulst in Error 2 on reinstall (I'm guessing because the install tries to create some of the working directories, and fails because they are already there?).
After reinstallation, the job appeared correctly in Medie Encoder when it was fired up from Export in PP, and it was also now possible to add files to Encoder directly. I tried a test run of my project with the following settings:
H264
Width : 1280
Height : 720
fps : 25
Field order : Progressive
Quality : 4.0 and 5.1 (tried to runs)
Bit rate : can't remember, but atleast 12M for target and perhaps 30M for max?
VBR 2 pass
Sound : AAC
The end video was incredibly jerky.
I tried a second time using the following settings:
Quicktime
Codec : H264
Quality : 100
Width : 1280
Height : 720
fps : 25
Field Order : progressive
Pixel Aspect : square
Use maximum bit depth ticked
Bit rate : 1k (I tried to move this to 5k however it kept reverting back)
Sound : AAC
Export from PP initially failed, the job appeared in the queue, however nothing actually happened, it just sat there. I read on another post that updating Quicktime to 7.5.5 fixes that (does PP rely on Quicktime for the codec?), tried and the job then started.
Upon completion, the video played smoothly, although quality was low (low bit rate?). However the video to audio sychronisation was completely out. 30 seconds of play, and the sound was around a second behind the video.
I then tried applying all of the updates. As with other people, the Encoder portion failed initially (even though I started the update process from Encoder), but then succeeded the second time.
Upon completion of the updates, the problem reverted back to the initial, i.e. the job started OK, but didn't actually do anything.
The render settings I'm using are required by the web site I'm trying to create this video for, and also worked without issue in CS3.
It would seem to me that the Media Encoder portion in CS4, on the Windows version atleast, is seriously flawed (and no, I'm not going to buy a MAC ;-)).
I would like some answers to these problems, despite all the issues, I did like the overall look and feel of the product compared to CS3, and I also now need the AVCHD support.
Forgive any innacuracies in the phrases used, settings etc, CS4 has been removed from my system for now, so it was all from memory.

Stuart,
Maybe I'm just too old and have seen too many "revolutions," to get onto that wagon.
However, the more I follow CS4 threads, the more I am starting to question whether I will upgrade from CS2, or not. Some things look useful to me (more than with CS3), but then there are the problems.
Adobe IS listening, as evidenced by a few of the folk on the team dropping by to give info on updates, etc. Having some major "fixes" so soon upon release, indicates to me, that they are working on it.
I didn't move to CS3 for similar reasons. Also, it really did not offer ME much in the way of useful features.
Whether it's through bug reports, posts in the forum or direct correspondence with Adobe, the best way to get their attention, and provide them with useful data, is to offer as much detail on the specific problem(s) as one can and demonstrate repeatability. General posturing might make one feel better, but does little to get improvements in the program.
As you state, some of the problems are probably OE. Some are system specific, and others are related to 3rd party software. Still, there do seem to be a lot of issues that ARE CS4-specific. These worry me. These are the issues that I would like to see Adobe address. So far, they seem to be, albeit maybe not quickly and efficiently enough for many users. CS4 does seem to be more of a "work in progress," than I am willing to take on just yet, especially as it would also likely mean a new workstation and new OS (one that is not without some problems of its own and a new learning curve also).
I'm fortunate enough to have CS2 and a rock-solid group of systems to use it on. It does 95% of what I'd like for it to do, and that extra 5% has yet to intice me, especially with the "problems" that I've been reading about.
As for the Adobe faces in the forum, they have shown up, when they could actually tell us something. I view that as a very positive sign. Even when they have dropped in, too many people demand to know "WHEN?" something will be fixed. If they knew, they'd tell us.
I'm sorry that CS4 has not gone more smoothly, upon release. It saddens me greatly. However, it is also why I will be waiting and keep reading. For me, this will be an upgrade that will be very expensive, because it's not just the software. I hope that Adobe does get it all running and running smoothly.
I would anticipate, and hope, that the next update fixes most of the issues. I anticipate, and hope, that Adobe will provide us with the same sort of info on it, as they have done with 4.0.1 & AME's update. I also hope that the forum subscribers will concentrate on the info provided and cease with the "WHEN?" The Adobe posters do not know yet, as the coders are still working on it. It *seems* that rushing to meet a product release date might have gotten us into this trouble to begin with.
My fingers are all crossed. Maybe 4.0.2 will signal that it's time for me to make the jump.
Hunt

Open .psd in FW CS3 and maintain paths?

I have a .psd file that when I open in FW CS3 it maintains all the layers just fine, but when I go to click on an object like a box it just shows as a bitmap rather than a path. So I can't edit the color or size.
Any workaround?
thanks much,
Justin

justinae wrote:
really? That's a bummer. Seems like the whole concept of a suite isn't exactly working out if you loose the ability to edit content on platforms that are meant to stream line the process from design to web.
You need to remember that Fireworks and Dreamweaver came to Adobe through the merger with Macromedia. While FW and DW always worked well together, the products of the two companies were not designed to interoperate. Historically, one would design in Fireworks and code in Dreamweaver.
Since the merger, Adobe has been working to improve interoperability between Fireworks and Photoshop (and also Illustrator) - mature applications with different approaches and code bases. There's a lot of code to revise and improve so that FW can read all PS effects and so that PS can read all FW layers. They're working on it.

Which? CS3 or Elements for HV20 24p work?

Hello:
I am an ELements user and I was made an offer to upgrade to Pro CS3 for $299. Will this upgrade buy me anything?
I have a Canon HV20 and the big pain is the 24p workflow. Does Pro CS3 offer any improvement over pulldown? I can see various 24p related options in Elments (grayed out and disabled of course) so it leads me to think that maybe working with this footage is easier.
Advice needed!
peace|dewde

> I have a Canon HV20 and the big pain is the 24p workflow.
Whatever you decide, keep in mind that HDV is a delivery format. Editing is
often easier when editing in a (drum roll please) editing format.
Best,
Christopher

Epson Printing Problem with CS3

My Epson Stylus Pro 9600 has a problem with CS3 printing. When printing large images (i.e. 36x60) a portion of the image would be missing at the bottom (blank) The 10.01 update addressed this issue but it seems not completely. The problem was attributed to using a "Custom" print resolution however I still have this problem and after much testing I have narrowed it down to the "Finest Detail" check box under the custom, advanced tab. Checking this "Finest Detail" check box reproduces the problem.
I'm not sure where the problem lies whether it be Photoshops new stripped down print code or Epsons drivers. For the mean time I will keep this feature de-selected. Hope this helps other frustrated Epson Owners.
Vista 32, dual quad xeon 2.33
Photoshop CS 3.3 Extended (Masters Collection)
Epson Stylus Pro 9600, Drivers ver 5.52, current printer bios

Adobe blamed Epson drivers for not anticipating CS3's changes. Like they're clairvoyant or something. Their reason was that it was too hard to take into account every printer on the market when writing the new (unasked for) CS3 printing module. A feeble excuse when it comes to Epson pro machinery, though - it is the industry standard, after all.
Solution? - use CS2 for printing, authored back when Adobe wrote its software to be compatible with existing equipment and drivers, not expecting the world to fall into line with whatever it decided it would do. CS2 works flawlessly with my 7800, CS3 remains a basket case for the same reasons you mention, though checking/unchecking the fine detail box makes no difference. CS3 is erratic - sometimes it works as directed, but then out of nowhere it will suddenly decide to attenuate a pano print.
We'll see if they get it right with CS4's "improved" printing, but don't hold your breath.

Premiere Pro CS3: Many Problems Fixed By Upgrading to Windows 7 Pro 64-bit

I recently installed an SSD drive and Windows 7 Pro 64-bit.
Installing the Adobe Master Collection CS3 went smoothly and only took a few minutes instead of an hour, as in the past.
Premiere, for the first time in the years I've used it, runs STABLE. Not only that, but I can have AfterEffects open at the same time. And Maya 2008. And everything chugs along smoothly.
Case in point tonight: Multicam Editor: Under XP, it worked, but the quality of the video displays would be badly pixellated when video was playing. Under Windows 7, all the four viewports plus the 'online' viewport are sharp and clear and I can see if a camera is slightly out of focus, which was impossible to detect in the past until I watched the finished result.
The audio dropouts everyone complained about for years are a thing of the past.
And here's the biggie: I can render, render, render and keep rendering h.264 files and Premiere keeps ticking. Under XP, 2 to 3 files and that's it. Unknown Error would be the next render result. Under W7-64, I rendered all night and day without shutting or restarting Premiere, and I even had Maya and AE going and was working in them at the same time, something I could never do in XP because it would run out of RAM. And I can do this in 4GB ram! With 8GB, AE renders 3.5X faster, but most other programs remain about the same. I figure in the case of AE, it has EXCLUSIVE use of 4GB ram all to itself on an 8GB system. At any rate, die-hard CS3 users, don't be afraid to upgrade to Windows 7 64-bit.
The only thing you need to do differently is put the Postscript fonts in Adobe's fonts folder, as it won't see the Windows\Fonts-located PS fonts.
My 2008-vintage editing workstation breaths new life, like a major hardware upgrade was done. The "$139 system performance upgrade" I call it. (Sure, adding the Intel 320 SSD helps, but mainly with launching programs--once they're running, the main improvement comes from Windows 7 64-bit.)

Actually, Win8 is really not a tablet OS... it is "essentially" Win7 with a different front end http://forums.adobe.com/thread/1101032
Anything other than a new Win8 "app" runs on the same kind of desktop you see with Win7

Errors galore in DW CS3

I have been developing with DW since 1.0 and have upgraded
through every version. I have been trying to use CS3 since its
release, however I find that due to so many issues I revert back to
DW8.
CS3 - Crashes continuously - Yes I deleted the appropriate
file and restarted. It is better but still crashes.
CS3 - I open an existing webpage and try to apply a new
behavior, any behavior - Sorry making this change would require
changing code that is locked by a template or translator. This
change will be discarded.
CS3 - Tried to implement the highly touted Spry assets - a
ton of extra work for an extremley boring effect.
CS3 - Yep, just crashed again.
CS3 - Never imported all of my site definitions and ended up
having to re-set them up - about 40 thats a lot of time.
CS3 - In design view when you select a table or element it
places a HUGE measuring tool over the top of the box which blocks
your view and does not allow for you to select anything in that
region.
Honestly, since the move to Adobe this product has quickly
gone down hill. Multiple upgrades with absolutely no reasonable
improvements, yet a less stable application. Not to mention our
complete history of purchases for Macromedia DW purchases and Adobe
purchases have never come together in our online account making
setting up a new computer difficult.
Is this a B$tch session and a rant, yes, absolutely it is.
Its just so dissappointing to have to pay for upgrades that are
totally un-usable. I wonder how many other developers are suffering
these same issues, how many have reverted back to DW 8, how many
have found real value in the last few "upgrades".
I know there are little to no alternatives to DW, or Adobe
products in general.... perhaps this is the problem.
Discovery

> With previous versions it mattered not where you sat an
> html site.
Most likely your previous versions didn't have testing
servers defined.
> If you need to change a server behaviour at all, best to
delete all the
> old
> behaviour code from the page before trying to make any
modifications.
If you are speaking of changing a legacy server behavior,
yes, that's a good
suggestion. If you are speaking of changing a CS3 SB, then I
have not found
this to be the case.
> You need some coding experience to use it properly.
Indeed.
> Adobe could make lots more profit if gave that a bit of
thought.
This is a matter of opinion. I tend to disagree. Publishing a
document
like that is a huge drain on resources.
> Selecting the content of input fields is best done in
code view, as if you
> try
> to do it in design view you have a fifty fifty chance
that any insert will
> be
> in the WRONG place - which often accounts for the
message regarding
> templates
> and translators.
I can't say this has ever happened to me.
> Some browsers will not work in F12 test mode
How bizarre. Which?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"whatalotofrubbish" <[email protected]>
wrote in message
news:[email protected]...
>I also have been using Dreamweaver since around 2002. The
most stable
>version
> was version 3, but then it was a html only program.
>
> Overall, Cs3 is about as stable as MX but it does come
up with lots of
> strange
> errors, such as "Please move this file to your defined
site" - this on a
> file
> created within and saved to the site. Fixed by moving
the html site into
> my IIS
> webserver folder root. With previous versions it
mattered not where you
> sat an
> html site.
>
> If you need to change a server behaviour at all, best to
delete all the
> old
> behaviour code from the page before trying to make any
modifications.
> Then check the code, because as sure as eggs are eggs
there will be
> remnants
> in the page which will cause problems. Not good for
people who have not
> much
> coding experience.
>
> However, I now think that CS3 has moved on so that it is
no longer
> suitable
> for designers to use. You need some coding experience to
use it properly.
> After
> returning to 8 for a while, I bought the Dreamweaver CS3
Bible to read
> while on
> holiday, and found that there was a bit more to CS3 than
met the eye.
> There is
> a lot to say for a proper works manual at a sensible
price. Adobe could
> make
> lots more profit if gave that a bit of thought. After a
long day at the
> keyboard, it is a pain to have to read Acrobat files to
learn about your
> software. Much better with a good book.
>
> Selecting the content of input fields is best done in
code view, as if you
> try
> to do it in design view you have a fifty fifty chance
that any insert will
> be
> in the WRONG place - which often accounts for the
message regarding
> templates
> and translators.
>
> Spry menus are to say the least a little touchy and
unreliable - 1.6
> included.
> I gave up with them and bought a third party extension
from PVII which
> works
> every time with no problems.
>
> The best part of DW CS3 is the CSS and the results pane.
For the first
> time I
> can get a sticker from the CSS people to say my code is
correct css. It is
> also
> compatible with most browsers - according to
Dreamweaver. Some browsers
> will
> not work in F12 test mode, so I have to upload to the
web before I can
> test in
> Opera for instance.
>
> But when the price in the UK is more than double what it
is in the states,
> I
> will be trying a free download very thoroughly before
purchasing the next
> version.
>
> Howard Walker
>

Bridge CS3 ver 2.1.0.100 most buggy bridge ever

With previous versions of bridge for CS3 I had occasional problems. The most vexing was that some Canon xti Camera raw files (CR2) and dng files could not have their file info changed via bridge. When I would right click on these files, the file menu that came up would lack the choice for modifying file information. It was impossible for these few files to use bridge CS3 to get to fields such as document title, author, author title, description, etc.
If I opened the same exact files in the bridge for CS2, it was possible to modify file info for every one of them. The problem files when later opened in bridge CS3 would show the file info put into them with the CS2 bridge--the one that worked. It was still impossible however in bridge CS3 to modify the file info for these occasional files.
I made the great mistake of upgrading to bridge CS3 2.1.0.100. Today I took more than 240 photos. It is not possible to modify the file info for any of them with lousy bridge 2.2.0.100.
The new version also crashes much more often,simply disappearing without any error messages.
In addition, at least some photos whose file info could be accessed via the older version of bridge CS3, no longer allow such access under the newest bridge version.
The new bridge version is a massive step backward.
Open challenge to Adobe--I will be happy to send you 200 plus problem files that only work properly with older versions of bridge. You could use them to fix bridge.
Gateway computer with latest version of Windows xp,
OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 2 Build 2600
OS Manufacturer Microsoft Corporation
System Name GATEWAYNEW
System Manufacturer GATEWA
System Model GM5076E
System Type X86-based PC
Processor x86 Family 15 Model 6 Stepping 2 GenuineIntel ~3199 Mhz
Processor x86 Family 15 Model 6 Stepping 2 GenuineIntel ~3199 Mhz
BIOS Version/Date Intel Corp. NT94510J.15A.0099.2005.1215.1455, 12/15/2005
SMBIOS Version 2.3
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.2765 (xpsp.050928-1517)"
User Name GATEWAYNEW\Owner
Time Zone US Mountain Standard Time
Total Physical Memory 3,072.00 MB
Available Physical Memory 1.96 GB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.95 GB
Page File Space 4.84 GB
Page File C:\pagefile.sys

I have found CS3 less buggy that I expected.
I have found "Bridge CS3" outstanding, but no doubt, some will experience problems.
Experience is great teacher
But I do keep CS2 on my machine for those times I cannot wait for whatever fix might be necessary.
Do not worry.
The problems many are having, whatever that may be, and it is somewhat varied, will most likely be worked out in CS4.
I contribute many of these problems to be lack of control over the hardware that the software must function on. Windows vs. Mac ideologies rear their heads here. I use Windows and that is definitely my problem.
Get used to it.
CS4 whatever = CS3 whatever with most problems fixed.
CS3 = CS2 with most CS2 problems worked out with some tool palette changes users have been asking for years, along with "some" real graphic ability improvement, along with some abilities that probably > 80% of us will never use. Better camera support in Camera RAW.
Most all of this depends on how much money you have to devote to Photoshop, its upgrades , and the cost of the demands for appropriate hardware.
Note:
I was just using the "spelling checker". On this forum "Photoshop" is an unrecognized word. It wants to spell it:
"Photo shop"
or
"Photos hop"
Go figure.
Just my 2 bit opinion which wouldn't buy you a cup of coffee or anything else.

CS3 improvements ...

Similar Messages

Maybe you are looking for