I gave it some more thought.

I at this point do not really Care WHO is at Fault. One Thing I do know

for sure. We Answer the phones 24 x 7 x 365 because Our customers work

those kinds of hours. We feel it is irresponsible to sell into a Market

that works Long hours and then not Make ourselves available in Case

there is a problem. Even if the problem has nothing to do with our

solutions.

Personally I would never leave a customer in this condition or situation

for any amount of time. The More I read the more disgusted I am with

Apple and others that just talk and We have no indication for sure what

is going on. We would tell our customers the truth. IF we were ever to

run into a situation we could not fix and that has not happened since

1983 when we started this company. I am just Fed up with Companys that

decide not to deal with a problem because "It is too Hard " or it is not

our policy or what ever the deal is" The Lame promises are just words of

"We are working on it". For 3 Years now? Get Real.

I WILL Take Care of My customers. Always have and always will. And I

expect the same from whom ever I purchase from. Since I was made aware

of this issue Late Last week I have looked into it and decided to fix it

ourselves. With or without your help. Apple Should be ashamed of itself

and now I feel that other companys should as well. WE are not perfect

but we would never do this or allow this to go on for this long or any

longer that it takes to fix it and we would if it was our code have

fixed it. Sure there are lots of Bugs in a company of Apple And Adobe's

size. But you also have resources. It is not always ONLY about $. IT

should also be about helping a loyal customer because it is the right

thing to do.

Jim Davison

Hi

Using Thursby Dave did work for some. However it will effect speed.  OSX

can work with SMB as Apple made it for compatibility but AFP is the way

OSX was intended to work. But even using SMB does not fix the issue, AFP

is Faster as it has larger Block sizes and it saves all Data in the

Resource fork as well as the Data fork.

NFS is so slow. It is a great tool and there are lots of uses for it.

But connecting to a Work Station that would put loads on both the Server

and the network to the extent that is found in the Publishing

and E.I..Fiber Channel is sometimes a way to go but it also has

Limitations. The Best way is 10 Gbps Ethernet with AFP. Apple uses AFP

as do at least one other solution besides us.

Anyway I would be happy to Give a server to anyone that wants to help us

with this issue. We are asking only for someone to cause the problem to

happen then we will get the Core Dump. Then after we make a fix you or

who ever can test it. No cost in $ and we are talking a very small

amount of time.

Let me know if you know of anyone.

Jim jim@packetcolor.com Cel 916-996-0956 or 310-770-0099

I am located in Beverly Hills so we are close to a lot of folks that

have this problem and have had to even resort to using PCs.

Hardly anyone that is any kind of Graphics Arts like to use PCs. They

learned on and like Apple for many reasons.

We have a location in Sacramento and one in Reno. So anyone anywhere

within a few hundred Miles of the CA Locations we will be happy to work

with.

Thank you.

Rumor is that 10.8.2 has some network fixes and that it might solve this issue.  Sadly I can report that is not the case.  The bug still exists.  Please Apple & Adobe fix this!

Jeremy

Apple has known of this problem since 09. Mid 09.

So has Adobe. Apple even has the problem listed in the bug report

database since 09. They call the database of Bugs "It's on our Radar".

And that is where it stayed. We have made fixes around Apple many times.

Apple and Adobe seem to be having some kind of issues. Not sure why.

I have some ideas but for the most part I think with Apple it is about

I-Pods etc.. Apple left Adobe Flash out of the new I-Pad. It really

sucks. So many sites use flash.

So if you have an I-PAD and folks that have been loyal to Apple for

years have asked Apple to support Flash. But Apple did not listen.

They are now the largest company in the world thus i guess they feel

they do not have to listen to anyone. Maybe that is the deal with Apple

ignoring such a large amount of customers. Who knows. All anyone can do

is speculate. Calling Apple is a waste of time for this issue.

Now

for your problem. It has been tracked down to an issue with the

programing API Apple uses and so do developers such as HELIOS and Adobe.

So it is not exactly Adobe's fault. However I would have made a work

around long ago. We have done so in several of these Apple situations.

And there are several of them. ILM uses a very good work around. Also I

have heard that Adobe 6 no longer has the problem as they bypass the

Apple API. But I have not had confirmation on that.

I just know that we started to make a work around and discovered

there were several that are very sloppy work around such as using Dave

and there are very good work around s such as mentioned that ILM uses

one that is very good.

I would tell you but you stated to me 2.5 years ago. Apple is a company

that moves forward and does not look back.

Anyway we help out and get our customers fixed up so they do not have to

deal with the problem. We did so within Days of finding out about it. We

even suggested a way for Adobe to fix it. Not sure if they used our fix

or not but it looks as if they had a different route if it is fixed in

the latest version of Adobe.

Jim Davison

By the way, Avid Media Composer has the same problem. Wonder when they'll get around to fixing it.

Hi Todd

Thanks for the message but is it not the same message from about 10

months ago???

I do not want to be rude but am I missing something here???

I never did blaime Adobe for the problem. It is clearly an Apple Problem

and SIRI is more important than the loyal customer base is what a lot of

folks are saying as they switch from Apple to Windows and quite a few to

Linux. There is some good ( Not as good as Adobe) tools for that OS that

do a good job.

Tell me what I am missing here Todd. I realy want to know and do care.

Thanks

Jim

OK

Thank you.

Jim

Thank you TODD! Those of us who have been in this thread since the beginning are grateful for the work/communication you've shared the entire way. The news wasn't always good, but you shared it nonetheless. Software is always going to have bugs. But every day there are giant companies NOT giving a $@%& about it for their customers. You have proven different. So I wanted to say Thanks for that. I do have one question. You said "next version". Does this mean that it will be packaged in an update to existing CS6 or waiting until CS7?

Thanks again for everything.

-Jason