Today, an update to Bridge CS6. And know what ? The bug preventing brdige starting on a user account in a domain network is still there !
Could we have an official word about that ?
Very sparse information on the download site for this update - fixes some hot issues huh!
Adobe can we get some idea of what was fixed in the update - like in some release notes - and not even mentioned on this forum
Alas, I've never seen Adobe be forthright about what bug fixes and/or improvements are contained in an update.
The updated application file shows created and modified dates of 5/11/2012 which is exactly what it was before this update. So we're left to speculate and Google…
At least an official word saying if they are working on it and when we can expect a fix would help. Some people here use Bridge extensively, and I have many licences (photoshops and suites) to upgrade, but won't till it is fix. I could explain switching to CS6 without Bridge during a few days, but not without knowing if they will fix it or not. Also buying all my updates sooner than later could help me developing my deployment with AAME (I need my volume licences numbers for that). Adobe, wake up please !
Photoshop CS6 works fine and read correctly temp folder variables, as it write its files into the right directory on D:\Temps.
Why the hell Bridge CS6 can't do that and still try to write to C:\ ? It even give an error message :
"failed to initialize Adobe PSL. Fails to write to temporary folder (D:\Temps). Please change the env vir to TMP to an existed folder :on C drive"
I won't change all my network config just because Adobe can't get things right ! Bridge behavior is against all basic security rules ...
As local administrator, it effectively write to C:\ !!
Contrast with the info - long list of items provided by Adobe for their photoshop cs6 13.0.1 update:
Same here. I must say, this is the lamest software "fix" I've seen in quite some time. The TEMP issue in Bridge was known for months. A lot of people use SSDs and set TEMP folder there; I actually use RAMDrive for this purpose -- it only makes sense. Now, instead of fixing some likely trivial issue (bad handling of backslashes or something of that magnitude) it produces this message with very poor grammar ("has encountered... and need to close," "to an existed folder" - how about a little proofreading). Completely unacceptable to put it mildly.
it produces this message with very poor grammar ("has encountered... and need to close," "to an existed folder" - how about a little proofreading). Completely unacceptable to put it mildly.
dmrking sollution solved this issue for me.
to run bridge as an admininistartor - right click on bridge's shortcut link and choose properties. go to "Shortcut" tab and choose advanced. tick the "run as administrator" and do the OKs.
Now bridge runs without problems (at least for me)
I was running into the same problem after upgrading to CS6; the Temp folder of my Win7 PC is located on "D:" not on "C:", and I have no intention of changing that for a variety of reasons.
Creating a symbolic link from "C:\Temp" to "D:\Temp" from the command line (run as admin) using "mklink /D C:\Temp D:\Temp" along with changing the TMP and TEMP environment variables to point to "C:\Temp" seemed to do the trick for me.
Bridge no longer crashes on launch when run as a regular user and my temp folder still resides on D:\Temp. Happy camper. This does not absolve Adobe from fixing their problem, but in my opinion it is a far better work around than running Bridge as an admin.
Caveat: I have no idea if the symbolic link will cause any system-wide performance issues.
Europe, Middle East and Africa