Hi Marc,
I do not want to enter an arguing match here, just some comments on things that are most definitely fixable in firmware if Imacon wants to spend the effort.
- That can easily happen Wilko, and I've seen it happen, due to user - error. Speculation is all we can do because we weren't there to see - what Jurgen did or didn't do wrong, if anything.
- Here are some IFs based on having done some myself, and having read - others on those MF digital blogs. Sorry for the length in advance, but - some may be interested in the specifics.
- IF the back is even momentarily subjected to a loss of power when - loading the firmware you have a problem (need a battery back-up system - on the computer).
Yes, absolutely. If the flash memory containing the firmware is being written you are toast. This we discussed earlier in the forum if I am not mistaken. This problem, however, shows marginal software design. There are multiple ways to avoid it, and they are being used in professional IT equipment. One solution is to split the flash ROM in two segments, one segment holding the currently running firmware, the other segment being used to download new firmware to. Once that download is completed, verified etc, a virtual switch is flipped allowing the newly loaded firmware be activated on the next powerup. Making it perfect would imply a user selectable option to forcibly select the 'old' firmware.
This also shows that simply downloading firmware without asking the user is a certifiably bad idea. Only allowing it with mains power connected to the back, or only if the battery is at least >85% charged or somesuch would also help. Using multiple firmware flash ROM segments is better however.
- IF you have a defective reader (I did) you're screwed. If the CF card - becomes corrupt the back will simply shut down and not recognize any
And that is sloppy firmware engineering. Filesystem corruption is what you are referring to. This can (and should be) detected and an appropriate message should be displayed like "CF media format corrupted" or somesuch. Simply shutting down is not appropriate.
- command. I had a CF card that would only write half of it's capacity, - which I immediately blamed the back for ... turned out it was a tiny - limiter switch on the CF card set to 2 gig instead of 4 which until - then I had never heard of.
I guess (!) that formatting using the wrong FAT filesystem type would have a similar effect.
- If you trash the card contents but do not empty the trash WHILE the - card is still mounted on the desktop, the files are still there when - you put it back in the CFV. If those files were seen by Flexcolor and - worked on in any way before trashing it could cause the camera to shut - down due to unrecognized file format.
I guess this is understandable if you know how this Thrash-can thing works under the surface. Basically only the reference (the little icon) is no longer shown on the screen, the files however are still there unaltered. They just took residence in the Thrash-can. This is the kind of cockpit mistake one typically only makes once, so it is mostly harmless. But annoying of course.
- IF the wrong button is pressed or wrong combination of buttons are - pressed at the wrong time you can cause a world of hurt. Flicking
Will the back lock up? Or will you just get the wrong settings? Lockup would signify a bug, wrong settings, well... you get what you asked for then.
- IF you aren't sure about what buttons you may have pressed, you can go - to settings and scroll to "set Camera Defaults" that usually clears - any CFV menu mistake.
Excellent option to have!
- Like mentioned by a previous poster here, these are basically - computers. If there is an issue in the field, I immediately shut down
Indeed, that is absolutely the right way to look at them. But I would make one small correction here "these are basically EMBEDDED computers". Embedded means task-specific computers, which are expected to always run, or (worst case) fail gracefully. The ignition-fuel injection system in your car is an ex&le, a heart pacemaker another one. Neither would be appreciated if they needed their batteries pulled to recover sometime during operation..
- the camera, replace the CF card, remove the battery, and remove the - back to break the connection. After a few seconds you can reconnect - everything. I have had this happen once with the CFV, and that - procedure corrected it. But it's not just pertinent to the CFV, all
In computer terminology we call that a "hard reboot".
- bullet-proof Canon 1DsMKII. The difference between the Canon and the - CFV is that if the Canon goes down, I can't slap a film back on it and - finish the job : -)
Hair raising, no doubt
- primarily designed for Professional photographers ... who by the way - often employ a tech person to run the back and software which clients
As long as there is a need to employ a seperate person/geek for care and feeding of your digibacks we are not talking mature technology yet. And the question is, given the limited production runs of these products, whether all the bugs will ever be fixed (for some definition of 'all' of course; bugs you never encounter are considered non-issues in the IT industry).
- (like me) have to pay for. If we buy one, WE have to learn that craft - ourselves. I'm a dangerous guy when Art Directing on a photo set - because I know a problem when I see one and they can't blow smoke up - my bum about it : -)
Heheh ;-)
Wilko