Jump to content

Canada's top-tier Telescopes & Accessories
Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
  • 0
Sign in to follow this  
t6aphp3

T6 CR2 files show as "local disk" in windows explorer

Question

Hi,

I've noticed a worrisome symptom using my Canon T6 after buying and installing BYEOS 3.1.13 last week. I'm worried something may not be compatible.  Canon T6 is a DIGIX 4+ camera manufactured in 2016.  That choice is not covered when connecting to the camera.  I got it to work by selecting DIGIX 5, and I was happy with BYEOS operation until I noticed the weird behavior today that I describe below. Should I be concerned about any compatibility issue here?

I have Backyard EOS 3.1.13 Classic on a Windows 8.1 laptop.  I have the Canon T6. I ran an imaging session, and the CR2 and JPG files were copied to the hard disk as we would expect. It's a nice product. But wait........

Today, I was getting ready to delete the files on the camera, and I connected it to the Windows 8.1 laptop with BYEOS 3.1.13 installed. When I view my files on the camera directly with Windows Explorer, the CR2 files are no longer listed, as they were before I bought and installed BYEOS 3.1.13 on the laptop last week. There are "local disk" listed on the camera, instead of the CR2 files.  The JPG are listed as normal.

On another computer, running Windows 7 without BYEOS, when viewing the files on the camera with Windows Explorer, both the CR2 and JPG are listed as normally expected. I never got the Canon utility running on windows 7. This computer does not have the Canon utility on it, just the Canon Digital Photo Professional software.

Does BYEOS make any permanent changes to the firmware or configuration on the camera itself?

Is something wrong on the Windows 8.1/BYEOS 3.1.13/T6 configuration?

Steve

 

 

Share this post


Link to post
Share on other sites

9 answers to this question

Recommended Posts

  • 0

Thanks for looking. Sometimes pictures explain the question better. File associations aren't the issue, because CR2 are listed normally in other directories on the hard disk on both computers.  Does BYEOS fetch new Canon drivers during install, perhaps?

Windows 8 won't even list CR2 on the camera, just everywhere else on the hard disk as normal.

windows 7 view of camera.JPG

windows 8 view of camera.jpg

Share this post


Link to post
Share on other sites
  • 0

As Guylain said, this is purely Windows and how it is treating the .CR2 files.

BYE does not change camera firmware nor does it download new drivers. The driver for your camera is part of Windows, but this has nothing to do with the driver. It has to do with how Windows is treating the .CR2 file extension. What happens if you copy the files to your local drive? I would expect that the files are fine.

Share this post


Link to post
Share on other sites
  • 0

Thanks for your responses.

On the Windows 8 machine, I can use the Canon EOS Utility to copy the files from camera to laptop hard disk.  All CR2 and JPG are then fine. The Canon EOS Utility I have was installed last year, and is dated 12/7/2015. I see Canon has a newer version that came out a couple of months ago.

I was spooked by the messed up view of the .CR2 in Windows Explorer, AND the fact that a DIGIX 4+ camera made in 2016 was not a choice on the BYE connect camera option.

I am able to work around all of this, but am concerned that something is not right, and who knows what will happen with the next Windows Update, or whatever.

I'm going to first process the pictures I imaged a few days ago, then backup the computer, and try installing the new Canon EOS Utility on the Windows 8 machine.  It sounds like that might be the best bet at this point. 

I'll let you know what happens.

Steve

 

 

 

Share this post


Link to post
Share on other sites
  • 0

Steve, even though Windows Explorer is not showing the .CR2 files correctly, you should be able to copy the files from one Windows Explorer window to another via drag and drop or cut and paste. I would try that before re-installing the EOS Utility.

If your PC has an SD card slot or you have a USB SD card reader you could also remove the card camera and plug it into the PC or reader. I do not have the EOS Utility installed on my laptop and I do this all the time.

Share this post


Link to post
Share on other sites
  • 0

I backed up the computer system image of the C drive, and tried installing the new EOS utility from Canon. There is no change in behavior.

1. I can use the Canon EOS utility to download files from the camera, and the CR2 and JPG appear correctly on the hard disk.

2. I can use a USB adapter for the memory card, and the CR2 and JPG appear correctly in Windows Explorer.

3. I can use BYE during imaging, and the CR2 and JPG are downloaded to the laptop correctly.

4. What no longer works is that the CR2 on the Camera can't be viewed, copied, or anything done with them directly thru Windows Explorer. The Local Disk that shows has 0 bytes, and a cut and paste copies nothing.

I can do everything I need to do with the camera and the laptop. If 1,2,and 3 continue to work, I'm good.

Out of curiosity, if anyone seeing these posts knows the reason for #4, I'd appreciate a post here. 

BYE is a nice product. I enjoyed my imaging session using it.

Thanks!

Share this post


Link to post
Share on other sites
  • 0

Hi, did you ever get an answer or fix to this? I now have he exact same issue - can view and copy my 5dmk3 .cr2 files from my CF card through a card reader or through EOS utility, but explorer just shows them as zero byte local disc files. Not sure if this was as a result of a windows 10 update or after I installed EOS utility, but its really annoying!

Share this post


Link to post
Share on other sites
  • 0

This does seems like an odd Windows behavior.  Did you try on another PC just to see if Windows show the correct file size there?  If it does at least now you'll it's specific to the windows installation on the other PC and your assessment of it being caused by a Windows update may be correct.

Also, can you restore your PC to a date where you know it was working?  This would also give you another clue if it was a Windows update issue.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use