A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows 7 » Windows 7 Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Did Miscrosoft change how it dates files?



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old March 11th 19, 06:23 AM posted to alt.windows7.general
pyotr filipivich
external usenet poster
 
Posts: 752
Default Did Miscrosoft change how it dates files?

Greetings

I have a batch file using Robocopy which is only suppose to copy
those files which are "newer" (I.e., modified) than the ones on the
drive. Usually, there is no problem. But tonight, as I go to close
up operations for the evening, it is copying far more files than
before. all tagged "newer".
Was there something magical about the shift to Daylight Savings
time which makes a source drive file dated "Jan 2 2019 10:20 AM" to
now be "newer" than the target drive file dated "Jan 2 2019 10:20
AM"?
I haven't changed "CHAR Sets.wpd" since 1996!?

I do remember something like this happening when the batchfile
correctly copied files from a flashdrive to the XP laptop, and then I
was done with the letter writing, the batchfile copied _all_ the files
just copied (but not used) back from the hardrive to the flash drive.

You'll have a great deal of difficulty convincing me that the
folks at Microsott really have an idea what they are doing.


--
pyotr filipivich
The question was asked: "Is Hindsight overrated?"
In retrospect, it appears to be.
Ads
  #2  
Old March 11th 19, 07:24 AM posted to alt.windows7.general
JJ[_11_]
external usenet poster
 
Posts: 744
Default Did Miscrosoft change how it dates files?

On Sun, 10 Mar 2019 22:23:09 -0700, pyotr filipivich wrote:
Greetings

I have a batch file using Robocopy which is only suppose to copy
those files which are "newer" (I.e., modified) than the ones on the
drive. Usually, there is no problem. But tonight, as I go to close
up operations for the evening, it is copying far more files than
before. all tagged "newer".
Was there something magical about the shift to Daylight Savings
time which makes a source drive file dated "Jan 2 2019 10:20 AM" to
now be "newer" than the target drive file dated "Jan 2 2019 10:20
AM"?
I haven't changed "CHAR Sets.wpd" since 1996!?

I do remember something like this happening when the batchfile
correctly copied files from a flashdrive to the XP laptop, and then I
was done with the letter writing, the batchfile copied _all_ the files
just copied (but not used) back from the hardrive to the flash drive.

You'll have a great deal of difficulty convincing me that the
folks at Microsott really have an idea what they are doing.


The only probably cause is that the flashdrive is using FAT file system. FAT
has lower time resolution than NTFS, which is 2 seconds. So, if a file is
set to 10:20:33 AM by a software, the result would be 10:20:32 AM. CMD
doesn't show the seconds part, so if you use the file property dialog,
you'll see the difference in the seconds part.
  #3  
Old March 11th 19, 08:05 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Did Miscrosoft change how it dates files?

JJ wrote:
On Sun, 10 Mar 2019 22:23:09 -0700, pyotr filipivich wrote:
Greetings

I have a batch file using Robocopy which is only suppose to copy
those files which are "newer" (I.e., modified) than the ones on the
drive. Usually, there is no problem. But tonight, as I go to close
up operations for the evening, it is copying far more files than
before. all tagged "newer".
Was there something magical about the shift to Daylight Savings
time which makes a source drive file dated "Jan 2 2019 10:20 AM" to
now be "newer" than the target drive file dated "Jan 2 2019 10:20
AM"?
I haven't changed "CHAR Sets.wpd" since 1996!?

I do remember something like this happening when the batchfile
correctly copied files from a flashdrive to the XP laptop, and then I
was done with the letter writing, the batchfile copied _all_ the files
just copied (but not used) back from the hardrive to the flash drive.

You'll have a great deal of difficulty convincing me that the
folks at Microsott really have an idea what they are doing.


The only probably cause is that the flashdrive is using FAT file system. FAT
has lower time resolution than NTFS, which is 2 seconds. So, if a file is
set to 10:20:33 AM by a software, the result would be 10:20:32 AM. CMD
doesn't show the seconds part, so if you use the file property dialog,
you'll see the difference in the seconds part.


The daylight savings time change (on FAT32) on Sunday,
might also be a problem, and cause "rampant copying" :-)
Aren't computers fun...

I think it's FAT32 that screws up and NTFS is OK ???

Paul
  #4  
Old March 11th 19, 04:23 PM posted to alt.windows7.general
Ken Blake[_5_]
external usenet poster
 
Posts: 2,221
Default Did Miscrosoft change how it dates files?

On Sun, 10 Mar 2019 22:23:09 -0700, pyotr filipivich
wrote:


You'll have a great deal of difficulty convincing me that the
folks at Microsott really have an idea what they are doing.




One of the problems with a giant company like Microsoft is that
different groups of people work on different things. It's no so much
that the folks at Microsoft have no idea what they are doing, it's
more that the folks in group A have no idea what the folks in group B
are doing.
  #5  
Old March 11th 19, 04:33 PM posted to alt.windows7.general
pyotr filipivich
external usenet poster
 
Posts: 752
Default Did Miscrosoft change how it dates files?

Paul on Mon, 11 Mar 2019 03:05:30 -0400 typed
in alt.windows7.general the following:
JJ wrote:
On Sun, 10 Mar 2019 22:23:09 -0700, pyotr filipivich wrote:
Greetings

I have a batch file using Robocopy which is only suppose to copy
those files which are "newer" (I.e., modified) than the ones on the
drive. Usually, there is no problem. But tonight, as I go to close
up operations for the evening, it is copying far more files than
before. all tagged "newer".
Was there something magical about the shift to Daylight Savings
time which makes a source drive file dated "Jan 2 2019 10:20 AM" to
now be "newer" than the target drive file dated "Jan 2 2019 10:20
AM"?
I haven't changed "CHAR Sets.wpd" since 1996!?

I do remember something like this happening when the batchfile
correctly copied files from a flashdrive to the XP laptop, and then I
was done with the letter writing, the batchfile copied _all_ the files
just copied (but not used) back from the hardrive to the flash drive.

You'll have a great deal of difficulty convincing me that the
folks at Microsott really have an idea what they are doing.


The only probably cause is that the flashdrive is using FAT file system. FAT
has lower time resolution than NTFS, which is 2 seconds. So, if a file is
set to 10:20:33 AM by a software, the result would be 10:20:32 AM. CMD
doesn't show the seconds part, so if you use the file property dialog,
you'll see the difference in the seconds part.


The daylight savings time change (on FAT32) on Sunday,
might also be a problem, and cause "rampant copying" :-)
Aren't computers fun...

I think it's FAT32 that screws up and NTFS is OK ???


Ah, so it is a "religious" thing (FAT32 vs NTFS).

Now to see if I want to go to the hassle of changing thumbdrive
formats.
--
pyotr filipivich
Next month's Panel: Graft - Boon or blessing?
  #6  
Old March 11th 19, 04:33 PM posted to alt.windows7.general
pyotr filipivich
external usenet poster
 
Posts: 752
Default Did Miscrosoft change how it dates files?

JJ on Mon, 11 Mar 2019 13:24:59 +0700 typed in
alt.windows7.general the following:
On Sun, 10 Mar 2019 22:23:09 -0700, pyotr filipivich wrote:
Greetings

I have a batch file using Robocopy which is only suppose to copy
those files which are "newer" (I.e., modified) than the ones on the
drive. Usually, there is no problem. But tonight, as I go to close
up operations for the evening, it is copying far more files than
before. all tagged "newer".
Was there something magical about the shift to Daylight Savings
time which makes a source drive file dated "Jan 2 2019 10:20 AM" to
now be "newer" than the target drive file dated "Jan 2 2019 10:20
AM"?
I haven't changed "CHAR Sets.wpd" since 1996!?

I do remember something like this happening when the batchfile
correctly copied files from a flashdrive to the XP laptop, and then I
was done with the letter writing, the batchfile copied _all_ the files
just copied (but not used) back from the hardrive to the flash drive.

You'll have a great deal of difficulty convincing me that the
folks at Microsott really have an idea what they are doing.


The only probably cause is that the flashdrive is using FAT file system. FAT
has lower time resolution than NTFS, which is 2 seconds. So, if a file is
set to 10:20:33 AM by a software, the result would be 10:20:32 AM. CMD
doesn't show the seconds part, so if you use the file property dialog,
you'll see the difference in the seconds part.


Ah. Hadn't thought of that. Ufda.
--
pyotr filipivich
Next month's Panel: Graft - Boon or blessing?
  #7  
Old March 11th 19, 05:05 PM posted to alt.windows7.general
Stan Brown
external usenet poster
 
Posts: 2,904
Default Did Miscrosoft change how it dates files?

On Sun, 10 Mar 2019 22:23:09 -0700, pyotr filipivich wrote:

Greetings

I have a batch file using Robocopy which is only suppose to copy
those files which are "newer" (I.e., modified) than the ones on the
drive. Usually, there is no problem. But tonight, as I go to close
up operations for the evening, it is copying far more files than
before. all tagged "newer".
Was there something magical about the shift to Daylight Savings
time which makes a source drive file dated "Jan 2 2019 10:20 AM" to
now be "newer" than the target drive file dated "Jan 2 2019 10:20
AM"?


If you use the /TS option, robocopy will show you the timestamps of
the source file. When the source file is on an NTFS drive, that will
be in UTC, not your local time. (The timestamps displayed in File
Explorer are converted from the NTFS native UTC to your time zone.)

When the source file is on a FAT or FAT32 drive, native time is the
local time zone when the file was created or modified. (I can't
remember whether robocopy shows that local time, or converts it to
UTC.) That means if you create a file on a FAT32 USB stick at
10:00:00 Eastern Standard Time, and then mount it in Eastern Daylight
Time, the timestamp will show in File Explorer as 10:00:00, even
though the file was created at 9:00:00 Easter Daylight Time.

Robocopy supposedly understands the semiannual daylight-time shift,
and doesn't copy files in such cases, but I don't know how it knows.
I just make sure that I have updated my USB stick the last thing
before going to bed the night before the shift, so that even if the
timestamps are wrong the file contents are correct.

This past weekend, after the time shift, out of hundreds of Eastern
Standard Time files on my USB stick, robocooy wanted to copy exactly
four. I don't know what made those different from the others, so I
don't know if robocopy does basically compensate for DST and just
failed with these four.

There is an option in robocopy to copy the timestamp of a file
without copying the file contents. You might want to use that, come
November.

--
Stan Brown, Oak Road Systems, Tompkins County, New York, USA
http://BrownMath.com/
http://OakRoadSystems.com/
Shikata ga nai...
  #8  
Old March 11th 19, 06:28 PM posted to alt.windows7.general
Micky
external usenet poster
 
Posts: 1,528
Default Did Miscrosoft change how it dates files?

In alt.windows7.general, on Mon, 11 Mar 2019 08:23:06 -0700, Ken Blake
wrote:

On Sun, 10 Mar 2019 22:23:09 -0700, pyotr filipivich
wrote:


You'll have a great deal of difficulty convincing me that the
folks at Microsott really have an idea what they are doing.




One of the problems with a giant company like Microsoft is that
different groups of people work on different things. It's no so much
that the folks at Microsoft have no idea what they are doing, it's
more that the folks in group A have no idea what the folks in group B
are doing.


Then I am better than a Microsoft employee, because I have no idea what
the folks in group A or B are doing.
  #9  
Old March 11th 19, 08:04 PM posted to alt.windows7.general
Big Al[_5_]
external usenet poster
 
Posts: 1,588
Default Did Miscrosoft change how it dates files?

On 3/11/19 1:23 AM, pyotr filipivich wrote:
Greetings

I have a batch file using Robocopy which is only suppose to copy
those files which are "newer" (I.e., modified) than the ones on the
drive. Usually, there is no problem. But tonight, as I go to close
up operations for the evening, it is copying far more files than
before. all tagged "newer".
Was there something magical about the shift to Daylight Savings
time which makes a source drive file dated "Jan 2 2019 10:20 AM" to
now be "newer" than the target drive file dated "Jan 2 2019 10:20
AM"?
I haven't changed "CHAR Sets.wpd" since 1996!?

I do remember something like this happening when the batchfile
correctly copied files from a flashdrive to the XP laptop, and then I
was done with the letter writing, the batchfile copied _all_ the files
just copied (but not used) back from the hardrive to the flash drive.

You'll have a great deal of difficulty convincing me that the
folks at Microsott really have an idea what they are doing.



Try this, I have it in all of my batch files like:
robocopy D:\src G:\dest /MIR /NJH /NJS /NDL
/DST

/dst Compensates for one-hour DST time differences.

https://docs.microsoft.com/en-us/win...mands/robocopy

Al
  #10  
Old March 11th 19, 08:32 PM posted to alt.windows7.general
pyotr filipivich
external usenet poster
 
Posts: 752
Default Did Miscrosoft change how it dates files?

Ken Blake on Mon, 11 Mar 2019 08:23:06 -0700
typed in alt.windows7.general the following:
On Sun, 10 Mar 2019 22:23:09 -0700, pyotr filipivich
wrote:


You'll have a great deal of difficulty convincing me that the
folks at Microsott really have an idea what they are doing.




One of the problems with a giant company like Microsoft is that
different groups of people work on different things. It's no so much
that the folks at Microsoft have no idea what they are doing, it's
more that the folks in group A have no idea what the folks in group B
are doing.


Yeah. I knew some 'softies.

--
pyotr filipivich
Next month's Panel: Graft - Boon or blessing?
  #11  
Old March 11th 19, 08:32 PM posted to alt.windows7.general
pyotr filipivich
external usenet poster
 
Posts: 752
Default Did Miscrosoft change how it dates files?

micky on Mon, 11 Mar 2019 19:28:51 +0200
typed in alt.windows7.general the following:
In alt.windows7.general, on Mon, 11 Mar 2019 08:23:06 -0700, Ken Blake
wrote:

On Sun, 10 Mar 2019 22:23:09 -0700, pyotr filipivich
wrote:


You'll have a great deal of difficulty convincing me that the
folks at Microsott really have an idea what they are doing.




One of the problems with a giant company like Microsoft is that
different groups of people work on different things. It's no so much
that the folks at Microsoft have no idea what they are doing, it's
more that the folks in group A have no idea what the folks in group B
are doing.


Then I am better than a Microsoft employee, because I have no idea what
the folks in group A or B are doing.


Word to the wise. Do not answer the question on the final "What
are the other parts of the team doing?" with "I have no idea." That
cost me the two points I needed for a passing grade needed in order to
pass the class for the last three credits towards my degree. As you
might have figured out, by then I was a wee bit past "burned out."

--
pyotr filipivich
Next month's Panel: Graft - Boon or blessing?
  #12  
Old March 11th 19, 08:32 PM posted to alt.windows7.general
pyotr filipivich
external usenet poster
 
Posts: 752
Default Did Miscrosoft change how it dates files?

Big Al on Mon, 11 Mar 2019 15:04:40 -0400 typed
in alt.windows7.general the following:
On 3/11/19 1:23 AM, pyotr filipivich wrote:
Greetings

I have a batch file using Robocopy which is only suppose to copy
those files which are "newer" (I.e., modified) than the ones on the
drive. Usually, there is no problem. But tonight, as I go to close
up operations for the evening, it is copying far more files than
before. all tagged "newer".
Was there something magical about the shift to Daylight Savings
time which makes a source drive file dated "Jan 2 2019 10:20 AM" to
now be "newer" than the target drive file dated "Jan 2 2019 10:20
AM"?
I haven't changed "CHAR Sets.wpd" since 1996!?

I do remember something like this happening when the batchfile
correctly copied files from a flashdrive to the XP laptop, and then I
was done with the letter writing, the batchfile copied _all_ the files
just copied (but not used) back from the hardrive to the flash drive.

You'll have a great deal of difficulty convincing me that the
folks at Microsott really have an idea what they are doing.



Try this, I have it in all of my batch files like:
robocopy D:\src G:\dest /MIR /NJH /NJS /NDL
/DST

/dst Compensates for one-hour DST time differences.

https://docs.microsoft.com/en-us/win...mands/robocopy


Which goes back to my question: apparently there is a difference
in how the times are computer, because I can't see what is the
difference between the source drive file dated "Jan 2 2019 10:20 AM"
and the target drive file dated "Jan 2 2019 10:20 AM".

I can see some confusion if I save a file at 01:20 AM Standard
time, run the backup before 01:58, amend the file at 01:10 Daylight
time, and then run backups again.

But backing up as "newer" files which haven't been touched since
1996 (45 time changes ago) - that is the confusing part.
--
pyotr filipivich
Next month's Panel: Graft - Boon or blessing?
  #13  
Old March 11th 19, 08:32 PM posted to alt.windows7.general
pyotr filipivich
external usenet poster
 
Posts: 752
Default Did Miscrosoft change how it dates files?

Stan Brown on Mon, 11 Mar 2019 12:05:59
-0400 typed in alt.windows7.general the following:
On Sun, 10 Mar 2019 22:23:09 -0700, pyotr filipivich wrote:

Greetings

I have a batch file using Robocopy which is only suppose to copy
those files which are "newer" (I.e., modified) than the ones on the
drive. Usually, there is no problem. But tonight, as I go to close
up operations for the evening, it is copying far more files than
before. all tagged "newer".
Was there something magical about the shift to Daylight Savings
time which makes a source drive file dated "Jan 2 2019 10:20 AM" to
now be "newer" than the target drive file dated "Jan 2 2019 10:20
AM"?


If you use the /TS option, robocopy will show you the timestamps of
the source file. When the source file is on an NTFS drive, that will
be in UTC, not your local time. (The timestamps displayed in File
Explorer are converted from the NTFS native UTC to your time zone.)

When the source file is on a FAT or FAT32 drive, native time is the
local time zone when the file was created or modified. (I can't
remember whether robocopy shows that local time, or converts it to
UTC.) That means if you create a file on a FAT32 USB stick at
10:00:00 Eastern Standard Time, and then mount it in Eastern Daylight
Time, the timestamp will show in File Explorer as 10:00:00, even
though the file was created at 9:00:00 Easter Daylight Time.

Robocopy supposedly understands the semiannual daylight-time shift,
and doesn't copy files in such cases, but I don't know how it knows.
I just make sure that I have updated my USB stick the last thing
before going to bed the night before the shift, so that even if the
timestamps are wrong the file contents are correct.

This past weekend, after the time shift, out of hundreds of Eastern
Standard Time files on my USB stick, robocooy wanted to copy exactly
four. I don't know what made those different from the others, so I
don't know if robocopy does basically compensate for DST and just
failed with these four.

There is an option in robocopy to copy the timestamp of a file
without copying the file contents. You might want to use that, come
November.


Thanks, I will look into that.

I'm already trying to remember the hack I had so that after it
ran, it then shut the computer off "for the night".
--
pyotr filipivich
Next month's Panel: Graft - Boon or blessing?
  #14  
Old March 12th 19, 01:45 AM posted to alt.windows7.general
JJ[_11_]
external usenet poster
 
Posts: 744
Default Did Miscrosoft change how it dates files?

On Mon, 11 Mar 2019 08:33:32 -0700, pyotr filipivich wrote:

Ah, so it is a "religious" thing (FAT32 vs NTFS).


FAT32 is irrelevant here. The 2 seconds time unit is a legacy of FAT12. So,
it's been there for a long time. FAT32 can not be a new file system format
because it needs some backward compatibilities with FAT16 and FAT12.

Now to see if I want to go to the hassle of changing thumbdrive
formats.


If you're considering it, for portable drives, consider exFAT instead of
NTFS. While you can use NTFS for portable drives, extra care must be taken.
Otherwise, you'll have higher probability of loosing some of your data.

FYI, exFAT has a 10 milliseconds resolution for file dates. NTFS has 100
nanoseconds.
  #15  
Old March 12th 19, 04:51 PM posted to alt.windows7.general
pyotr filipivich
external usenet poster
 
Posts: 752
Default Did Miscrosoft change how it dates files?

JJ on Tue, 12 Mar 2019 07:45:27 +0700 typed in
alt.windows7.general the following:
On Mon, 11 Mar 2019 08:33:32 -0700, pyotr filipivich wrote:

Ah, so it is a "religious" thing (FAT32 vs NTFS).


FAT32 is irrelevant here. The 2 seconds time unit is a legacy of FAT12. So,
it's been there for a long time. FAT32 can not be a new file system format
because it needs some backward compatibilities with FAT16 and FAT12.

Now to see if I want to go to the hassle of changing thumbdrive
formats.


If you're considering it, for portable drives, consider exFAT instead of
NTFS. While you can use NTFS for portable drives, extra care must be taken.
Otherwise, you'll have higher probability of loosing some of your data.

FYI, exFAT has a 10 milliseconds resolution for file dates. NTFS has 100
nanoseconds.


Joy.

Thanks. I'll put reformatting the thumb drives on the list of
things to do after I figure out what Jar-Jar mean when he said "Mesa
cause one, two-y little bitty axadentes, huh? Yud say boom de gasser,
den crashin der bosses heyblibber, den banished."
--
pyotr filipivich
Next month's Panel: Graft - Boon or blessing?
 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 10:55 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2023, Jelsoft Enterprises Ltd.
Copyright 2004-2023 PCbanter.
The comments are property of their posters.