Previously flawless M240 fails after 30 day return period

I see this thread has been busy, thanks for the discussion.

How does one lock down the card? I do use a Mac.... Also have never taken the card out with camera power on.

I have owned and used an M8 and M9 previously, and as has been said, never had lock up or freeze up issues with those cameras.
 
Godfrey said:
In 15 years of using flash-based storage cards to transfer files from camera to computer with OS X, I've never once had OS X write any files back to the card.

OS X does write UNIX hidden files to directories when running its own file system, but I haven't seen it write these files to FAT16, FAT32, or ExFAT file systems at all.

G
Click to expand...

Ah, but it do write there!

I just inserted a SD card "get info" says Format: MS-DOS (FAT32)

And typed at terminal: ls -a /Volumes/NO_NAME

And found
. ._.Trashes MISC
.TemporaryItems .fseventsd PRIVATE
.Trashes
._.TemporaryItems DCIM

Leica is not the least interested in these files. But the Mac needs them to erase files, which I have done many times with no issues. I have also formatted Fat32 on my Macs, but have only used them on an M8 -- and every other camera I have, Lumix, Nikon, Canon.

Note if you have Stuffit installed you will also write:
.. ._StuffIt 10.0 MP_ROOT
.Trashes AVF_INFO StuffIt 10.0

chaospress said:
How does one lock down the card?
Click to expand...

Just put the lock switch on the card in the "lock" position.

Of course one is free to tap oneself three times on the head, and wave a feather in the air before inserting an SD card, just to be sure.
 
Ah, so the little switch on the side that slides? I've never even noticed it. Sorry, but what exactly does that do? Just allow download and nothing coming back to the card? I'm admittedly better at composing pictures than technical stuff, with which I tend to learn just enough to do what I want to accomplish.
 
photomoof said:
I assume you mean "copy" from an inserted drive, not "download' from drive on Wifi or over the internet?
Click to expand...
Nope. A simple copy will lead to chaos, unfindable files, false duplicates, etc. Normally I will use (obviously) a card reader, and running ImageIngester Pro rename the files, number them individually, add copyright info to EXIF, put them into the proper folder, tag them and write a backup to an external drive and to an off-site NAS with a few mouseclicks.
 
chaospress said:
Ah, so the little switch on the side that slides? I've never even noticed it. Sorry, but what exactly does that do? Just allow download and nothing coming back to the card? I'm admittedly better at composing pictures than technical stuff, with which I tend to learn just enough to do what I want to accomplish.
Click to expand...

Yes, set it to lock the card become read only.

jaapv said:
Nope... Normally I will use (obviously) a card reader
Click to expand...

Yes I would think of a reader as a "download," it has just been so long since I used one myself, used to putting SD cards directly into my Macs. :angel:
 
Try Photomechanic for ingesting, editing and all manner of file transfers. One of the, if not the best program out there for ingesting, captioning etc.. There's a reason this is a must have program on most photojournalists' computers.
 
newsgrunt said:
Try Photomechanic for ingesting, editing and all manner of file transfers. One of the, if not the best program out there for ingesting, captioning etc.. There's a reason this is a must have program on most photojournalists' computers.
Click to expand...

TY for this. LR is so crappy for image review, I can't believe we put up with it. I'm used to the controls but I curse it every time I use it, even on my fastest machine.

Not to mention the ridiculous import times.

But what are the serious alternatives for a combined bowser and editor?
 
photomoof said:
Ah, but it do write there!

I just inserted a SD card "get info" says Format: MS-DOS (FAT32)

And typed at terminal: ls -a /Volumes/NO_NAME

And found
. ._.Trashes MISC
.TemporaryItems .fseventsd PRIVATE
.Trashes
._.TemporaryItems DCIM

Leica is not the least interested in these files. But the Mac needs them to erase files, which I have done many times with no issues. I have also formatted Fat32 on my Macs, but have only used them on an M8 -- and every other camera I have, Lumix, Nikon, Canon.

Note if you have Stuffit installed you will also write:
.. ._StuffIt 10.0 MP_ROOT
.Trashes AVF_INFO StuffIt 10.0
Click to expand...

Thanks, I forgot the -a option on ls... :)

Using
> diskutil list
shows the card out of my X as a WINDOWS_FAT32 volume.

And yes, ._.Trashes, .fseventsd, and .Trashes are there. None of the others, other than the DCIM folder.

Never made a darn bit of difference in any of my cameras, Leicas or not.

G
 
Godfrey said:
Never made a darn bit of difference in any of my cameras, Leicas or not.

G
Click to expand...

Thus my suggestion for fixing SD cards:
"Of course one is free to tap oneself three times on the head, and wave a feather in the air before inserting an SD card, just to be sure."
 
chaospress said:
Just wondering with Jaap mentioning he uses a 16GB card, if it's best not to go to a 32GB card with the M240?
Click to expand...

Not really I use 2 32gb Sandisk 95mb/sec cards exclusively.
the issue is that with the M240, the bigger the card the longer it takes the camera to be ready to shoot from when you first turn it on. So to maximize performance use the smallest, fastest card you are comfortable with. For me that's 32gb. For a lot of people it's 64gb. For Jaap it's 16gb.
We think what is happening is that when you first turn on the camera it reads/scans the card in its entirety before it's ready for the first shot. Hence the higher capacity cards take longer - just a theory, no one seems to know for sure but the anecdotal evidence seems to bear this out.
 
Last edited:
Yep - I dislike large cards. 16 GB matches battery life approximately.
The risk of losing everything should a card die / be lost / stolen / eaten by the dog gets too high IMO.
 
You must log in or register to reply here.
Back
Top Bottom