I have a nice older Quicksilver G4 that I re-appropriated for my daughter to learn with. I've adjusted the sleep settings a few times, but it will not automatically sleep. It will sleep if I manually chose "Sleep" from the Apple drop-down menu. Upon waking, the trouble begins. It tends to have issues related to the NIC, resulting in loss of network connection. Occasionally OS X will simply freeze.

On a few Macs, I've been having issues with Adobe Bridge CS3 crashing when browsing to folders that contain EPS files, both on AFP servers and local drives.

I've been focusing my attention on a specific G5 Power Mac running 10.5.8 and Creative Suite CS3, though both Intel and PPC Macs have been affected. I've run Disk Utility permission repairs, run hardware diagnostics, run OS X and Adobe software updates, all to no avail. The issue actually expanded to a handful of other Macs with no explanation.

Recently, I stumbled upon a site which yielded a possible culprit. I found a comment posted on a blog with a possible solution. It seems that at times, Symantec AntiVirus can cause Adobe Bridge to crash. After some testing, I found that disabling the Auto-Protect feature alleviated the issue under 10.4 and 10.5.

After a bit more research, I've found that the EPS parser plug-in for Bridge is not exactly reliable and stable. Removing it gives SAV the ability to run with Auto-Protect enabled. The down-side is that EPS files will not have thumbnail previews in Bridge unless saved as such.

To remove the plug-in, delete the following file. They will not have thumbnails unless they have been saved as such.

/Applications/Adobe Bridge CS3/Plug-Ins/EPS Parser.plugin

References:

http://kb2.adobe.com/cps/404/kb404904.html

http://designslink2.wordpress.com/2007/08/25/a-few-problems-with-adobe-cs3-bridgeversion-cue/#comment-2747

Well, it could have been worse:

Much worse:

I have a few Windows machines (and virtual machines) that connect to an Apple Xserve. I had some issues with certain folders not being displayed recently and it came down to a folder naming issue. If there was a space as the last character, the PC could not see or browse to that folder, even if it were keyed in manually with the space. Once the bad folder name was corrected, Windows access worked fine again.

References:

http://support.microsoft.com/kb/320081

This one always makes me laugh...

Maybe Adobe will finally get around to building an updater that rolls previous releases into one.