CHDK Forum
CHDK Development => General Discussion and Assistance => Topic started by: rohling on 10 / September / 2010, 15:07:58
-
Hi,
I just prepared a new memory card by copying over the chdk files, and set the volume label of the card to CHDK (I hadn't used this name before). Then, with this card in the cam and CHDK started via firmware update, it gave me a headache. The settings were gone, and copying CCHDK.CFG anew din't change anything, and other things where strange. Then, in the file browser, I saw that the directory CHDK appeared as a file of length 0. Ok, gave it a try and set the volume label to something else, and things where fine.
Thought it might be worth mentioning, in case someone else wants to name his card CHDK...
Hans
-
I just prepared a new memory card by copying over the chdk files, and set the volume label of the card to CHDK (I hadn't used this name before). Then, with this card in the cam and CHDK started via firmware update, it gave me a headache. The settings were gone, and copying CCHDK.CFG anew din't change anything, and other things where strange. Then, in the file browser, I saw that the directory CHDK appeared as a file of length 0. Ok, gave it a try and set the volume label to something else, and things where fine.
Thought it might be worth mentioning, in case someone else wants to name his card CHDK...
AFAIK CHDK or Camera do not care about volume label. Must be some other "problem".
Which Camera are you talking about?
-
AFAIK CHDK or Camera do not care about volume label. Must be some other "problem".
Which Camera are you talking about?
It is a A590IS with firmware 1.01b.
Well, just now I've tried it again, changed the volume label to CHDK, and nothing happened: everything is ok.
But the effect definately was there, I had tried it twice.
I hate such things.
Hans
-
I've just reproduced the problem.
What I did:
- Format the SD-card (on Vista Home Premium) to FAT
- Set the Volume-Label of the card to CHDK
- Copy the CHDK-Stuff (0.9.9-938) onto the card
- dismount the card
Then I place the card in the camera, and start CHDK via firmware update.
And there it is, the problem: the directory CHDK seems unreachable, and in the file browser it shows up as a file of zero length.
Changing the volume label (on Windows) to anything else solves the problem, and renamimg it to CHDK brings it back.
Formatting the card in the camera produces the same result.
Hans
-
Formatting the card in the camera produces the same result.
Looks like an issue of the SD card...is it reproduceable with another card ?
-
Hi guys !
I can confirm this behaviour on ixus 70: just renamed card as 'CHDK' and presto ... CHDK folder shows up in file browser as file with length 0 ... note that ixus70 is a VxWorks cam, so this is not just a DryOS issue.
Considering that CHDK just uses Canon supplied routines to access the file system, the thought just struck me
that in that case the camera without CHDK might also show strange behaviour if you used 'DCIM' as the
volume name ... just tried & confirmed, changed name to DCIM, start cam -> Canon says "No Image !"
(note: my DCIM/100CANON/ folder was holding 239 images)
Anyway, this wouldn't be the first difference between DCF ("Design rule for Camera File system") and FAT/FAT32,
remember the recent change of CHDK/SCRIPTS/EXAMPLES to CHDK/SCRIPTS/EXAM ?
So, for the time being, the rule seems to be:
* Do NOT give your card the same name as any of the folders in the cards' root, or that folder will become inaccessible
On the other hand, I can't see what's wrong with CANON_DC as volume name ;)
Excellent catch Hans !
wim
[edit: tried to formulate it a bit better]
edit2: Mmmmh... maybe useful to create 'protected' folders on the card ?
-
The "volume label" is a FAT entry, so this isn't entirely surprising. Whether it breaks may depend which one is first.
-
The "volume label" is a FAT entry, so this isn't entirely surprising. Whether it breaks may depend which one is first.
Thats it!
In my reply to pixeldoc2000 I had mentioned, that the problem would not show up at that point of time, when I renamed the card. Now I repeated the complete procedure with the steps in this order:
1. format, no volume label
2. create the folder DCIM
3. set volume label to DCIM
This card put in the cam, there is no problem!
Whereas the problem is there, when I switch the order of steps 2 and 3.
Hans
-
Formatting the card in the camera produces the same result.
Looks like an issue of the SD card...is it reproduceable with another card ?
Yes. It is the same with both of my 2 cards. But see my reply to reyalp.
Hans
-
* Do NOT give your card the same name as any of the folders in the cards' root, or that folder will become inaccessible
Now it seems that it makes a difference, if the volume label is created first, or the folder. See my reply to reyalp.
On the other hand, I can't see what's wrong with CANON_DC as volume name ;)
Thats right. I simply had the choice, and I took it. Was it a snakes voice, which told me to?
Hans
-
Checked & double-checked: order of creation does NOT matter on ixus70
1. Formatted card (32M Canon) on computer, named it CANON_DC
2. copied a valid DCIM (with 100CANON + 1 pic & CANONMSC subdirs) + a valid CHDK
3. start cam with card, pic shows; after CHDK start (via PS.FIR) both CHDK and DCIM
show as "<dir>" in file browser
4. rename card in computer to "DCIM"
5. start cam with card -> "No Image !"; after CHDK start (via PS.FIR) DCIM shows as file with size 0
6. Reformat card, this time as DCIM
7. copied a valid DCIM (with 100CANON + 1 pic & CANONMSC subdirs) + a valid CHDK
8. start cam with card -> "No Image !"; after CHDK start (via PS.FIR) DCIM shows as file with size 0
9. rename card in computer to "CANON_DC"
10. start cam with card, pic shows; after CHDK start (via PS.FIR) both CHDK and DCIM
show as "<dir>" in file browser
11. added (on the computer) a folder called "CANON_DC" containing a dummy.txt
12. start cam with card, then start CHDK: filebrowser shows CANON_DC as file with size 0
wim