My situation matched only one of your symptoms: the error on closing Bridge. I got the error only when closing Bridge after closing Photoshop. Who knows, the solution I found may solve your problem, too, so check it out.
Open Bridge and press Ctrl-K for Preferences. Click Startup Scripts and, near the bottom of the larger scroll box, make sure Photoshop Services is checked. If that doesn’t cure all, come back to the same window and click the Enable All button. I didn’t have to do that, but then, your symptoms are somewhat different from mine.
Thanks Joe, that helped some, then I found more suggestions on the dpreview forum. I enabled all my scripts and from dpreview I checked the box for "use software rendering". I don’t gert the problem boxes anymore in MS XP Service pack 2 but everyonce in a while bridge still will not open after closing CS3. I found that if I used task manager to close bridge, it works just fine and opens up after every shutdown. This suggestion was also on the dpreview site. Figured i would pass this on just in case it would help msomebody else with similar problems.
Eugene
There are all sorts of ad hoc work-arounds to at least minimise these problems but this is no way for a market leading professional software to behave.
Let’s face it; the higher management at Adobe cocked it up big time releasing CS3 upon an unsuspecting customer base before it was ready.
It’s a great pity there’s no real competitor!
I agree 100%, John. Every product has glitches, but this one sets a new low, handily besting the worst pieces of crap that Microsoft has ever knowingly foisted upon the public.
_______________________________________________
Beta: Latin for "It still doesn’t work."
I’ve got to admit that the ad-hoc refusal of Bridge to open once it had been closed and then requiring a reboot to open was a strange one to me – thanks for posting that tip, Eugene. I was thinking that it was a conflict problem within my machine (and no doubt Adobe would have preferred it that way as well).
I had been ignoring those close-down warning dialogs because they never really made sense or seemed to do anything. What use is a dialog that warns you Bridge has to close when that is what you’ve just done, anyway?
I have to agree with previous comments that there really are some problems with this release.
CS3 Bridge Startup Problem
When I try and start Bridge I get an error message headed Windows-No Disk The body of the message says Exception Processing Message c0000013 Parameters 75b6bf9c 4 75b6bf9c 75b6bf9c
If I click "continue" the message pops up one or two more times and eventually Bridge will open.
Once it opens it’s usually okay, but it’s a pain to start. Any ideas?
I am getting the identical problem to Richard Mittleman (post of May 13)and a reinstall of CS3 has made no difference.
I’d welcome some advice on how to solve it.
I had the same issues with the Bridge "…has encountered an error…" and this was on a fresh install.
However, resetting the (Bridge) Preferences cured the problem and everything runs super smoothly now.
John’s advice (above) re the starting script prefs is good for a "Photoshop only" setup. The only thing different in my own case is that I have Adobe Version Cue checked too, to enable the use of the Adobe "Open" and "Save" dialogues.
As for all the critisism of CS3. I get the feeling most of the problems stem from the fact the Beta has left little bits of garbage behind which is interferring with release version.
I get the feeling most of the problems stem from the fact the Beta has left little bits of garbage behind which is interferring with release version.
Lots of people who did not try the Beta have had problems too Chris.
And I was one of the brave ones who ran the CS3 beta clean utility on both the desktop and laptop, Chris. If they wrote the code for that better than the code for CS3, then there should be no traces of CS3 beta on my machines, but I still had all the problems.
Particularly with printing and Bridge’s silly closing idiosyncracies.
I also had the shutdown problem. I did a repair reinstall of the whole CS3 stuff, reset all preferences, and I ticked the same script prefs as John Joslin plus the one for Adobe Stock Photos, and I have never had the shut down problem again on both my desk and my laptop computers.
Also, I never had the Beta installed. I downloaded it but then got afraid it would screw up my CS.
Rob
Well that’s crap, I work independently on a work-station from home, I shouldn’t have to select ‘Version Cue’ or ‘Adobe Stock Photos’ to have my apps work correctly. Glad I’ve been waiting to update.
AdobeSoft, the new mega-bloatware corp.
I’ve been using Adobe apps since the beginning, liked them better when they worked independently.
Yep, Rob, I went for a while without the problem after setting those script prefs, but then tonight – Wham! Not only the screwy behavior, but this time clicking a NEF file from Bridge launched CS2. Checked the file associations, and CS3 had been reverted to CS2. And I never touched that.
This release is seriously screwed.
