The cool thing is if you can create files via 400plus (e.g. just an empty file in any subdirectory) you could have a simple bash script watching for the existence of this file and execute another script (e.g. for transferring your pictures to a NAS, etc.)
There's an issue to overcome there...
What you've effectively got, is an SD card that's connected to two computer systems at the same time - using a file system that doesn't have any support for such a configuration.
So if you create a file using 400plus, you can't necessarily see it from the Transcend CPU (because the FAT info is stale). Even if you overwrite an existing file with new data, you may or may not be able to see that data from the 'other side'; it depends on where precisely it got written on the card.
Maybe there's a mechanism in Linux to force the OS's view of the file system to be refreshed? ... the only thing I could think of, was to umount /dev/mmcblk0p1 and then re-mount it (on /mnt/sd). Unfortunately, every time I try it, the IP connection drops. Sometimes the link comes back up, without having to power-cycle, but I've not seen the mount command work yet (it gives "Invalid argument").
I bought my Transcend card to use with a Photo Frame, rather than the camera. When the 'card' boots, a script renames all the image directories, so that it doesn't always play the photos in the same order (a feature the Photo frame doesn't have as standard). Of course, this script was also running when I inserted the SD card into my PC to copy on new JPEGS - the result was instant corruption, due to the aforementioned stale FAT info. I ended up having to check for the presence of a 'flag file' on the card, in the Linux bash script.
As an aside, this card doesn't work in my Photo Frame's SD slot - but it does work in the USB slot, using the supplied SD card reader. Possibly the fact that it draws 150~250mA is the reason?
