Skip to main content
Canon Zoombrowser 20D nightmare

I have owned Canon EOS digital cameras since early 2003. I currently own a 20D and I recently purchased a little Canon Powershot SX200 IS Point and Shoot for those times when I can't lug my SLR and supporting equipment around.

The Powershot came with a new version of Zoombrowser which is the sofware I use to manage my rather extensive digital photo collection. Unfortunately, when I installed the new Zoombrowser software (version 6.3) it stopped working with my 20D!

Here I am with 200+ photos from a gymnastics meet on my SLR and I can't download any of them. Going to the Canon site (http://www.usa.canon.com) provides for some pretty good support options in the form of software downloads. In fact, after navigating my way to the EOS 20D support page, the top download listed is an update for ZoomBrowser to version 6.4.

Ah ha, they are aware of the problem and they fixed it. Not so. Turns out all the software on this page is listed here only because it is supposed to work for the 20D, not as upgrades or fixes for the 20D.

In fact I tried every version of Zoombrowser on this page (and a couple others that I found on disc) and could not get one to work. They all gave me the "camerawindow" not supported error.

In the end, after too many installs and reboots to count it turned out to not even be a ZoomBrowser problem. One of the updates on the 20D software page was for "EOS Utility 2.6.1 Updater for Windows". Apparently ZoomBrowser doesn't support the 20D, you have to use the EOS Utility software for any interaction with your camera, then once the images are pulled down locally to your PC it opens ZoomBrowser and you go from there.

Wish someone told me that about 10 hours ago!

Comments

Popular posts from this blog

Troubleshooting a Discourse Update on DigitalOcean: Resolving Unresolvable Errors

For the past three years, I've maintained a Discourse server on a DigitalOcean Droplet. Recently, I decided to update it with some of the latest Discourse features. What I anticipated to be a straightforward update process turned into several days of frustrating setbacks. The version of Discourse I was running was already three years old, so I assumed that running the built-in "Update" feature would suffice. However, after clicking the update button, the progress bar sluggishly crawled forward over the next half hour, only to display the dreaded message: "Error – Update Failed." The logs provided little to no help, but based on my experience with other software updates via GIT, I suspected that the failure might be due to the repository head still being called "Master." In recent years, there has been a shift away from using "Master" as the repository head, with "Main" becoming the preferred term. Despite trying several methods ...

Ethereum Merge - So What?

Artwork by Steven Grundy The long awaited Ethereum "Merge" is finally upon us.  I've heard people say "So what".   So what?  I think they don't understand the implications of the merge.  Either that or they really are betting against Ethereum. I think this upgrade is probably the biggest thing for Ethereum since smart contracts first came out.  This change has the possibility of upsetting the apple cart in terms of Ethereum and BTC.  That's a big claim, but I really think it's possible. The Ethereum Merge has been set for the week of September 19th, 2022.  The merge is when the Ethereum execution layer will be joined with the new proof of stake consensus layer.  What does that mean and why should I care? What it means is that Ethereum will be changing from an energy intensive Crypto coin like all others to a 99% more efficient crypto coin like only a few have done.  Right now Ethereum is mined just like BTC and a host of other Crypto cur...

Yelp api via Coldfusion and oAuth

What should have been a fairly easy implementation turned into several frustrating hours. I was using the old Yelp API that is accessed simply by passing your yelp key in the url. But, I wanted to take advantage of some of the new functionality only available in their API version 2.0. Unfortunately Yelp API v2 requires an oAuth key/signature type access. Having already written similar code to access the Amazon web services with a signature I thought this would be a simple as reusing some existing code. Man was I wrong. Turns out a "correctly" implemented version of oAuth is much less tolerant than AWS is. Simple things, such as what characters in the URL must be encoded, invalidated the Yelp signature. After much searching and screwing around with various proposed implementations it became clear that the easiest and best implementation was to use the Java library provided by Yelp and simply access it from Coldfusion. To make this process easier I've consolidated th...