How to prevent corruption of Photoshop...

I run CS3 on a MacPro, running OS 10.4.11. I defragment files, repair permissions %26amp; optimise the hard drive every month or so using TechTool Pro v.5.0.2. Every time, subsequent printing is completely skewed, usually with severe colour shifts. It is independent of the paper used. B%26amp;W is not affected. After a lot of sweat, including reinstalling printer drivers, checking my custom profiles, %26amp; extended consultation with the printer experts (here in New Zealand)?I have established that CS3 communication with my Epson 3800 is corrupted, by printing using the ''Printer manages color'' option in the printer driver 閳?no shifts. The only way around that I've been able to find is a complete reinstall of CS3, a pain, to put it mildly. Has anyone else experienced this %26amp; been able to prevent it happening?

How to prevent corruption of Photoshop...

As a side question, does one really need to defragment drives under OS X? I was under the impression that it really wasn't an issue any more. I've heard that current OS X defraggers often cause more problems than they solve.

How to prevent corruption of Photoshop...

OSX defrags itself on the fly there is no need to defrag.

Well unless you like problems.

the only thing I rebuild is the directory using Diskwarrior.

TechTool Pro itself causes more problem than is solves. I would stay away from TechTool Pro.

Navarro Parker wrote:

As a side question, does one really need to defragment drives under OS X?

TechTool Pro itself causes more problem than is solves...

Thanks for all the responses. Yes, theoretically OSX should manage

defragging, but I'm a multi-media artist %26amp; shift a lot of very large

files around. If I don't defrag %26amp; optimise regularly, Photoshop really

slows down %26amp; the tools start to behave in very idiosyncratic ways.

Perhaps the way forward is to try a different programme instead of

TechTool.

Further to my last response: when I think about it, the problem is

fairly recent %26amp; may have begun only after the last upgrade of

TechTool. Go figure?