> > > > When I look at the output of the above command, I see JFIFs in the > ASCII > > > column. I don't see date/time strings. > > > > i'm not familar with the term JFIF > > I get this: > > 00000000 10 4a 46 49 46 00 01 01 00 00 01 |......JFIF......| > 0001af60 ff e0 00 10 4a 46 49 46 00 01 01 00 |........JFIF....| > 0002cde0 d9 ff d8 ff e0 00 10 4a 46 49 46 00 |...........JFIF.| > 0002d030 01 ff d8 ff e0 00 10 4a 46 49 46 00 |...........JFIF.| > 00033800 b2 7e 86 51 7f ff d9 ff d8 ff e0 00 |?....~.Q........| > > Maybe it matters that I'm not really using a CF card image. I just > took several jpgs, cat'd them together, and am working on that.
hmmmmm ... I would think the procedure would work with cat'd jpgs, but i could be wrong. if the jpgs do not contain exif data, then there is no hope, of course, for creating the optional CF_short -- at least not by the method I give in my worksheet. i am suprised that grep reported that it found matches within the first two lines that you've pasted, and i am suprised that hexdump -C is not showing ff d8 as the initial two bytes of the cat'd file. what is the origin of your jpgs? Mike -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
