I could have written this better, sorry. Yes it is a Core Duo. And the problem is Quark accessing our office network. While there probably is some performance penalty with Quark on the Intel, the G5 is still faster than what we were using.
The issue is that it hangs trying to work with documents which reside on our Apple AFP network. It especially hangs when trying to Get Picture.
On the AFP server log, I can see the Core Duo machine demanding up to 80% of the server's processor capacity and yet accomplishing nothing.
So, the question is, are we experiencing a problem between the apparently new AFP2 standard of the CoreDuo Intel and our existing G4AFP standard?
Are we seeing some problem related to Quark and AFP networking?
Quark performs just fine on this machine when everything it needs is relocated to its own local hard drive. It does not like our AFP network.
I have seen another comment on this Board where someone with In Design from Adobe and a Core Duo Imac is having issues where files on their network will not launch unless they rename them. Also sounds like an AFP issue of some kind.
We upgraded to 10.4.5 immediately on installing the machine (it's that new) so we have no reference for whether the problem is just related to 10.4.5
Our business model, like many design firms, is that work remains on the office network where it is accessible to all and immediately backed up. So, this problem is hurting, not helping, our workflow.