cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Update of Camera Window DC8 software for Mac OS Mojave

CanalogSE
Enthusiast

When will this Canon software Camera Window DC8 be updated? Presently is the Mac OS 10.14 2 Mojave 64 bit installed on my Mac Book Pro,  and the next OS update from Apple (mid-year 2019?) will probably disable USB cable download from my PowerShot (G1x MK III) to my laptop. Any Canon software in sight?

 

CanalogSE

 

3 ACCEPTED SOLUTIONS


@CanalogSE wrote:

 

On one hand it is good that we are at least two Canon users that have this problem...on the other hand, we may have to wait until we have been assured that our requirement for an program update has reached the right descision level within the Canon corporation, and if an update is not intended we have to re-tthink what to do....

 


I would be beg to differ.  You are two Apple users with “this problem.”  In fact, every Apple user suffers from the problem of Apple’s bad habit of periodically releasing updates to their OS that break the codebase of existing applications.  In other words, Apple likes to keep moving the goal posts by altering the design rules of how their OS works.

 

Consider this analogy of how software works, and interacts with the OS.  Look at the OS as being a grocery store, and software developers are chefs.  You, the user, would be the customer in the chef’s restaurant.  The chef obtains the ingredients for his dishes from grocery store, which is the Apple OS.  The chef obtains the gas for his stoves and ovens from the Apple OS.

To obtain the items that chef needs from the Apple OS, he goes to a ticket window.  In fact, there are hundreds of ticket windows for software developers to use.  There are established rules for how the transactions work at each ticket window.  The chef fills out a ticket request, and the Apple OS returns goods and services to the chef to use in his restaurant.  

 

Of course, some chefs obtain goods on the black market, which the Apple OS considers as rouges and dangerous.  Some chefs create their own paths and back channels into the supply chain, which ultimately originates from the core of the Apple OS.  Unfortunately, the only access to the actual physical hardware of the Apple devices is through such means.  This is also true of the Microsoft Windows, too, but apparently to a much lesser degree.

 

Now, this is where the ‘fun” begins.  When Apple updates their OS, their goal is to get rid of the black market, which I hope you have surmised is my analogy for malware.  Their goal is close up the back channels into the OS, although they may choose to allow some back channels to continue to exist, or even promote it into a full service ticket window.  

 

Ultimately,  Apple’s goal is close off as many of these back channels and black markets as they can.  Chefs whose restaurants are critically dependent on these avenues of access to the OS operate at their own peril.  Frequently, the process of closing off these back channels means altering the rules of a valid ticketed service window, or even completely eliminating it.  

 

Changes of this sort are most common for the service windows that control access the hardware [like USB ports].  


--------------------------------------------------------
"The right mouse button is your friend."

View solution in original post


@Waddizzle wrote:

 

 


I would be beg to differ.  You are two Apple users with “this problem.”  In fact, every Apple user suffers from the problem of Apple’s bad habit of periodically releasing updates to their OS that break the codebase of existing applications.  In other words, Apple likes to keep moving the goal posts by altering the design rules of how their OS works.

 

Consider this analogy of how software works, and interacts with the OS.  Look at the OS as being a grocery store, and software developers are chefs.  You, the user, would be the customer in the chef’s restaurant.  The chef obtains the ingredients for his dishes from grocery store, which is the Apple OS.  The chef obtains the gas for his stoves and ovens from the Apple OS.

To obtain the items that chef needs from the Apple OS, he goes to a ticket window.  In fact, there are hundreds of ticket windows for software developers to use.  There are established rules for how the transactions work at each ticket window.  The chef fills out a ticket request, and the Apple OS returns goods and services to the chef to use in his restaurant.  

 

Of course, some chefs obtain goods on the black market, which the Apple OS considers as rouges and dangerous.  Some chefs create their own paths and back channels into the supply chain, which ultimately originates from the core of the Apple OS.  Unfortunately, the only access to the actual physical hardware of the Apple devices is through such means.  This is also true of the Microsoft Windows, too, but apparently to a much lesser degree.

 

Now, this is where the ‘fun” begins.  When Apple updates their OS, their goal is to get rid of the black market, which I hope you have surmised is my analogy for malware.  Their goal is close up the back channels into the OS, although they may choose to allow some back channels to continue to exist, or even promote it into a full service ticket window.  

 

Ultimately,  Apple’s goal is close off as many of these back channels and black markets as they can.  Chefs whose restaurants are critically dependent on these avenues of access to the OS operate at their own peril.  Frequently, the process of closing off these back channels means altering the rules of a valid ticketed service window, or even completely eliminating it.  

Changes of this sort are most common for the service windows that control access the hardware [like USB ports].  




No no...! I don’t know who accepted the above as a solution, but I strongly disagree. What ”Waddizzle” writes is to me irrellevant mumbo-jumbo. If the short answer to my initial problem is that the software Canon Camera Window DC8 will not be updated to be compatible with future Mac versions of OS Mojave, then I would like to hear that from  the Canon corporation directly. Then I will decide whether I will get me a camera of another brand that allows me to cable download my images to my Mac laptop, or to take out the memory card from the camera for image transfer to my computer. However awkward, this is likely to be the case in the future. And in any case of the two, Canon earns a lot of badwill in my opinion anyway. Finaly, I do not think that we are only twp persons worldwide that would prefer downloading images by cable from their compact Canon camera.

View solution in original post

Since Canon apparently is uninterested to solve this problem or to even reply, I have found a way around the problem and use another way to be able to download images taken with my Canon PowerShot G1X Mk III to my MacBookPro through the USB Cable...

 

Through the Mac OS Mojave to the present OS Catalina, the problem with the Canon 32 bit image download software still remains.

 

The Solution is Adobe Bridge software...which has the download images function which works just fine in this respect. Great! For others who might have the same problem...try this solution! 

 

I have been a faithful customer to Canon during 50 years now...constantly since 1971 with my first SLR camera Canon FTb and I have spent a lot of hard earned money on lots of new Canon photo equipment over the years, but haven't even received any tip or sort of reply to this. Sorry to say, their total uninterest has surprised me greatly.

/B

View solution in original post

16 REPLIES 16

mauricejones
Apprentice
I'm in the same boat. Need for upgrade/update was announced by Apple months ago. What are our options if no upgrade/update is planned?


@mauricejones wrote:
I'm in the same boat. Need for upgrade/update was announced by Apple months ago. What are our options if no upgrade/update is planned?

Hello and thanks for your message -

 

On one hand it is good that we are at least two Canon users that have this problem...on the other hand, we may have to wait until we have been assured that our requirement for an program update has reached the right descision level within the Canon corporation, and if an update is not intended we have to re-tthink what to do....

 

Let´s first give it another week or so - I have a very skilled computer programmer in the family who will visit me next week - maybe he has some good practical suggestions how to approach a possible lack of interest from the Canon side, and can suggest a possible solution for you and me!!

 

 

Thank you.  Will keep our fingers "crossed"....

I just received this email - half an hour ago...

But it does not work toclick on any of the blue-colored links to see the massage...

What to do??

 

Skärmavbild 2018-12-29 kl. 10.12.31.png

Have you heard anything yet? I haven´t, but I am of course still interested to know if there is any progress...

Regards

/B


@CanalogSE wrote:

 

On one hand it is good that we are at least two Canon users that have this problem...on the other hand, we may have to wait until we have been assured that our requirement for an program update has reached the right descision level within the Canon corporation, and if an update is not intended we have to re-tthink what to do....

 


I would be beg to differ.  You are two Apple users with “this problem.”  In fact, every Apple user suffers from the problem of Apple’s bad habit of periodically releasing updates to their OS that break the codebase of existing applications.  In other words, Apple likes to keep moving the goal posts by altering the design rules of how their OS works.

 

Consider this analogy of how software works, and interacts with the OS.  Look at the OS as being a grocery store, and software developers are chefs.  You, the user, would be the customer in the chef’s restaurant.  The chef obtains the ingredients for his dishes from grocery store, which is the Apple OS.  The chef obtains the gas for his stoves and ovens from the Apple OS.

To obtain the items that chef needs from the Apple OS, he goes to a ticket window.  In fact, there are hundreds of ticket windows for software developers to use.  There are established rules for how the transactions work at each ticket window.  The chef fills out a ticket request, and the Apple OS returns goods and services to the chef to use in his restaurant.  

 

Of course, some chefs obtain goods on the black market, which the Apple OS considers as rouges and dangerous.  Some chefs create their own paths and back channels into the supply chain, which ultimately originates from the core of the Apple OS.  Unfortunately, the only access to the actual physical hardware of the Apple devices is through such means.  This is also true of the Microsoft Windows, too, but apparently to a much lesser degree.

 

Now, this is where the ‘fun” begins.  When Apple updates their OS, their goal is to get rid of the black market, which I hope you have surmised is my analogy for malware.  Their goal is close up the back channels into the OS, although they may choose to allow some back channels to continue to exist, or even promote it into a full service ticket window.  

 

Ultimately,  Apple’s goal is close off as many of these back channels and black markets as they can.  Chefs whose restaurants are critically dependent on these avenues of access to the OS operate at their own peril.  Frequently, the process of closing off these back channels means altering the rules of a valid ticketed service window, or even completely eliminating it.  

 

Changes of this sort are most common for the service windows that control access the hardware [like USB ports].  


--------------------------------------------------------
"The right mouse button is your friend."


@Waddizzle wrote:

 

 


I would be beg to differ.  You are two Apple users with “this problem.”  In fact, every Apple user suffers from the problem of Apple’s bad habit of periodically releasing updates to their OS that break the codebase of existing applications.  In other words, Apple likes to keep moving the goal posts by altering the design rules of how their OS works.

 

Consider this analogy of how software works, and interacts with the OS.  Look at the OS as being a grocery store, and software developers are chefs.  You, the user, would be the customer in the chef’s restaurant.  The chef obtains the ingredients for his dishes from grocery store, which is the Apple OS.  The chef obtains the gas for his stoves and ovens from the Apple OS.

To obtain the items that chef needs from the Apple OS, he goes to a ticket window.  In fact, there are hundreds of ticket windows for software developers to use.  There are established rules for how the transactions work at each ticket window.  The chef fills out a ticket request, and the Apple OS returns goods and services to the chef to use in his restaurant.  

 

Of course, some chefs obtain goods on the black market, which the Apple OS considers as rouges and dangerous.  Some chefs create their own paths and back channels into the supply chain, which ultimately originates from the core of the Apple OS.  Unfortunately, the only access to the actual physical hardware of the Apple devices is through such means.  This is also true of the Microsoft Windows, too, but apparently to a much lesser degree.

 

Now, this is where the ‘fun” begins.  When Apple updates their OS, their goal is to get rid of the black market, which I hope you have surmised is my analogy for malware.  Their goal is close up the back channels into the OS, although they may choose to allow some back channels to continue to exist, or even promote it into a full service ticket window.  

 

Ultimately,  Apple’s goal is close off as many of these back channels and black markets as they can.  Chefs whose restaurants are critically dependent on these avenues of access to the OS operate at their own peril.  Frequently, the process of closing off these back channels means altering the rules of a valid ticketed service window, or even completely eliminating it.  

Changes of this sort are most common for the service windows that control access the hardware [like USB ports].  




No no...! I don’t know who accepted the above as a solution, but I strongly disagree. What ”Waddizzle” writes is to me irrellevant mumbo-jumbo. If the short answer to my initial problem is that the software Canon Camera Window DC8 will not be updated to be compatible with future Mac versions of OS Mojave, then I would like to hear that from  the Canon corporation directly. Then I will decide whether I will get me a camera of another brand that allows me to cable download my images to my Mac laptop, or to take out the memory card from the camera for image transfer to my computer. However awkward, this is likely to be the case in the future. And in any case of the two, Canon earns a lot of badwill in my opinion anyway. Finaly, I do not think that we are only twp persons worldwide that would prefer downloading images by cable from their compact Canon camera.

Seems that there still is no canon software solution to the problem.   

Are there any news yet?

 

I fear that Adobe will upgrade their OS Mojave within the coming six months....Then a number of my 32 bit photography software programs I regularly use in my MBP 15" will reach the final "out of order"- stage.

 

This means that I can no longer easily download images from my PowerShot G1x digital camera BY CABLE...in the time to come thereafter, I have to insert the camera memory card memory card into my laptop and manually create folders/folder structures as well as transfer images to those newly created folders. Tedious work - but since I really am satisfied with the camera I will have to accept that as it appears. 

 

But I find it discouraging tha Canon corporation won´t even reply to this matter...the small individual compact camera user that isn´t taking pictures professionally isn´t that important to them apparently...as it seems.

 

Maybe change to a Fuji camera of a similar type will be advantageous?

 

CanalogSE

 

 

Announcements