DOS timestamp vs Explorer timestamp
-
I never noticed this before. Some of my users have shown me folders in Explorer have one time. The same folder in DOS CMD window are off by 1 hour. DST happened recently so could be involved. I've googled and found mention that the timestamps are supposed to reflect that. But it should be consistent. New files have identical timestamps, so it's just existing files. Also, any workaround to get the DOS window to match timestamps? Scripts are feeding bad data.
I need an app that will automatically deliver a new BBBBBBBBaBB (beautiful blonde bimbo brandishing bountiful bobbing bare breasts and bodacious butt) every day. John Simmons / outlaw programmer
This has been a problem for over a decade. I particularly see it with networked drives. If I have the same file on a local drive and on a networked drive, the file timestamps are off by one hour for 6 months of the year. File timestamps should only be valid in GMT. Let the final software call an OS function to convert it to local time just before displaying the file time. It's when the OS tries to be too smart that the problem arises. Some BIOS can automatically adjust for DST. But so can the OS. I believe the problem is when one drive is already automatically adjusted, but another drive is not. As in local drive versus networked drive.
-
I never noticed this before. Some of my users have shown me folders in Explorer have one time. The same folder in DOS CMD window are off by 1 hour. DST happened recently so could be involved. I've googled and found mention that the timestamps are supposed to reflect that. But it should be consistent. New files have identical timestamps, so it's just existing files. Also, any workaround to get the DOS window to match timestamps? Scripts are feeding bad data.
I need an app that will automatically deliver a new BBBBBBBBaBB (beautiful blonde bimbo brandishing bountiful bobbing bare breasts and bodacious butt) every day. John Simmons / outlaw programmer
I hate the timestamps. It drives me batty to see a Modified Date earlier than the Created Date. Yes, I know how that happens, but it still drives me crazy.
We won't sit down. We won't shut up. We won't go quietly away. YouTube and My Mu[sic], Films and Windows Programs, etc.
-
I never noticed this before. Some of my users have shown me folders in Explorer have one time. The same folder in DOS CMD window are off by 1 hour. DST happened recently so could be involved. I've googled and found mention that the timestamps are supposed to reflect that. But it should be consistent. New files have identical timestamps, so it's just existing files. Also, any workaround to get the DOS window to match timestamps? Scripts are feeding bad data.
I need an app that will automatically deliver a new BBBBBBBBaBB (beautiful blonde bimbo brandishing bountiful bobbing bare breasts and bodacious butt) every day. John Simmons / outlaw programmer