Olympus-OM
[Top] [All Lists]

Re: [OM] Pervasive Windows file system bug and E-M5 date/time failure

Subject: Re: [OM] Pervasive Windows file system bug and E-M5 date/time failure
From: Chuck Norcutt <chucknorcutt@xxxxxxxxxxxxxxxx>
Date: Sun, 03 Nov 2013 11:10:24 -0500
The statement I made about non-numeric values bothered me.  My bad 
memory.  There is no such thing as non-numeric values in the FAT/FAT32 
date/time fields.  The time and date components are simply bit fields 
within a 16-bit word for date and also a 16 bit word for time.  All 16 
bits of both fields are used but there are invalid bit combinations 
within the sub-fields.  For example, the hour of the day is an integer 
ranging from 0-23 but it appears in a 5 bit field.  The sub-field could 
hold values as large as 31 but anything larger than 23 would be invalid. 
  Having all zeros in the time stamp sub-fields is valid (the 
representation for midnight) but all zeros in the month and day 
sub-fields is not since 0 is not a valid value for day of the month or 
month of the year.

Now I've confused myself even more.  I can't figure out what the E-M5 
could have written in the date/time fields that would be construed as 
"blank" on the display unless it's used to indicate an invalid entry.

Moral of the story again:  Don't forget to set the date and time.

Chuck Norcutt


On 11/3/2013 8:48 AM, Chuck Norcutt wrote:
> 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.
-- 
_________________________________________________________________
Options: http://lists.thomasclausen.net/mailman/listinfo/olympus
Archives: http://lists.thomasclausen.net/mailman/private/olympus/
Themed Olympus Photo Exhibition: http://www.tope.nl/

<Prev in Thread] Current Thread [Next in Thread>
Sponsored by Tako
Impressum | Datenschutz