MacBook Pro 15" Unibody keyboard trouble

Just had a look at a MacBook Pro with keyboard issues. Whenever you tried to type anything it'd make a "nope" noise. Restarted in single user mode "cmd + s", and whenever you tried to type it'd come up with all sorts of stuff.

I rebooted into Windows XP and could not use the ctrl + alt + del key to login. I assume it was a hardware failure at this point.

I tried to update firmware, I might have figured that there would be a keyboard firmware update but couldn't find any such thing.

I rebooted and connected an external keyboard which worked quite well, although when this was connected, occasionally it'd make a 'nope' noise.

I opened up the keyboard viewer in the top right corner and noticed that cmd + shift keys were always held down:

Looks like it thinks these keys are being constantly pressed.

Looking into replacing the keyboard, but after looking at this take-down tutorial and this video:

I think perhaps not.

Will update this when its' fixed.

MacBook Pro left hand fan noisy

After turning on one of our 2009 MacBook Pro 17", after about 5 seconds, the left hand side fan would start making a buzzing noise. Thought it'd be something rattling around with it, or maybe catching a wire so I took it apart.

When I took the fan with the casing out I noticed nothing catching. It seemed to be rattling of its' own accord. I found this good post on how to fix the fan. Basically just take the two screws holding it together off. Then prize the fan off the motor.

Inside I found a little tiny bit of grit underneath the magnet on the main base. I tried to get it out but it proved pretty tricky. After 5 mins I got most of the bits out (very tiny bits), and I oiled the fan axle.

I put it back together and it worked a treat.

Thank you very much  ifixit.com and nofilmschool.com. This internet thing is very helpful.

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.