I suspect the difference lies in the E-PL3 and E-M5 firmware... what do
they put in the date/time fields when the clock is not set. When I
transferred the images read by Linux over to Win7 Linux had changed the
non-numeric (blank or null) values written by the E-M5 to Saturday, Dec
31, 2011 at 11:00:00 PM EST. Making it even more strange on the Linux
side is that, although it had initially assigned a valid but fictitious
date/time to the files without dates, when it wrote those same files out
to other media so I could move them to Win7 it changed the time stamp to
0000:00:00 00:00:00 which is something Windows does handle and likely
because it's numeric.
I'm curious as to what the values are in the date/time fields produced
by the E-P3 when the clock isn't set. I think a problem with the
Windows file system that is in both WinXP and Win7 would be unlikely to
have been fixed in Vista and then lost in Win7.
The really bizarre thing is that what's in the date/time fields has any
effect at all on whether a file is found or not. The filename and type
and all relevant location pointers are there. That should be all that
matters. But I can think of some poor programming practices that might
yield such a result. An invalid file date is a trivial problem compared
to loss of the file itself.
Chuck Norcutt
On 11/3/2013 1:22 AM, Moose wrote:
> As a result of the above, I've had shots without date/time data downloaded to
> my Vista machine. And I've had none of the
> problems you did. They downloaded properly in PIE and showed up properly in
> Explorer and FastStone. I fixed them to
> correct date and approx. time easily.
>
> The only differences I see are E-PL3 vs. E-M5, Vista vs. 7 and downloading
> with PIE.
--
_________________________________________________________________
Options: http://lists.thomasclausen.net/mailman/listinfo/olympus
Archives: http://lists.thomasclausen.net/mailman/private/olympus/
Themed Olympus Photo Exhibition: http://www.tope.nl/
|