Photoshop could not save because of a disk error

Well, quite recently students have been having trouble saving from Photoshop CS5 version 12.0.

It comes up with:
It's strange because if you try multiple times, sometimes it saves and others it comes up with the error.

Could not save as because of a desk error.

Looking in the console log I found these entries:

26/11/2012 16:09:36 /Applications/Adobe Photoshop CS5/Adobe Photoshop CS5.app/Contents/MacOS/Adobe Photoshop CS5[1697] Allocator race detected: transaction is not verified for -103/2 - _mac_bind/Library/Preferences/Adobe/Color/ACEConfigCache2.lst
26/11/2012 16:09:48 /System/Library/CoreServices/Dock.app/Contents/MacOS/Dock[1652] Allocator race detected: transaction is not verified for -103/248 - Untitled-4.psd
26/11/2012 16:09:49 kernel smb_maperr32: no direct map for 32 bit server error (0xc0000279)
26/11/2012 16:09:49 kernel smb_maperr32: no direct map for 32 bit server error (0xc0000279)

It seems to be a problem with users whose home drive is on Windows 2003 or before shares. Luckily I have my home drive on a Windows 2008 share.

Looking on the internet for the kernel error I found this down in the "Mac OS X bug: Empty oflders when browsing Samba shares on Windows 2003 Server". He gets the error when looking in sub-folders on a Windows 2003 server. Might be related.

Tried it with my login with my home drive on Windows Server 2008 share and works without problems.

So far I've tried:

• OS X 10.7.4
• OS X 10.6.6
• OS X 10.6.8
• Photoshop CS5 12.0.4
• Redirecting ~/Library/Application Support/Adobe/ to a local folder

Just had a very similar problem with Windows PC's. Students trying to save from Photoshop to their home drive came up with a similar error:

Could not save as because the file could not be found

It looks like it's a server problem as it happens on both Windows and Mac. I shall update when I find out more.

HP Designjet 500 error 02:10 ribbon problems- trailing cable

I went to use the HP Designjet 500 and upon switching it on I noticed the print carriage stopping abruptly half way along the bed. Looking inside I noticed the ribbon which connects to the carriage was crumpled and had dried ink all over it. Thought this was causing the problem because it was unable to slide along with the carriage so I cleaned it.

After this it's had a few problems loading the paper, and also whilst printing. Just noticed this "System Error 02:10".

Found a few forums on the subject referring to the carriage and print heads. Replaced yellow printhead adn while it was performing an alignment it came up with:
System Error:  79:04

Found this (right at the bottom) one saying it was the connection with the ribbon cable. Looks like it's not getting the right 2.5V signal from the carriage. Needs reseating. Otherwise replace the cable.

The trouble is: How to get into the printer to reseat the cable? Looks like a bit of work.

Found a quick little tutorial on how to get the main cover off. Simply remove the three screws (hex) on the back main part. I unclipped the lift up cover, and you need to unclip the main cover by lifting it up.

Not sure how to remove the side panels.

I reseated the cables on the print carriage but after doing about 2 inches of print on a 36" roll it came up with this error again.

Found a service manual for the HP Designjet 500.
The error is found in section 2-8, carriage failure. It says to replace the Carriage Assembly, but my suspisions point to specifically the "Trailing Cable" as this was quite bent, possibly shorting when the carriage is moving.
To replace the "Trailing Cable" go to section 8-40

Looks like the trailing cable is about £15 so pretty cheap to try out.

If this doesn't work perhaps a carriage assembly. About £120 refurbished, or £350 new



Note ...................
7th Feb 2013
So, it's 3 months on and I finally got the chance to install a new "Trailing Cable". Nothing to note about changing the cable over, the manual is quite self explanatory. The only thing I found was that the torx screws were not size T20, were actually a size or two smaller.

After installation it worked perfectly!

Fixed.