-
1. Re: Adobe Bridge CS6 5.0.1 Update
MikeKPhoto Sep 13, 2012 6:31 AM (in response to Nicolas.k)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
-
2. Re: Adobe Bridge CS6 5.0.1 Update
station_two Sep 13, 2012 12:45 PM (in response to MikeKPhoto)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…
-
-
4. Re: Adobe Bridge CS6 5.0.1 Update
Nicolas.k Sep 14, 2012 1:05 AM (in response to MikeKPhoto)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 !
-
5. Re: Adobe Bridge CS6 5.0.1 Update
Nicolas.k Sep 14, 2012 2:22 AM (in response to Nicolas.k)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:\ !!
-
6. Re: Adobe Bridge CS6 5.0.1 Update
RWSP Sep 14, 2012 10:10 AM (in response to MikeKPhoto)Contrast with the info - long list of items provided by Adobe for their photoshop cs6 13.0.1 update:
http://blogs.adobe.com/photoshopdotcom/2012/08/photoshop-cs6-13-0-1-update-now-available.h tml
-
7. Re: Adobe Bridge CS6 5.0.1 Update
VasylT Sep 14, 2012 11:06 PM (in response to Nicolas.k)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.
-
8. Re: Adobe Bridge CS6 5.0.1 Update
station_two Sep 15, 2012 11:06 AM (in response to VasylT)The downward spiral of deterioration in all aspects of the Adobe corporation seems to be turning into a free fall.
-
9. Re: Adobe Bridge CS6 5.0.1 Update
Nicolas.k Sep 17, 2012 9:31 AM (in response to station_two)This bug is so simple to fix, it is absurd. Reading a key registry or an environement variable shouldn't be too hard for adobe developers. They even have the code right in photoshop !
-
10. Re: Adobe Bridge CS6 5.0.1 Update
Nicolas.k Sep 28, 2012 12:15 AM (in response to Nicolas.k)WoW ! Today,
CS6 5.0.1.1 Update !
And know what ? Still not fixed, can't use it ! Right Adobe ... Really, can't your read a variable in a regkey ?
-
11. Re: Adobe Bridge CS6 5.0.1 Update
Yammer Sep 28, 2012 1:36 AM (in response to Nicolas.k)It's a security fix:
http://helpx.adobe.com/x-productkb/global/certificate-updates.html
-
12. Re: Adobe Bridge CS6 5.0.1 Update
Nicolas.k Sep 28, 2012 1:57 AM (in response to Yammer)Ok, but like usual on the download page nothing about what is fix or not, no changelog, what's new etc ...
-
13. Re: Adobe Bridge CS6 5.0.1 Update
station_two Sep 28, 2012 10:04 PM (in response to Nicolas.k)Par for the course...
-
14. Re: Adobe Bridge CS6 5.0.1 Update
Samoreen Sep 29, 2012 1:11 AM (in response to VasylT)VasylT wrote:
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.
Offshore development?
-
15. Re: Adobe Bridge CS6 5.0.1 Update
drmrking Oct 31, 2012 11:58 AM (in response to Nicolas.k)OK in Windows 7, I had same Bridge problem with "failed to initialize Adobe PSL",
fixed by running Bridge in administrator mode - now it can use a drive other than C: as temp.
Mike
-
16. Re: Adobe Bridge CS6 5.0.1 Update
Arielinson Nov 1, 2012 3:30 PM (in response to drmrking)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)
-
17. Re: Adobe Bridge CS6 5.0.1 Update
Curt Y Nov 1, 2012 4:44 PM (in response to Arielinson)That has been a long known workaround, but it does not solve problem and there are some computer security risks from operating in that mode.
-
18. Re: Adobe Bridge CS6 5.0.1 Update
GSCrowe Nov 19, 2012 11:37 AM (in response to Nicolas.k)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.


