View Full Version : Mark II and 70-200/4L locked up
Mike H
23rd of February 2005 (Wed), 09:50
My Mark II locked up after I took a two-shot bracket sequence. The lens was the 70-200/4L, and the camera was set to aperture priority, high speed advance, matrix metering pattern. The card light remained illuminated, and Err 99 showed in the display. Nothing would operate, and turning the camera off and on several times did not unlock the camera. Despite my fear of taking out the battery with the access lamp on, there was no other choice. I turned off the camera, pulled the battery out, put the battery back in, and then turned the camera back on. Everything returned to normal (aside from my blood pressure), and the camera and lens were fine for the rest of the day. I shot about 150-200 shots after the lockup.
I did a search in the forum and didn't find posts indicating that anyone else was having such a problem with this camera and lens combination. The camera hasn't locked up this way before with that or any other lens. If anyone can shed light on what happened and what can be done to prevent this in the future, please share. Thanks.
Mike H
Cadwell
23rd of February 2005 (Wed), 09:54
The Mark II is a computer that takes pictures... it has microprocessors, memory and firmware. Like all computers they crash sometimes. Usually it's down to bad programming, often facilitated by a liquid lunch (I used to be a programmer so I know of what I speak). Unless it makes a habit of it, ignore it.
rfreschner
23rd of February 2005 (Wed), 10:24
Usually it's down to bad programming, often facilitated by a liquid lunch (I used to be a programmer so I know of what I speak).
Come on now, there's a lot of bad programmers out there that can't even use that excuse!! :lol:
lmelendez
23rd of February 2005 (Wed), 11:21
The Mark II is a computer that takes pictures... it has microprocessors, memory and firmware. Like all computers they crash sometimes. Usually it's down to bad programming, often facilitated by a liquid lunch (I used to be a programmer so I know of what I speak). Unless it makes a habit of it, ignore it.
:D
so, the Airbus has computers too... bad programming there... :O
Leo.
Mike H
24th of February 2005 (Thu), 06:51
I guess no one else having this problem is a good thing. Maybe it's very rare and I can expect to not have it happen anymore.
Mike H
ssim
24th of February 2005 (Thu), 06:56
I've had one Err99 on my 1DMKII but I can't recall which lens it was with. I did just what you did. Stuff happens, I wouldn't be overly worried unless it is consistent.
Cadwell
24th of February 2005 (Thu), 07:06
I guess no one else having this problem is a good thing. Maybe it's very rare and I can expect to not have it happen anymore.
Mike H
Levity aside, it isn't normal behaviour. IF it makes a habit of doing it then send the lens and camera off to Canon for them to investigate / resolve. Otherwise chalk it up to "one of those things".
Mike H
24th of February 2005 (Thu), 07:11
Levity aside, it isn't normal behaviour. IF it makes a habit of doing it then send the lens and camera off to Canon for them to investigate / resolve. Otherwise chalk it up to "one of those things".
I totally agree. I won't be laughing at all if the problem happens when I'm shooting an important event and it won't unlock. Thanks to everyone that reponded.
Mike H
vBulletin® v3.6.12, Copyright ©2000-2012, Jelsoft Enterprises Ltd.