Corrupted files on Canon EOS300D when using larger Viking ..

Archived from groups: rec.photo.digital (More info?)

I shoot raw files on my EOS300D, and I have been using Viking 256MB CF cards
without any problems.

However, I have recently obtained some larger cards (512MB and 1GB cards)
and with these I have had some corrupted files. The file system on the card
itself is fine - I can download the files from the card onto my computer.
However, the Canon raw format is corrupt, so I cannot open the files, either
on the camera or in the various applications on the computer.

The files which get corrupted are always the last ones taken before the
camera has been switched off. Please note that I ALWAYS wait until the
camera has finished writing the file (i.e. the red light is OUT) before
switching off the camera. In addition, the file is NOT corrupt when it is
first written - it can be viewed normally. It only gets corrupted when
further files are written.

The obvious possibility here is that the files are getting very slightly
overwritten by the new session. I say 'very slightly' because the file size
of the corrupted files is as normal. However, I am under the impression that
the file system controller is on board the CF card itself, which would imply
that I have 3 separate cards all with the same fault - unlikely. It could of
course be a design fault, but if it were, then everyone would experience it
with any camera - again unlikely. That leaves the camera, but as I said
above, it works fine with the 256MB cards.

I repeat for the sake of clarity that the corruption is NOT with the card
itself - the file system is fine. The corruption is with the Canon raw
format.

Canon, naturally, recommend use of CF cards branded by them (which I believe
are made by SanDisk). Can anyone think of any compatability issues which may
cause this effect? Just to complicate things a little more, the problem is
intermittent.

Has anyone here had similar experiences, or can anyone shed some light on
this mystery?

Thanks in advance.

--
John
Replace 'nospam' with 'todnet' when replying.

Archived from groups: rec.photo.digital (More info?)

"Jim Townsend" <not@real.address> wrote in message
news:1196p1398omll9b@news.supernews.com...
>
> How are you downloading the images to your computer and processing
> them ?
>
I normally use a card reader, but I have also tried using USB, but not often
as it takes ~ an hour to download a full card:-( However, the file gets
corrupted before any download takes place. To explain this more clearly,
suppose I take a series of shots. I can look at them all through the
camera's LCD monitor, zoom them, whatever I like. Now I switch the camera
off, and later, switch it back on and take a further series of shots. If I
now look back at them using the camera's LCD, the last shot of the first
session will show 'file corrupted' and I will no longer be able to view it
as I could before. All the others will be OK. I can download ALL of them,
either by reader or USB, including the corrupted one(s). If I do a chkdsk on
the card in Windows XP, the file system is OK. Weird, eh?


--
John
Replace 'nospam' with 'todnet' when replying.

Archived from groups: rec.photo.digital (More info?)

http://www.dpreview.com/news/0505/ [...] ralert.asp
"John" <warthog@nospam.demon.co.uk> schrieb im Newsbeitrag
news:429349d5_4@mk-nntp-2.news.uk.tiscali.com...
>I shoot raw files on my EOS300D, and I have been using Viking 256MB CF
>cards
> without any problems.
>
> However, I have recently obtained some larger cards (512MB and 1GB cards)
> and with these I have had some corrupted files. The file system on the
> card
> itself is fine - I can download the files from the card onto my computer.
> However, the Canon raw format is corrupt, so I cannot open the files,
> either
> on the camera or in the various applications on the computer.
>
> The files which get corrupted are always the last ones taken before the
> camera has been switched off. Please note that I ALWAYS wait until the
> camera has finished writing the file (i.e. the red light is OUT) before
> switching off the camera. In addition, the file is NOT corrupt when it is
> first written - it can be viewed normally. It only gets corrupted when
> further files are written.
>
> The obvious possibility here is that the files are getting very slightly
> overwritten by the new session. I say 'very slightly' because the file
> size
> of the corrupted files is as normal. However, I am under the impression
> that
> the file system controller is on board the CF card itself, which would
> imply
> that I have 3 separate cards all with the same fault - unlikely. It could
> of
> course be a design fault, but if it were, then everyone would experience
> it
> with any camera - again unlikely. That leaves the camera, but as I said
> above, it works fine with the 256MB cards.
>
> I repeat for the sake of clarity that the corruption is NOT with the card
> itself - the file system is fine. The corruption is with the Canon raw
> format.
>
> Canon, naturally, recommend use of CF cards branded by them (which I
> believe
> are made by SanDisk). Can anyone think of any compatability issues which
> may
> cause this effect? Just to complicate things a little more, the problem is
> intermittent.
>
> Has anyone here had similar experiences, or can anyone shed some light on
> this mystery?
>
> Thanks in advance.
>
> --
> John
> Replace 'nospam' with 'todnet' when replying.
>
>

Archived from groups: rec.photo.digital (More info?)

Colin D wrote:

> How are you formatting the cards? If you format in the computer, you
> may run into problems with the camera writing to the card. It is always
> best to use the camera format command. I use Sandisk Ultra II 512MB
> cards in my 300D, and always format in the camera. I don't use the
> 'erase all' function, I go straight to 'format', and have never had a
> problem with full cards.

Sorry about the threading but my news server hasn't picked up your post (but
Google has).

I always format from the camera, never from the computer. However, the
corruption takes place before any download has even taken place (see my
reply to Jim Townsend's post in this thread).

--
John
Replace 'nospam' with 'todnet' when replying.

Archived from groups: rec.photo.digital (More info?)

Paul J Gans <gans@panix.com> wrote in
news73gki$ef2$3@reader1.panix.com:

> John <warthog@nospam.demon.co.uk> wrote:
>>"Ingo Kniest" <me@privacy.net> wrote in message
>>news71nc3$is7$1@ulysses.news.tiscali.de...
>
>>> http://www.dpreview.com/news/0505/ [...] ralert.asp
>
>>That's interesting, thanks! The article seems to be fairly
>>specifically about Lexar cards, but logically, if there are
>>problems with one it is likely there are problems with others.
>>I'll keep a lookout for the firmware upgrade when it arrives.
>
> That depends on what causes the problem.
>
> What I find curious is that LEXAR is issuing the firmware
> update. I don't understand this. I'm not about to put
> a Lexar update into my 300D without approval by Canon.

The OP should realize that the problem is with his Canon DSLR and not
the Lexar. I've read numerous reports of the same problem from Canon
users and the problem was always found to be Canon's problem.

Archived from groups: rec.photo.digital (More info?)

"George Preddy" <george.preddy@gmail.com> wrote in message
news:Xns966294470BBxxxxSIGMASD10xxxx@82.106.6.176...
> Paul J Gans <gans@panix.com> wrote in
> news73gki$ef2$3@reader1.panix.com:
SNIP
>> What I find curious is that LEXAR is issuing the firmware
>> update. I don't understand this. I'm not about to put
>> a Lexar update into my 300D without approval by Canon.

No, Lexar is going to update their card, and Canon will update their
firmware to circumvent the issue with faulty Lexars.


> The OP should realize that the problem is with his Canon DSLR and
> not
> the Lexar.

Yet we never read about Sandisk users having that issue..., so it
seems you are wrong again, as usual.

> I've read numerous reports of [...]

Yes we know about your problems with reading comprehension as well.

Bart